Checkout Items in a Cart

The Checkout API finalizes a CPQ cart by performing all mandatory validations, pricing recalculations, asset‑generation steps and transaction commits required to create a ready‑to‑bill Order.
It is the logical culmination of the add → configure → price → validate → checkout pattern common to digital‑commerce and assisted‑selling flows.

Based on the header object, submit the object to create the quote, order, or assets.

• If the header object is Opportunity, submit the opportunity to create a quote.

• If the header object is Quote, submit the quote to create an order.

• If the header object is Order, submit the order to create assets.

These APIs replace the following methods in OmniCPQServiceWrapper:

• Submit Opportunity replaces OmniCPQServceWrapper submitOpportunity.

• Submit Order replaces OmniCPQServiceWrapper submitOrder.

• Submit Quote replaces OmniCPQServiceWrapper submitQuote.

The call path depends on the OdinAPIHandler interface chosen at runtime:

• OdinAPIAutoAssetizeHandler – routes directly to Java core classes (CheckoutAction, CheckoutServiceImpl) for high‑volume assetisation use‑cases.
• Any other implementation – executes entirely in Apex inside the managed package, allowing org‑specific extensions before/after core logic.

For more information, see OmniCPQServiceWrapper.

This API supports the guest user enhancements that Salesforce introduced with the Winter ‘21 release. To encrypt and decrypt data for guest users, use the UserSecurity class with this API. See Guest User Technical Details.

For additional information, ​see UserSecurity Class and CPQ and Digital Commerce Changes for Guest Users.

ContextId is required for the Checkout Items in Cart remote action, which is used in the Guided Selling OmniScript.

Communication (vlocity_cmt)

For API parameter names and descriptions, see Cart-Based API Swagger Reference.