You do not create a checkout product. You configure the Checkout component on your store's checkout page in Experience Builder, then make sure the products buyers add are sellable. Here is the high-level path for a B2B or D2C store.
- Open the store in Experience Builder
From Commerce setup, open your store and launch Experience Builder. Go to the Checkout page, where the Checkout component already sits on stores created from a standard template.
- Choose the checkout flow or layout
On an Aura store, select the checkout flow the component should run in its properties. On an LWR store, pick the one-page or accordion layout for the Salesforce Commerce Checkout and arrange its sections.
- Configure the steps
Add, remove, or reorder subflows (Aura) or child sections (LWR) to match your process. Set slow integrations to asynchronous where supported so they do not block the buyer.
- Connect payment
Set up Salesforce Payments or your chosen gateway so the payment step can authorize transactions. Confirm the payment section appears and accepts a test method.
- Make products sellable, then test end to end
Give each product a price in the store's price book, set inventory if you track it, and confirm buyer entitlements. Run a full test purchase in the live storefront, not just the preview.
Aura stores run a Flow Builder checkout flow; LWR stores use the packaged Salesforce Commerce Checkout components. The template you chose at store creation decides which you configure.
On LWR, one-page keeps all sections open for completion in any order; accordion forces shipping then method then payment in sequence.
On Aura, a subflow can run synchronously (the buyer waits) or asynchronously (it runs in the background) to keep slow integrations from stalling checkout.
Use the native Salesforce Payments API integration or register a third-party gateway to authorize and capture funds during the payment step.
- A product without a price in the assigned price book cannot be purchased even if it shows in the catalog.
- Order creation runs only after payment authorization succeeds, so a declined card never produces a real order.
- The Experience Builder preview does not exercise every integration; always test a real storefront session before go-live.
- On LWR, a custom child component that fails to report validity can block or silently break the place-order action.