How do you architect a B2B Configure-to-Order process that spans CPQ, B2B Commerce, and an external manufacturing system?

A Configure-to-Order (CTO) process for B2B manufacturing requires orchestrating configuration, quoting, and production across systems:

B2B Commerce configurator: The buyer self-configures a product on the B2B Commerce storefront (colour, dimensions, material, accessories). Configuration selections map to CPQ product options via the Commerce-CPQ bridge.

CPQ Quote generation: When the buyer adds a configured product to the cart and requests a formal quote, B2B Commerce triggers CPQ via API to generate an SBQQ__Quote__c with the configuration translated to CPQ product options and pricing. The quote is surfaced back to the buyer for review and approval.

Order to Manufacturing: When the quote is accepted and ordered, a Platform Event (ConfiguredOrder__e) notifies the manufacturing execution system (MES) or ERP. The event payload includes the product configuration specifications (BOM — Bill of Materials). The MES creates a work order for production.

Production status back to Salesforce: Manufacturing status updates (In Production, QA, Ready to Ship) are pushed back to Salesforce via the Salesforce REST API, updating the Order record and triggering customer notifications via Flow (email, SMS, portal notification).

Asset creation: Upon shipment, a Salesforce Asset record is created, linking the manufactured product to the Account for warranty tracking, field service entitlement, and future renewal quoting.