Standard Cart APIs retain the same API names, inputs, and response formats as Cart APIs (Classic) unless a topic calls out a difference. This topic lists behaviors that still differ from Classic, and Cart APIs that continue to run on the Classic Apex path.
Before you enable Standard Cart APIs, review Check Feature Compatibility and the API list in Standard Cart APIs.
You can enable only the APIs listed in Standard Cart APIs. Other Cart APIs continue to run using Apex libraries.
The following operations have Classic usage examples and are not on the Standard Cart APIs list. Treat them as Classic unless a later release adds them to that list.
| Operation | Remote method | Classic usage example |
|---|---|---|
| Validate Cart | runCartValidation | Validate Cart Action |
| Clone Line Items | cloneItems | Clone Line Items in Cart |
| Cancel Order / Submit Cancel | cancelCart / submitCancelOrder | Cancel Order, Submit a Cancel Order Request |
| Get Product Details / Get Products by ID | getCartsProductDetails / getCartsProductsById | Get Details of Product, Get Products by ID |
| Get Catalog Information | getCatalogs | Get Catalog Information |
| Get Price Lists for Cart | getCartsPriceLists | Get Price Lists for Cart |
| Update Item Attributes | putCartsItemsAttributes | Update Item Attributes |
| Get / Add Promotions | getCartsPromotions / postCartsPromotions | Get Cart Promotions, Add Promotion to Cart |
| Get Price Waterfall | getCartsItemPrices | Get Price Waterfall for Price |
| Delete Adjustment | deleteAdjustment | Delete Adjustment |
| Get All Assets | getAllAssets | Get Assets for Account |
For validation and pricing on the Standard path, use Run Pricing for Items to Cart. Dedicated runCartValidation remains a Classic Cart API.
| Area | Classic Cart APIs | Standard Cart APIs |
|---|---|---|
| Transformation of multi-play offers | Supported | Change of Plans is compatible, but replaceOffers does not support complex multi-play transformations |
| ProductSelector interface | Supported | Not supported. Use the sortBy parameter on getCartsProducts |
| Field Settings / CPQV2 field settings | Supported for cart responses | Supported for getCarts and GetCartsItems only. For other Standard Cart APIs, pass custom fields in the fields parameter |
noResponseNeeded | Supported | Supported for Add, Update, and Delete Standard Cart APIs from 258. Multi-item add defaults to noResponseNeeded=true unless you pass false |
maintainAssetPrice | Supported | Supported from 258 |
includeAttachment | Supported | Ignored on addToCart |
| Custom Expression mode in RuleSets | Supported | Not supported |
Context mappings with Initialization Type Type In and Scope SObject | Supported | Not supported |
nameResult node (attributeCategories, productAttributes) | Present | Not present. Data nodes are returned directly |
actions node | Populates both remote and rest | Populates only the protocol you invoked |
| Cart document / line items in custom code | Full line-item sObject list | CpqCartDocument contains only items affected by the current operation. GetCartsItems is the full-cart read |
| Currency and pricing field types | Integer values are often accepted | Double is required (for example, 0 must be 0.0) |
| AssetToOrder invocation | OmniFDOWrapper uses the Classic flow | REST /v2/carts uses the Standard flow |
| AssetToOrder CPQ settings | UsingPromotions, DeltaPrice, and IsCachingEnabledForAssetToOrder apply | Functionality exists, but those settings do not control Standard AssetToOrder |
Because not all APIs have migrated to the Standard Cart framework, custom implementations must accommodate both Classic and Standard Cart flows and switch dynamically based on context. See Use CpqCartDocument.
Note
j
