FAQ Athos Migration
Commonly asked Athos migration questions
Q: Why should I migrate to Athos Commerce if my Searchspring integration is still working?**
A: While we support legacy Searchspring indefinitely, Athos Commerce is built for the "Innovation Era." By migrating, you unlock the Variant-First data structure and our new feature endpoints. Additionally, all new feature releases and performance optimizations are now exclusive to the Athos architecture.
Q: What is the most critical technical change for my implementation?
A: The shift to Explicit Versioning and Module Routing. You will need to update your base URLs from the legacy .searchspring.io domain to the new versioned v1 path on a.athoscommerce.net. Crucially, any personalization or bundling logic must now be routed through a.p13n.athoscommerce.net.
Q: How does the "Variant-First" response change my front-end integration?
A: With Athos, every search and autocomplete response includes a native variants object. This allows your front-end to render complex product options (like size-specific inventory or color swatches) immediately from the initial API response, leading to a better user experience.
Q: Will my existing Searchspring storefront experience any downtime during this transition?
A: No. We are maintaining full uptime support and providing critical patches for all legacy Searchspring endpoints. Your current integration will remain stable, allowing you to schedule your migration to Athos Commerce during a window that best fits your development cycle without fear of service interruption.
Updated 3 months ago