Tithi Mondal

Article5 min readUpdated

Shopping Cart Design: Price Breakdown, Coupons, Wishlist

Shopping cart design for Indian apps: item rows, coupon field, price breakdown, delivery charges, wishlist rules, every state and sample wording.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Shopping Cart Design: Price Breakdown, Coupons, Wishlist: cover illustration

Imagine a customer in Asansol adds a kurta to the cart. At the last step, a delivery fee and a handling fee appear that she did not see before. The total is ₹180 higher. She closes the app. Shopping cart design exists to stop that. The cart is the screen where the user reviews what they chose and what it will cost, before they pay. Its job is to build confidence in the total.

For the payment step that follows, read UPI payment UX and checkout design. This article covers the cart and the wishlist.

What should a cart screen do?

A cart screen must let the user check, change and trust the order in one glance. It must answer three questions: what am I buying, how much will I pay, and what happens next.

The cart also has one quiet job: to remove doubt. Show stock, delivery date and return rules near the items, not in a policy page. For more on trust, see trust signals in website and app design.

What goes on the cart screen, from top to bottom?

The cart screen has a fixed order that matches how people check an order. This is the cart screen UI I use as a starting point.

  1. Title and count. "Your cart (3 items)".
  2. Delivery address row. "Deliver to: Salt Lake, 700091" with "Change". Needed early because it affects price and date.
  3. Item rows. Image, name, size or variant, price, quantity stepper, "Remove" and "Save for later".
  4. Stock and delivery notes. "Only 2 left" or "Delivery by Fri, 21 Nov".
  5. Coupon row. "Have a coupon?"
  6. Price breakdown. Detailed below.
  7. Sticky bottom bar. The total on the left, a button on the right: "Place order" or "Continue to payment".

Keep the bottom bar fixed so the total and button are always visible while scrolling. The quantity stepper should have large tap areas. A "minus" at quantity 1 should either remove the item with an undo message or become a bin icon. Never leave it dead.

How should the price breakdown look?

The price breakdown should list every amount that makes up the total, in the same order every time. This is the price breakdown users read before trusting the app.

LineExample
Item total₹1,598
Discountminus ₹200
Coupon: FIRST100minus ₹100
Delivery charges₹40
Taxes₹59
Total to pay₹1,397

Add a line such as "You save ₹300 on this order" in green only when the saving is real.

Rules that help:

  • Use the rupee sign and Indian number grouping: ₹1,00,000, not ₹100,000.
  • Show the maximum retail price crossed out only if it is a real price.
  • Make the total larger than any other line.
  • Do not add a fee that appears only in the last step.
  • If taxes are already included, say "Inclusive of all taxes". Your accountant decides the rule, not the designer.

How should delivery charges be displayed?

Delivery charges display works best as a simple line with a reason and a goal. Example: "Delivery ₹40. Add ₹150 more for free delivery." A thin progress bar under that line helps. If the address is not set yet, write "Calculated after you add an address" rather than leaving the line blank. If delivery is free, write "Free" in green, not ₹0.

How should the coupon field work?

The coupon field should be hidden by default and easy to find. A large empty box invites users to leave and search for codes, and many do not return.

  • Collapsed state: "Have a coupon? Apply here".
  • Open state: a text field with "Enter coupon code" and an "Apply" button. Below it, a list of coupons the user can actually use now.
  • Success: "FIRST100 applied. You save ₹100."
  • Invalid code: "This code is not valid. Check the spelling."
  • Expired code: "This code expired on 15 November."
  • Not eligible: "Add items worth ₹300 more to use this code."

The last message matters most. Tell people exactly what to do to qualify. Codes should work in upper or lower case. Also show a way to remove a coupon.

How do you design a wishlist?

A wishlist design is a separate screen where users save items for later without buying. It should be easy to reach from the product page and the profile.

  • A heart icon on each product, which fills when tapped, with a short message: "Saved to wishlist".
  • A wishlist screen with a grid or list, the same card style as the catalogue.
  • Each card has "Move to cart", plus a small "Remove".
  • Notes that matter: "Price dropped by ₹150", "Back in stock", "Only 1 left".
  • Optional: let users turn on alerts for price drops. Link this to notification UX.
  • Empty state: "Nothing saved yet. Tap the heart on any item to keep it here." with a "Browse products" button.

For a first-time user, the wishlist is also a safe step when they are not ready to pay. A user who saves an item has shown interest, and the app can bring them back politely. Do not remove sold out items without telling them. Keep them with the label "Out of stock" and an option to be notified.

What are all the cart states?

The cart has more states than the busy one, and each needs a message.

  • Empty: "Your cart is empty. Add items you like and they will appear here." Button: "Start shopping". Include "Saved for later" below if any exist.
  • Loading: grey shapes for rows and a disabled bottom button.
  • Price changed: "The price of Blue kurta changed from ₹799 to ₹849." Show it before payment, never silently.
  • Out of stock: "Sorry, this item is no longer available. Remove it to continue."
  • Below minimum order: "Add ₹60 more to place this order." Disable the button but explain.
  • Address not serviceable: "We do not deliver to this pincode yet. Try another address."
  • Error: "Could not update your cart. Try again."
  • Offline: show the cart in read-only mode, with "You are offline".

See empty, loading and error screens for how to design these. For grocery and local delivery examples, see grocery and kirana app design and marketplace app UI/UX design.

If you are building a store app and want the cart, wishlist and checkout designed as one flow, see my mobile app design service.

Frequently asked questions

Should the cart show delivery charges before checkout?

Yes. Show the delivery fee, or a clear note such as "Delivery calculated after you add an address", on the cart screen. A new charge at the payment step makes users abandon the order.

Where should the coupon field go?

Below the items and above the price breakdown, as a collapsed row that says "Have a coupon?". A big open field makes people without a code leave to search for one.

What is the difference between a cart and a wishlist?

A cart holds items the user plans to buy now. A wishlist holds items they want to save for later, and does not reserve stock or take payment.

Should the cart save items after the user closes the app?

Yes. Keep the cart linked to the account so it appears on every device and after a restart.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.