Amazon FNSKU Code: 2026 Label Requirements and FBA Prep

An Amazon FNSKU code is required when Seller Central assigns an Amazon barcode to an FBA offer. Under Amazon’s March 31, 2026 changes, resellers generally need Amazon barcode labels, while eligible Brand Representatives may use manufacturer barcodes for qualifying products. Always check the exact marketplace, Seller SKU, condition, and barcode setting before printing.

Amazon also ended prep and item labeling for US FBA shipments created on or after January 1, 2026. This guide explains how to retrieve the right file, control batch errors, and choose where labeling should be completed before inventory reaches Amazon.

Which FBA Products Need an Amazon FNSKU Code in 2026?

An FBA product needs an Amazon barcode when that barcode type is assigned to its offer. The requirement depends on the seller’s relationship to the brand, the product’s manufacturer barcode, and the offer setting in Seller Central.

Amazon ended inventory commingling for inventory shipped on or after March 31, 2026. Its official announcement establishes three main rules:

Seller and Product Situation	Is an Amazon Barcode Sticker Required?	What to Check
Brand owner with the Brand Representative selling role and an eligible manufacturer barcode	Not always	Confirm product eligibility and the offer’s barcode setting
Reseller without the Brand Representative selling role	Yes, even when the product has a manufacturer barcode	Use the Amazon barcode assigned to the FBA offer
Brand owner or reseller selling a product without a manufacturer barcode	Yes	Create the FBA offer and download the assigned Amazon barcode

A UPC does not provide a universal exemption. A reseller may need an Amazon FNSKU code even when a valid UPC is printed on the package. Brand Registry membership by itself is also insufficient. Amazon’s announcement refers specifically to sellers with the Brand Representative role.

The effective date applies to inventory shipped on or after March 31, not only to new listings. A reseller that previously used manufacturer barcodes may need Amazon barcode stickers for later replenishment. Remove outdated instructions and label files from supplier folders before the next production run.

Check the exact offer whenever you change marketplaces, variations, conditions, fulfillment channels, or listing records. Two sellers can list the same ASIN but receive different barcode requirements. Seller Central, rather than the package or the first characters of a code, should determine which barcode you use.

Before approving a production run, record the decision for every Seller SKU: marketplace, selling role, manufacturer-barcode eligibility, assigned barcode type, and effective shipment date. This short approval record gives purchasing, packaging, and warehouse teams the same instruction. It is especially useful during the 2026 transition, when older inventory and new replenishment may follow different barcode requirements.

How Is an FNSKU Different From an ASIN, Seller SKU, and UPC?

An FNSKU identifies inventory under an FBA offer and its barcode setup. An ASIN identifies an Amazon catalog page, a Seller SKU identifies the seller’s internal offer record, and a UPC or other GTIN identifies the commercial product.

Identifier	Assigned By	What It Identifies	Printed on the Unit?
ASIN	Amazon	A product page in Amazon’s catalog	No
Seller SKU	Seller or Amazon	A seller’s inventory offer	Optional
FNSKU	Amazon	Inventory associated with an FBA offer	Yes, when an Amazon barcode is required
UPC, EAN, JAN, or ISBN	GS1 system, publisher, or brand owner	A commercial product	Often

Amazon’s SKU guide explains the difference between seller inventory records and commercial product identifiers. A Seller SKU printed as plain text cannot replace an FNSKU label, and an ASIN should not be used as an item label.

Do not judge an FNSKU only by whether it begins with X00. The identifier displayed in Manage Inventory can reflect the offer’s barcode setup. Confirm the barcode preference and use the file Amazon generates.

For a business working with factories and a warehouse, the internal SKU can remain the common operational reference. The handoff file must then map that SKU to the correct marketplace, ASIN, Seller SKU, condition, and FNSKU.

Where Do You Find and Download the FNSKU in Seller Central?

Find the FNSKU on the correct FBA offer and download the item-label PDF from Seller Central. Menu names can change, so focus on validating the offer rather than memorizing one navigation path.

Confirm the Offer

Before downloading labels, compare these fields with your listing and purchase order:

Marketplace: The country where the inventory will enter FBA.
Seller SKU: The offer reference used in your ERP or warehouse records.
ASIN and Variation: The exact color, size, model, or pack count.
Condition: New, used, refurbished, or another applicable condition.
Fulfillment Channel: FBA rather than merchant fulfillment.
Barcode Setting: Manufacturer barcode or Amazon barcode.

Changing an account-level preference may not alter an existing offer. Follow the current Seller Central instructions if an offer was created with the wrong barcode setting.

