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 how many capabilities to take off your commerce platform and run as specialised services. Each one you pull out gives you a choice later. It also adds a contract, an integration and an owner for as long as it runs. Moving content or search into an external service is easy to start and slow to undo, so the first components you choose shape your architecture for years.
Composable and headless solve different problems
Headless separates the storefront from the commerce engine. Composable separates the capabilities themselves. You can run a headless storefront on Salesforce B2C Commerce and still keep search, promotions and Page Designer content on the platform. You can also swap your search provider while keeping a traditional storefront.
The two are often sold as one package, which blurs the business case. Our overview of headless commerce on Composable Storefront covers the storefront side. The composable question is narrower: which capability is worth running outside the platform, and why.
The main benefit is replacing one part without rebuilding the rest
A composable set-up lets you change one capability while the rest of the shop keeps running. If your search provider stops meeting your needs, you replace search. Checkout, content and the order flow stay as they are. On an all-in-one platform, the same change often means waiting for the vendor's roadmap or building around it.
That independence has two practical effects. Teams can release changes to one component on their own schedule. And you keep a stronger position with each vendor, because leaving one of them no longer means leaving all of them.
Every component adds a contract, an integration and an owner
The running cost of a composable set-up grows with the number of components. Each one brings its own licence, its own integration to maintain and its own release cycle to test against the others. Those costs multiply. Five components mean five vendors, and every combination of their releases can break something in production.
Incidents get harder too. When an order fails, someone has to find out whether search, the payment service or the storefront caused it. On a project with several suppliers, that question often turns into a discussion about responsibility. FORWARD works as one accountable party for the integration between every Salesforce product involved, because a customer with a failed order does not care whose component it was.
