FNSKU Amazon FBA Definition
The FNSKU Amazon FBA barcode is a 10-character code (like X001ABC234) Amazon generates when you create or convert a listing for FBA. It’s printed as a Code 128 barcode and scanned at every step of the FBA workflow: receive, putaway, pick, pack. The FNSKU pairs the physical unit to your seller account inside the warehouse, separating your inventory from another seller’s identical-ASIN units. Stickerless commingling exists but only for sellers who specifically opt in; default is FNSKU labeling.
You’ll see FNSKUs in Seller Central under Manage FBA Inventory. They are not the same as your seller SKU (your internal identifier) or the ASIN (Amazon’s product identifier). The mapping is:
- ASIN → product catalog page (one per product)
- Seller SKU → your internal name (whatever you choose)
- FNSKU Amazon FBA → Amazon’s warehouse barcode for your specific unit
Most prep centers and 3PLs apply FNSKU labels for you. If you ship with manufacturer barcodes (UPC/EAN) and have stickerless commingling on, Amazon may pool your units with other sellers’ identical units, which creates risk around inauthentic-claim allegations on items you didn’t actually ship.
FNSKU format
Example: 2,800-unit private label shipment
A private label seller with 18 active SKUs is preparing a 2,800-unit shipment to a Texas FC. They run the Print Item Labels workflow in Seller Central:
- Each FNSKU label includes the 10-character code, the seller SKU, the product title, and a Code 128 barcode
- The seller exports labels in 30-up Avery 5160 format
- Two options: send the PDF to their China supplier for application before ocean freight, OR ship unlabeled to a US prep center for ~$0.18 per unit
For this 2,800-unit shipment:
- Supplier-applied FNSKU labels: $0 incremental (cost rolled into supplier price)
- US prep center FNSKU labels: 2,800 × $0.18 = $504
Skipping FNSKU labels and relying on stickerless commingling would save $504 BUT exposes them to the risk of receiving customer returns from another seller’s lower-quality unit, with the inauthenticity claim landing on their account. For private-label sellers, the $504 is cheap insurance.
Why FNSKU matters for FBA sellers
FNSKU Amazon FBA vs. UPC/EAN matters most when you have a private-label brand. If you sell on a shared listing without registering your brand via Brand Registry, multiple FNSKUs (one per seller) coexist on the same ASIN. Each seller’s FBA inventory is tracked separately by FNSKU. With Brand Registry and a unique ASIN, you control the listing entirely and your FNSKU is the only one in play.
A second wrinkle: when you change ASINs (re-merge variations, recreate a listing), the FNSKU usually changes too. Any units in FBA with the OLD FNSKU label won’t match the new SKU and become stranded inventory. This is one of the most common causes of stranded SKUs at $1M+ accounts.
Common mistakes
- Reprinting after listing changes without recalling units. Updating a listing can generate a new FNSKU; old units in FBA become stranded.
- Skipping FNSKU labels under stickerless commingling. Saves a few cents per unit but exposes the brand to inauthentic claims from other sellers’ returns.
- Confusing FNSKU with seller SKU. They look similar in Seller Central screens. Always verify barcodes by scanning a sample before sending the whole pallet.