When a 3PL handles your returns, the customer sends the item back to the warehouse that holds your inventory, not to your garage or office. The warehouse receives it, matches it to the original order, inspects it, and either puts it back into sellable stock or routes it to rework, donation or disposal. Then it updates your inventory count and reports what came back and why. The return policy, the refund decision and the conversation with the customer stay with you.
That split is easy to miss when you hand off fulfillment. "The 3PL handles returns" sounds like the whole problem goes away. What actually moves is the physical work. What stays is every decision that costs or saves money: how long the window is, who pays for the label, whether a worn item gets a refund, and what happens to stock that can't be sold again. Those decisions are where returns programs leak money, and a 3PL can only apply the rules you give it.
Retailers surveyed by the National Retail Federation and Happy Returns expected 19.3% of online sales to be returned in 2025. That is a share of sales value rather than of orders, and your own rate depends on what you sell. Whatever yours turns out to be, every return is a box someone has to open, grade and put somewhere. Returns are the slice of reverse logistics that a small brand deals with every week.
Who does what when a 3PL handles returns
Step | Your 3PL | You |
|---|---|---|
Return policy (window, condition, who pays) | Applies it | Set it |
Customer request and label | Runs the portal, or receives the box with the label you supplied | Choose in-box or on-demand labels |
Receiving, inspection, grading | Does it | Set the grading rules |
Restock, rework, donate or discard | Does it | Decide the rule for each outcome |
Refund, exchange or store credit | Reports what arrived and its condition | Issue it in your store |
Inventory update | Does it | Check that counts match |
Return-reason data | Reports it | Act on it |
What happens to a return, step by step
1. The box arrives and is matched to the order
The customer's label brings the box to the 3PL's receiving dock. Someone scans it, finds the original order in the warehouse system and logs the return as received. That timestamp matters more than it looks. It is the evidence when a customer says they sent it back two weeks ago, and it starts the clock on how fast the unit becomes sellable again. The gap between carrier delivery and that scan is where slow operations lose days, often because returns sit behind inbound pallets in the same receiving queue. Ask how returns are prioritized against regular receiving.
2. The item is inspected and graded
Sealed, opened, worn, damaged, missing parts. The grade decides what happens next, and the rules for grading should be yours, written down before the first return arrives. A good 3PL grades against that rubric and photographs anything that isn't clear-cut, so nobody is arguing about a stained sweater from memory. For apparel this step is most of the work: a returned garment usually has to be checked, refolded and re-bagged before it can go back on the shelf.
3. The item is restocked, reworked, donated or discarded
A return that arrives unused and complete goes straight back into inventory. Some need light rework first, such as a fresh polybag, a replaced insert or a new tag. Some can't be sold as new but still have value, so they're donated, sent to a liquidator or shipped back to you. The rest are discarded. Each path has a cost and needs a rule, and the rule should be yours. At what point does a cosmetic flaw mean "donate" instead of "restock"? What happens to opened consumables or cosmetics you won't resell? Settle that before launch, not during the January pile.
4. Inventory updates, and you issue the refund
Once the disposition is set, the warehouse system records it, and not every path puts stock back on sale. A unit graded sellable returns to available inventory and your connected store sees it again. A unit sent to rework stays out of the available count until the rework is done. Units marked for donation, liquidation, return to you or disposal leave your sellable count for good and should show in the report as a write-off or a transfer, not as stock. Check that your store's count only rises when a unit is actually sellable. Then comes the refund, and this is where expectations drift. In most setups the 3PL does not issue refunds. It reports that the item arrived and how it graded; your store, your returns app or your own rules then release the refund, exchange or store credit. The delay customers notice is between "received" and "refunded", so decide who closes it. Refund on receipt? On grading? Manual approval above a certain order value? Pick one and make sure the data flows that way.
5. The reasons are reported
The most underused output of 3PL returns handling is the data. Wrong size, arrived damaged, not as described, changed my mind, wrong item shipped. Ask for a monthly breakdown by SKU and reason. Two of those reasons can point at the operation rather than the product. Wrong item shipped is a warehouse error. Arrived damaged could be the packing, the carrier or the product itself, and you want to know which. Track both separately from the reasons that point at the product or the listing. A 3PL that can't tell you its own error rate isn't going to fix it.
How your customer gets a return label
There are two common patterns, and the choice is yours even when a 3PL runs the process.
- A prepaid label in every box. Easiest for the customer. You pay to print one in every shipment, and a paper label can't ask why the item is coming back.
- An on-demand label from a returns portal. The customer enters the order number, picks the item and a reason, and gets a label or a QR code by email. Nothing is generated until a return actually starts, you capture the reason, and the portal can apply your policy, such as no label for final-sale items.
One fact makes the choice cheaper than it looks. USPS merchant return labels are scan-based: you're billed per label scanned, not per label printed, and the return products carry no minimum annual volume, per USPS Return Services. An unused in-box label costs you the paper, not the postage. Other carriers have their own return products, so check how each bills an unused label. Past the unused-label question, compare the two patterns on the reason data and policy control they give you, which is why a portal usually wins once you have one.
In-house, a returns app, or your 3PL
Returns have two halves: the customer-facing part (the request, the label, the refund trigger) and the physical part (receiving, inspection, restock or disposal). In-house means you cover both. A standalone returns app covers the customer-facing half only. A 3PL covers the physical half and, depending on the provider, some or all of the customer-facing half. An app and a 3PL are not rivals; brands often run both. Compare the options by which half each one covers and how well, not by the label.
Setup | How you pay | Customer-facing flow | Physical handling and restock | Load on your team |
|---|---|---|---|---|
In-house | No per-return invoice; labor, space and label software are fixed overhead | Whatever you build, and every gap is yours | You receive, inspect and restock. Fine at low volume, slow the moment a spike hits | Highest. Returns compete with everything else |
Standalone returns app | A subscription, plus whoever physically handles the box, plus return shipping | Self-serve portal, instant exchanges, store credit | Not covered. The box still goes to you or your 3PL, and restock speed is that operation's queue | Medium. One more vendor, and a data seam between returns and inventory to check |
3PL-integrated returns | Return handling on the 3PL's rate card, plus return shipping | Depends on the 3PL: a bare page or a branded portal | The box arrives where your stock lives, so no transfer between vendors. Restock speed is the 3PL's returns queue, so ask for its number | Lower on the physical side. Policy, refunds and the customer conversation stay with you |
In-house: full control, hidden cost
Picture twenty returns a week: one person absorbs it between other tasks. Now picture two hundred in the week after Black Friday: that person becomes the bottleneck, refunds sit unprocessed and customers email asking where their money is. The exact numbers depend on your product, but the shape is the same. In-house makes sense when volume is low and steady, or when your product needs an inspection nobody else will do as carefully. It stops making sense when volume swings, which is exactly when returns matter most. If returns are a few boxes a week for you, keeping them in-house is often the right call for now.
A returns app: strong front end, separate back end
Returns apps solve the customer-facing half well: a self-serve flow, instant exchanges, store credit, a label by email. For brands that live on repeat purchase, that's worth paying for. The catch is the back end. Something still has to receive the box, inspect it and decide whether it goes back on the shelf. If that happens somewhere other than where your inventory lives, you have two systems that must agree on what is sellable, and a lag between "customer shipped it" and "it counts as stock again". That lag is cash tied up in units you can't sell, and it is where inventory counts drift. If you run an app for the customer flow and a 3PL for the physical side, ask both how the two systems talk.
3PL-integrated: one building, one count
When the 3PL that ships your orders also receives the returns, the box comes back to the building that holds your stock. Inspection and restock happen there, so a resellable unit does not need a transfer between vendors, and one system owns both directions, which keeps the count honest. What that removes is a handoff, not the wait. How fast the unit becomes sellable depends on how the 3PL prioritizes returns against inbound receiving and whether its system updates your store automatically, so speed is the provider's number, not a property of the setup. The customer-facing side is also only as good as the 3PL makes it, which is why many brands keep a returns app on the front and let the 3PL handle the box. The question isn't "do you do returns" (every 3PL says yes) but "what does my customer see, and how many days until a returned unit is sellable again".
What a return actually costs
There's no single number, because the three setups bill in different ways. A returns app charges a subscription that usually scales with volume, on top of the physical handling and the return postage. A 3PL usually charges for return handling on its rate card, sometimes per item and sometimes per box, plus the return shipping. In-house has no invoice line at all, which is exactly why brands underestimate it; the cost sits in payroll and floor space. Our guide to 3PL fees beyond the per-order price covers where returns usually sit on a rate card.
The number that matters is total cost per return: the postage back, the labor to receive and inspect, the restock or disposal work, and the days the unit spends out of inventory. A low handling fee with a two-week restock lag can cost more than a higher one that has the unit back on the shelf in a day or two.
On speed, there's no industry standard, and "how long does it take" is a question to put to each 3PL directly. For a reference point, DCL Logistics commits to 48 hours from receipt to disposition at its own facilities, and its evaluation guide lists five to seven business days as the slower benchmark for a 3PL that runs returns through general receiving labor. Treat those as one provider's figures rather than a norm, and ask yours for its number in writing. Also keep returns separate from receiving turnaround for new inventory. They're different queues, and a 3PL's receiving promise tells you nothing about its returns queue unless it says so.
Should you offer free return shipping?
A return is a second fulfillment event, and under a free-returns policy you fund all of it: the refund, the return postage and the handling, whatever happens to the unit afterward. Shoppers do weigh the policy. In the same NRF and Happy Returns survey, 82% of consumers called free returns a major consideration when deciding what to buy, and a free-returns policy can also raise the number of boxes coming back. So the decision is a trade. On one side are the orders and repeat customers the policy brings in, plus the resale value of units that come back sellable. On the other are the postage, handling and refund on every return, plus the units that come back unsellable or sit so long they miss the season. Quick restocking protects the resale side of that trade. It does not pay for the postage or the handling, so a policy that loses money on the round trip is not rescued by a fast dock.
Start selectively. Free returns on a $60 order behave differently from free returns on an $18 one, so begin where the margin supports it, watch the restock rate and expand from there. Whatever you decide, the policy should state the window, the condition an item has to be in, who pays return shipping, and the refund method and timing, and it should be linked from every product page. Ask for a return reason in the flow so the data is usable. Keep returns caused by a fulfillment or shipping error (wrong item, damaged in transit) in a separate bucket from "changed my mind" returns. Lump them together and you can't tell an operations problem from a product-fit problem.
What to ask a 3PL about returns
Put these on the table before you sign, and write the answers into the agreement where you can.
- Where does a returned box physically go, and is it the same warehouse that holds my inventory?
- How many days from "delivered back to you" to "counts as sellable stock again", and is that separate from your receiving queue?
- What does my customer see: a branded self-serve portal, or an email to my support inbox?
- How are returns billed (per item, per box, bundled), and what does the all-in cost per return work out to?
- What grading rules do you follow, and do you photograph exceptions?
- What are my options for units that can't be restocked: rework, donate, liquidate, ship back to me?
- What report do I get, how often, and does it split your errors from customer-initiated returns?
A 3PL that answers all of these cleanly has treated returns as part of the operation. One that hedges is telling you returns are an afterthought there too, and that afterthought becomes your problem the first busy week. For everything else on the shortlist, from pricing structure to integrations, use our checklist for choosing a 3PL.
How Simpl handles returns
Returns management is one of our core services, not a bolt-on. Every client gets a branded returns portal, included. We ship from one warehouse in Austin, Texas, so a return comes back to the building that holds your inventory and is inspected there before it goes back to stock. For apparel brands that means bag-and-fold on returns: inspect, re-bag, refold. Returns that can't be resold can be donated.
Returns are billed per your rate card, separate from the per-order fulfillment price. The exception is our own errors. Simpl runs 99.99% order accuracy, and when a fulfillment error is ours (wrong item, wrong quantity) we cover the return shipping and the re-fulfillment at our cost; here's how that works. That keeps the "our error" bucket separate from customer-initiated returns in your numbers from day one.
Your policy and your refund decisions stay yours. Every client has a dedicated account manager, reachable by email with same-day responses, for the questions that come up once real returns start arriving. To see where returns fit in the rest of the per-order flow, read about our ecommerce fulfillment service, or talk to us about your catalog.