Build a Returns Portal in an Hour

Your return process still runs on a favour

A shopper receives the parcel, opens it, and the colour is wrong. What happens next decides whether your store keeps the customer or keeps the refund, because the way your returns work is the way your store apologises. Most small stores still run returns over email, one message at a time, which makes the buyer chase you for the label, the refund moment, and the status. A returns portal does this better, costs almost nothing, and takes under an hour to build without a paid app. Here is the build.

Step 1: Decide the three outcomes every return can have

A portal feels complex because nobody defined the end states. Ours are exactly three, in line with Australian Consumer Law: exchange for another size or colour, store credit issued instantly, or refund to the original payment method. Every request the portal collects resolves to one of those three, and anything outside them goes to a human. Write your three on paper before you build anything.

Step 2: Build one page that asks everything in one form

The portal itself is a single page with an order lookup, a reason selector, a photo upload, and a confirmation. On WordPress and Shopify alike, this is a standard page with a form handler (your platform’s own form tooling or store contact form plus order-number field does the job), no paid returns app required to start.

<form action="/returns-received" method="post">
  <input type="text" name="order_number" placeholder="Order number (e.g. 10234)">
  <select name="outcome">
    <option>Exchange for a different size</option>
    <option>Store credit</option>
    <option>Refund to original payment method</option>
  </select>
  <select name="reason">
    <option>Too small</option>
    <option>Too large</option>
    <option>Colour wrong</option>
    <option>Changed my mind</option>
    <option>Damaged or faulty</option>
  </select>
  <input type="file" name="photo" accept="image/*">
  <button>Start my return</button>
</form>

The photo upload matters for one reason: when the reason is damaged or faulty, the picture is your evidence and the portal becomes the proof store for later disputes.

Step 3: Auto-reply with the label and the timeline

The moment a form arrives, the reply goes out, same minute, every time:

Hi [first_name],
Return received for order [number]. Here is what happens next:
1. Post it back with the label attached below (free prepaid label).
2. We check it the day it arrives, usually 2-3 days after you post.
3. Your [exchange/credit/refund] is issued same-day we finish checks.
Label: [download link]
Nothing else is required from you. We will email at each step.

If your carrier offers a digital label service, paste that link; otherwise a prepaid PDF label attached to the email does the same job at small scale. The three numbered steps are what removes the “where is my refund” email entirely, because the buyer now owns a timeline instead of a question.

Step 4: Publish the statuses where the customer looks

A portal without a status page just becomes email again. Add a short status lookup on the same return page: order number in, three states out (received, checking, resolved). If you do not want to build the lookup, a plain table updated each morning achieves ninety percent of the value for zero code.

<h3>Return status</h3>
<p>Order 10234: checking (arrived Wednesday)</p>
<p>Order 10198: resolved, credit issued</p>
<p>Order 10155: resolved, exchanged and re-shipped</p>

Step 5: Count the reasons quarterly and act on the top one

The portal’s quiet gift is data. Your reason counts, read every quarter, will show one fixable problem outweighing the rest: a size chart that misleads at one product, a colour that photographs wrong, a packaging that faults in transit. Fix the top reason and the next quarter’s count drops, which is the only meaningful return rate you can actually manage from the inside.

What this replaces

Email tag about labels, refund-status chasing, “did my return arrive” messages, and the one customer who gave up entirely. An hour of building, a standing status habit, and the apology your store makes on its worst day starts working like the rest of the store does: on its own, at any hour, in writing.

Want more like this? Join MOKU Club for free. Weekly resources, early access to new guides, and occasional templates you can actually use. Join below.