These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Delivery Slot Management
- Features
- Carts and checkout
Carts and checkout
Carts and checkout records and decisions for a commerce team.
OverviewActive promotions×
Delivery Slot Management · Carts and checkout
New
Active promotions
Discount rules
| Code | Name | Type | Scope | Starts at | Ends at | |
|---|---|---|---|---|---|---|
| CDE-402 | Rule 186 | Percent off | Cart | 18 Oct | 23 Oct | |
| CDE-316 | Rule 366 | Amount off | Line | 23 Oct | 27 Oct | |
| CDE-264 | Rule 374 | Free shipping | Shipping | 09 Oct | 18 Oct | |
| CDE-431 | Rule 194 | BOGO | Cart | 14 Oct | 19 Oct | |
| CDE-720 | Rule 554 | Fixed price | Line | 15 Oct | 19 Oct |
6 of 6 records
CDE-402Discount rules · DR-44115
Percent offNameRule 186
ScopeCart
Starts at18 Oct
Ends at23 Oct
StatusActive
What you can do
Run the work
A cart holds a shopper’s selected items before a booking is placed. Cart items retain a variant, quantity and unit price, while the cart carries its catalog, currency, activity time and checkout state. Addresses and configured shipping and payment methods provide the information needed to form a booking.
How the work is organized
- Keep the basket tied to its market. The cart points to a catalog, while each item points to a variant and preserves its unit price.
- Check checkout choices. Merchant Owner reviews active shipping and payment methods, tax rates and discount eligibility before orders are taken.
- Trace conversion. Customer Service Rep compares a converted cart with the booking and its ordered resources when a shopper asks about a charge.
For a shopper who leaves after selecting a product, Marketing Manager can review the abandoned cart record and its recovery stage. When the shopper returns, staff can distinguish a current basket from one already converted or expired. A checkout review should inspect the selected shipping method and its price, the tax jurisdiction, the payment method and any discount rule before treating the order total as final.
What to agree during setup
Merchant Owner should agree the supported markets, tax treatment, shipping methods and accepted payment methods. Decide what checkout does when an address is incomplete, a method is inactive or a promotion has ended. Config validation runs records whether the configuration set passed or failed and the unmet conditions; it does not replace a final check of a real customer’s order.
A pilot should use a real product range, one supported market, a shipping method and a representative order. Confirm which person owns each state change. Review the information that will arrive from payment, carrier and messaging services, and decide how the team will reconcile a delayed or failed response. Keep the customer’s original transaction visible when correcting a later event.
Check the handoff on an actual case
Start with a customer selecting a shippable variant. Compare the item quantity and price in the cart with the resulting booking line. Confirm the delivery address and shipping method. Then follow payment evidence, shipment status and any service request in sequence. If an exception arises, the next person should be able to see the affected booking and the reason for the handoff without guessing from a single overall status.
This exercise also tests access. Customer (external) should be able to work the records in this module. A colleague with read-only responsibility should be able to inspect the relevant result without gaining permission to change payment or fulfillment evidence. Rehearse an incorrect address and a failed payment result so the team knows how to stop and correct the case.
What your team sees
- Active carts — Carts still active or at checkout, with customer and last activity for follow-up.
- Recovery follow-up — Abandoned baskets grouped by their recorded recovery stage.
Follow the work through
What it keeps track of
Data model- Carts
- A record is a shopper's in-progress basket, letting the team track what people are about to buy before they check out.
- Cart items
- A record is one item sitting in a shopper's basket, used to see what they've added before booking.
- Addresses
- A record is a delivery or billing address, kept so bookings and shipments use the right location.
- Shipping methods
- A record is a delivery option offered at checkout, used to manage carriers, cost, and how long delivery takes.
- Payment methods
- A record is a way customers can pay, used to control which payment options are offered and how they're processed.
- Tax rates
- A record defines the tax rate for a region, so staff can use the applicable rate when calculating tax.
- Discount rules
- A record defines one discount or promo code, used to control who qualifies and how much they save.
- Config validation runs
- Checkout configuration validation runs produced by the Pricing, tax, shipping, payment workflow. One row per validated configuration set; validation never mutates the merchant configuration.
Who uses it
Permissions- Customer
- (external) owns the routine handoff.
- Merchant Owner
- Reviews configuration and material exceptions.
- Other configured roles see or update records according to their assigned permissions.
Set up Delivery Slot Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.