Tithi Mondal

Article7 min readUpdated

Order Tracking Page Design, Returns and Refund Flow

Order tracking page design for Indian stores: status steps, cancel order screen, return and refund flow, refund status and exact wording for each state.

By Tithi Mondal, UI/UX Designer

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

Order Tracking Page Design, Returns and Refund Flow: cover illustration

A shopper in Asansol orders a pair of sandals on Monday. On Wednesday she asks herself the same question that millions of shoppers ask: where is my parcel. If the store answers in two seconds on one screen, she stays calm. If she must open WhatsApp and write to support, the store has already lost some trust. An order tracking page is the screen that shows the current status of an order, the steps still to come and the actions allowed now. It is also called the order status page. This guide also covers the cancel order screen, the return and refund flow, and the refund status page.

For notifications that point to these pages, see notification UX for push, SMS and WhatsApp. For apps that live on tracking, see logistics and delivery tracking app design.

What does an order tracking page need to show?

An order tracking page needs the current status in words, a timeline with dates, the items, the delivery address, and the next action. The status sentence comes first, because it is the answer to the question the shopper came with.

From top to bottom:

  1. Status sentence. "Out for delivery. Arriving today by 7 pm."
  2. Timeline. Ordered, Packed, Shipped, Out for delivery, Delivered. The current step is filled, past steps carry a date and time, future steps are grey with an expected date.
  3. Courier block. "Shipped with Courier Name. Tracking ID 1234567890." A "Track on courier site" link and a copy button for the ID. Show the real name of the courier you use.
  4. Delivery address and phone. With "Edit" only while the order is not yet shipped.
  5. Items. Image, name, size, quantity, price.
  6. Payment summary. Method, amount, and whether cash is due: "Pay ₹899 in cash on delivery".
  7. Actions. Cancel order, Return items, Need help.
  8. Order ID and date, with a copy button.

Open the page from three places: the order list, the confirmation email or SMS, and the WhatsApp message. Make the link work without a login if the store sends it by SMS, using the order ID and phone number as a light check. Guests are common in Indian stores.

What status steps and wording should you use?

Use five to seven plain steps that match what really happens in your warehouse, and describe each in a full sentence. A timeline that shows steps you do not track is a false promise.

StatusSentence the shopper reads
Placed"Order placed on 19 Nov. We sent a confirmation to your phone."
Confirmed"Seller has confirmed your order."
Packed"Your order is packed and waiting for the courier."
Shipped"Shipped on 20 Nov. Expected by 24 Nov."
Out for delivery"Out for delivery. Keep ₹899 ready if you pay in cash."
Delivered"Delivered on 23 Nov at 4:10 pm."
Delivery attempt failed"The courier could not reach you. They will try again tomorrow."
Delayed"Your order is late. New date: 26 Nov. We are sorry."

Two statuses are often missing and cause the most support messages. The first is "delivery attempt failed". Add a button, "Update phone or address", and a line telling the shopper when the next attempt happens. The second is "delayed". Say it, give a new date and apologise in one short sentence. Silence looks worse than a late parcel.

Festival weeks are busy for couriers. In Durga Puja or Diwali weeks, add a banner above the timeline: "Festival week. Some deliveries take 1 to 2 days longer." Only write it if it is true for your couriers.

How should the cancel order screen work?

The cancel order screen must show only while cancelling is possible, ask for a reason, show what the shopper will get back, and confirm in one extra tap. Cancel is a quiet action. Hide it in the page, not in the main button area, but never make it hard to find.

Rules:

  • Before dispatch: show "Cancel order". After dispatch, replace it with "Return after delivery" and explain: "This order has shipped. You can return it after it arrives."
  • Reason list: "Ordered by mistake", "Found a better price", "Delivery is too slow", "Want to change size or colour", "Other". Make it one tap, with an optional text box.
  • Offer an alternative: for "change size", offer "Change size instead" and keep the order alive.
  • Show the refund before confirming: "You will get ₹899 back to your UPI account in 3 to 5 working days." For cash on delivery orders: "No payment was made, so there is nothing to refund."
  • Confirm: a button, "Yes, cancel order", and a plain "Keep order".
  • Result: "Order cancelled. Refund started." with a link to the refund status.

