commerce-b2b-open-code-components-replace

To replace out-of-the-box B2B Commerce components with open code, you update site metadata in Experience Cloud by swapping OOTB commerce_builder definitions with their site: equivalents in content.json files for site views and theme layouts.

Component mapping for B2B Commerce content.json files is the process of discovering and looking up exact open code site: equivalents for supported commerce_builder components using an authoritative OOTB-to-site mapping validation.

Yes, you can perform lookup-only analysis to understand which OOTB commerce components can be migrated, allowing you to compare OOTB definitions against available open code equivalents before changing any site metadata files.

Replacing B2B Commerce components in site metadata preserves your existing JSON content by using JSON-preserving read-modify-write updates, ensuring all other definitions in content.json remain intact during the component replacement workflow.

During a bulk replacement, the workflow verifies repository availability and confirms mapped components exist in the open code repo, reporting any unmapped or missing items before changing files to prevent metadata corruption.

You should use a bulk replacement workflow for B2B Commerce storefront components when you need to replace multiple components across several site views simultaneously after an open code component rollout, ensuring consistent metadata updates.