Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
The decision on the table is whether to replace your storefront in one launch or page group by page group. A phased move limits the damage of a wrong assumption and lets you measure the new front end on real customers. It also doubles part of your operation for as long as the hybrid period lasts, so the plan needs an end date as much as a start date.
What a hybrid deployment looks like
In a hybrid set-up, each page type is served by one of two storefronts on the same domain. A common split puts home, category and product detail pages on Composable Storefront (PWA Kit), while basket, checkout and account pages stay on SFRA or SiteGenesis. Shoppers move between the two without seeing a difference.
Both storefronts read the same products, prices, promotions and customer accounts from Commerce Cloud (Agentforce Commerce). Only the front end is split. How the headless side works in general is explained in our overview of headless commerce on Composable Storefront.
A phased move protects you if plans change halfway
The strongest argument for a hybrid deployment is what survives if the programme stops. Every page group that has moved is live and earning. The pages that have not moved keep running on the existing storefront. Nothing sits half-built behind a launch date.
The same logic spreads the investment. Budget goes to one page group at a time, and each release gives you conversion and speed data from real traffic before you commit to the next. A single big launch asks you to approve the whole budget on assumptions alone.
Which pages move first
Browse pages usually move first. Home, category and product detail pages carry most of the traffic, benefit most from a faster and more flexible front end, and read data without changing orders. If something goes wrong there, no payment is at risk.
Checkout usually moves last, because it carries payment, tax and fraud integrations that SFRA often handles through ready-made cartridges. Moving it means rebuilding or replacing each of those. Fast FORWARD, our pre-built headless storefront on Composable Storefront, can power selected pages in a hybrid set-up while SFRA or SiteGenesis keeps checkout and payment processing.
Sessions, baskets and routing have to work across both
A hybrid deployment only works if the shopper never notices the seam. Routing rules decide which storefront serves which URL. The login session and the basket have to carry across when a shopper moves from a product page on one storefront to checkout on the other. Analytics and consent have to follow the same visitor through both.
This integration is where hybrid projects succeed or fail, and it involves several parts of the Salesforce stack at once. We take responsibility for it as one accountable party, including the integration between every Salesforce product involved. A basket that empties at the seam is our problem to solve.
