Building the Returns Experience on Your Online Store: Policy Page, Return Request Form, Status Updates and What to Show Before Checkout
A returns experience on an online store has four parts the website must deliver: a policy page that says plainly what is and is not returnable, a return request form that a customer can finish on a phone in a couple of minutes, status updates that tell the customer where their return stands, and a few reminders placed before checkout so nobody is surprised. The legal wording of your policy matters, but for most D2C stores the bigger problem is the build: a good policy hidden in a footer link, a return process that exists only as an email thread, and no way for a customer to see what is happening. This guide explains how to build the website side of returns for a Shopify, WooCommerce or custom store in India.
It is written for store owners and the people briefing a developer. It is not legal advice: the rules that apply to you depend on your business structure and products, so have the final policy text reviewed by a qualified professional. Examples are hypothetical and numbers are illustrations. Courier choices, tax treatment of credit notes and payment-gateway refund mechanics are left out on purpose; they belong to operations and accounting, not to the website build.
What changed in this edition
Earlier versions of this article tried to cover everything from reverse logistics to GST records. That is the wrong shape for a website guide. This version keeps the useful policy checklist but focuses on what the storefront and admin should do, so a developer can build from it.
Start with the policy content a customer needs
Before design, settle the facts. A customer reading the policy wants to know eight things, and your page should answer them in this order.
- Who can return what, and by when. State the number of days, and say whether it counts from delivery or from the order date. Delivery is easier for customers to understand, since they cannot inspect the goods before they arrive; whichever you choose, say it and apply it consistently.
- Which products are excluded, and why. Personalised items, perishable goods, opened hygiene or personal-care products, digital downloads and gift cards are common exclusions. Say it in plain words. "All sales are final" with no explanation reads as a warning, and it does not remove your duties for defective or misdescribed goods.
- What condition the product must be in: unused, with tags, in original packaging, with accessories. Mention it before purchase, not only when a return is requested.
- What the customer can ask for: return, replacement, exchange, refund or store credit. Define each in a line. Do not call store credit a refund.
- What to do if the item is damaged, defective or wrong. Give this its own short section with its own route. These complaints should not be pushed through the same path as a change-of-mind request.
- Who pays return shipping, and when. If "free returns" means the customer pays first and is reimbursed, say so.
- How and when the refund arrives, and what triggers it: approval, pickup, receipt or inspection.
- How to complain or escalate, with a real contact.
Keep the language consistent between this page, product pages, order emails and support replies. If the product page says "free returns" and the policy says "return shipping charged", you have created a dispute in advance.
The legal reference points, in one paragraph
India's Consumer Protection Act, 2019 and the Consumer Protection (E-Commerce) Rules, 2020 are the main reference points for online sellers. Secondary summaries by law firms describe the rules as requiring e-commerce entities to display information such as returns, refunds, exchanges, warranty, delivery and grievance redressal, to appoint a grievance officer who acknowledges complaints within 48 hours and resolves them within a month, and to take back and refund defective or misrepresented goods and goods delivered late, unless the delay is due to unavoidable circumstances. These summaries do not agree on every detail, and duties differ between a marketplace and a seller operating its own website, so check the notified text of the rules from the Department of Consumer Affairs and ask your adviser which duties apply to you.
Where to put the policy so it is actually seen
A policy page that exists is not the same as one customers can find at the moment they need it. Link it from:
- The footer, as a clearly named link: "Returns and refunds", not "Policies".
- Product pages, near the add-to-cart button, as a short summary and a link: "Returns accepted within X days of delivery. See conditions."
- The cart and checkout, as a one-line reminder next to the payment step.
- The order confirmation page and email, next to the order details. Our guide to order confirmation pages and purchase tracking covers what that page should contain.
- The support or contact page, with a direct link to the return request form.
Use the same short summary text everywhere, held in one place such as a reusable block or a theme setting, so that changing the return window updates every page. This is a small development task that prevents the most common inconsistency.
Make the page easy to read on a phone
Most customers will read it on a phone. Put a short summary box at the top, then use headings, short paragraphs and a table for product categories. Avoid walls of legal text. A page that is clear on a phone is also easier for support staff to quote from.
| Situation | What the customer can ask for | What the page should say |
|---|---|---|
| Item arrives damaged | Replacement or refund, subject to review | Report within the stated period; add photographs |
| Wrong item delivered | Replacement or refund | Report within the stated period |
| Defective item | Repair, replacement or refund, depending on the case | Describe the fault; review may apply |
| Size or fit issue | Exchange or return, if you offer it | Tags and packaging conditions |
| Change of mind | Only what you choose to offer | Window, condition and shipping terms |
| Personalised item | Usually restricted | Exceptions for defects or wrong fulfilment |
This is an example of policy categories, not a rule for every business. Your own products and fulfilment process decide the final terms.
Build a return request form that works on a phone
A return process that begins with "email us" costs you support time and loses information. A short request form gives you structured data and gives the customer a clear next step.
What the form should ask
- Order number and the email or phone used, so the customer can be matched to an order. Better, let a logged-in customer pick the order from a list.
- Which item or items, with quantities, since multi-item orders are common.
- The reason, from a short list: damaged, wrong item, defective, size or fit, changed my mind, other. Each reason can lead to a different next step.
- A resolution preference, if you offer a choice: replacement, exchange, refund, store credit.
- Photographs, required for damage, defect or wrong-item reasons and optional otherwise. Allow upload from a phone camera and set a sensible file-size limit.
- A short note, optional.
Do not ask for more than you need. Do not ask for card numbers, passwords, OTPs or UPI PINs, now or later in the process, and say on the page that you will never ask for them. If bank details are needed for a refund on a cash-on-delivery order, collect them through a controlled form or verified support process, not by open chat or email.
What the form should do
- Check eligibility automatically against the delivery date, return window, product category and previous requests, and tell the customer straight away if the item is outside the window or excluded. A refusal should say which condition was not met and what other option exists. "Not eligible as per policy" helps no one.
- Give a request number and show it on screen and by email.
- Route by reason. Damage and defect requests go to a person quickly; size exchanges may follow an automated path.
- Keep the data tidy. Save the request against the order in your admin or CRM, with the photographs, the reason and the decision.
- Protect personal data. Returns involve addresses, phone numbers, photographs and sometimes bank details. Collect only what you need, limit who can see it and say what you do with it in your privacy notice. Our DPDP compliance guide for websites explains the duties in plain language. Do not use a customer's return photographs in marketing without proper permission.
What platforms offer out of the box
Shopify and WooCommerce both have order and refund tools in the admin, and both have apps and plugins that add customer-facing return portals. What each does, and what it costs, changes often, so check the current feature list before you choose. Ask any app vendor:
- Can the customer start a return without logging in, using order number and email?
- Can rules differ by product type, tag or collection?
- Does it support photographs, reason codes and notes?
- Which emails and messages does it send, and can we edit them?
- Where is the data stored, and can we export it?
- How much does it slow the page? Portals load scripts; see our guide to auditing third-party scripts.
- What happens to our data and links if we stop using the app?
For stores with unusual rules, a custom form connected to the admin or CRM can be simpler than bending an app to fit.
Status updates: let customers see where the return stands
Most return-related support messages are a version of "where is my return?" Reduce them by making status visible.
The stages to show
A simple set of stages is enough: Requested, Approved, Pickup or shipping arranged, Received, Inspected, Refund or replacement initiated, Completed, Declined (with reason). Use the same labels in the admin, in the customer-facing page and in emails.
Where to show them
- A return status page, reached by a link in the confirmation email, or a section in the customer's account.
- Emails or WhatsApp messages at key steps: request received, pickup scheduled, pickup failed, item received, refund initiated, request declined. If you use WhatsApp for updates, get opt-in first and use approved templates; see our WhatsApp opt-in checklist and our guide to WhatsApp order updates.
- The admin, so your team can change a stage and trigger the message without editing text by hand.
Be honest about timing
Do not promise a refund date that your warehouse, finance and payment processes cannot reliably meet. State the trigger ("after we receive and check the item") and the usual range, and say that banks and payment providers can take additional days. A range you meet is better than a promise you break.
Cash on delivery and the refund details form
For prepaid orders, refunds usually go back to the original payment method, subject to how the payment provider processes them. For cash-on-delivery orders there is no payment to reverse, so you need somewhere to send the money. That raises a design question: how does the customer give you refund details safely?
- Offer a short form that is only reachable from the customer's own return request, not a link anyone can guess.
- Show the details back to the customer for confirmation before submitting.
- Tell them that you will never ask for card numbers, PINs or OTPs.
- Restrict who in your team can see the details, and delete them when no longer needed, as your privacy notice states.
Whether your store keeps COD at all is a business decision outside this article; our guide to Shopify COD setup and order verification covers the build side.
What to show before checkout
A few lines at the right moment prevent many returns and many disputes.
- Size and fit help on apparel and footwear: measurement charts, model details and fit notes. Fewer wrong-size orders means fewer returns.
- Accurate product pages: images that show the real product, accurate descriptions, clear variant selection. Many "not as described" returns begin with unclear listings. Our product page conversion checklist covers this.
- A one-line returns reminder next to the payment step.
- Sale and clearance conditions, stated before purchase. If sale items follow different terms, say it on those product pages, not only in the policy.
- Delivery estimates that your operations can keep.
The admin side: what your team needs
The customer-facing page is half the job. Your staff need tools too.
- A queue of return requests with filters by status, reason and age.
- Templates for replies, consistent with the policy, that include the specific reason for a decline.
- Reason reports, to see which products and reasons cause the most returns. If one product keeps coming back as "not as described", fix the listing.
- Links between the return, the original order and any refund or replacement, so that finance and operations see one record.
- An internal checklist for inspection, by product type: tags and wear for apparel, serial numbers and accessories for electronics, batch and expiry for consumables.
- An audit trail, showing who approved what and when.
A hypothetical worked example
A Pune-based homeware store sells 30 SKUs on WooCommerce. Returns arrive by email, WhatsApp and phone. The owner spends a few hours a week answering "where is my return?" and often cannot find which order a photo belongs to.
The developer builds the following over two weeks: a returns page with a summary box and a category table; a form with reason codes, photo upload and eligibility checks; return statuses in the order admin; three automated emails; and a returns reminder block shown on product pages and in the cart. A QR code on the packing slip links to the form.
Suppose, hypothetically, that the owner then notices that most "damaged" requests relate to one fragile product with thin packaging. That is a packaging problem, found because requests are now recorded by reason. The returns page did not fix it, but it made it visible.
These details are invented to show how the pieces connect; your results will depend on your products and your operation.
Common mistakes in building returns
- Copying a marketplace's policy, whose warehouses and refund systems differ from yours.
- Hiding conditions until a customer requests a return. Mention tags, seals and packaging before purchase.
- Using absolute language such as "no refunds under any circumstances" or "company decision is final", which can create trust and compliance problems. Separate ordinary change-of-mind requests from defective, damaged or wrong-item cases.
- Treating all reasons the same. A size exchange and a suspected defect should not follow the same path.
- Not telling marketplace buyers what to do. If you also sell on a marketplace, say that marketplace orders follow the marketplace's return process, and explain your own process for direct orders.
- No owner for the policy. Assign one person to keep the policy, the page, the form and the emails in step.
- Staff who contradict the page. Give support a short internal guide with examples and escalation rules.
What to ask a developer before you build
- Where will the returns summary appear, and is it maintained in one place?
- What does the request form ask for, and how are photographs stored and protected?
- How does the form decide eligibility, and what does the customer see on a refusal?
- Which statuses will the customer see, and which messages are sent at each?
- How are COD refund details collected and who can see them?
- What reports will we get by reason and by product?
- How will this be tested on a phone?
Working with Govindani Infotech on store returns and order workflows
Govindani Infotech is a Pune-based website and software company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. We build e-commerce websites, order and customer workflows, CRM integrations and WhatsApp notifications. Our e-commerce development service page describes the range, and our WhatsApp commerce page covers order messages.
If you want to review your current returns experience, send us your store address and tell us how requests arrive today. We will say what we would build first, before any scope or price is discussed. Message us on WhatsApp at wa.me/919201958278 or use our contact page. Have a qualified professional review the final policy wording for your business.
Frequently Asked Questions
Is a returns policy mandatory for an ecommerce website in India?
Online sellers and e-commerce entities have consumer-facing duties under the Consumer Protection Act, 2019 and the Consumer Protection (E-Commerce) Rules, 2020, which law-firm summaries describe as including information about returns, refunds, exchanges and grievance redressal. The exact duties depend on your role, so check the notified rules and ask a legal adviser. A clear written policy is the practical way to share the terms.
Can an Indian online store offer no returns?
A store may restrict ordinary change-of-mind returns for certain products if it says so clearly before purchase. That does not remove its responsibilities for defective, damaged, wrong or misdescribed goods. Have your exclusions reviewed for your product category.
Where should I link the returns policy on my website?
In the footer, on product pages near the buy button, in the cart and checkout, in the order confirmation page and email, and on the support page. Use one short summary stored in one place so that every page stays consistent.
What should a return request form ask for?
Order number and contact details, the item or items, a reason from a short list, a preferred resolution if you offer a choice, and photographs for damage, defect or wrong-item requests. Do not ask for card numbers, PINs or OTPs.
How do I handle refunds for cash-on-delivery orders?
There is no payment to reverse, so you need refund details from the customer. Collect them through a controlled form tied to the return request, confirm them back to the customer, restrict access and never ask for PINs or OTPs.
How long should I take to refund?
State the trigger, such as receipt and inspection of the item, and a realistic range, and add that banks and payment providers can add days. Promise only what your operation can deliver.
Sources: Consumer Protection Act, 2019 and Consumer Protection (E-Commerce) Rules, 2020 — Department of Consumer Affairs, Government of India, Mondaq: The Consumer Protection (E-Commerce) Rules, 2020, IndiaLaw: A summary of the Consumer Protection (E-Commerce) Rules, 2020, Digital Personal Data Protection Act, 2023 (MeitY)