What Is a Returns Disposition Workflow and Why It Affects Inventory Trust

A returns coordinator at a $15M contemporary brand opens Monday with 312 returned units stacked on three pallets in the receiving zone. About 90 came back through the 3PL, 140 through the brand’s own warehouse from DTC, and the rest from a wholesale account that shipped a chargeback-laden return authorization on Friday afternoon. Each unit needs a decision: back to sellable, send to the repair vendor, route to the outlet bin, or write off. There is a spreadsheet from the last person who held this role. There is a Slack thread. There is no system that tells the order desk which of those 312 units it can sell tonight. By Wednesday, customer service has oversold a dress that was sitting on pallet two the whole time.

What is a returns disposition workflow in apparel operations?

A returns disposition workflow apparel teams can actually run is the codified, repeatable decision path that every returned unit follows from the moment a carrier scan hits the WMS to the moment that unit is either back in available-to-sell, in a repair queue, in an outlet pool, or written off the books. The workflow has four moving parts: a trigger (return received, RMA matched), a grading step (condition assessment against SKU-specific criteria), a disposition decision (one of a finite set of codes), and a posting event that updates inventory, finance, and the customer record in the same pass.

Most brands in the $5M to $100M band have something they would call a returns process. Very few have a disposition workflow in the sense above. The difference matters because disposition is where physical reality reconnects with the inventory ledger. If that reconnection is slow, manual, or inconsistent, BP5 of the 6 Breakpoints framework, warehouse execution becoming less predictable, shows up as oversell, mis-promised ship dates, and a reporting layer that no one trusts.

Why does returns disposition affect inventory trust more than receiving does?

Receiving against a PO is structured. The PO tells the warehouse exactly what to expect, the ASN narrows it further, and the variance is a clean exception. Returns are the opposite. The unit shows up with a label, sometimes the right one, often the wrong size noted in the customer’s RMA, sometimes with damage that was not declared. The default state is ambiguity.

What I see consistently in the first 30 days after a customer goes live is that the returns lane is the single largest source of inventory drift, and it is almost always invisible on the org chart. The receiving team owns it operationally but has no authority to grade. The merchandising team owns the call on what goes to outlet but is not in the warehouse. The finance team owns write-offs but learns about them at quarter close. Each handoff adds days. Each day of delay is a unit that is physically in the building but not in available-to-sell, which means the brand is either overselling it or under-promising on a different SKU to be safe.

For a $15M brand running wholesale + DTC + 3PL, this is part of the 6 to 9 hours per week that gets spent reconciling inventory across Shopify, the 3PL, and wholesale. Returns disposition is not the whole reconciliation problem, but in our experience it is the largest single contributor inside the warehouse breakpoint, and it is the one that compounds because returned inventory that sits in limbo eventually gets miscounted, then miscycled, then quietly written off without a disposition decision at all.

What does a defensible disposition workflow actually look like?

The shape is consistent across brands that get this right. Five disposition codes, no more. A grading rubric per product class, not per SKU, because SKU-level rubrics never get maintained. An SLA expressed in days from receipt to posting. And a single system of record where the disposition decision posts to inventory, finance, and the customer record in one event.

The five codes that hold up in practice:

• A1, return to sellable. Unit is in original condition, original tags, original poly bag if applicable. Posts to ATS within 48 hours of receipt.
• A2, return to sellable after light refurb. Needs a steam, a re-tag, or a re-bag. Posts to ATS within 5 business days.
• B, route to outlet or sample pool. Unit is sellable but not at full price. Posts to a separate location code, never reappears in full-price ATS.
• C, route to repair vendor. Unit has a known defect that is economical to repair. Posts to a work-in-process bucket with an expected return date.
• D, write off. Unit is unsellable. Posts as a loss with a reason code that rolls into the monthly quality review.

The specificity matters. A workflow that says “inspect and decide” is not a workflow. A workflow that says “if seams intact, tags present, no fabric pulls visible at arm’s length under warehouse lighting, code A1” is a workflow. The grading criteria should be printable, lamination-grade, and posted at the grading station.

Why do most returns workflows stall after 90 days?

What stalled rollouts have in common, in my experience, is that the disposition codes were designed by the merchandising or finance team without the warehouse team in the room. The codes look clean on paper. They map to GL accounts. They make the season-end report tidy. They are also impossible to execute at the grading bench because the criteria require judgment calls that the grading associate is not paid to make and not trained to make consistently.

