Alexa+ Add-on Certification Guidelines
Customer Experience Principles
These five principles govern every requirement across all integration paths (Category SDK and MCP Toolkit) unless otherwise noted. When in doubt, apply these principles:
- The customer completes their task with Alexa. No redirects to websites or apps are necessary to finish the action.
- The customer always knows what they are committing to. No hidden costs, no surprise requirements, and no ambiguous next steps.
- If customers need to share data with you, use that only with a clear purpose. Identify what you need, disclose why, and never exceed the stated scope.
- The experience completes the full workflow regardless of device. Display, headless, and mobile surfaces might differ in presentation, but none should block the customer from finishing their task.
- When something fails, the customer gets a clear path forward. No dead ends or no silent failures.
Certification Requirements
Your add-on is evaluated across the following areas, each organized into common requirements and feature-specific requirements. Review all areas to ensure certification readiness.
-
Functional Requirements — Key areas include error handling, context handling, search, transactions, accessibility, and device-specific behavior.
Note: Requirements differ based on integration path and feature set — not all requirements apply to every add-on. -
Policy Requirements — Key areas include content standards, data privacy, intellectual property, metadata accuracy, and business eligibility.
Related topics
Was this page helpful?
Last updated: Jul 10, 2026
