What is FNSKU?

What is an FNSKU, and what does the label look like?

FNSKU stands for Fulfillment Network SKU. The code is a 10-character string that almost always starts with the letter "X", and it renders as a Code 128 barcode on the FNSKU label. A typical FNSKU example is X0024ABCDE printed above a barcode, often alongside the product title and a condition note. Amazon generates one FNSKU per SKU per condition when you set the item up for FBA.

The FNSKU label goes on the product (or its outer packaging) and must cover or replace any existing manufacturer barcode so scanners read your code, not the UPC. Amazon's stated FNSKU label size is a standard thermal label format, and many sellers print them on a dedicated FNSKU label printer. If you import goods, a common request to suppliers is to apply the FNSKU at the factory, which is what "FNSKU made in China" refers to: having the overseas manufacturer or your prep center print and stick the labels before the units ship.

• •Starts with X and is 10 characters long
• •Rendered as a Code 128 barcode on the label
• •One FNSKU per SKU, per condition (new vs used)
• •Must cover the manufacturer UPC/EAN on the unit
• •Printed on standard thermal label stock, often via a label printer

How FNSKUs get created, and when they change

You never invent an FNSKU yourself. Amazon assigns it the moment you convert a listing to FBA or create a new FBA offer, deriving it from the combination of your seller account, your SKU, and the item's condition. That derivation matters in practice: the same ASIN sold by you in New condition and in Used - Like New condition gets two different FNSKUs, because the warehouse must never ship a used unit against a new-condition order.

FNSKUs are stable, but not permanent. Delete an offer and recreate it under a new SKU and Amazon will usually mint a fresh FNSKU, which means any old labeled stock you send in later scans against a code that no longer maps to an active offer. Sellers hit this most often after a catalog cleanup or a migration between accounts: pallets arrive at the fulfillment center wearing last year's labels, receiving can't match them, and units sit in limbo or get logged as problems. Before you relabel or delete anything, export your current FNSKU list from the FBA inventory report and confirm which codes are still live.

There's also a choice to make at setup: Amazon lets some products use the manufacturer barcode (the UPC or EAN) instead of an FNSKU, which enrolls the stock in virtual tracking. It saves labeling labor, but it's the mechanism behind commingling, and eligibility depends on the product's condition and category rules. If unit-level accountability matters to you, and for reimbursement work it does, choosing the Amazon barcode (the FNSKU) is the conservative default.

FNSKU vs ASIN vs SKU

The cleanest way to keep these straight: the ASIN names the product, the SKU names your offer, and the FNSKU names your physical unit. The ASIN is shared across all sellers of a product. The SKU is your internal label that you assign and never changes unless you choose to. The FNSKU is what Amazon stamps on the actual item so the warehouse can route it back to your account.

Mapping FNSKU to ASIN is a routine task when you're auditing inventory or building a reimbursement case, because Amazon's lost-and-damaged reports often reference one identifier while your records reference another. The FNSKU is the one that proves ownership at the unit level, so it anchors any claim that Amazon owes you money. BeanHawk ties reimbursement events back through the FNSKU and SKU so the recovered amount lands against the right product cost in your books.

A worked example: tracing one lost shipment through the FNSKU

Say you send an inbound shipment of 200 units of a single SKU, all labeled with FNSKU X003EXAMPL, and your landed cost is a hypothetical $7.50 per unit. Amazon's receiving scan closes the shipment at 188 units. Twelve units, $90 of inventory at your cost, have vanished somewhere between your carrier's dock and the shelf.

The FNSKU is what makes that loss provable instead of arguable. Your shipment plan says 200 of X003EXAMPL went in. The received-inventory report says 188 of X003EXAMPL arrived. The delta is specific, unit-level, and tied to your account, which is exactly the evidence an inbound discrepancy case needs. If those units had gone in under the manufacturer barcode into commingled stock, the same discrepancy would be tangled up with every other seller's identical units, and your claim gets much harder to document.

Now follow the money side. If Amazon later reimburses you for the 12 units, the credit appears in your reports referenced by FNSKU, and the amount is based on Amazon's estimate of the unit's value, not automatically on your $7.50 landed cost. Suppose the reimbursement comes through at $6.80 per unit. You've recovered $81.60 against a $90 loss, and unless your records connect FNSKU to landed cost, that $8.40 shortfall disappears into the noise. Multiply small shortfalls across hundreds of events a year and the gap becomes a real number worth disputing with documentation.

Why the FNSKU matters for reimbursements and COGS

Because the FNSKU uniquely identifies your units, it is the foundation of FBA reimbursement recovery. When Amazon loses, damages, or destroys a unit, the event is logged against an FNSKU. To value that loss, and to confirm any reimbursement Amazon issues actually covers what you paid, you need the landed cost behind that FNSKU. A reimbursement that pays you less than your true unit cost is still a partial loss you should be tracking.

This is also why commingling matters. If you let Amazon use the manufacturer barcode instead of your FNSKU ("stickerless" / virtual tracking), your units can be pooled with identical units from other sellers. That speeds inbound but muddies accountability: a customer return or a warehouse error may be settled against pooled stock rather than your specific units, which complicates both reimbursement claims and accurate per-SKU inventory valuation.

How the FNSKU fits into your bookkeeping

Your general ledger never sees an FNSKU, and it shouldn't. Journal entries summarize revenue, fees, and COGS at the account level. The FNSKU lives one layer down, in the subledger that tracks which physical units you own, where they are, and what each one cost. Good amazon fba accounting keeps both layers and reconciles them: the subledger's unit counts times landed cost should equal the inventory balance on the books.