Do not hide cancel to reduce cancellations. A shopper who cannot cancel will refuse the parcel, and that costs the store shipping both ways.

How should the return and refund flow be designed?

The return and refund flow should have four short steps: choose items, choose reason, choose pickup or drop-off and refund method, then confirm. The page must state the return window and the conditions before the shopper begins.

Show the rule on the product page and again at the top of the flow: "Returns accepted within 7 days of delivery. Item must be unused with tags." Use your own window. Do not copy a number from another store.

The four steps:

  1. Choose items. A checklist with images. Let her return one item of an order without cancelling the rest.
  2. Reason. "Wrong size", "Different from photo", "Damaged", "Wrong item received", "Changed my mind". For damage or wrong item, ask for 1 to 3 photos. For size, offer "Exchange for another size" first.
  3. Pickup and refund. Show the pickup address, a date, and the refund options: "Original payment method", "Store credit" or "Bank account". If the order was cash on delivery, ask for UPI ID or bank details here, and say why: "You paid in cash, so we need your UPI ID to send the refund."
  4. Confirm. A summary with item, reason, pickup date, refund amount. Button: "Request return".

After submission show a return ID, the next step and a date. Send the same text by SMS or WhatsApp. Check UPI ID format on the spot and let the shopper confirm the account name if your payment partner returns it.

If the store pays for return shipping, say so in one line. If the shopper pays, show the amount before she confirms, not after.

What should the refund status page show?

The refund status page must show the amount, the destination, the current stage and the expected date, in that order. Refunds create more anxiety than orders, because the money has already left the shopper's account.

Example layout:

  • Headline: "Refund of ₹899 is on its way".
  • Destination: "To your UPI ID, ravi@bank" with part of the ID hidden: "r***@bank".
  • Stages: Return received, Quality check, Refund started, Refund credited. Each with a date.
  • Expected date: "Expected by 28 Nov".
  • Reference number: a bank or gateway reference the shopper can quote at her bank, with a copy button.
  • Help: "Not received after 28 Nov? Tell us".

State times honestly. Banks and gateways take different times, so say "3 to 5 working days after we receive the item" only if that is your real policy, and say which step you control and which belongs to the bank. Store credit can be instant, so say "Credited now" when it is.

States to design: refund pending, refund started, credited, failed (with the reason and a button to give new account details), and partial refund (with a line-by-line reason such as "₹60 return shipping deducted").

What mistakes make tracking and returns pages fail?

The common failures are vague status words, hidden returns, no refund visibility and forcing a chat with support for routine actions. These cost support time and reduce repeat orders.

  • "Processing" as a status for three days. Say what is processing.
  • Tracking links that open a courier site in a language or layout the shopper cannot use.
  • No action for failed delivery attempts.
  • Return buttons that vanish after the window without any explanation. Show "Return window ended on 30 Nov" instead.
  • Asking for the order ID when the shopper is already logged in.
  • Showing the refund as "Done" when the store has only started it.
  • Using different words in SMS, email and the page. If the SMS says "Dispatched" and the page says "Shipped", shoppers doubt both.

I think about this as a journey: order, wait, receive, doubt, return, refund. A customer journey map helps list every moment where the shopper needs a sentence from you. For a store that needs these pages designed with the rest of the checkout, see my mobile app design service or get in touch.

Frequently asked questions

What should an order tracking page show first?

The current status in one sentence with a date, such as Out for delivery, arriving today by 7 pm. The timeline, courier details and items come below it.

How do you show the refund status in a return flow?

Show the amount, where the money is going, the current stage and an expected date. Add a reference number the shopper can give her bank and a help link.

Should a store allow cancelling after shipping?

Usually no. After dispatch, replace Cancel order with a Return after delivery explanation so the shopper knows her options.

What if a cash on delivery order needs a refund?

The shopper paid cash, so ask for her UPI ID or bank details inside the return flow and explain why. Validate the format before she submits.

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.