Download the Item Labels

Open Manage Inventory or the current inventory view, select the FBA offer, and use the print item labels action. Enter the required quantity and download the Amazon-generated PDF. Do not create the underlying FNSKU with an independent barcode generator.

A missing FNSKU can mean that you are viewing the wrong offer, the listing is not set to FBA, or the offer uses a manufacturer barcode. It can also mean that you are looking at the ASIN instead of the FNSKU field. Never solve the problem by copying a label from a similar product.

Control the Handoff File

Keep the original PDF and a mapping file containing:

Internal SKU and product description
Marketplace, ASIN, Seller SKU, and FNSKU
Variation, condition, and sellable-unit format
Expected unit quantity
Label-file version and approval date

The product description gives warehouse staff a visual reference, while the version field prevents an old PDF from returning to production after a listing change.

What Are Amazon’s FNSKU Label Requirements?

An Amazon FNSKU label must be readable, connected to the correct offer, and visible on the final sellable unit. Other scannable product barcodes must be covered when the offer requires an Amazon barcode.

Print a Scannable Label

Amazon’s FBA prep and labeling guide specifies a scannable barcode, the FNSKU, the product title, and the item condition. Labels should use black ink on non-reflective adhesive-backed stock and measure 1 to 2 inches high by 2 to 3 inches wide.

Use these controls for each print batch:

Print from the approved Amazon PDF or an output that preserves its data and text.
Use 100% scale or no scaling when printing the Amazon template.
Keep the barcode sharp and leave its white space clear of logos or borders.
Replace faded media and correct printer problems before production.
Scan labels after printing and after applying them to the real package.

A clean PDF does not guarantee a readable physical label. Thermal darkness, stock quality, wrinkles, glare, and packaging texture can affect scanning. Approve a sample made with the same printer, label stock, and package that production will use.

Label the Final Sellable Unit

Place the FNSKU on the package Amazon will receive as one sellable unit:

Boxed product: Use a flat outside panel.
Poly-bagged or shrink-wrapped product: Put the label outside the final bag or wrap.
Multipack or bundle: Label the complete set represented by the offer.
Case pack: Label every sellable unit inside the shipping case when an Amazon barcode is required.

Do not apply a barcode across a seam, fold, edge, corner, or tight curve. If a factory labels the retail box and a warehouse later adds a protective bag, the label must remain visible and scannable outside the final preparation layer.

Prevent Competing Barcodes

Cover every other visible, scannable product barcode when the offer requires an Amazon barcode. Use an opaque label that covers the complete UPC, EAN, or old FNSKU, including the bars rather than only the printed numbers. Check retail cards and inserts visible through clear packaging.

Keep the item label separate from the other shipment labels:

Label Type	Placement	Purpose
FNSKU or item label	Each sellable unit	Identifies the product under the FBA offer
FBA box label	Shipment carton	Connects the carton to the inbound shipment
Carrier shipping label	Shipment carton	Routes the carton through the carrier network

Neither the FBA box label nor the carrier label replaces the unit-level item label.

Which FNSKU Errors Should Be Caught Before Shipping?

FNSKU quality control must confirm both scan quality and product identity. A label can scan successfully and still be wrong because it belongs to another variation, condition, marketplace, or offer.

Common unit-level failures include:

A valid label applied to the wrong color, size, model, or pack count
A label downloaded from another Amazon marketplace
New and used inventory sharing the same uncontrolled file
A bag, wrap, or sleeve hiding the barcode
An old FNSKU or UPC remaining scannable
Faded, wrinkled, damaged, or reflective labels
Components labeled separately when the Amazon offer is a bundle

Batch failures often begin with spreadsheets and file names. One supplier may receive a revised PDF while another continues using the previous version. When both batches reach the same warehouse, visually similar units can be mixed before anyone notices the change.

Use this check before carton sealing:

Approve the mapping: Match the internal SKU, description, ASIN, FNSKU, marketplace, and condition.
Reconcile quantities: Record received, labeled, rejected, reworked, and packed units.
Inspect the final package: Confirm label placement and coverage after bagging or bundling.
Scan the batch: Test the first unit, samples during production, and a final unit from each SKU batch. Increase inspection for first runs, relabeling, or mixed variations.
Archive evidence: Store the approved files, sample records, batch date, and exceptions.

Photos can prove placement and product match, but they cannot prove that the barcode data scans correctly. Keep item-label and carton-label files in separate folders, and use file names containing the marketplace, Seller SKU, FNSKU, revision date, and label type.

