FNSKU vs ASIN vs SKU: Amazon Barcode Labels Explained

Every unit you send to FBA carries three identities at once. The SKU is yours, the ASIN is Amazon's catalog ID, and the FNSKU is the barcode that ties a physical unit on a fulfillment center shelf back to your seller account. Mix them up and the consequences are concrete: shipments rejected at check-in, your inventory commingled with a counterfeiter's stock, or a lost-unit reimbursement claim you can't file because you can't say which FNSKU went missing.

This guide covers what an FNSKU code on Amazon actually is, when you must apply an FNSKU label versus shipping with the manufacturer barcode, how to print the labels correctly, and why the FNSKU is the unit of account for every inventory reconciliation and reimbursement claim you'll ever file.

What Is an FNSKU?

FNSKU stands for Fulfillment Network Stock Keeping Unit. It's a short alphanumeric identifier (typically around 10 characters, usually starting with X0) that Amazon generates when you convert a listing to Fulfilled by Amazon. The FNSKU is printed as a barcode (with the code and a product name abbreviation beneath it) and applied to each unit so Amazon's scanners can attribute that exact physical item to your seller account.

That last part is the point. An ASIN identifies a product in Amazon's catalog; an FNSKU identifies your stock of that product. If five sellers sell the same ASIN, there are five different FNSKUs for it. When a unit with your amazon FNSKU barcode is scanned at receiving, picked for an order, or counted in a cycle count, the event lands in your inventory ledger, not a competitor's.

The FNSKU is also account-specific and marketplace-network-specific. The same product in your account will have a different FNSKU than in someone else's account, and if you ever merge or migrate accounts, plan for relabeling.

FNSKU vs ASIN vs SKU: Who Uses Which

The three identifiers answer three different questions, and each one matters to a different system in your business.

• •SKU (Merchant SKU / MSKU): created by you, used by your own systems. It's how your accounting software, purchase orders, and inventory valuation track a product. Example: BH-GRINDER-BLK-2026.
• •ASIN: created by Amazon, one per catalog product per marketplace. It's what customers land on and what your listing, reviews, and Buy Box attach to. Example: B0ABC12345.
• •FNSKU: created by Amazon for FBA, one per product per seller account. It's what the fulfillment network scans. Example: X0012ABC34.
• •UPC/EAN (manufacturer barcode): created by GS1 for the brand. Amazon can fulfill against this barcode instead of an FNSKU — but only under specific conditions, covered next.

When Amazon Requires an FNSKU Label vs the Manufacturer Barcode

When you create an FBA listing, Amazon assigns a barcode setting: manufacturer barcode (UPC/EAN) or Amazon barcode (FNSKU). With the manufacturer barcode setting, you ship units as-is and Amazon tracks them by the UPC. With the Amazon barcode setting, every unit needs an FNSKU label covering or replacing any other scannable barcode.

Amazon generally requires the FNSKU label when the manufacturer barcode option isn't available or safe to use. Common triggers include: the product has no scannable UPC/EAN, the same UPC maps to multiple conditions (new vs used), the item is in a category or program where Amazon mandates per-unit labeling, expiration-dated products that need lot-level tracking, or you've deliberately opted out of commingling.

Practical rule: unless you have a specific operational reason to use the manufacturer barcode, choose the Amazon barcode setting in your account's FBA settings and label everything with the FNSKU. The labeling cost is small; the traceability is worth it. One caution — the barcode setting is hard to change once you have inventory in the network under the old setting, so decide before your first shipment, not after.

How to Print FNSKU Labels (Without Getting Flagged at Check-In)

Label mechanics are simple but unforgiving. The FNSKU barcode must scan; a label that smudges, wraps around a corner, or sits on a curved seam will fail at receiving and can get the shipment placed in problem status.

You have three options for who applies labels: you (print from Seller Central onto label stock), your supplier or prep center (send them the PDF — most experienced FBA suppliers apply FNSKU labels at the factory for a few cents per unit), or Amazon's FBA Label Service, which charges a per-unit fee to label for you. Factory labeling is usually cheapest at scale; just require a photo of a labeled unit before the production run ships.

Commingled vs Labeled Inventory: The Real Risk

