Fixed quote after a free call

Ecommerce returns management that applies the right rule every time

Returns are where policy, law and money meet, and doing them by hand means inconsistent decisions and slow refunds. We build a workflow that reads each request, checks the delivery date and item against your policy and the customer's market, issues a label for eligible change-of-mind returns, routes faulty or unusual cases to an agent, and prepares the refund when the warehouse confirms receipt. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why ecommerce returns management breaks at scale

A return request looks simple until you check it: was it delivered within the window, is the item excluded (personalized, perishable, hygiene-sealed), is it change of mind or faulty, and which country is the customer in? Each answer changes what the store must do.

The rules really do differ. Consumers in the EU have 14 days to withdraw from most online purchases, counted from delivery, and the UK Consumer Contracts Regulations set a 14-day cancellation period from when the goods reach the consumer. Marketplaces add their own policies on top, and peak season multiplies the volume.

What we build

What our ecommerce returns software build includes

Returns intake

Requests from your returns portal, help desk or a simple form, matched to the order and delivery date.

Policy engine

Your returns policy plus market rules (window, exclusions, who pays return postage) encoded as reviewed rules.

Labels and instructions

Eligible change-of-mind returns receive a label and packing instructions automatically.

Faulty and damaged routing

Photos requested and the case sent to an agent; faulty goods are never auto-declined.

Receipt-triggered refunds

When the warehouse or 3PL marks the item received, the refund or exchange is prepared for release under agreed rules.

Return reason reporting

Monthly reasons by product and size, so buyers can fix sizing guides and listings.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Request submitted

    The customer starts a return in the portal, by email or chat.

  2. 02 Automated

    Eligibility checked

    Delivery date, item type, reason and market rules are checked against your policy.

  3. 03 Automated

    Label or route

    Eligible returns get a label; faulty, excluded or unusual cases go to an agent.

  4. 04 Team review

    Receipt and inspection

    The warehouse confirms receipt and condition; agents handle disputes.

  5. 05 Founder or ops lead decides

    Refund exceptions

    Deductions, goodwill refunds and anything outside policy are decided by the ops lead.

How it behaves

How Shopify returns automation behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A clear yes, no or "we need a photo" within minutes
  • A label and instructions for eligible returns
  • A refund confirmation when the item is received

What the team sees

  • Only faulty, excluded and unusual returns in the queue
  • Refunds ready to release with order and receipt details
  • Monthly return reasons by product

What the automation does

  • Checks dates, items and market rules
  • Issues labels and watches warehouse receipts
  • Logs every decision with the rule that made it

Edge cases and fallbacks

Delivery date missing from tracking
Order date plus typical transit is used only to flag; an agent decides.
Item outside the window by a day or two
Routed to an agent for a goodwill decision instead of an automatic decline.
Marketplace order returned to the brand
Handled under the marketplace's own policy and flagged separately.
Warehouse marks item damaged on receipt
Refund held and the case sent to an agent with photos.
Returns platform or store API down
Requests are queued and the ops lead is alerted; nothing is declined during an outage.

Architecture

Returns and refunds for an online store at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Return request Portal or email n8n workflow Order and dates Policy rules By market, by item Label sent Eligible returns Agent review Faulty or unusual Warehouse receipt 3PL or own stock Refund prepared Store or payments
  • Input
  • Logic and services
  • AI step
  • Output
  • People
  • Data

How it flows

  1. 1 A customer requests a return through the portal, email or chat.
  2. 2 n8n reads the order and delivery date, then applies your policy and the customer's market rules.
  3. 3 Eligible returns get a label straight away; faulty, excluded or unusual cases go to an agent.
  4. 4 When the warehouse confirms receipt, the refund or exchange is prepared for release.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Returns management & refund automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current policy, markets, excluded items, returns platform, warehouse process and refund approvals.

  2. 02

    Design

    2 to 3 days

    Rules per market reviewed by you (and your counsel where needed), routing and refund release rules.

  3. 03

    Build

    1 to 2 weeks

    Intake, policy engine, label service, warehouse trigger and reporting.

  4. 04

    Shadow run

    About 1 week

    Decisions are suggested only while agents compare with their own call on each return.

  5. 05

    Launch

    1 to 2 days

    Switch on for change-of-mind returns first.

  6. 06

    Support

    Ongoing

    Policy updates, new markets and peak-season tuning.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Shopify Admin API returns (returnRequest, returnApproveRequest) Loop Returns API and webhooks ShipStation or carrier label APIs WooCommerce REST API refunds Gorgias or Zendesk

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Policy review, market rules and refund approvals.

    $200 – $400

  • Build

    Intake, eligibility engine, routing and refund preparation.

    $500 – $1,300

  • Integrations

    Store, returns platform, labels and warehouse.

    $150 – $400

  • Testing and shadow run

    Suggest-only run against real returns.

    $100 – $250

  • Launch and training

    Staged switch-on and run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Returns platform, label and n8n costs are billed to you directly. Exchanges with inventory reservation may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Returns platform: Loop or your returns app's own plan, if used.
  • Return labels: Billed by your carrier or shipping platform at your negotiated rates.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: 14-day withdrawal right

Most online purchases can be cancelled within 14 days of delivery without a reason; exceptions include personalized goods, rapidly perishable goods and unsealed audio, video or software.

Source: europa.eu

UK: Consumer Contracts Regulations

For sales contracts the cancellation period ends 14 days after the goods come into the consumer's physical possession.

Source: www.legislation.gov.uk

US: refunds for orders not shipped

Under the FTC Mail Order Rule, cancelled unshipped orders must be refunded promptly and cannot be replaced with store credit.

Source: www.ftc.gov

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Returns management & refund automation questions, answered.

It is the system that takes return requests, decides eligibility, issues labels and triggers refunds or exchanges. Platforms such as Loop handle much of this for Shopify; we connect them to your help desk, warehouse and accounts and add the rules they do not cover.

Usually not. Shopify's own returns flow and dedicated returns apps work well for intake. We automate around them: eligibility rules, routing, warehouse triggers and refunds through the Shopify Admin API return mutations.

Yes. Each market gets its own window and exclusions, reviewed by you before launch. We encode the rules you approve and do not give legal advice on what they should be.

Only within rules you set, typically eligible change-of-mind returns confirmed received in good condition. Deductions, faulty goods and goodwill refunds always go to a person.

It flags patterns such as repeated returns, mismatched items or empty-box claims for an agent to review. It never accuses a customer or blocks them automatically.

Return rate by product and reason, time from request to refund, share of returns handled without an agent, and refunds released outside policy.

Free 20-minute call

Want this for your e-commerce brand?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call