Short answer: An LPN (License Plate Number) is a unique code Amazon prints on a sticker and attaches to a single customer-returned unit when it is processed at a fulfillment center. It links that physical unit to exactly one line in your FBA Customer Returns report, so copying it correctly is the first step in any return dispute.
Key takeaways
- An LPN identifies one returned unit, not a product, a SKU or a shipment.
- The sticker usually shows the LPN code with a barcode, and often the FNSKU or ASIN of the product the unit was received as.
- In reports the value appears with the "LPN" prefix and no spaces, for example LPNR8K2M4QX7T. Copy it exactly that way.
- The license-plate-number column of the FBA Customer Returns report connects the sticker to the order, reason, disposition and customer comments.
- One LPN equals one unit equals one line in a dispute. Never merge two units under one LPN or split one unit across two.
- A missing or unreadable sticker does not end your case, but you need other identifiers and a clear photo record to compensate.
What is an LPN sticker on an Amazon return?
An LPN sticker is a small label that Amazon applies to a returned unit so it can be tracked individually from that point forward. The code on it is called a License Plate Number, and no two returned units share the same one.
Think of it as a serial number that Amazon assigns at the moment of return processing. Your FNSKU tells Amazon which product a unit is supposed to be. The LPN tells Amazon which specific physical unit came back from which specific customer.
This distinction matters because sellers often receive several returned units of the same SKU in one removal box. They look identical on the outside. The only reliable way to tell them apart, and to connect each one to its return record, is the LPN. If you are new to the overall process, start with what an FBA return dispute is and when you can file one.
Where does Amazon apply the LPN sticker?
Amazon applies the LPN sticker when a customer return is received and inspected at a fulfillment center, typically on the outside of the unit's packaging or on a bag the unit was placed in. The exact placement varies by facility, product size and how the item arrived.
In practice you will find LPN stickers in a few common places:
- On the retail box itself, often near or over the original barcode area.
- On a clear poly bag that holds a loose or repackaged item.
- On a shrink wrap layer around a multi-piece kit, such as a kitchen knife set or a makeup brush set.
- On the product directly, when the unit arrived without any packaging.
You will usually see these units when they come back to you through a removal order. Inside the removal box there is typically a return slip listing the Shipment ID, VRET ID, RA# and a process date. The slip describes the removal as a whole, while each LPN describes one unit inside it. Our guide on how to read an Amazon return slip walks through those fields line by line.
What is printed on an LPN sticker?
An LPN sticker typically carries the LPN code in human-readable text and a barcode that encodes the same value. Many stickers also show the FNSKU or ASIN the unit was received under, and sometimes a short product description or condition note.
Layouts differ between facilities and have changed over time, so treat the list below as a guide rather than a fixed specification.
| Element on the sticker | What it looks like | What it tells you |
|---|---|---|
| LPN code | Alphanumeric string, for example LPNR8K2M4QX7T | Unique ID of this one returned unit |
| Barcode | Linear barcode near the LPN text | Machine-readable version of the LPN |
| FNSKU | Usually starts with X0, for example X00ABC1234 | Which of your listings the unit was received as |
| ASIN | Usually starts with B0, for example B0C7XK2P9M | The catalog product the unit is tied to |
| Short title or note | Truncated product name or condition text | Helpful context, not an identifier |
The FNSKU or ASIN on the sticker reflects what Amazon recorded, not necessarily what is physically inside. That gap is exactly where disputes come from. If a sticker says your cordless hair clipper kit but the box holds a different product, the sticker becomes evidence of the mismatch.
Is the LPN the same as the FNSKU label?
No. The FNSKU label identifies your product listing and is the same on every unit of that listing. The LPN identifies one unit and is different on every returned unit. A returned unit can carry both: your original FNSKU label from when you sent inventory in, and the LPN sticker added when the return was processed.
How do I write the LPN correctly?
Write the LPN exactly as it appears in the FBA Customer Returns report: with the "LPN" prefix, in capital letters, and with no spaces, dashes or line breaks. For example, LPNR8K2M4QX7T, not R8K2M4QX7T and not LPN R8K2 M4QX 7T.
This sounds trivial, but a single wrong character means Seller Support cannot match your unit to the return record. The claim then stalls or comes back asking for information you already thought you provided.
Watch for look-alike characters
Printed stickers are small, and thermal print fades. The most common transcription errors come from characters that look alike:
- The letter O versus the digit 0.
- The letter I versus the digit 1, and sometimes the lowercase l.
- The letter S versus the digit 5.
- The letter B versus the digit 8.
- The letter Z versus the digit 2.
The safest approach is to not rely on your eyes alone. Scan the barcode with any barcode reader app and compare the result to what you typed. Then search for the value in your Customer Returns report. If the search returns exactly one row with the right SKU, you have it right.
A quick transcription routine
- Photograph the sticker straight on, in good light, with the whole code in frame.
- Scan the barcode and copy the decoded value.
- Confirm the value begins with LPN and contains no spaces.
- Search for the value in the license-plate-number column of your Customer Returns report.
- Check that the matching row's SKU, ASIN or FNSKU fits the product you are holding.
- Paste the confirmed value into your dispute notes, never retype it by hand.
How do I find a unit in the FBA Customer Returns report by LPN?
Download the FBA Customer Returns report from Seller Central, then search the license-plate-number column for the full LPN. The matching row is the return record for that exact unit.
Report menus move around, so look for it under the fulfillment or inventory reports section, or search Seller Central for "Customer Returns". Choose a date range wide enough to include the return. If the return happened a while before the unit reached you, widen the range rather than assuming the record is missing.
What the other columns tell you
Once you have the row, the surrounding columns give you most of what you need for a dispute:
- return-date: when the return was recorded. Useful for context and for checking current filing rules in Seller Central Help.
- order-id: the customer order the unit came from. Seller Support often asks for it.
- sku, asin, fnsku, product-name: what Amazon believes the unit is.
- quantity: how many units the row represents. For LPN-level records this is normally one.
- fulfillment-center-id: the facility that processed the return.
- detailed-disposition: Amazon's condition grading, such as SELLABLE, DEFECTIVE, CUSTOMER_DAMAGED or CARRIER_DAMAGED.
- reason: the return reason code the customer selected.
- status: where the return stands in Amazon's process.
- customer-comments: free text from the customer, when provided.
Two columns deserve special attention. The detailed-disposition shows how Amazon graded the unit. If the report says SELLABLE but you received an empty box or a different product, that contradiction is worth documenting. The customer-comments field sometimes explains what happened in plain words, which can support or contradict what you see in the box.
The Customer Returns report is not the only report you will use. Units reach you through removal orders, which appear in the Removal Order Detail report. Our article on removal orders vs. customer returns reports explains how the two connect.
Why does one LPN equal one line in a dispute?
Because an LPN identifies exactly one returned unit, each LPN should appear exactly once in your dispute, with its own description, photos and requested outcome. This keeps every claim traceable to a single return record.
When sellers group units ("3 units of the blender with attachments were missing parts"), Seller Support has to work out which units, which orders and which records. That creates back-and-forth and increases the chance that part of the claim is overlooked. When each unit has its own line, the reviewer can verify each one independently.
A clean line per unit usually contains:
- The full LPN.
- The order ID from the matching report row.
- The ASIN or FNSKU.
- A one-sentence factual description of what arrived versus what should have arrived.
- A reference to the photos for that unit.
Here is an illustrative example of how two units from the same removal box might be listed:
Unit 1 LPN: LPNR8K2M4QX7T Order ID: 111-2345678-9012345 ASIN: B0C7XK2P9M / FNSKU: X00ABC1234 Observation: Wireless earbuds received without the charging case. Expected contents: two earbuds, charging case, USB cable. Photos: unit1_product.jpg, unit1_lpn.jpg, unit1_slip.jpg, unit1_contents.jpg Unit 2 LPN: LPNT4W9H2ZK6D Order ID: 111-9876543-2109876 ASIN: B0C7XK2P9M / FNSKU: X00ABC1234 Observation: Retail box received empty. Expected contents: two earbuds, charging case, USB cable. Photos: unit2_box.jpg, unit2_lpn.jpg, unit2_slip.jpg, unit2_open_box.jpg
The IDs above are fictional. For guidance on wording and structure, see our Seller Support ticket template.
What if the LPN sticker is missing or unreadable?
If the sticker is missing or unreadable, you can still document the unit, but you must rely on other identifiers and be transparent about the gap. State clearly that no legible LPN was present and provide everything else you have.
Start by photographing whatever remains: a torn sticker, a faded barcode, or the spot where a sticker was removed. Even a partial code can help narrow the search in your report. Try scanning a damaged barcode anyway, since barcode readers can sometimes decode what the eye cannot.
Then gather supporting identifiers:
- The Shipment ID, VRET ID and RA# from the return slip in the removal box.
- The FNSKU label on the unit, if your original label is still attached.
- The removal order ID, which is the middle part of the RA#. For example, in RA# QW3M7-tRk8Vn2pLx-CHA1-1, the removal order ID is tRk8Vn2pLx.
- The process date printed on the slip.
With the removal order ID and the SKU, you can often narrow the Customer Returns report to a small set of candidate rows. Be careful here. If several units of the same SKU could match, do not guess and do not assign an LPN you cannot confirm. Describe the unit as "LPN not legible" and let Seller Support match it using the other identifiers.
Expect that claims without a confirmed LPN may take longer or be harder to resolve. That is one more reason to photograph every sticker as soon as you open a removal box, before handling or repacking can damage it.
What happens if the same LPN is uploaded twice?
Uploading the same LPN twice usually means one of two things: a duplicate photo set for the same unit, or a transcription error where two different units were recorded with the same code. Either way, resolve it before you file.
A true duplicate happens easily when you photograph a box, get interrupted, and photograph it again later. If you file both, Seller Support sees two claims for one unit. At best one is rejected as a duplicate. At worst it makes your other claims look less careful.
A false duplicate is more serious. If two physically different units show the same LPN in your notes, one of them is wrong. Re-scan both stickers and compare them to the report. Look-alike characters are the usual culprit.
Whether you track units in a spreadsheet or a dedicated tool, set it up so a repeated LPN stands out before it reaches a ticket. The rule is the same either way: one LPN, one unit, one line.
A simple deduplication habit
Keep a running list of every LPN you have documented, with the date and removal order it came from. Before starting on a new unit, check the list. A spreadsheet works fine. Later, the same list helps you match reimbursements back to your cases using the Reimbursements report.
How does the LPN fit into the rest of your evidence?
The LPN is the anchor that ties your photos, the return slip and the report row together into one verifiable story. Without it, even strong photos are hard for a reviewer to connect to a specific return.
A practical evidence set for one unit usually includes a clear photo of the product, a close-up of the LPN sticker, the return slip from the removal box, and either the box label or a second product shot showing the problem. Return Disputes is built around exactly that set: you upload the photos, and it reads the LPN and slip identifiers and drafts the ticket text for you to file in Seller Central yourself.
Whatever your workflow, make the LPN close-up sharp enough that someone else could read every character. If you can't read it confidently in the photo, a reviewer won't be able to either.
Frequently asked questions
Does every returned FBA unit get an LPN sticker?
Most customer-returned units that go through fulfillment center processing receive an LPN, but you may occasionally receive a unit without a visible sticker. Stickers can fall off, be placed on outer packaging that was discarded, or be damaged in transit. Document such units using the return slip and your FNSKU label instead.
Can I search the Customer Returns report without the LPN prefix?
A partial search may still find the row, but you should always record and submit the full value with the LPN prefix as it appears in the report. Using the complete value avoids ambiguity and makes the reviewer's lookup straightforward. Always confirm that exactly one row matches.
Why does the disposition in the report not match the condition of my unit?
The detailed-disposition reflects Amazon's grading at the time of processing, which may not match what you find when you open the box. A unit graded SELLABLE might arrive with parts missing or with a different product inside. That difference is worth documenting with photos and a neutral description.
Is one LPN ever linked to more than one unit?
An LPN is designed to identify a single returned unit. If you believe two units share one LPN, the most likely cause is a transcription error, so re-scan both barcodes and check the report. Keep each confirmed LPN on its own line in any dispute.
Where can I check the current rules for filing a claim on a returned unit?
Amazon updates its reimbursement policies and claim windows periodically, so check the current rule in Seller Central Help before filing. Search for the relevant FBA customer returns reimbursement policy there. Do not rely on dates or windows quoted in older forum posts or articles.