
Extension Review Policy
Purpose and Scope
The Configura Extension Review (ER) is designed to ensure all
CET users enjoy a consistent, high-quality experience across all
extensions. This policy outlines the standards, processes, and
requirements for the Extension Review program.
Benefits of Extension
Review
- Ensures consistent user experience across all
extensions
- Maintains high standards for performance and stability
- Provides accountability between Configura and Extension
Owners
- Creates a standardized process across all CET industry
editions
- Identifies and addresses potential issues before they impact
users
Extension Review Types
On-Demand Review
When it occurs: Required for all new
extensions before publication to the MyConfigura
Marketplace.
Outcome: Extensions must pass this review to
be publicly available.
Scope: Comprehensive review of all
applicable criteria.
Annual Review
When it occurs: All extensions are eligible
for annual review, but due to resource limitations, not every
extension will be reviewed each year. Reviews are scheduled
based on multiple factors including extension usage, previous
review history, and available capacity. Extension Owners will be
notified in advance when their extension is selected for
review.
Outcome: Issues identified will be
documented and must be addressed according to their
severity.
Scope: Focuses on basic functionality and
identifying issues that may have developed over time.
Note: The annual review is not a replacement
for ongoing quality assurance and testing by Extension
Owners.
Review Criteria
Common Criteria (All
Extensions)
Installation
- Verifies installation completes successfully
- Confirms any required data downloads correctly
- Tests compatibility with existing extensions
UI/UX
- Product organization and grouping
- Icon consistency (size, alignment, style)
- Text standards compliance
- Intuitive interface design
- Accessibility considerations
Compatibility with CET
Core
- Integration with walls and architectural objects
- Support for custom finishes
- Compatibility with generic elevation
- Proper visibility handling
- Block functionality
- Multi-floor support
- Tagging functionality
- Graphics editing
- Rendering compatibility
- Lighting compatibility
- Startup time within acceptable limits
- Drawing load performance
- Large drawing capability
- Memory usage optimization
- Model optimization (triangle budget compliance)
Stability
- UI interaction without crashes
- Save and load reliability
- Data integrity preservation
- Legacy drawing support
Marketplace Presence
- Complete and accurate information
- Appropriate logo and branding
- Clear title and descriptions
- Correct categorization
- Valid support contact information
Industry-Specific
Criteria
Commercial Interiors (CI)
- Furniture component behavior
- Material legends
- Panel functionality
- Product categorization
- Material application and schemes
- Order export compatibility. OFDA XML, Configura SIF, and
PMX
Material Handling (MH)
- Pallet racking functionality
- Conveyor system behavior
- CollabPro compatibility
Kitchen and Bath (KB)
- Cabinet behavior
- Inserts, covers, and fillers
- Worktop functionality
- Sink and tap integration
- Appliance integration
- Kitchen preset modes
- Auto-measure capabilities
Issue Severity Levels
Blocking Issues
Definition: Critical problems that must be
resolved before approval.
Examples:
- Installation failures
- Severe performance degradation
- Data corruption
- System crashes
- Security vulnerabilities
Resolution Timeline:
- For On-Demand Reviews: Must be fixed before approval
- For Annual Reviews: Must be addressed within 30-90 days,
depending on severity
Very High Issues
Definition: Significant problems that
substantially impact user experience.
Examples:
- Major UI inconsistencies
- Significant performance issues
- Incompatibility with core CET features
- Misleading product information
Resolution Timeline:
- For On-Demand Reviews: Must be fixed before approval
- For Annual Reviews: Should be addressed within 60-120
days
High Issues
Definition: Important issues that should be
addressed to improve quality.
Examples:
- Minor UI inconsistencies
- Non-critical performance optimizations
- Marketplace information improvements
- Feature enhancements
Resolution Timeline:
- For On-Demand Reviews: Should be fixed before approval but
may receive conditional approval
- For Annual Reviews: Should be addressed within 90-180
days
Review Process
Preparation
- Extension Owners may provide notes or special information
for consideration in the submission of an On-Demand review or
directly to their Account Exectutive for an Annual Review.
- Test environments will be prepared by Configura
Review Execution
- Configura conducts the review against established
criteria
- Issues are documented in Jira with appropriate severity
levels
- Preliminary findings are shared with Extension Owners
Resolution
- Extension Owners review findings and address issues
- Configura verifies resolved issues
- Final approval or rejection decision is made
Communication
All communication regarding Extension Review will occur
through:
- Jira tickets for issue-specific questions and verification
requests
- Direct email to extension-review@configura.com
for general questions
- Scheduled review meetings as needed
Jira Setup and Ticket
Questions
Each manufacturer has a dedicated Jira project in Configura’s
Jira instance for Extension Review work. Each project includes
an Extension Review Epic that is used to organize review
activity. Do not close or delete this epic.
Extension Review tickets will be linked to the Extension
Review Epic. When a manufacturer has a question about a specific
review ticket, or needs Configura to verify completed work, the
manufacturer should:
- Comment directly on the Jira issue with the question,
context, or verification request
- Move the issue to the appropriate status:
- More Info Needed when asking Configura a
question or requesting clarification
- Ready For Test when requesting verification
of a fix or update
General Extension Review questions that are not tied to a
specific ticket can be sent to extension-review@configura.com.
Appeals Process
If an Extension Owner disagrees with review findings:
- If a Jira issue has already been logged, comment on that
issue with a detailed explanation and transition it to
“More Info Needed.”
- If no Jira issue exists, send a detailed explanation to extension-review@configura.com.
- A secondary review will be conducted.
- Final determination will be made within 10 business
days.
For time-sensitive appeals, please send an email to extension-review@configura.com,
regardless of whether a Jira issue exists.
Policy Changes
This policy may be updated at any time. Configura reviews
publishing policies bi-annually for larger updates and will
communicate material changes to Extension Owners with
appropriate notice.
Resources and Support
Document Version: 1.2
Last
Updated: June 18, 2026
Configura Publishing
Program
© 2026 Configura, Inc. All rights
reserved.