Use this configuration when the standard cart row title and subtitle are not enough for every product type. Product-type-specific detail providers let the shopping cart show tailored supporting content for selected product types while leaving other product types on the default cart presentation.
This setup maps a product type to a provider class. The mapping is admin-managed, but the provider class itself must already exist in the org. If no suitable provider class is available yet, a developer must build and deploy one before you can select it here.
What this configuration changes
This feature controls the extra detail content shown in the cart for specific product types.
With this configuration, you can:
- assign a custom cart item detail provider to a product type
- let different product types render different supporting detail content in the cart
- keep product types without a configured provider on the default cart row behavior
The configuration does not create provider classes and does not change the base cart table columns. It only controls which provider class is used for each product type.
Before you start
Make sure the following prerequisites are in place:
- you can access the OrderCentral app and the OrderCentral Configuration area
- the storefront uses the standard shopping cart experience that supports cart item detail content
- the product types you want to configure already exist as Web Product record types
- any provider class you plan to select has already been deployed by a developer and implements the supported cart item detail provider contract
If you do not see a suitable provider in the list, stop here and have a developer create or deploy the provider first. This article covers the mapping step only.
Open the cart item detail override configuration
Use these steps to open the override mapping screen:
- Open the OrderCentral app.
- Go to OrderCentral Configuration.
- Select the Shopping Cart tab.
- In the Configure Shopping Cart Details card, click Configure displayed product details.
This opens a modal for product-detail override mapping.
What the modal shows
The modal loads the current override configuration each time it opens.
It shows:
- one row for each eligible product type
- the product type label on the left
- a provider selection list on the right
- Save and Cancel actions at the bottom
Eligible product types come from the available Web Product record types. System record types such as Master and Package are not included in the list.
The provider list is discovered automatically from Apex classes in the org that implement IUIContentProvider and can be instantiated at runtime. After a developer deploys a valid provider class, it becomes available for selection the next time you open the modal.
Map product types to provider classes
Use the modal to assign the correct provider class to each product type that needs custom cart detail content.
- Review the list of product types shown in the modal.
- For each product type that needs custom detail content, open the provider drop-down.
- Select the provider class that should generate the cart item detail content for that product type.
- Leave product types on the default state when you do not want custom detail content for them.
- Click Save.
Use these guidelines while mapping:
- map only product types that need different cart detail behavior
- use provider names agreed with your delivery team so admins and developers are selecting the same implementation intentionally
- validate mappings in a representative storefront after each change instead of updating many product types at once without testing
Save and validate the deployment
When you save, OrderCentral does not apply the change instantly in the storefront. Saving enqueues a metadata deployment in the background.
Expected behavior after saving:
- the modal closes after the save request succeeds
- the shopping cart configuration page shows that the override deployment is in progress
- an initial success toast confirms that deployment was queued
- a later success toast confirms when the configuration update completes
- if deployment fails, the page shows the returned deployment error message instead
Because the change is deployed asynchronously, allow a short time for the update to finish before validating the storefront. Then refresh the relevant storefront page or cart view and confirm the updated detail content appears for the mapped product type.
If you click Save without any effective mapping changes, no deployment is started.
What happens when no provider is configured
If a product type has no configured provider, the cart does not add provider-generated detail content for that product type.
In that case, the cart continues using the standard row presentation for the line item. Buyers still see the normal cart row information that the storefront already supports, such as the product title and any standard subtitle behavior, but no extra provider-driven cartItemDetail content is injected.
This fallback behavior is useful when only a subset of product types need special detail rendering.
Troubleshooting
The provider class is not available in the list
Verify that the provider class has been deployed to the org and implements the supported IUIContentProvider interface. The list is populated from available Apex classes that match that contract, so a class that has not been deployed or does not implement the interface will not appear.
The wrong product types appear in the modal
Check the Web Product record types in the org. The configuration uses product types from those record types and excludes only the system entries Master and Package.
The storefront does not change right after saving
Wait for the background deployment to complete, then refresh the storefront cart. The configuration is applied asynchronously, so the storefront may continue showing the previous behavior until deployment finishes.
The cart still shows default detail content after a mapping is saved
Confirm that:
- the correct product type was mapped
- the save completed successfully
- the selected provider class is the intended implementation for that product type
- the storefront cart is rendering the affected cart item through the standard shopping cart flow
If the mapping is correct but the output is still not what you expect, the next step is usually a developer review of the provider implementation rather than another admin configuration change.
Related articles
- Implement custom cart item detail providers
- Shopping cart widget
- refreshshoppingcart-c