Short answer: The FBA Customer Returns report tells you what happened when a customer sent a unit back to Amazon, one row per returned unit with its LPN. The Removal Order Detail report tells you what you asked Amazon to send back to you or dispose of, one row per removal line with quantities. You connect the two through the FNSKU/SKU, the Removal Order ID printed inside the RA# on your return slip, and the LPN sticker on each unit.
Key takeaways
- A removal order is a request you create to get inventory out of an FBA warehouse, either shipped back to you (return) or destroyed (disposal).
- The FBA Customer Returns report is unit-level: each row describes one customer return, including the license-plate-number, order-id, fnsku, detailed-disposition and reason.
- The Removal Order Detail report is order-level: each line describes a removal request for a SKU/FNSKU and how many units were requested, shipped, cancelled or disposed.
- The middle segment of the RA# on your return slip is the Removal Order ID, which lets you find the right removal order for the box in your hands.
- Both reports have an "order-id" column, but they mean different things. Mixing them up is one of the most common reconciliation errors.
- Report downloads are limited to date ranges, so a long lookback often needs several downloads stitched together.
What is a removal order in FBA?
A removal order is a request you submit in Seller Central to pull units out of Amazon fulfillment centers. You choose whether the units are shipped back to an address you provide (a return removal) or disposed of by Amazon (a disposal removal).
Sellers create removal orders for many reasons. Some want to recover unsellable inventory, such as units that customers returned and Amazon graded as damaged or defective. Others want to move slow stock, relabel it, or inspect returns before deciding what to do.
Return to seller vs. disposal
The difference matters for disputes. A return removal puts the physical unit in your hands, which means you can photograph it, read its LPN sticker and compare it with what you originally sent in. A disposal removal ends with the unit destroyed, so there is nothing left to inspect.
If you suspect that customer returns are coming back switched, incomplete or missing accessories, return removals are the only way to see the evidence. Many sellers who start disputing returns change their default from disposal to return for exactly this reason. Removal fees apply either way; check the current fee schedule in Seller Central Help before deciding.
How does a customer return end up in a removal shipment?
A customer return becomes part of a removal shipment when Amazon grades it as unsellable (or you request sellable stock back) and you create a removal order that covers that FNSKU. The unit keeps its LPN sticker from the return process, and it ships to you inside a box that also contains a return slip.
Here is the typical path. A customer requests a return, ships the unit back, and the fulfillment center receives it. Staff inspect the unit, apply or scan an LPN (License Plate Number) sticker that identifies that single returned unit, and assign a disposition such as SELLABLE, DEFECTIVE, CUSTOMER_DAMAGED or CARRIER_DAMAGED.
Sellable units usually go back into your available inventory. Unsellable units sit in an unfulfillable status until you decide what to do with them. When you create a return removal for that FNSKU, Amazon picks units, packs them and ships them to you. Your removal box then contains a mix of units, often several LPNs from different customer returns under the same FNSKU.
Why the LPN survives the trip
The LPN sticker is the thread that connects the physical item to the data. It was attached when the return was processed, and it usually remains on the unit or its packaging through the removal. That is why the sticker is the single most important photo in any dispute. If you want a deeper look at the sticker format, see LPN stickers explained.
What is the difference between the Removal Order Detail report and the FBA Customer Returns report?
The FBA Customer Returns report describes returns from customers at the unit level, while the Removal Order Detail report describes your removal requests at the order-line level. One tells you why a unit came back to Amazon; the other tells you what Amazon agreed to send back to you.
What the FBA Customer Returns report contains
Each row represents one returned unit. The columns you will use most are:
- return-date: when the fulfillment center processed the return.
- order-id: the original customer order the unit was sold under.
- sku, asin, fnsku, product-name: which of your products it was. ASINs usually start with B0 and FNSKUs usually start with X0.
- quantity: normally 1 per row.
- fulfillment-center-id: the warehouse that processed the return.
- detailed-disposition: Amazon's grading, such as SELLABLE, DEFECTIVE, CUSTOMER_DAMAGED or CARRIER_DAMAGED.
- reason: the customer's stated return reason.
- status: the state of the return record.
- license-plate-number: the LPN of that unit, which matches the sticker you will find on it.
- customer-comments: free text from the customer, when provided.
What the Removal Order Detail report contains
Each row represents a removal request for one SKU/FNSKU within a removal order. You will typically see the removal order ID, the request date, the order status, the SKU and FNSKU, the disposition of the stock removed (sellable or unfulfillable), and quantity fields such as requested, cancelled, disposed, shipped and still in process. Column names can change, so confirm them against the file you actually download.
Notice what is missing: the Removal Order Detail report does not list individual LPNs. It tells you that, for example, five unfulfillable units of FNSKU X00ABC1234 were requested and shipped, but not which five customer returns they were.
Side-by-side comparison
| Aspect | FBA Customer Returns report | Removal Order Detail report |
|---|---|---|
| What one row represents | One unit returned by a customer | One SKU/FNSKU line within a removal order |
| Main identifier | license-plate-number (LPN) | Removal order ID |
| Meaning of "order-id" | The customer's original purchase order | Your removal order |
| Product fields | sku, asin, fnsku, product-name | sku, fnsku |
| Condition info | detailed-disposition, reason, customer-comments | Disposition of removed stock (sellable or unfulfillable) |
| Quantity logic | Usually 1 per row | Requested, shipped, cancelled, disposed quantities |
| Best used for | Proving which customer return a unit came from | Confirming what should be in the removal box |
| Link to the box in hand | LPN sticker on each unit | RA# middle segment on the return slip |
Which ID ties the two reports together?
No single ID appears in both reports and on the unit. You link them in two steps: the RA# on the return slip gives you the Removal Order ID, which finds the removal line; the FNSKU and LPN on each unit find the matching row in the FBA Customer Returns report.
The return slip in a removal box usually shows a Shipment ID, a VRET ID, an RA# and a process date. The RA# follows a pattern like QW3M7-tRk8Vn2pLx-CHA1-1, where the middle segment (tRk8Vn2pLx in this fictional example) is the Removal Order ID and the next segment is the fulfillment center code. Our guide on how to read an Amazon return slip walks through each field in detail.
The FNSKU is the shared product key. It appears in both reports and on the product label, so it narrows a removal line down to a specific set of customer returns. The LPN then pins down exactly which customer return a given physical unit came from.
How do I trace one unit from customer return to the box I opened?
Start from the physical unit and work backward through both reports. The LPN takes you to the customer return; the RA# takes you to the removal order; the FNSKU confirms the two belong together.
Here is an example with fictional data. You open a removal box containing a cordless hair clipper kit. The LPN sticker reads LPNR8K2M4QX7T, and the product label shows FNSKU X00ABC1234. The return slip shows Shipment ID 518203947261830, VRET4830916257204 and RA# QW3M7-tRk8Vn2pLx-CHA1-1.
- Photograph the LPN sticker, the product label, the return slip and the unit itself before handling anything further.
- Search the FBA Customer Returns report for license-plate-number LPNR8K2M4QX7T. Note the return-date, the customer order-id, the detailed-disposition and the reason.
- Confirm that the fnsku on that row matches X00ABC1234 and the asin matches your listing, for example B0C7XK2P9M.
- Take the middle segment of the RA#, tRk8Vn2pLx, and search the Removal Order Detail report for that removal order ID.
- Check that the removal line includes FNSKU X00ABC1234 and that its shipped quantity is at least as large as the number of units of that FNSKU you found in the box.
- Compare the unit against your catalog: what should be in the box, where the brand should appear, and which accessories belong to the set.
- Record the result for that LPN: matches, wrong item, incomplete set, missing case, or missing accessories.
Once this chain is complete, you have everything a Seller Support agent needs to locate the unit in Amazon's systems. Doing this by hand for every LPN is slow, which is why some sellers use Return Disputes to read the LPN, FNSKU, Shipment ID, VRET ID and RA# from photos and check each unit against their catalog automatically.
What is a practical workflow for reconciling a removal box?
Treat each removal box as a small audit: list what the slip and removal report say should be inside, list what is actually inside by LPN, and flag every difference. Do it the day the box arrives, before units get mixed with other stock.
Before you open the box
Download fresh copies of both reports covering the relevant period. Customer returns can be processed well before the removal ships, so pull a Customer Returns range that starts earlier than the removal request date. Report downloads in Seller Central are limited to date ranges, so you may need several downloads to cover a long period.
While you unpack
Work one unit at a time and keep each unit with its own packaging and accessories. Mixing parts between units destroys the evidence you need for incomplete-set claims. A consistent set of photos for every unit makes later matching much easier; the 4-photo checklist for every return dispute covers the shots that matter.
Build a simple sheet with one row per LPN. For example:
| LPN | FNSKU | Customer return found? | Disposition in report | What you found | Action |
|---|---|---|---|---|---|
| LPNR8K2M4QX7T | X00ABC1234 | Yes | CUSTOMER_DAMAGED | Charging cable and guide combs missing | Dispute: incomplete set |
| LPNT5W9J3HB2D | X00ABC1234 | Yes | DEFECTIVE | Different clipper model, not your product | Dispute: wrong item |
| LPNK7Q2V8NM4C | X00ABC1234 | Yes | SELLABLE | Complete, undamaged | No action |
After you unpack
Compare the count of units per FNSKU with the shipped quantity on the removal line. If fewer units arrived than the removal report shows as shipped, that is a separate issue from a bad return, and it should be raised separately. Then group the units that need a dispute, keep their photos organized by LPN, and file your cases. Once cases are open, keep a log of case IDs so you can later match payouts in the Reimbursements report, which lists reimbursements with a case-id, reason, fnsku/asin, quantity and amounts. The process is covered in tracking reimbursements and matching payouts to cases.
What are the most common pitfalls when matching these reports?
Most reconciliation problems come from date ranges that are too narrow, units that arrive without an LPN, removal lines that cover several units, and confusing the two kinds of order ID. Each has a straightforward fix.
Date-range limits
Seller Central restricts how much data one report download covers. If your Customer Returns download starts after the return was processed, the LPN simply will not appear, and it is easy to wrongly conclude that the unit was never a customer return. Pull overlapping ranges and combine them into one sheet before searching.
Units without an LPN
Not every unit in a removal box carries an LPN sticker. Units that were never customer returns, such as unsold stock removed from your sellable inventory, typically have no LPN. A sticker can also fall off or be covered. In these cases, record the FNSKU and the product label, note that no LPN was present, and do not guess which customer return the unit belongs to.
Multiple units per removal line
A single removal line can represent many units of the same FNSKU, possibly from many different customer returns processed at different times. The removal report cannot tell you which customer return each unit came from. Only the LPN can. That is why you should never assign a removal line's details to a unit without also matching its LPN in the Customer Returns report.
Two different "order-id" columns
In the Customer Returns report, order-id is the customer's purchase order, formatted like 114-5820193-7736401. In the Removal Order Detail report, order-id is your removal order ID, the same value as the middle part of the RA#. Label them clearly in your working sheet, for example "customer order" and "removal order", to avoid pasting the wrong one into a ticket.
Same LPN appearing twice
If the same LPN shows up on two units in your box, or twice in your notes, stop and recheck. Each LPN identifies one returned unit. A duplicate usually means a photo was mislabeled or a sticker was misread, and filing a dispute with a duplicated LPN weakens the whole ticket.
Frequently asked questions
Does the Removal Order Detail report show LPNs?
No. The Removal Order Detail report works at the order-line level and shows quantities per SKU/FNSKU, not individual units. To identify a specific returned unit, read the LPN sticker on it and look that number up in the license-plate-number column of the FBA Customer Returns report.
Where do I find the Removal Order ID for a box I received?
Look at the return slip packed in the box. The RA# has several segments separated by hyphens, and the middle segment is the Removal Order ID. Search for that value in the Removal Order Detail report to find the matching removal order and its lines.
Why can't I find an LPN from my box in the Customer Returns report?
The most common cause is a report date range that does not reach back far enough, since returns are often processed long before the removal ships. Download earlier ranges and search again. Also double-check the sticker reading, because similar-looking characters are easy to confuse.
Should I choose disposal or return for unsellable customer returns?
That is a business decision that depends on your product value, removal fees and how often returns come back wrong. Disposal is simpler, but it removes any chance to inspect the unit and document a switched or incomplete return. Check current removal and disposal fees in Seller Central Help before setting a default.
Can one removal box contain units from several removal orders?
It can happen, so read every return slip in the box and do not assume a single RA# covers everything. Group units by the slip they came with when possible, and check each unit's FNSKU against the removal lines of the matching removal order.
What should I do if fewer units arrived than the removal report says were shipped?
Treat it as a separate issue from disputing bad customer returns. Document the box contents, the return slip and the shipped quantity from the Removal Order Detail report, then contact Seller Support about the shortage. Check the current rules and timelines for removal shipment issues in Seller Central Help.