This feature gives storefront teams more control over how shopping cart rows behave, how cart details are presented, and how totals reflect pricing logic. Buyers can be prevented from changing protected lines, cart rows can show more useful descriptive content, handling fees can appear as summary rows instead of ordinary product lines, and discount percentages can better match subtotal-based pricing expectations.
These capabilities matter most for storefronts that need tighter control over cart behavior without making the cart harder to understand. They are especially useful when a storefront includes auto-added items, grouped products, addons, product-type-specific detail rules, or pricing models where the discount shown to buyers should reflect the full summarized line value.
What this feature does
The shopping cart experience supports four practical behaviors:
- selected cart lines can remain visible while staying locked against buyer edits
- cart item presentation can show more descriptive subtitle and detail content
- handling fees can appear as summary rows instead of standard editable cart lines
- discount percentages and totals can align more closely with subtotal-driven pricing logic
Together, these changes help storefront teams make the cart feel more intentional. The cart can now separate what buyers should control directly from what the business needs to manage automatically, while also making line-item information and totals easier to understand.
Protect cart lines that buyers should not edit
Some cart rows need to stay in the cart without behaving like ordinary shopper-controlled items. Typical examples include auto-added service lines, protected bundle rows, required charges, or products that should remain visible but not be changed after they are added.
OrderCentral supports read-only cart items. When a line is locked, buyers can still see it in the storefront cart, but they can no longer treat it like a normal editable row. This helps implementation teams keep business-critical lines stable while still showing buyers how the cart is built.
This is most useful when your storefront needs to:
- keep automatically added lines visible without letting buyers remove them
- protect bundled or approval-driven items from quantity changes
- prevent buyers from changing derived cart rows that support pricing or service logic
The buyer-facing lock remains in place even when a controlled integration or automation path is designed to maintain the same line behind the scenes. That distinction lets storefront teams protect the buyer experience without losing operational flexibility.
Show more descriptive cart item content
Cart rows often need to show more than a product title. Buyers may need option-based subtitles, grouped-product context, addon information, or product-type-specific detail content that explains what they are actually ordering.
Cart item presentation supports two useful patterns. First, standard cart row data can present more descriptive subtitle information for configured products and option selections. Second, implementations can provide product-type-specific detail content so the cart can show tailored supporting information for different kinds of items.
This makes the cart easier to understand when:
- product options need clearer summary text in the row itself
- grouped or extended products need more context than a title alone provides
- different product types require different explanatory content in the cart
For storefront teams, the practical benefit is a cart that communicates more clearly without forcing every item into the same generic row presentation.
Represent handling fees as cart summary rows
Handling fees do not always belong in the cart as ordinary product rows. In many storefronts, buyers should see these charges clearly, but the charge should behave more like a calculated summary item than like a line they can edit, remove, or interpret as a normal product.
OrderCentral supports handling-fee-style rows as summary-only fee lines. These rows can participate in cart totals while appearing separately from the main editable item list. That gives storefront teams a clearer way to show fee-based charges without making the cart table feel cluttered or misleading.
This approach is useful when you want to:
- show a handling fee clearly without presenting it as a normal merchandise line
- keep fee rows read-only in the buyer experience
- recalculate totals automatically when fee logic is applied or removed
The exact fee label can still depend on how the implementation defines and prices the fee line, so the business meaning of the row remains configurable.
Make discount percentages better match business expectations
Discount display can become confusing when the percentage shown to buyers is based on a unit-price assumption while the business actually thinks about discounts at a subtotal level. That mismatch becomes more noticeable when cart rows include grouped items, addons, or summarized pricing.
OrderCentral supports discount calculation based on either unit price or subtotal. This gives implementation teams a clearer way to align storefront discount presentation with the pricing logic the business expects buyers to see.
Subtotal-based calculation is especially relevant when:
- grouped items contribute to a summarized cart row
- addons affect the effective line value
- buyers should see a discount percentage that reflects the whole line subtotal rather than an isolated unit value
The result is more consistent discount presentation across cart totals, summarized rows, and the pricing story shown to buyers.
When to review your cart setup
Review this functionality if your storefront needs to:
- lock selected cart rows after they are added
- make cart item content clearer for configured, grouped, or specialized products
- separate fee-style charges from normal product rows
- align discount percentages more closely with subtotal-based pricing behavior
A short design and configuration review is usually enough to determine whether these changes should stay at the default behavior or be rolled out more intentionally for your storefront.
Related setup and technical articles
Use this overview to understand the business value of these cart capabilities. When you are ready to configure or extend the behavior, continue with the deeper follow-on articles:
- Read-only shopping cart item workflows
- Configure cart item detail content overrides
- Implement custom cart item detail providers
- Configure discount calculation base
- Add and remove handling fee lines with Flow
For existing technical reference, review the current ShoppingCartApi, read-only cart item, shopping cart LWC, and cart column-mapping documentation alongside these related articles.