E-commerce Return Request Automation
Returns are one of those things that look small until you’re the one handling them. Every request needs checking against the policy, instructions, tracking, and then a refund or replacement at the end.
01 · Why it mattered
What the manual way was costing
- Policy was applied differently depending on who handled the request.
- Requests could get lost between the first message and the refund.
- Customers had no idea where their return was.
02 · System concept
What I set out to build
Check eligibility first, record everything, send clear instructions, track it, then finish with a refund or replacement. Anything that doesn’t fit the rules goes to a person.
03 · Before / after
From manual steps to a system
Toggle between the manual process and the system. Click any step to see what it does, what tools it touches, and what happens if it goes wrong.
How it ran manually · depends on whoever is free
- 01Customer sends a return request by message or emailby hand
- 02Someone checks the order and the return policy by handby hand
- 03Instructions are typed out each timeby hand
- 04Return shipment is tracked loosely, if at allby hand
- 05Refund or replacement waits on someone rememberingby hand
04 · Decision log
Why I built it this way
D-01Invalid doesn’t mean auto-reject
I didn’t want the system rejecting customers on its own. If a request fails the rules, a person reviews it. The automation handles the clear cases, people handle the judgement calls.
D-02Test the scenarios, not just the happy path
I ran it through different scenarios (eligible, outside the window, unmatched orders) because a returns flow that only works for perfect requests isn’t really working.
05 · Reliability layer
What can go wrong, and who steps in
- Where it happens
- Step 02 Eligibility check
- What goes wrong
- Request doesn’t meet the policy
- What the system does
- Instead of auto-rejecting, it goes to manual review so a person makes the call.
- Who handles it
- A person: support team
Human-in-the-loop points
- Human in the loopRequest doesn’t meet the policy → support team
- Human in the loopOrder can’t be matched → support team
- Human in the loopReturn not received after a while → support team
06 · Evidence
What exists today
- Built in n8n and tested against different return scenarios, including valid, invalid and manual-review cases.
07 · What this demonstrates
What this demonstrates
Turning a policy into consistent logic while keeping humans in charge of the exceptions.
08 · Stack / integrations
What it’s built with
- n8nWorkflow logic, eligibility and routing
- Data storeReturn records
- NotificationsCustomer instructions and updates
- → support teamOrder can’t be matched
- → support teamRequest doesn’t meet the policy
- → support teamReturn not received after a while
More systems
Keep reading
E-commerce Order-to-Delivery Automation
Every order gets one record that follows it from fulfilment to rider to doorstep, and the customer hears what is happening without having to ask.
- New order
- Order record created
- Fulfilment
- Rider assigned
- Delivery update
- +1 more
Dental Patient Reactivation System
Patients who are overdue for a visit get a personal follow-up with a booking link, and the clinic can see who booked from one Airtable view.
- Identify overdue patients
- Personalised follow-up
- Booking link
- Booking tracked
- Clinic sees results
Similar workflow?
Got a process that looks something like this?
Tell me how it runs today and where it hurts. If it’s a good fit for automation I’ll tell you how I’d approach it. If it isn’t, I’ll tell you that too.
Tell me what you’re trying to automateOr reach me directly