Returns and Refunds Workflow for Online Stores, Step by Step

A good returns and refunds workflow for an online store matches each request to its order, sorts change-of-mind returns from faulty goods, checks eligibility against your policy and the customer's local law, issues a label, records what the warehouse receives and releases the refund before any legal deadline. Software can run most of the routine steps. People decide faults, deductions and exceptions.

Returns look like one process but are several: a change of mind, an item that broke after a month, a crushed parcel, a wrong pick, and a buyer abroad whose rights differ from your returns page. Treating them all the same is where most problems start.

This guide goes deeper than our broader ecommerce automation guide, walking through one workflow with the rules that differ between the US, UK, EU, Canada and Australia. Check the rules where you operate and where your customers live before you encode anything.

Key takeaways

Split change-of-mind returns from faulty-goods claims at the very first step, because the legal rules, costs and decision makers differ.
In the EU and UK, most online purchases carry a 14-day cancellation right and refunds are due within 14 days, while US, Canadian and Australian change-of-mind returns are largely set by your own policy.
Automation can match orders, check eligibility, issue labels and track refund deadlines, but faulty-goods decisions, deductions and goodwill stay with people.
Encode each market's rules only after your team, with legal advice where needed, has written and checked them.

Why returns workflows break

Most small stores run returns from a help desk inbox, a spreadsheet and memory. When volume spikes after a peak season, the same failures appear:

The clock is invisible. Nobody tracks when the item arrived back, so a refund that is legally due slips.
Every return gets the same treatment. A faulty item goes down the change-of-mind route and the customer is asked to pay postage they shouldn't.
Warehouse and service don't talk. The parcel is received, the agent doesn't know, and the customer chases.
Policy lives in one person's head. Final-sale items, market windows and deductions vary by who picks up the ticket.
Reasons are lost in free-text emails, so a bad batch takes months to notice.

These are mostly tracking and routing problems, which automation handles well. It doesn't replace the judgement calls.

The legal rules your returns workflow has to respect

Your policy can be more generous than the law, never less. The baseline differs a lot by market, so your workflow needs to know where the customer is.

Market	Change-of-mind return right for online purchases	Refund timing and key points	Faulty goods
EU	Yes, 14 days from delivery under the EU right of withdrawal, with exceptions such as personalised and perishable goods	Refund within 14 days of being told about the withdrawal, but you may wait until the goods or proof of return arrive (Article 13). If you didn't give the required withdrawal information, the period runs 12 months longer (Article 10)	Minimum two-year legal guarantee from delivery
UK	Yes, customers can cancel within 14 days of receiving the item, then have 14 more days to send it back (GOV.UK)	Refund within 14 days of receiving the item back, including standard delivery costs; no deductions unless the item was used or damaged	Separate rights under the Consumer Rights Act, including a 30-day short-term right to reject
US	No general federal right; mostly set by your own policy	The FTC's Mail Order Rule sets refund deadlines when an order is cancelled because it can't ship on time. Some states add rules, such as California Civil Code 1723 on displaying a less-than-full-refund policy	Warranty law and state rules apply
Canada	No general federal right; provinces set rules	In Ontario, CLEO's guide explains that online buyers can cancel in specific cases, such as missing required information or late delivery, and sellers then have 15 days to refund	Provincial consumer law applies
Australia	Not required by law; a change-of-mind policy you offer is binding on its own terms	The ACCC says there is no automatic cooling-off period for website purchases	Consumer guarantees can't be excluded; for a major failure the customer chooses refund or replacement

What this means for your workflow:

Change of mind and faults must be separate branches. In every market above, faulty goods carry rights a returns window can't remove.
Return postage rules differ. In the EU, the customer usually pays to return a change-of-mind item unless you offered to pay or didn't tell them before purchase; the trader pays for defective goods.
Dates matter. EU and UK clocks run from delivery and from receipt of the return, so you need delivery dates from tracking, not order dates.

This is a summary, not legal advice. Have each market's policy written and checked, with a lawyer where needed, before anything is automated.

The returns and refunds workflow, stage by stage

Here is how the workflow can run, with the trigger, the automated action and who reviews at each stage.

1. Return request

Trigger: the customer opens your returns portal, replies to an order email or messages support.

Action: the request is matched to the order by order number and email. Many platforms have this built in; Shopify's self-serve returns, for example, let customers request returns from the order status page for you to approve or decline. A short form collects the reason, condition and, for faults, photos. A QR code on the packing slip that opens the portal, made with our free QR code generator, keeps requests out of the inbox.

Who reviews: nobody, unless a free-text email can't be matched.

2. Classification

Action: the request is sorted into change of mind, faulty, damaged in transit, wrong item or not delivered. AI can help read free text, but the customer's form answers should drive the category. Mentions of injury, safety, legal threats or chargebacks go straight to a person.

Who reviews: an agent, for anything uncertain.

3. Eligibility check

Action: the request is checked against the customer's market rules and your policy: delivery date, window, excluded items such as personalised, perishable or sealed hygiene goods, and any more generous brand policy. iPhone photos often arrive as HEIC files; a HEIC to JPG converter keeps them readable.

Who reviews: clear change-of-mind returns inside the window can be approved automatically. Faulty, damaged and out-of-window requests go to an agent and are never auto-rejected, because faulty-goods rights outlast most windows.

4. Label and instructions

Action: approved returns get a carrier label or drop-off code and a return authorisation number. Printed as a Code 128 barcode with a free barcode generator, it lets the warehouse match a parcel in one scan.

Who reviews: the team sets postage rules once, per market and reason. Faulty and wrong-item returns shouldn't cost the customer.

5. Receiving and inspection

Trigger: the carrier scans the parcel back, or the warehouse or 3PL records it.

