Submission Process
Steps
- Go to Fynd Partners portal.
- Select extension → <your-extension>
- Click Publish
- Fill in the required details.
- Click Submit.
Review Checklist
Documentation
Business Document: Provide a detailed explanation of the extension’s use case, target audience, and specific user flows from a product perspective.
Testing Document: Provide a step-by-step guide for the Fynd developer experience team to test your extension.
Technical Specification: Notify the technologies (language, libraries, DB, hosting platforms, etc.) and the Fynd APIs (and their versions) used to build this extension.
User Document: Provide clear, user-friendly documentation for end users. This should include setup instructions, a detailed usage guide, and common troubleshooting steps to help users navigate and resolve potential issues.
Support Information: Ensure contact info, support hours, and issue resolution timelines are available.
Compliance & Legal
Relevant Use Case: Ensure that the extension solves a real customer problem that is aligned with Fynd's platform goals and target audience.
Terms of Service: Ensure that your extension fully complies with Fynd’s marketplace terms of service. Review all terms and conditions to make sure your extension follows Fynd’s policies regarding usage, data handling, and customer interactions.
Data Compliance: Ensure that user data is handled responsibly and in compliance with applicable legal regulations.
Licensing: Verify that all libraries, assets, and tools used in your extension are properly licensed.
Security
Authentication & Authorization: Validate secure access protocols, ideally OAuth or token-based methods.
Data Privacy: Confirm that your extension adheres to relevant data protection regulations, such as GDPR, CCPA, or other applicable privacy laws.
Encryption: Ensure that sensitive data is encrypted both in transit and at rest.
Vulnerability Scanning: Run vulnerability scans to detect and address common security issues like SQL injection, cross-site scripting (XSS), and cross-site request forgery (CSRF). Tools such as OWASP ZAP, Burp Suite, or similar automated scanners can help identify potential weaknesses before deployment.
Code Quality Certification: Perform thorough code reviews to inspect code quality by identifying bugs, vulnerabilities, and code smells.
Technical & Business Requirements
Tech Compatibility: Ensure that your extension is fully compatible with the current version of the Fynd Commerce and any required dependencies.
API Usage: Ensure all API requests are properly documented, optimized for performance, and follow best practices, such as rate limiting, error handling, and secure access.
Performance: Check load times, response times, and resource utilisation. Evaluate the extension’s performance, focusing on load times, response times, and resource utilization.
Error Handling: Ensure the app manages errors gracefully without crashing.
Scalability: Ensure that the extension can handle the expected volume of users and data without performance degradation.
UI/UX & Accessibility
User Experience: Ensure that the extension includes clear navigation, consistent design patterns, and responsive layouts that work well across various devices and screen sizes.
Accessibility: Validate that the extension is accessible to all users by adhering to Web Content Accessibility Guidelines (WCAG 2.1).
Branding Compliance: Verify the app follows marketplace branding and style guides. Verify that the extension aligns with Fynd’s marketplace branding and style guides.
Localisation: Check for support of relevant languages and region-specific formats, such as date, time, currency, and number formats.
Quality Assurance
Testing: Ensure that the extension passes testing, including functional, usability, and performance testing.
Error Reporting: Verify that the extension is integrated with error-tracking and logging tools.
Update Strategy: Confirm a well-defined strategy for regular updates and ongoing maintenance.