Hybrid Storefront Routing Matrix
Use this routing matrix to choose a hybrid storefront split between Storefront Next and SFRA/SiteGenesis.
The examples in this guide apply to all hybrid setups:
- For local hybrid proxy setups, set
HYBRID_ROUTING_RULESin your environment variables. - For on-demand sandbox (ODS) and production setups, paste the same rule expression directly into eCDN routing rules.
Use the same expression pattern in every setup, but use different input formats:
- Local hybrid proxy (
.env): Assign the rule toHYBRID_ROUTING_RULESand wrap the expression in single quotes. - ODS and production (eCDN UI): Paste only the rule expression in Rule expression. Do not include
HYBRID_ROUTING_RULES=and do not wrap the expression in single quotes.
Example for local hybrid proxy:
Example for eCDN:
HYBRID_ROUTING_RULES: A single Cloudflare expression used by the edge routing layer. The pattern supports optional/:siteId/:localeprefixes using^(/[^/]+/[^/]+)?.PUBLIC__app__hybrid__legacyRoutes: A JSON array used by the Storefront Next client-side routing middleware to force a full-page navigation to SFRA/SiteGenesis routes.
Check out some examples of the different ways you can set up your hybrid storefront.
- Strategy: The active customer discovery funnel, search, account, and social authentication routes run on Storefront Next. Only checkout (
/cartand/checkout) stays on SFRA/SiteGenesis. - HYBRID_ROUTING_RULES:
PUBLIC__app__hybrid__legacyRoutes:
- Strategy: Use this split to test or roll out a Storefront Next checkout while keeping browse and discovery routes on SFRA/SiteGenesis.
- HYBRID_ROUTING_RULES:
PUBLIC__app__hybrid__legacyRoutes:
- Strategy: Use this split during early pilots when only the home page is modernized and deeper flows remain on SFRA/SiteGenesis.
- HYBRID_ROUTING_RULES:
PUBLIC__app__hybrid__legacyRoutes:
- Strategy: Use this split when the home page stays on SFRA/SiteGenesis, while deeper browse and transactional routes move to Storefront Next.
- HYBRID_ROUTING_RULES:
PUBLIC__app__hybrid__legacyRoutes:
- Strategy: Move high-volume catalog routes (category, product, search) to Storefront Next while preserving legacy account and checkout routes.
- HYBRID_ROUTING_RULES:
PUBLIC__app__hybrid__legacyRoutes:
- Strategy: Move account and authentication experiences to Storefront Next while leaving catalog and checkout on SFRA/SiteGenesis.
- HYBRID_ROUTING_RULES:
PUBLIC__app__hybrid__legacyRoutes:
Keep these route clauses in every matrix configuration:
^/resource.*and^/action/.*to avoid loop routing on modern layouts and handlers..*\.data.*to prevent React Router 7 data prefetch requests from being routed to SFRA/SiteGenesis.^/assets/.*and^/favicon\.ico$for core Storefront Next static assets.