Action: the record updates, the customer gets a "we've got it" message, and the refund clock starts where the law ties it to receipt. The inspector records condition: unused, used, damaged, missing parts, wrong item.

Who reviews: the inspector, always. A person decides whether an item was handled more than necessary, which is what justifies a deduction in the EU and UK.

6. Refund decision and release

Action: a refund is prepared to the original payment method, including standard delivery costs where required. Clean change-of-mind returns can be released automatically under agreed rules; everything else waits for approval, with alerts before deadlines.

Who reviews: a team lead approves partial refunds, deductions, exchanges, store credit and goodwill. Store credit should never replace a refund the customer is legally owed.

7. Exceptions and closing the loop

Action: lost return parcels, disputed faults and carrier damage claims go to an exceptions queue with full history. An image to PDF tool bundles customer and inspection photos into one evidence file for a carrier claim. Reasons are tagged by product so buyers see patterns.

Who reviews: a named owner, checking daily.

Summary table: who does what

Stage	What is automated	Who checks	Systems
Request	Order matching, reason capture	Agent for unmatched requests	Returns portal, store orders
Classification	Sorting by reason, urgent flags	Agent for unclear cases	Help desk, AI with rules
Eligibility	Window, market rules, exclusions	Agent for faults, late requests	Store data, tracking
Label	Label and authorisation number	Rules set by team	Carrier label service
Receiving	Customer notice, refund clock	Inspector	Warehouse or 3PL
Refund	Refund prepared, deadline alerts	Approval if non-standard	Payment provider
Exceptions	Queue, evidence packs	Named owner	Help desk

What stays human

As our page on automation for online retailers sets out, some decisions stay with people:

Faulty-goods claims: whether something is faulty, how serious the failure is, and which remedy applies.
Deductions and restocking fees.
Goodwill refunds outside policy.
Fraud and chargebacks: suspected wardrobing or empty-box returns need a person reviewing evidence, and the customer should be able to explain.
Complaints and vulnerable customers, who should reach a person quickly.
Policy wording for each market.

Automated messages should make it easy to reach a human. A bot that confidently refuses a faulty-goods claim creates legal risk and a lost customer.

Data protection and legal checks before going live

Returns collect personal data: addresses, payment references, photos that may show a customer's home, sometimes health details ("caused a rash"). Before you connect systems:

Know which privacy laws apply. The GDPR in the EU and UK GDPR, the CCPA for California residents and other US state laws, PIPEDA in Canada and the Privacy Act in Australia each set rules on purpose, security and retention.
Have a contract with every processor: returns app, help desk, AI provider, 3PL.
Collect only what you need. Ask for photos only when a fault is claimed, and set retention periods.
Keep marketing out of service messages. Adding promotions to return confirmations can bring rules such as CAN-SPAM, PECR or CASL into play.
Make sure the emails arrive. A refund confirmation in spam becomes a "where's my money?" ticket. Test your domain with the email deliverability checker and see our guide to Gmail, Yahoo and Microsoft sender requirements.
Write the rules down per market, get them checked, and log changes.

How to start small and measure

Don't automate the whole chain at once:

Map your current process, from request to refund, including where it waits.
Add a deadline tracker first. Recording delivery and receipt dates and alerting before refund deadlines is low risk.
Introduce a portal for change-of-mind returns in your main market only.
Connect receiving to customer messages.
Add markets and automatic refund release once the rules are reviewed and the data proves reliable.

Measure qualitatively: are refunds on time, are customers chasing less, do agents trust the classification, are return reasons visible by product? Review a sample of automated decisions weekly at first.

Make It Flow maps how returns actually move through your store, help desk and warehouse before suggesting any automation, and designs the review points with your team. For help with your own returns process, talk to us.

FAQ

How long do customers have to return online orders?

It depends on where the customer is. In the EU and UK, most online purchases can be cancelled within 14 days of delivery without a reason, with exceptions such as personalised goods. In the US, Canada and Australia there is generally no automatic change-of-mind right for online shopping, so your own policy sets the window, but faulty goods carry separate rights everywhere.

When must an online store issue a refund?

In the UK, refunds for cancelled online orders are due within 14 days of receiving the item back. EU rules require refunds within 14 days of being told about the withdrawal, though you can wait until the goods or proof of return arrive. In the US, the FTC's Mail Order Rule sets refund deadlines when an order is cancelled because it can't ship on time.

Can refunds be fully automated?

Parts can. Many stores release refunds automatically for clean change-of-mind returns once the warehouse confirms receipt and condition. Faulty-goods claims, deductions, partial refunds, store credit and goodwill should be approved by a person, because they involve judgement and legal rights. Deadline alerts protect you while approvals wait.

Can I charge a restocking fee on returns?

In the EU and UK you generally can't deduct fees from a cancellation refund unless the item was handled more than necessary or damaged, and the deduction should reflect that. In the US, Canada and Australia, restocking fees are mostly a matter of your disclosed policy and local rules. Never apply one to faulty goods, and let a person decide each deduction.

Do I have to accept returns of faulty items after my return window ends?

Usually yes. Rights for faulty goods outlast returns windows: the EU has a minimum two-year legal guarantee, the UK has Consumer Rights Act remedies, and Australia's consumer guarantees can't be excluded. That is why a returns workflow should route out-of-window fault claims to a person instead of rejecting them automatically.

What should a returns portal ask the customer?

Keep it short: order number and email, which items, the reason (change of mind, faulty, damaged, wrong item), condition and, only for faults or damage, photos. Ask for the preferred outcome where your policy allows a choice. Structured reasons make eligibility checks reliable and turn return data into product feedback.

Returns and Refunds Workflow for Online Stores: What to Automate and What to Keep Human

Why returns workflows break

The legal rules your returns workflow has to respect