Using the manufacturer barcode opts you into commingled (stickerless) inventory. Your units are pooled with identical units from other sellers and the manufacturer, and when a customer orders from you, Amazon ships whichever pooled unit is closest — not necessarily one you sourced.

The upside is real: no labeling cost, faster prep, and inventory that can be fulfilled from more locations. The downside is that your account absorbs the quality of the worst seller in the pool. If another seller dumps counterfeit or shopworn units into the commingled pool and one ships against your order, the resulting complaint, return, or authenticity claim lands on your account health. You did nothing wrong and you have limited ability to prove it, because the unit that shipped was never physically yours.

Commingling also muddies reconciliation. With FNSKU-labeled stock, a discrepancy between your records and Amazon's is a clean question: where did my labeled units go? With commingled stock, attribution runs through Amazon's pooled bookkeeping. For most private-label and brand-registered sellers, the FNSKU label is cheap insurance; commingling makes sense mainly for high-velocity, low-risk replenishables where you trust the pool.

FNSKU Is the Unit of Account for Reimbursement Claims

Here's the part most sellers miss: when FBA loses or damages your inventory, the claim is filed and paid per FNSKU/SKU. Amazon's inventory ledger records every receipt, sale, return, removal, and adjustment against the FNSKU. A lost-unit claim is essentially an argument that the ledger doesn't balance for a specific FNSKU — units in, minus units out, doesn't equal units on hand.

The timing rules got much tighter. As of October 23, 2024, claims for inventory lost or damaged in fulfillment centers must be filed within 60 days, down from the far longer window Amazon previously allowed. Since November 1, 2024, Amazon has auto-reimbursed many US lost-inventory cases — helpful, but auto-reimbursements only catch what Amazon's own systems flag. And since March 31, 2025, reimbursements are valued at your manufacturing or sourcing cost (Amazon's own estimate unless you provide your costs), excluding your margin and fees. That makes two things matter: filing fast, and having your per-SKU cost data on record so you aren't paid on Amazon's lowball estimate.

Clean FNSKU-level records are what make any of this work. If you can show 500 units of FNSKU X0012ABC34 shipped, 480 checked in, and no adjustment ever restored the missing 20, you have a claim. This is the audit BeanHawk runs automatically — a free FBA reimbursement audit (no card, you keep 100% of recoveries) that reconciles your inbound shipments and inventory ledger per FNSKU and flags the discrepancies worth claiming before the 60-day window closes.

A Worked Example: What One Mislabeled Carton Costs

Say you ship 300 units of a $25 product across two cartons, but your supplier applied the FNSKU label for a different variant to one carton of 100 units. At check-in, those 100 units scan as the wrong FNSKU. Your ledger now shows 200 received of the SKU you actually shipped and a phantom 100 of a variant you didn't.

The fallout compounds. The 'missing' 100 units can trigger a research case you must resolve within the 60-day claim window. Meanwhile the mislabeled units sell against the wrong listing — wrong price, wrong photos, near-certain returns. On a $25 sale price with a referral fee in Amazon's typical 8-15% range plus fulfillment fees and return processing, each wrong-item sale can flip a roughly $6 expected profit into a loss, while your variant listing collects negative reviews. A two-minute label check at the factory — photo of a labeled unit, FNSKU verified against Seller Central — is the entire prevention plan.

Keep SKU, ASIN, and FNSKU Tied Together in Your Books

The accounting failure mode is fragmentation: your purchase orders track your internal SKU, Amazon reports settlements by SKU and inventory by FNSKU, and your books track neither. When a reimbursement hits your settlement, you need to know which SKU it relates to and what that unit cost you — otherwise recovered cash gets booked as miscellaneous income and your inventory valuation quietly drifts from reality.

Keep one mapping table — internal SKU to Amazon SKU to FNSKU to ASIN — and treat it as a controlled document. Record landed cost per SKU so reimbursement valuations can be checked against your real sourcing cost, not Amazon's estimate. BeanHawk handles this end to end: perpetual SKU-level inventory valuation, a PO and landed-cost engine, and summarized settlement journals posted to QuickBooks Online or Xero, with flat all-channel pricing from $19/mo. However you do it, the principle stands — the FNSKU is where Amazon's physical reality meets your financial records, and every reconciliation runs through it.