E-Commerce Returns Reduction

Returns management for e-commerce: read the reason, work the exception, stop the next one.

Return reasons can inform the next recommendation, product description, or sizing decision. We help group those reasons, apply your disposition rules, and surface fit issues for your team to review.

  • AI implementation services
  • Return reasons read at scale
  • Your disposition rules, encoded
  • Fit signal moved upstream

Built with the leading AI platforms

NVIDIAAnthropic
Peter Enestrom, founder of Zaigo

Led by Peter Enestrom and the Zaigo AI & engineering team

YaleColumbia UniversityMicrosoft

The board metric

Returns management is a board-level priority with an inbox for a system.

From a standing AI program with a luxury fashion e-commerce retailer: the board named returns the number one opportunity, and the actual system was a queue of reason codes nobody had time to read.

  • “Mitigating returns is our number one opportunity.”

    The board has said it plainly. Meanwhile the working system is a returns queue and good intentions — the AI that could read it all hasn’t been built yet, so the priority sits above a manual process.

  • Every return carries a reason nobody reads

    Reason codes, return-form notes, support threads, stylist feedback — thousands of signals about fit, fabric, and expectation. Individually they’re anecdotes; at scale they’re the answer. No one has the hours to read them all.

  • The 48-hour window slips

    The team’s own rule is follow-up within 48 hours of a return. The queue doesn’t know the rule — so the clients with the most at stake wait in line behind routine refunds, and the window closes quietly.

  • The recovery email re-shows the returned item

    Recover-return outreach should offer the next size down or a similar piece in the client’s palette. Re-showing the item she just sent back isn’t recovery — it’s a second miss, from the brand that’s supposed to know her.

  • The designers don’t conform to standard size scales

    A UK 10, a French 34, an Italian 38 — the same fit across three national conventions, and many designers don’t conform to standard size-scale conventions at all. The conversion lives in stylists’ heads, not in the store.

  • The sale dies at the doorstep

    “Clients will just not even take it out of the packaging.” The delivery window is the last chance to secure the sale from the point of delivery — and nothing watches it.

What the manual way costs

The recover-return window closes in 48 hours.

What it looks like when returns management runs on a queue instead of encoded rules. Your numbers will differ — the first thing we build puts figures on yours.

48 hoursThe follow-up window the client-experience team holds itself to after a return lands — and the one a manual queue keeps missing
3 size scalesUK 10, French 34, Italian 38 — the same fit, converted by hand because many designers don’t conform to standard size-scale conventions
$10,000The cart value that earns prioritization — “prioritization should go to carts over $10,000” — while high-value returns wait behind routine ones

From an anonymized engagement — a luxury fashion e-commerce retailer with ~12,500 client profiles under management

How it works

Read the reasons, encode the rules, move the fit finder signal upstream.

We build the AI that does the reading and the routing, on your book of business and your rules. Three steps, fixed order.

  1. 01

    Read every return reason

    The AI reads reason codes, return-form notes, support threads, and stylist feedback across the whole book — 12,500 client profiles, not a weekly sample — and turns them into a reasons report the ops team can actually act on.

    Weeks 1–2
  2. 02

    Encode your disposition rules

    The 48-hour follow-up. Recover-return outreach that offers the next size down or a similar item in the client’s palette — never the returned item. Prioritization for carts over $10,000 and fine jewelry, average unit retail thresholds, the lot. Your rules, not a vendor’s defaults.

    Your rules, encoded
  3. 03

    Catch the fit signal before the next shipment

    Kept-size history — “the most consistently purchased and kept size” — feeds size guidance upstream, across designers that don’t share a size scale. The wrong size stops shipping; the return never happens.

    Upstream of the return
The tool isn’t the judgment

Returns management software sorts the queue. It doesn’t decide.

Returns management software is good at the mechanics — RMAs, labels, refund routing, status emails. What it doesn’t do is decide: which client gets a call instead of a credit, what to offer when the size was wrong, when to stop pushing and let a return go. Those are your rules, and they live in your team’s heads.

We’re an AI operating partner — we build and run the machine that reads the reasons and applies your rules, on top of whatever returns software you already have. How to reduce returns in ecommerce isn’t another dashboard; it’s the 48-hour follow-up that actually goes out and the fit signal that reaches the product page before the next order ships.

Peter Enestrom, founder of Zaigo
Who builds it

Led by Peter Enestrom.

Co-Founder — leads AI & Engineering

Pete Enestrom

Every engagement is led personally by Pete, working with the Zaigo AI & engineering team from the two-week audit through the production handover. The person who scopes the work is the person who builds it.

Education
Yale & ColumbiaGraduate
Background
Microsoft & IntelFormer
Experience
Exited FounderVenture-Backed

Background

Questions

How to reduce returns in ecommerce, answered straight.

What e-commerce operators and CFOs ask before anything ships.

What’s holding your business back?

A workflow ready for automation. An AI product you want to build. A problem that has sat on the roadmap for years. Let’s talk about what it would take to solve it.

Talk to Zaigo