Uploading a cartridge to an instance does not automatically make its code available to a storefront. B2C Commerce resolves application resources according to thecartridge path configured for the relevant site. Consequently, the new custom cartridge must be added to that storefront site ' s cartridge path, normally in the correct precedence position relative to SFRA base and other cartridges.

Salesforce ' s cartridge documentation describes two distinct steps: upload the cartridge code and register the cartridge with the applicable site through its cartridge path. Site configuration is performed from the site ' s settings, where the cartridge path controls which controllers, templates, scripts, models, and other cartridge resources can participate in storefront execution.

Rebuilding indexes is unrelated unless the customization specifically changes indexed catalog/search data. An index rebuild does not register executable storefront code. Likewise, configuring the Business Manager application ' s cartridge path would affect Business Manager customizations rather than the customer-facing storefront identified in the question.

Cartridge ordering is also significant because B2C Commerce searches the path according to precedence, enabling custom cartridges to extend or override functionality from cartridges located farther to the right.

Study Guide reference:B2C Commerce Setup — cartridges, site cartridge paths, SFRA deployment, and cartridge precedence.

===============