A shopping cart has to answer three questions before checkout: what am I buying, what does it cost so far, and what happens next? Show each product with the option chosen and its quantity. Show every automatic discount where it changes a price. Call the running figure Subtotal while shipping and tax are still open, and say when they will be settled. Make changing a quantity or removing a line easy. On a phone, keep the checkout button within reach without letting it cover totals, errors, or item controls.
A screenshot of one full cart won’t show you whether any of that works. Carts break when a discount drops off, the last item is removed, or an update is slow, so most of this guide is about testing those moments. The state matrix further down lists them.
Make every line recognizable
A shopper should recognize each product in the cart without going back to its page: image, full product name, the chosen option, quantity, and price. Use the same names and price format as the product page.
Test similar products side by side. If two mugs differ only by capacity, each cart line must say which capacity it is. Setka supports product variants, so add every option you sell to the cart and check that each line names the one the shopper picked.
Keep the image small enough to help recognition without taking over a phone screen. Put your longest product name in the cart and check that it wraps without running into the price or the controls. Don’t promise that items are reserved unless your store actually reserves them.
Label unit price, line total, and subtotal
Shoppers must be able to tell a unit price from a line total, and both from the cart subtotal. Two unlabeled figures beside one product make them guess.
Shoppers can change quantities in a Setka cart. Test the smallest and largest quantity, repeated taps, and a slow connection, and check that every affected amount updates together. At no point should a new quantity sit next to an old total.
Put the subtotal after the product lines and call it Subtotal, not Total, while shipping, tax, or other charges are still open. Check it against what the store calculates from real products and rules. A number typed into a mockup proves nothing about the calculation.
Show automatic discounts where they change the price
Setka applies configured promotions to eligible products, categories, order totals, and shipping. When an offer changes a line, the shipping charge, or the subtotal, show it right there with its name and amount, so shoppers don’t have to work out why two figures differ.
Show only what the campaign actually does: no countdown, combination, or condition it doesn’t have. Test just below, at, and above any threshold. Then remove an eligible product and check that the discount and the subtotal change together.
Whether a promotion is worth running at all is covered in the guide to discounts without damaging margins. In the cart, describe the exact rule configured for the store.
Say when shipping and tax will be settled
Until checkout has the delivery details your rules need, the cart may not know the final shipping or tax amount. Say so, and say when it will be known: “Shipping is calculated from your delivery details at checkout” or “Tax is confirmed at checkout.”
Don’t show a guessed cost, a tax figure, a delivery promise, or “free shipping” unless an active rule produces it. In Setka you set shipping rules and product-type tax in the admin, and the shipping zones and delivery rates guide covers how to structure the rules. Then compare what the cart says with what checkout charges.
A compact subtotal block looks like this:
Items subtotal €84.00
Automatic promotion −€10.00
Subtotal €74.00
Shipping and tax Confirmed at checkout
Test edit and remove until they hold
An edit works only when the new quantity sticks, every amount recalculates, the shopper can see that the change happened, and checkout receives the revised cart. Remove has to take out the intended line, cope with the last item, and leave a cart that still makes sense.
Try each action with one item and with several. Tap twice during a slow update. Setka carts persist between visits, so leave the store, come back, and check that the edit is still there. On a phone, watch where the screen lands after each change: the shopper shouldn’t lose their place.
Give an empty cart a way back
An empty cart should say it’s empty and offer a clear way back to the products. Check where “Continue shopping” leads, and that no stale price, promotion message, or checkout button is left behind.
Test a cart that starts empty and one emptied by removing the last item. Don’t fill the space with recommendations just to avoid a blank screen.
Cart-state matrix
Run this with representative products and the store’s real rules. If a state doesn’t apply to your store, record it as N/A with a reason, not as a pass.
| State | What the shopper must understand | Action to test | Pass evidence |
|---|---|---|---|
| One product | Identity, quantity, price meaning, subtotal | Open cart and continue | Product data matches catalog and checkout |
| Several products | Which amount belongs to which line | Review each line | Lines remain distinct; subtotal recomputes correctly |
| Quantity change | New quantity and resulting price | Use every supported quantity method | One update persists; all affected amounts agree |
| Automatic discount eligible | Why the price fell and by how much | Meet the configured rule | Discount appears truthfully in cart and checkout |
| Automatic discount lost | Why the benefit disappeared | Remove or reduce an eligible item | Discount and subtotal update together |
| Remove one line | Which product will leave | Use the supported remove action | Correct line leaves; remaining amounts are correct |
| Remove last line | That the cart is empty | Remove the only product | Empty message and route back replace checkout |
| Invalid quantity or stale data | What failed and how to recover | Trigger a safe supported failure | Message is near the problem; no false total remains |
| Slow or failed update | Whether the action is pending or failed | Constrain connection and retry | Duplicate changes are prevented; recovery is clear |
| Shipping/tax undecided | Why subtotal is not final | Continue with test details | Cart wording agrees with checkout calculation |
| Narrow mobile | What is selected and how to proceed | Review, edit, and continue by touch | No overlap, hidden error, or covered action |
Annotated mobile cart example
┌────────────────────────────────┐
│ Cart (2 items) │ 1 State is named
├────────────────────────────────┤
│ [image] Column lamp │ 2 Product remains identifiable
│ Qty 2 │ 3 Verify supported edit behavior
│ €32.00 each €64.00 │ 4 Unit and line price are labeled
│ Remove │ 5 Verify target and result
├────────────────────────────────┤
│ Automatic promotion −€10.00 │ 6 Explain a real applied rule
│ Subtotal €54.00 │ 7 Do not call this the final total
│ Shipping and tax at checkout │ 8 No invented estimate
│ │
│ [ Continue to checkout ] │ 9 Visible; covers no content
└────────────────────────────────┘
On a real phone, scroll from the first product to the checkout button and back. Enlarge the text, use the longest product name, trigger an error, and open the keyboard where there’s an input. A sticky checkout button fails if it hides a product, a message, the subtotal, or a control. The mobile e-commerce UX checklist covers the rest of the path.
Test errors before you send shoppers onward
A cart error should keep the remaining information trustworthy, name the affected line or rule, and tell the shopper what to do next. “Something went wrong” isn’t enough when the quantity or subtotal may be stale.
Reproduce failures you can trigger safely: an invalid quantity, an interrupted update, a rule changed mid-session. Write the final error copy only after you’ve seen what the store actually does. Test with your own orders, never with customer data.
Then continue to checkout. Turning on payments is covered in the Stripe setup guide; this guide stops at the handoff. Once a successful payment creates a paid Setka order, follow the first-order runbook for fulfillment.
Why the cart and checkout agree in Setka
On a theme-based platform, the cart is a theme template, sometimes swapped for a cart-drawer app, while discount and shipping messages can come from other apps. Each piece shows its own part of the price, and the states in the matrix are where they drift apart: a discount that appears only at checkout, a shipping message that misses a rule change, a drawer that doesn’t refresh after a quantity change.
Setka is our product, and it doesn’t have that layer. It generates the cart together with the homepage, category pages, product pages, and navigation, and the cart works from the same product, promotion, shipping, and tax rules as checkout. There is no cart template or cart app to keep in step, so the subtotal a shopper sees is the one checkout continues from. You still set the rules and test the states. If a line or message reads unclearly, open the page, describe the change, preview it, and publish when it’s right.
Open your store in Setka and run the matrix in preview with representative products and your real rules. For each state, note the expected result, what you saw, the device, and a screenshot. Then publish, place a real order through checkout, refund it, and launch.