FNSKU vs. Manufacturer Barcode — Amazon FBA Requirements

Overview

Amazon FBA requires every unit to carry a scannable barcode, but which barcode is required depends on the seller's relationship to the product. Confusing these two barcode types — or allowing Amazon to incorrectly flag a shipment — can block inventory from entering FBA and stall sales entirely.

This distinction surfaced during a January 2026 review of ^[1]'s account, where Amazon incorrectly required an FNSKU on a manufacturer-owned product, blocking ~1,000 units of high-selling yellow cornmeal from entering FBA for over a month.

The Two Barcode Types

FNSKU (Fulfillment Network Stock Keeping Unit)

• An Amazon-generated barcode assigned to a specific seller's listing.
• Required when a seller is a reseller (i.e., they did not manufacture the product).
• Must be printed on a label and physically applied to every unit before shipment to FBA.
• Ensures Amazon can attribute the inventory to the correct seller in a commingled warehouse environment.

Manufacturer UPC / EAN

• The brand owner's barcode, registered through GS1 and printed directly on the product packaging.
• Permitted — and preferred — when the seller is the manufacturer and owns the UPC code.
• When creating a listing, the seller selects "Use manufacturer barcode" to indicate this status.
• No additional labeling is required; Amazon should accept the product as-is.

When Each Applies

Amazon Errors and the Dispute Process

Amazon's receiving systems can incorrectly flag manufacturer-barcoded shipments as requiring an FNSKU. This is an Amazon-side error, not a seller error, and it must be disputed promptly.

How to Dispute

1. Navigate to the affected shipment in Seller Central.
2. Locate the defect detail — look for a "Defect Quantity" row citing a barcode mismatch.
3. Click Submit Dispute.
4. In the dispute text, clearly state:
   - The brand is the manufacturer of the product.
   - The product has always been sold using the manufacturer's UPC.
   - The seller is not required to use Amazon barcodes (FNSKU).
   - The UPC is registered to the brand through GS1.
5. Submit — Amazon should be able to verify manufacturer status through the listing configuration.

Supporting Evidence

• The listing itself should already be configured to "Use manufacturer barcode."
• GS1 registration records confirm UPC ownership.
• Historical shipment records showing the same product was previously accepted without FNSKU.

From the Doodla case: "Doodla Farms is the manufacturer of this product. We have always sold it using the manufacturer's UPC code. We are not required to use Amazon barcodes." — Mark Hope, January 2026

Operational Impact of Barcode Errors

Inventory blocked by a barcode defect:
- Shows as "Inbound" in Seller Central but never transitions to "Available" FBA stock.
- Cannot be sold, even if physically present at the fulfillment center.
- Causes stockouts on high-velocity SKUs, directly suppressing sales and ROAS.

In the Doodla case, the error went undetected for approximately one month, contributing to a ROAS decline from ~3.8 to 3.29 and sales reverting to September levels during what should have been a strong post-holiday period.

Prevention and Monitoring

• Check shipment status within 1–2 weeks of the expected receiving date. If units remain "Inbound" beyond that window, investigate immediately.
• Look for "Defect Quantity" rows in shipment details — these indicate units Amazon has rejected or flagged.
• Maintain a shipment tracker with columns for: request date, ship date, expected arrival, and FBA status. This makes delays visible at a glance.
• When setting up new listings for manufacturer brands, always confirm the barcode setting is "Use manufacturer barcode" — not "Use Amazon barcode (FNSKU)."

Related Articles

• ^[2]
• ^[3]
• ^[4]