The practical annoyance is that Amazon's own reports don't agree on identifiers. Settlement reports speak SKU. Inventory ledger and adjustment reports speak FNSKU and ASIN. Reimbursement reports mix all three. Reconciling a lost unit to its cost means joining across those reports, which is tedious in a spreadsheet at ten SKUs and genuinely error-prone at a hundred. This is the mapping work that amazon accounting software should do for you: resolve FNSKU to SKU to ASIN automatically, attach landed cost at the unit level, and post the summarized result to QuickBooks or Xero. If you're comparing tools, ask whether the product actually ingests the inventory ledger at FNSKU level or just the settlement file; plenty of connectors do only the latter.

The same identifier plumbing is what separates serious reimbursement tooling from a dashboard. Amazon reimbursement software earns its keep by scanning FNSKU-level inventory events for losses Amazon never self-corrected, valuing each one against your real cost, and generating the evidence a case needs. A percentage-fee fba reimbursement service does the same work with humans in the loop and takes a cut of recoveries, which can still be the right call if you'd rather not manage cases at all. Either way, the honest comparison point is recovery net of fees, and either approach beats not filing. At small scale, checking the lost-and-found reports by hand every month is a perfectly workable third option; it just stops scaling around the point where your catalog and shipment volume outgrow one person's patience.

Common FNSKU mistakes

Most FNSKU problems trace back to one of a short list of process gaps, and almost all of them surface weeks later as receiving discrepancies, stranded inventory, or reimbursement claims you can't document. The fix is rarely clever. It's usually a checklist at labeling time and a monthly identifier audit.

• •Shipping units with the manufacturer UPC exposed, so scanners read the wrong barcode and the unit enters commingled or mismatched stock
• •Reusing old labeled stock after deleting and recreating the offer, so the printed FNSKU no longer maps to an active listing
• •Labeling two different conditions (new and used) with the same FNSKU, which guarantees wrong-item complaints
• •Printing labels that smudge, wrap around a seam, or sit on a curved surface where the barcode won't scan
• •Letting the factory print labels from a stale export instead of the current FBA inventory report
• •Keeping cost records only by SKU with no FNSKU mapping, which makes lost-unit claims slow to evidence
• •Ignoring the FNSKU column in reimbursement reports, so recoveries never reconcile back to specific units and costs

Frequently asked questions

What is an FNSKU on Amazon?

An FNSKU (Fulfillment Network SKU) is the Amazon-generated barcode that identifies a specific physical unit in an FBA warehouse as belonging to your account. It starts with X, is 10 characters long, and is applied to the product so Amazon can track and credit your inventory.

What does FNSKU stand for, and how is it different from a SKU?

FNSKU stands for Fulfillment Network SKU, and it's Amazon's barcode for your physical unit. Your SKU is the internal identifier you assign to an offer. Amazon derives the FNSKU from your SKU when you enroll the item in FBA, but the SKU lives in your records while the FNSKU lives on the warehouse shelf. The practical FNSKU meaning is narrower than the name suggests: it answers "whose unit is this", not "what product is this", which is why it's the identifier that carries a lost-inventory claim.

Where does the FNSKU label go on a product?

The FNSKU label goes on the outside of the unit (or its sellable packaging) and must cover any existing manufacturer barcode so scanners read your code instead of the UPC. Many sellers have a prep center or the overseas factory apply the labels before inbound shipment.

Do I have to use an FNSKU, or can I use the manufacturer barcode?

Some products are eligible to go into FBA under the manufacturer barcode instead of an FNSKU, which skips labeling but pools your stock with identical units from other sellers (commingling). If you care about proving which units are yours for reimbursements and returns, use the FNSKU. Check the current eligibility rules in Seller Central before deciding, because they vary by category and condition.

How do I convert an FNSKU to an ASIN?

Inside Seller Central, the FBA inventory and shipment reports list the FNSKU alongside its SKU and ASIN, so you can map FNSKU to ASIN there. Catalog and reimbursement tools can also resolve the relationship automatically when you're investigating a discrepancy.

What FNSKU label size should I print?

FNSKU labels print on standard thermal label stock sized to fit the barcode and text clearly without wrapping around edges or seams. A dedicated thermal label printer handles this cleanly; the key requirement is that the barcode scans reliably and fully covers the manufacturer code.

What happens if a unit goes in with the wrong or missing FNSKU?

Expect friction at receiving: units can be logged as problems, stranded, relabeled at a per-unit service fee, or received against the wrong offer. Wrong-condition mislabels are worse, since a used unit shipped against a new-condition order invites returns and account health complaints. A label check before every inbound shipment is cheaper than any of those outcomes.

What should software do with FNSKU data for accounting and reimbursements?

It should join the reports Amazon won't join for you: map every FNSKU to its SKU, ASIN, and landed cost, watch the inventory ledger for lost and damaged events, value each event at your real cost, and reconcile any reimbursement credits back to the units they cover. BeanHawk approaches it this way, and A2X and Link My Books cover the settlement-to-ledger side; whichever direction you go, confirm the tool works at FNSKU level rather than treating inventory as one blended number.

Related terms

Go deeper

• Amazon FBA Reimbursements in 2026: The Complete Guide
• FNSKU vs ASIN vs SKU: Amazon Barcode Labels Explained