Reverse Logistics for Ecommerce: How Returns Move Through a 3PL

Reverse logistics is the path a product takes after a customer sends it back: the return gets authorized, the parcel gets received and inspected, someone decides whether the unit can be sold again, and the inventory count gets corrected. For an ecommerce brand, the work lands on whoever shipped the order, usually a 3PL, so the quality of your returns depends on the same warehouse that handles your ecommerce fulfillment.

Without a returns process, a box comes back with no paperwork, sits on a cart for a week, and gets restocked without anyone checking what's inside. Your system still shows the unit as sold, the refund waits, and the next customer who orders that SKU might get the damaged one. A controlled process ties each return to the order it came from, checks it at the dock and scans it back to a shelf location.

What does reverse logistics cover for an ecommerce brand?

For most DTC and marketplace brands, reverse logistics covers four kinds of parcels coming back to the warehouse:

• Customer returns. The buyer changed their mind, ordered the wrong size, or got something they didn't expect.
• Damaged in transit. The carton got crushed or wet, and the customer sent it back or refused it.
• Refused or undeliverable. The address was wrong, nobody signed, or the customer refused delivery, and the carrier returned it.
• Wrong item shipped. The warehouse sent the wrong SKU or quantity, and the customer returned what arrived.

Each one needs the same answers before the unit goes anywhere: which order it belongs to, what came back, what condition it's in, and whether it can be sold again. The last category also tells you something about your 3PL, because a wrong item shipped is a forward-fulfillment error that became a return.

How is reverse logistics different from forward logistics?

Forward logistics moves new inventory to a customer on a schedule you control. Reverse logistics moves single units back in whatever condition the customer left them, and every one needs a decision before it can count as stock again.

A forward order is finished when tracking posts. A return is finished only when the unit's status in your inventory matches the shelf.

Which returns does a 3PL handle, and which go somewhere else?

Reverse logistics covers more than customer returns. Repair and warranty service, refurbishment, recycling programs and recalls all move product backward too. For an ecommerce brand, the split usually looks like this:

• The 3PL receives and decides: customer returns, refused and undeliverable parcels, damaged-in-transit returns and wrong-item returns. The warehouse matches each one to its order, inspects it and either restocks it or holds it out.
• The 3PL holds and reports, you decide: units that need repair or refurbishment, and recalled lots. You decide what happens to recalled stock, and the warehouse stops the lot and tells you which orders received it. For lot-tracked products like supplements, KSP puts the affected lot on hold in the WMS so no new order can allocate it, pulls the units on hand from pickable locations, lists every shipped order that received the lot with ship dates and destinations, and then carries out your instruction to return, destroy or rework the stock.
• Usually outside the 3PL: repair work itself, refurbishment and recycling programs, handled by the brand, the manufacturer or a specialist.

How does a return move through a 3PL, step by step?

A controlled return follows the same path every time, from authorization to a closed record. Here is the sequence KSP's returns team follows in Logiwa, our warehouse management system:

1. Authorize the return against the original order. An RMA (return merchandise authorization) is created from the shipped order itself, so the return is tied to the exact order, customer and products that went out.
2. Set what's coming back. The RMA records the return quantity for each product, the reason for the return, a scheduled return date, and the carrier and shipping service you choose for returns.
3. Check the shipment on arrival. When the parcel arrives, the associate verifies the RMA number, compares the shipment to the RMA, and inspects every carton.
4. Scan the return label. Scanning the label pulls up the shipment and the product it belongs to. The associate confirms the item in hand matches what the system shows before accepting the return.
5. Record what the unit needs. The expiration date (for dated products) and the return reason go into the record, and the unit is assigned to a tote or license plate so it can be tracked inside the building.
6. Cover the old label. The original shipping label gets covered, so its barcode can't be scanned again inside the building.
7. Assign a disposition. Inspection decides whether the unit goes back to sellable stock or stays out of it. Damage is documented, and the disposition is recorded on the return.
8. Put it away by scan. Restockable units go back to the shelf through directed put-away: the associate scans the location and the product, so the inventory count updates to the bin.
9. Close the RMA after a final check. The RMA closes only when every field in the closing check below matches.

Steps 1 and 2 are the ones brands skip when they process returns in-house, and they cause most of the problems downstream. A box with no RMA has no order to match against.

What is the RMA process, and why does it start before the box arrives?

The RMA process is how a return gets approved and tracked from the customer's request to the restocked unit. RMA stands for return merchandise authorization: a record that says this order, these products, this quantity, for this reason, are expected back.

Creating it before the parcel arrives does three things. The warehouse knows what to expect, so a box with the wrong product or quantity gets flagged at the dock instead of disappearing into stock. The return reason gets recorded once, from the customer's documentation, instead of guessed later from the condition of the box. And refunds can be tied to an actual receipt, because the RMA shows when the return was received and what came back.

At KSP, the RMA is created from the shipped order in Logiwa, with the carrier and service you designate for returns. If the shipment doesn't match its RMA when it lands, the mismatch gets handled before the unit moves: a wrong product is isolated and flagged to KSP customer service, a short quantity gets recounted against the RMA, and a missing reason gets added to the RMA before the return is completed.