The other stall pattern is SLA drift. Brands set an SLA of three business days from receipt to disposition, then quietly stop measuring it after the first quarter. By month nine the average is twelve days. By month twelve, returns are a pallet problem instead of a workflow problem. Returns should post to inventory in days, not weeks. If you cannot post a unit’s disposition within five business days of receipt, the workflow is broken regardless of what the SOP document says.

A third stall pattern, specific to brands running both DTC and wholesale, is that the two return streams get treated as one queue. They are not the same queue. A wholesale return often arrives with a chargeback attached, a packing slip that does not match what is in the carton, and a timeline tied to the retailer’s vendor agreement. A DTC return arrives with a customer expecting a refund within a fixed window. The grading is similar; the downstream posting is not. Mixing the queues guarantees that one of the two clocks gets missed.

How does this connect to BP5 and the 3PL blind spot?

BP5 in the 6 Breakpoints framework is warehouse execution becoming less predictable, and it is where the 3PL blind spot lives. The blind spot is not that the 3PL is bad at their job. It is that the brand cannot see what the 3PL is doing in enough detail to act on it. Returns disposition is the most acute version of this.

When a 3PL handles returns, the brand typically receives a daily or weekly file that lists units received and units put away. What is usually missing: the disposition code, the grading reason, the time from receipt to posting, and the location code the unit landed in. Without those four fields, the brand has no way to know whether the 3PL is grading consistently, whether B-grade units are leaking back into full-price ATS, or whether write-offs are being applied to units that should have gone to outlet.

Magnolia Pearl runs drops, same-day fulfillment, and global returns, including international units that come back with duty implications. The disposition workflow there has to handle currency, customs, and the question of whether a unit is economically worth returning to US ATS versus liquidating in-region. Their reconciliation time was cut roughly two-thirds and oversell rate held under 0.5 percent through peak. The disposition workflow was a material part of that, because every returned unit that posts cleanly is a unit that does not need to be reconciled by hand on a Friday afternoon.

What is the right sequence to fix a broken returns workflow?

The sequence matters more than the tooling. Brands that try to buy their way out of this with a returns app before fixing the workflow end up with a faster version of the same chaos.

1. Audit the current state. Pull the last 90 days of returns. Count how many ended up in each disposition (even if the categories are informal). Measure the median days from receipt to inventory posting. If you cannot answer that question from data, the audit is the first deliverable.
2. Lock the five codes. Resist the urge to have eleven. The grading team will not maintain eleven.
3. Write the grading rubric per product class. Get the warehouse lead to sign off before merchandising or finance touches it.
4. Set the SLAs by code. A1 within 48 hours, A2 within 5 business days, B and C within 5 business days, D within 10 business days with a finance review attached.
5. Wire the posting event. The disposition decision should update inventory ATS, the location code, and the finance ledger in one transaction. If three systems are involved and the data flows in three different jobs, the workflow will drift.
6. Measure weekly. Median days to post, percent of returns by code, percent of B-grade units that show up in full-price ATS by mistake. Those three numbers tell you whether the workflow is healthy.

The right tooling is whatever runs orders, warehouse execution, and inventory in the same connected system. The wrong tooling is a returns app that bolts onto a stack of disconnected tools and adds a fourth place for inventory to disagree with itself.

What this means for an apparel operations team

Returns disposition is not a back-office hygiene problem. It is the single most leveraged workflow for inventory trust in the warehouse, and it is the one most often left to tribal knowledge. A brand at $15M that fixes this workflow recovers a meaningful share of the 6 to 9 hours per week currently spent on reconciliation, and it stops the slow leak of B-grade units showing up in full-price ATS and getting oversold or, worse, sold at full price and returned again.

The operational stance is straightforward. Five disposition codes. Printed grading criteria at the bench. SLAs in days, measured weekly. A single posting event that updates inventory and finance together. Separate queues for DTC and wholesale returns because the downstream clocks are different.

If the disposition workflow lives in a spreadsheet and a Slack thread, the inventory ledger is lying to the order desk every day. Fixing the workflow is cheaper than buying another tool to paper over it, and it is the prerequisite for any conversation about returns automation, customer-facing return portals, or 3PL scorecards. Get the workflow right first, then make it faster.