Storefront site cartridge path versus Business Manager cartridge path
Key Takeaway
Each storefront site has its own site cartridge path, separate from the Business Manager cartridge path. Storefront code and hooks go on the site cartridge path, ahead of app_storefront_base, which stays last. Code that extends Business Manager goes on the Business Manager cartridge path.
In B2C Commerce, a cartridge path is the list of cartridges a site uses. There are two kinds: one for each storefront site and one for the Business Manager site. Uploading a cartridge is not enough. You must also add its name to the right path, in the right order, so the server knows to use that code.
Two cartridge paths
Each storefront site, such as RefArch, has its own site cartridge path. The Business Manager site has a separate Business Manager cartridge path.
For a base SFRA setup, the RefArch site cartridge path is app_storefront_base. The Business Manager cartridge path is bm_app_storefront_base.
| Cartridge | Path in a base SFRA setup | What it holds |
|---|---|---|
app_storefront_base | RefArch site cartridge path | Foundational storefront code, such as models and ISML templates |
bm_app_storefront_base | Business Manager cartridge path | Page Designer starter files, plus code for customizing Business Manager and Einstein functionality |
The SFRA modules folder must be uploaded with the cartridges, but it does not follow a normal cartridge structure. The base RefArch site cartridge path is still just app_storefront_base.