What happens when a return doesn't match its RMA?

When the parcel and its RMA disagree, a unit can enter stock under the wrong SKU or quantity. At KSP, each mismatch has a set response before the return can close:

If a wrong product gets accepted as a match, your count gains a unit of the SKU on the RMA that isn't on the shelf, and the next order for it ships short or late.

What should a 3PL check before a return goes back into stock?

Before KSP closes a return, ten things have to check out:

Each check catches a specific failure. A return restocked without the SKU and quantity check adds the wrong units to your count. A return closed without a disposition leaves a damaged unit in sellable stock, where the next order can pick it.

When should the customer's refund go out?

A refund can go out at one of three points, and each trades speed for risk:

• When the carrier first scans the return label. The customer gets the money within days of shipping the return. You refund before anyone knows what's in the box, so a wrong item, an empty box or a swapped unit costs you the full refund.
• When the warehouse receives the parcel against its RMA. The return is confirmed as arrived and matched to the order. You still refund before inspection, so damage and swaps get caught after the money is gone.
• After inspection and disposition. Slowest, but the refund is tied to what actually came back and the condition it's in. This is the safest point for high-value, serialized or dated products.

Whichever point you pick, your 3PL's record has to support it. An RMA that shows when the return was received, what came back and what was decided gives your customer service team a fact to refund against instead of a guess.

How do lot numbers, expiration dates and serial numbers change returns?

Products with lots, expiration dates or serial numbers need more than a condition check, because a unit that looks fine can still be unsellable.

For dated products like supplements, cosmetics and food, the expiration date goes into the return record, so a returned unit doesn't go back on the shelf with less shelf life than the stock around it without anyone knowing. That matters most for supplement fulfillment, where retailers and customers both check dates.

For serialized products like electronics and medical devices, the serial number settles whether the unit that came back is the one that shipped. KSP scans serials at receiving, picking and pack-out, so a return gets checked against the exact unit on the order. That's how serial number tracking stops the swap where a customer returns an older or broken unit in place of the new one.

How should you use returns data?

Return reasons show which part of the operation caused the return: packaging, the product page, checkout or the warehouse. At KSP, you get a report of every return and its condition. Read it by reason and SKU, then fix the cause upstream:

This only works when the reason is recorded from the customer's documentation on the RMA, before the parcel arrives. A reason guessed at the dock from the condition of the box sends you fixing the wrong thing.

How do you reduce returns caused by the warehouse?

Some returns start at the pack station. A wrong item, a short shipment or a unit packed into the wrong box comes back as a return, costs you the reship, and shows up in your reviews. The best returns process can't fix a warehouse that ships the wrong thing, so look at forward accuracy before you look at returns.

KSP holds 99.999% order accuracy across 32.1M orders, counted on whole orders shipped correct. Every pick gets an RF barcode scan against the order line, so fewer orders come back as "wrong item shipped" to begin with. Our guide to 3PL order accuracy explains how that rate is measured and what to ask a provider about theirs. When KSP does lose or damage a unit, we pay its cost.

What should you ask a 3PL about returns before you sign?

Ask every provider these questions, and ask them to show you the answer on the floor:

1. Is every return tied to the original order? Ask how an RMA is created and what it records. A provider that receives returns without one can't tell you which order a box belongs to.
2. What gets scanned when a return arrives? You want the label and the product scanned and matched to the order before anyone accepts the return.
3. Who decides whether a unit is restocked? Ask what the inspection records and how the disposition shows up in the record you can see.
4. How are lot, expiration and serial data captured on returns? If you sell dated or serialized products, this decides whether returned stock is safe to sell again.
5. Does a returned unit go back into the same inventory count? Returns should update the same stock your store and marketplaces draw from, through a scan to a location.
6. What happens when the return was the warehouse's fault? Ask who pays for a unit the 3PL lost or damaged, and how fast they respond when you raise an issue. KSP's issue response SLA is 2 hours.

How KSP handles returns

KSP processes returns in the same Brooklyn Park, MN building that ships your orders, in the same Logiwa system that holds your inventory:

• RMA from the shipped order, with the return quantity, reason, scheduled return date, and the carrier and service you pick.
• Dock check against the RMA, with every carton inspected and the return label scanned to the original order.
• Item confirmed before acceptance, with expiration date, reason, and lot or serial data recorded where the product carries them.
• Scan-confirmed put-away of restockable units to a tracked location, so your count updates when the unit hits the shelf.
• A ten-point check before the RMA closes, from SKU and quantity through disposition and stock status.
• A report of every return and its condition, so you can read your return reasons by SKU.
• Lot holds and traced order lists when a lot-tracked product is recalled, with the stock handled on your instruction.
• Scheduled cycle counts included at no charge, so the count your returns feed into stays true to the shelf.
• A 2-hour issue response SLA when something about a return needs your call.

Brands selling both DTC and retail get returns from both channels landing against one inventory, which keeps the count your store sells from in step with what's on the shelf. If you're comparing how 3PLs keep that count right, read how warehouse inventory management works at a 3PL.

Frequently asked questions