Treat a failed scan or product mismatch as a batch exception rather than an isolated sticker problem. Stop the affected SKU, separate completed and unprocessed units, identify the last accepted check, and determine which quantity may need reinspection. Record whether the cause was the source file, printer, label stock, placement, or product sorting. Resume work only after an approved sample passes both the scan and product-to-label check. This containment step limits how many finished cartons must be reopened when a problem is found late.

Where Should FNSKU Labeling Be Completed?

Complete labeling where your business can control the approved file, access the product, and correct errors before the FBA shipment leaves. The best location depends on catalog complexity, packaging stability, supplier count, batch size, and rework risk.

Amazon confirmed in an official staff response that it no longer offers prep and item labeling for US FBA shipments created on or after January 1, 2026. This also covers inventory entering US FBA through AWD, AGL, Amazon SEND, and the Supply Chain Portal. Shipments created before the cutoff may still receive the service even when they arrive later.

Labeling Location	Suitable Situation	Main Control
Factory printing	Stable listings, packaging, and high volume	Prevent obsolete data from being printed on a full packaging run
Supplier-applied stickers	A small catalog and a supplier with a verified process	Check variation matching, coverage, placement, and quantity
China warehouse or 3PL	Several suppliers, mixed SKUs, consolidation, or relabeling	Control mapping, batch separation, scanning, and evidence
Seller’s facility	Test batches or listings requiring a late review	Reserve enough time before the FBA appointment

Direct printing removes a separate application step, but it is difficult to correct after thousands of boxes are produced. Supplier-applied labels can work when there are few SKUs and the supplier can follow controlled files. Request a physical sample before approving the production batch.

A china warehouse can provide one control point when goods come from several factories. Inventory can be received by SKU, checked against the mapping, relabeled when approved, and consolidated into the outbound plan.

Whichever location you choose, send the final files before cartons enter global shipping. A late barcode change may require reopening cartons, isolating affected units, and repeating the quantity reconciliation.

How Can CFC Handle an Approved FNSKU Labeling Project in China?

CFC can review a China-based project involving SKU sorting, seller-approved labels, packaging, and outbound preparation. Confirm in the quotation whether the requested scope includes barcode printing, scan sampling, placement photos, relabeling, or removal of obsolete labels. The seller remains responsible for selecting the barcode type in Seller Central.

This setup can suit businesses using several Chinese suppliers or completing the final packaging after production. Prepare five items for the handoff:

The internal SKU, product description, ASIN, FNSKU, marketplace, condition, and quantity
The Amazon-generated PDFs with clear revision dates
The final sellable-unit format, such as a box, bag, multipack, or bundle
The acceptance criteria for placement, coverage, sampling, photos, and rejected units
The carton quantities, FBA box labels, destination, and required release date

After the approved item label is applied, CFC’s pick and pack services can keep similar SKUs separated and place units into the agreed protective packaging. Labeling can also sit within a wider order fulfillment sequence covering supplier receiving, inspection, packing, carton reconciliation, and release.

CFC should execute the seller’s approved mapping rather than decide which Amazon barcode an offer requires. If the marketplace, variation, condition, or offer changes, withdraw the previous file and issue a new approved mapping before work continues.

For a quote, send the SKU list, quantities, label PDFs, packaging photos, target marketplace, required checks, and dispatch date. If your suppliers are in China, CFC can review these labeling tasks as part of an ecommerce fulfillment workflow.

Frequently Asked Questions

Does Every Unit Need a Different FNSKU Code?

No. Identical units tied to the same seller, marketplace, offer, and condition normally use the same FNSKU. Each physical unit still needs a readable label when an Amazon barcode is required. Create a separate mapping for each variation, condition, marketplace, or offer record.

Does an FNSKU Replace Expiration-Date or Lot Labels?

No. An FNSKU identifies the FBA offer; it does not replace product-specific date requirements. Amazon’s expiration-dated inventory guidance requires applicable dates to remain visible, and lot numbers alone are insufficient for ingestible products. Check the current category and marketplace rules before covering information printed on the package.

Does a 3PL Need Access to Your Seller Central Account?

Usually not. You can export the Amazon-generated PDF and provide a controlled SKU mapping without sharing account credentials. If a missing code or incorrect barcode setting needs investigation, keep that task with an authorized Seller Central user and issue a new approved file after correcting the record.

How Much of an FNSKU Labeling Batch Should Be Scan-Tested?

Do not assume one sampling rate suits every batch. Define the check in the work instructions based on batch risk. A first run, mixed-variation batch, or relabeling project may require 100% product-to-label verification, plus scan tests at agreed intervals. Record failures and recheck the affected batch before release.