The volume problem is not going away.
In January 2026, an estimated £1.55 billion worth of goods bought during the November–December 2025 peak returned to UK retailers in the opening weeks of the year. The industry calls it Returnuary. For the warehouses processing those returns, it is five to six weeks of sustained operational pressure arriving immediately after the most demanding outbound period of the year.
But peak is only the most visible part of the problem. Ecommerce return rates run at 20–30% year-round across most product categories. In apparel, that figure is higher. For a warehouse processing 1,000 outbound orders a day, that means 200–300 items coming back through the doors daily — every day, not just in January.
Why Ecommerce Returns Are Operationally Different
Ecommerce returns are structurally different from retail returns, and the operational setup needs to reflect that.
In a physical store, a return arrives in person, is inspected on the spot, and is either put back on the shelf or flagged for disposal. The whole interaction takes minutes. In an ecommerce environment, a return travels by courier, arrives at a warehouse dock with varying levels of pre-notification, may be in damaged or inadequate packaging, and needs to pass through a multi-stage process before it can be restocked or written off.
Three characteristics make ecommerce returns particularly challenging to manage at scale:
Volume unpredictability. Returns do not arrive in a steady stream. They cluster — after peak trading periods, after a promotional push, after a product quality issue surfaces. A warehouse that can handle 200 returns a day cleanly may struggle badly when that spikes to 600 for three weeks.
SKU variety. An ecommerce operation returns items across the full product range, often in mixed condition, with mixed packaging. There is no pre-sorting before they hit your dock. The sortation work happens in your building.
Speed expectations. Customers expect refunds and exchanges to be processed within 48–72 hours. That means returned items cannot sit in a processing queue for days. The moment a return arrives, the clock is running.
The Real Cost of Poor Returns Management
Returns management is consistently undercosted. Most operations track carrier fees and labour time. Few track the full picture.
The actual cost of processing an ecommerce return typically includes:
- Inbound carrier cost
- Goods-in logging and administration time
- Triage and condition assessment labour
- Repackaging materials and labour (where applicable)
- Return-to-stock time and WMS update
- Lost margin on items that cannot be restocked
- Customer service cost associated with refund or exchange queries
Research consistently shows that brands underestimate their true cost per return by 20–40%, because the hidden costs — particularly repackaging labour and the delay cost on resaleable stock — are not attributed back to the returns operation.
The delay cost is worth dwelling on. A resaleable returned item that takes five days to process is an item that could have been sold again on day two. In a high-SKU ecommerce operation with tight stock levels, that is not a minor inefficiency. It is a directly measurable revenue impact.
“We’ve spoken with ecommerce operations managers who’ve done a rough cost-per-return calculation and come up with a number like £2.50. When we’ve worked through it properly with them — adding in the repackaging time, the WMS update, the customer service queries chasing the refund, and the stock that didn’t get relisted for four days — the real figure is closer to £6–8. That gap between perceived and actual cost is why returns infrastructure investment is chronically underfunded.”
Setting Up a Returns Processing Area That Can Handle Ecommerce Volume
The most common reason ecommerce returns processing slows down is not a process failure. It is a physical infrastructure failure. The processing area was designed for a lower volume, or was never properly designed at all.
What Goes Wrong
Returns areas in ecommerce warehouses tend to fail in one of three ways:
The staging problem. Everything arrives on a flat bench or open shelf. There are no defined bin locations for triage grades, so items pile up in mixed condition. Staff spend time sorting through the pile to find what they are looking for rather than processing in a clear sequence.
The capacity problem. During normal trading, the returns area is manageable. During peak — Returnuary, post-Black Friday, post-summer-sale — volume triples and the same space is expected to absorb it. It cannot, so a backlog forms and processing times blow out.
The reconfiguration problem. The product mix changes — a new category is added, a client changes their SKU range, a product line is discontinued — and the storage layout cannot adapt quickly. Staff workaround the layout rather than working with it, which creates inconsistency and errors.
What a High-Performing Returns Area Looks Like
Clear triage zones with bin-level storage. Every triage grade (resaleable, repackage required, refurbishment, write-off) has a dedicated, labelled bin location. Items are placed immediately on receipt into the correct grade location. There is no intermediate staging pile.
Storage that can absorb volume spikes. The configuration for peak trading periods should be different from everyday configuration. That requires a storage system that can be expanded, contracted, or reconfigured quickly — without specialist labour or significant downtime.
Product-matched apertures. Ecommerce SKU ranges are typically wide. Small accessories, mid-sized apparel, large boxed goods — these all need different bin sizes within the same processing area. Fixed racking with uniform apertures creates dead space and mismatched locations.
Visual management built in. Staff should be able to see at a glance which bins are full, which grades are backing up, and where stock needs to be cleared. This is not a technology question — it is a layout and labelling question.
The PALLITE PIX storage system is designed for exactly this environment. The modular bin structure can be configured to any aperture size, reconfigured without tools, and expanded or contracted to match seasonal volume requirements. It is used by ecommerce warehouses and 3PLs specifically in returns processing contexts because of that flexibility.
The Ecommerce Returns Process: Stage by Stage
Stage 1: Pre-Notification and RMA
The returns process should begin before the item arrives at your dock. A Return Merchandise Authorisation (RMA) system — whether built into your ecommerce platform or managed separately — creates a record for each return at the point the customer initiates it.
That record contains the order number, the item, the stated return reason, and the expected arrival window. With that data, your receiving team knows what is coming before it arrives, which means routing decisions can begin before goods hit the goods-in area.
Operations that start the process at goods-in, with no pre-notification, add unnecessary time to every single return they process.
Stage 2: Goods-In and Logging
On arrival, each return needs to be logged against its RMA record immediately. Batch processing — holding returns until the end of the day and logging them together — creates inventory inaccuracies and delays restocking.
The goods-in area for returns should be physically separate from outbound goods. Mixing inbound returns with outbound pick-and-pack creates contamination risk and slows both processes.
Stage 3: Triage and Grading
Triage is where the processing time is won or lost. Each item needs a rapid condition assessment and immediate placement into the appropriate grade location.
A standard four-grade system works for most ecommerce operations:
| Grade | Condition | Next Step |
| A | Resaleable as-is | Return to primary stock location |
| B | Minor damage or repackaging required | Repackaging workstation |
| C | Requires refurbishment or repair | Refurbishment area or third party |
| D | Not resaleable | Disposal, recycling, or liquidation |
The speed of triage is directly linked to the clarity and accessibility of the storage at that stage. When each grade has a defined, clearly labelled bin location, the triage decision and the physical action happen simultaneously. When staff have to find a place to put something, or make a decision about which pile it belongs to, you lose time on every single item.
Stage 4: Restocking and Inventory Update
Grade A returns need to be back in primary stock locations as fast as possible. This is the highest-value outcome in the returns process — a resaleable item that is restocked within 24 hours is available to sell again the next day.
Two things slow this stage down in practice. The first is the WMS update — return-to-stock processes that skip proper system updates will produce pick errors downstream. Every return going back into stock needs its location updated in the warehouse management system before it is picked again.
The second is FIFO discipline. For operations managing date-sensitive or season-sensitive stock, returned items need to enter the pick sequence at the correct position. A returned winter coat coming back in November should not end up at the front of the location ahead of stock that arrived last week. The PIX FIFO configuration handles this by physically enforcing first-in, first-out stock rotation at the bin level.
Stage 5: Non-Resaleable Processing and Clearance
Grade C and D stock needs a scheduled clearance cadence. Returns areas that accumulate unprocessed non-resaleable stock end up with space compression, inaccurate counts, and a processing environment that is harder to work in.
Set a clear clearance schedule — weekly minimum — for grade C and D items. This is not just an efficiency measure. It is a space management requirement.
Returns Volume Planning: Preparing for Peak
Ecommerce returns management fails most visibly at peak. The volume arrives, the processing area is overwhelmed, backlogs form, customer service tickets spike, and refund timelines blow out.
The fix is not always more staff. Often it is more capacity in the right place.
Planning for peak returns should be part of the same planning cycle as peak outbound. That means:
Calculating your expected returns volume. If you processed 50,000 orders in November–December, and your average return rate is 25%, you are expecting approximately 12,500 items to come back in January. Map that against your processing capacity. If your current setup can handle 150 returns per day, that is 83 days of processing — far beyond when those customers expect their refunds.
Expanding your processing area in advance. A storage system that takes a full working day to reconfigure is not compatible with peak planning that happens three weeks before Christmas. The decision to expand your returns area for Returnuary needs to be made in November — and executed quickly when the time comes.
Pre-positioning materials. Repackaging materials, labels, void fill, and boxes should be pre-stocked in the returns area before volume arrives. Running out mid-peak creates a bottleneck that has nothing to do with the processing system.
Ecommerce Returns KPIs to Track
| KPI | Target | Why It Matters |
| Return rate by SKU | Monitor for outliers above category average | Flags product quality or listing accuracy issues |
| Processing cycle time | Under 48 hours for Grade A | Drives speed to restock and customer refund time |
| Return-to-stock rate | Track as % of total returns | Measures recovery value; declining rate signals product quality trend |
| Cost per return | Calculate monthly; include all costs | The true margin metric — most operations undertrack this |
| Refund resolution time | Under 72 hours from receipt | Customer satisfaction and chargeback risk management |
| Grade D write-off rate | Monitor trend over time | Rising rate signals product or packaging issues upstream |
Common Ecommerce Returns Mistakes
Not separating returns from outbound goods-in. When returns arrive through the same physical flow as new stock, contamination errors occur and both processes slow down.
Processing in batches. Daily batch processing means inventory is wrong all day. Every pick from a location that contains a recently returned but unlogged item is a potential error.
Undersizing the processing area for peak. Planning peak capacity for outbound without planning equivalent capacity for the returning wave is a recurring operational failure.
No pre-notification or RMA system. Starting the process when the parcel arrives — rather than when the customer initiates the return — adds unnecessary handling time to every return.
Writing off Grade B stock instead of repackaging it. In a margin-pressured environment, taking 10 minutes to repackage a Grade B item and return it to stock is nearly always worth it. Operations that default to write-off when repackaging is possible are destroying margin they could recover.
Further Reading
For a broader overview of how returns management works across all operation types, see our complete guide to returns management.
How PALLITE Supports Ecommerce Returns Operations
The PIX modular storage system is used in ecommerce returns processing areas specifically because it handles the two things fixed racking cannot: rapid reconfiguration for volume spikes, and flexible bin sizing for wide SKU ranges.
It assembles without tools, reconfigures in hours rather than days, and scales up or down as volume changes. The PIX FIFO configuration enforces date-ordered stock rotation at bin level, which keeps FIFO discipline intact even when returned stock is entering the pick sequence from multiple sources.
