Skip to content
All guides

Returns recovery and disposition

What should my warehouse record on each return, and nothing else?

Record each returned unit, not the parcel: the order line, the SKU, when it arrived, one condition code and the route. Add notes and photos only for exceptions.

6 November 2026 · 3 min read · Taimoor ul Hassan, founder, WeaveCycle

Record each returned unit, not the parcel, and keep the default record to five fields: the order or return line reference, the SKU or variant, the time it arrived, one condition code from a fixed list, and the route it takes. Pull customer and order details from the order system rather than retyping them. Add notes and photos only for exceptions. The field that matters most is the route tied to a repeatable condition code, because that is the decision the business will audit later.

Record the unit, not the parcel

A parcel can hold different outcomes. The T-shirt is clean. The dress has deodorant marks. The shoes are in the wrong box. A parcel status cannot carry that. Record at the item level, because the business needs to know which item goes back to stock, which needs work, and which leaves the main resale path.

Parcel-level receipt also breaks on partial returns: an order can come back in several boxes, or with items missing. Record what is in your hand.

The minimum record

In the normal flow, record only:

  • the order or return line reference
  • the SKU or variant
  • the time it arrived
  • the condition code
  • the route

Each has a job. The reference ties the item to the order. The SKU says what should be in hand. The timestamp shows when it came under your control, which also matters for refund deadlines. The condition code says what the inspector saw. The route says what happens next.

Everything else has to earn its place. Customer name, shipping method and payment details already live in the order system. If the warehouse does not use a field to decide, route, audit or defend a claim, it should not be in the default scan flow.

Condition code before customer reason

Record what the inspector can observe. Do not retype what the customer said.

A slip may say "too small" when the item arrives with a broken zip. The warehouse can see the zip. It cannot verify the fit. The same goes for marks, odour, washing, missing tags, wrong items, worn soles and missing parts.

The customer's reason still matters for service, policy and merchandising. Join it from the order system later. If the inspection field mixes the stated reason with the observed condition, the data stops being consistent.

The route is what makes the record useful

A condition only becomes a decision when the record also says where the item goes: back to stock, rework, resale, supplier claim, recycling or, in documented cases, disposal. Keep it as its own field, even when it usually follows from the condition. That is what you review for claims, supplier chargebacks and recovered value. You review decisions, not adjectives.

It is also what you will need if the EU destruction ban applies to you: a record of what was disposed of and why. See the EU ban on destroying returned clothes.

What to leave out

  • packaging trivia, unless it affects a claim or a resale route
  • a second copy of the customer's reason
  • overlapping quality grades
  • a free-text box by default
  • a photo by default

With only a notes box, the same condition gets written as "fine", "ok", "good" and "new". That trains nobody, routes nothing and does not stand up in an audit.

Notes and photos for exceptions only

Use them when the decision needs evidence: contamination, damage disputes, missing parts, supplier claims, a wrong item, or a condition that does not fit the list. For standard items, skip them. See do you need photos for every returned garment?

Keep the code list short and stable

Each code should describe something a person can see at the bench, with an example next to it. "Unworn, tags attached" works. "Good" does not. "Deodorant marks" works. "Light wear" is too loose if inspectors read it differently.

Do not let every supervisor add local synonyms. A short, stable list tied to a clear routing matrix keeps decisions repeatable. See the condition grading checklist.

The test: a supervisor should be able to look at the item, its code and its route, and understand why it went where it went.

The same record in WeaveCycle

WeaveCycle keeps one record per returned item with its grade, the route chosen, who chose it and when, and the photo check if there was one. Order and customer details come from Shopify, so nobody retypes them. See how it works.

Related reading

WeaveCycle checks return photos before the package is back and gives every returned item a route your policy allows. See how it works.

Early access

Run this workflow on your own returns.

Starter is free with 10 returns a month, each with a photo check.

Install free on Shopify

Early access: we're recruiting pilot brands.

Ask a question first

Analytics choice

We use PostHog analytics to understand how the public site is used, only if you accept. Sign-in still works if you decline. Read the Privacy Policy.