Overview

Amazon has upgraded the barcode‑scanning systems in its fulfillment centers, and the change now obliges every FBA seller whose items carry an FNSKU label that begins with “X” to conceal all secondary barcodes—UPC, EAN, or any manufacturer code—before the units reach an Amazon warehouse. The rule takes effect immediately, and non‑compliance can trigger processing delays, stranded inventory, or misallocation of stock to another seller.

Key Points

• FNSKU “X” prefix requirement — Only products labeled with an FNSKU that starts with the letter X must have every other barcode fully covered.
• Automation‑driven scanning — Amazon’s new scanners read the first visible barcode they encounter, so any uncovered UPC or EAN can cause a misread.
• Opaque label mandate — Sellers must use fully opaque stickers that block the original barcode; translucent labels are insufficient because scanners can see through them.
• Potential inventory loss — A mis‑scanned secondary barcode can assign a unit to the wrong listing, leading to days‑long case work and unavailable inventory.
• Broad seller impact — Private‑label, wholesale, and arbitrage sellers who apply their own FNSKU labels are all subject to the rule, even if they previously relied on manufacturer barcodes for identification.

What's Changing

1. Upgrade to high‑speed scanners — The fulfillment center now employs scanners that automatically capture the first barcode in the line of sight; for example, a box with a visible UPC alongside an “X”‑prefixed FNSKU will be logged under the UPC instead of the seller’s label.
2. Mandatory coverage of secondary codes — Sellers must place an opaque FNSKU sticker over every existing barcode, whether on the product’s packaging, the inner label, or the box. A common scenario is a multi‑pack of cosmetics that shows a UPC on the outer carton and an EAN on each individual bottle; both codes must be hidden.
3. Elimination of manual barcode selection — Previously, a human operator could choose the correct FNSKU among several codes; the new system lacks that discretion, so any visible secondary code creates a conflict that forces the item into a manual review queue.