Labeling for Amazon prep: FNSKU, suffocation warnings, and what triggers rejects
Labeling for Amazon Prep: FNSKU, Suffocation Warnings, and What Triggers Rejects
Amazon labeling is an identifier control problem, not a sticker problem. Every unit entering Amazon’s fulfillment network must carry the correct identifier in the correct position, readable by Amazon’s scanners, without ambiguity about which product it represents. When that fails — because of label drift, incorrect placement, or a missing suffocation warning — the unit either gets rejected at receiving or creates an inventory error that surfaces later as a customer complaint or account flag.
The solution is not more careful labeling. It is a controlled labeling process: map identifiers to SKUs before anything gets printed, verify scans before anything gets packed, and reconcile inventory states when identifiers change. Each of those steps has a specific failure mode. Understanding them is the operational starting point.
Why Amazon Labeling Is a Truth Problem
Labeling errors are rarely the result of carelessness. They’re the result of labeling without a verification step — processing units at speed without confirming that the label being applied matches the unit in hand.
FNSKU (Fulfillment Network Stock Keeping Unit): Amazon’s internal identifier that links a physical unit to a specific seller’s listing. Every unit enrolled in FBA must have an FNSKU label that replaces or covers the manufacturer barcode. Without it, Amazon cannot correctly attribute the unit to the seller’s inventory account.
ASIN (Amazon Standard Identification Number): Amazon’s product identifier, shared across all sellers who list the same product. An FNSKU is seller-specific; an ASIN is product-specific. A unit sent without an FNSKU — relying only on the manufacturer barcode — is vulnerable to commingling: Amazon may fulfill the seller’s order with a unit from a different seller’s inventory of the same ASIN.
The reason labeling becomes a truth problem is that Amazon’s system trusts what it scans. When a unit arrives with an FNSKU label, Amazon attributes that unit to the seller associated with that code and the listing associated with that ASIN. If the FNSKU is wrong — because it belongs to a different variant, a different listing, or an outdated version — the unit gets attributed incorrectly. The seller’s inventory position is wrong. The customer may receive the wrong item. The account may receive a performance notification.
The classic mistake here is not mislabeling intentionally — it’s labeling a mixed batch of units without physically sorting them first. A seller with three variants of a product (size S, M, L) prints labels in batches by variant. If the units aren’t segregated before labeling begins, labels end up on the wrong units. By the time the shipment arrives at the fulfillment center, the error is inside Amazon’s system, and correcting it requires a removal, relabeling, and reshipping process that costs time and fees.
The Identifier Hierarchy: Unit, Carton, and Pallet
Labeling for Amazon prep operates at three levels, and errors at any level create downstream problems.
At the unit level, each individual product must carry the FNSKU label in the correct position, covering or replacing the manufacturer barcode. The label must be scannable — no wrinkles, no partial adhesion, no placement behind a seal or flap that obscures it. If the product is polybagged, the label goes on the outside of the polybag, not on the product inside. This matters because the scanner at the fulfillment center reads what it can see. A label inside a polybag is a label that isn’t there.
At the carton level, each shipping box must carry a carton content label that declares the ASIN (or multiple ASINs) and the unit count inside. This is the document Amazon uses during receiving to verify what it’s receiving against what the inbound plan says it should receive. A carton whose declared contents don’t match the actual contents creates a discrepancy that Amazon’s system logs and the seller is eventually asked to explain.
Carton content label: A label applied to the outside of each shipping carton that identifies the ASINs and quantities inside. Required for all FBA inbound shipments. Amazon’s receiving team scans this label before opening the carton; any mismatch between the label and the contents triggers a discrepancy report.
At the pallet level (for LTL shipments), each pallet must carry a pallet label generated from the inbound plan, with the correct shipment ID, case pack configuration, and destination fulfillment center code. A pallet routed to the wrong center, or carrying a label from an earlier inbound plan, will be refused or rerouted at the seller’s cost.
The practical implication of this hierarchy is that labeling is not one step. It is three steps that must stay aligned with each other and with the inbound plan. A change in the plan — Amazon splits the shipment to route to two fulfillment centers instead of one — requires updates at the carton and pallet level. A change in the product — a new FNSKU issued because of a listing update — requires verification that every unit in the current batch carries the new code, not the old one.
Suffocation Warnings: What’s Required and Where Errors Cluster
Suffocation warnings are one of the most consistently mishandled labeling requirements in Amazon prep. The requirement is specific, the enforcement is real, and the failure mode is almost always the same.
Suffocation warning: A required printed warning on any polybag or plastic bag used to package a product where the bag opening is wider than 12.5 centimeters (approximately 5 inches). The warning must appear on the bag itself — not on an interior card, not on the product box inside the bag — in a font size proportional to the bag’s dimensions. Amazon’s specification ties font size to the surface area of the bag: larger bags require larger text.
The failure mode is predictable: a seller or prep facility adds the suffocation warning as a sticker or a card placed inside the bag. The bag arrives at the fulfillment center with no visible warning on the exterior. Amazon flags it during receiving. The shipment may be refused or the units may require rework.
The second failure mode is font size. A suffocation warning printed at the same size regardless of bag dimensions doesn’t meet the requirement for larger bags. Amazon’s specification is not advisory — it’s a receiving gate.
Where this gets operationally complex is in the distinction between bags that require the warning and bags that don’t. Not all polybags require a suffocation warning. The threshold is the 12.5cm opening measurement. A product in a small, tight polybag with an opening well under that threshold doesn’t require the warning. A product in a loose, standard clear polybag almost certainly does. The mistake is applying the same polybag spec — with or without the warning — to every product without checking the opening dimensions.
A carton of 24 units arrives at the fulfillment center. Half the units are polybagged with a compliant suffocation warning; half are in bags from a previous supply order that predates the warning requirement. Amazon’s receiving process doesn’t sort by compliance — it processes the whole shipment and logs the discrepancy. The seller receives a non-compliance notification and a request to remove or rework the affected units.
FNSKU Placement Rules That Create Receiving Problems
Correct FNSKU placement is specific enough that a label applied in the wrong position can fail Amazon’s scanning process even if the label itself is correct.
The general rule is that the FNSKU label must be scannable — meaning it must be on a flat, accessible surface, not obscured, not wrinkled, and not positioned where packaging structure (a fold, a seal, an indent) distorts the barcode. For most products, this means the largest flat surface of the outer packaging. For products in polybags, the label goes on the polybag, not inside it. For products with an existing manufacturer barcode, the FNSKU label must cover it completely — a partially covered barcode creates two scannable codes, which creates an ambiguity in Amazon’s receiving system.
For sets and bundles, the labeling requirement extends to indicating that the units are not to be separated. The packaging — not just the label — must make the set identity clear. A set of three items packaged together needs a label on the outer packaging that identifies the ASIN of the set, not the individual component ASINs. A receiving team that opens the carton and sees three loose items with individual labels, rather than a packaged set with a set label, logs a discrepancy.
The expert observation worth making here: the most common FNSKU placement failure is not on the unit itself — it’s on the polybag. Teams that have been labeling products for a long time develop muscle memory for where the label goes. When the workflow introduces polybagging, the label position changes, but the muscle memory doesn’t. Regular spot-checking of polybagged units, specifically for label position and legibility through the polybag, catches this before the carton is sealed.
Reconciling Identifiers When They Change
FNSKU changes happen. A listing is updated, a product variation is restructured, a multi-pack configuration changes, or a marketplace migration requires a new ASIN setup. Each of these events can generate a new FNSKU for inventory that may already be in the system — at the prep facility, at a fulfillment center, or split across both.
When an FNSKU changes, the operational risk is mixed inventory: units with the old FNSKU and units with the new FNSKU in the same location, attributed to the same product. In a prep facility, this means labeling the wrong units if the transition isn’t managed explicitly. Inside Amazon’s network, this means inventory reconciliation problems as Amazon’s system sees two FNSKUs for what appears to be the same product.
FNSKU reconciliation: The process of verifying and updating unit-level identifiers when a listing or variation structure changes. This includes quarantining existing labeled inventory, relabeling with the new FNSKU, and confirming inventory states in Seller Central before sending additional inbound shipments.
The controlled workflow for a transition is: freeze labeling on the affected ASINs, quarantine any labeled inventory that hasn’t shipped yet, confirm the new FNSKU from Seller Central, relabel the quarantined units, verify the inbound plan reflects the new FNSKU, and only then resume shipment. Skipping the quarantine step — continuing to label while waiting for confirmation — is how mixed FNSKU inventory gets into cartons.
The audit loop that catches drift early is simple: after every inbound shipment, verify that the FNSKUs in the shipment match the FNSKUs confirmed in Seller Central for those ASINs. This takes a few minutes and catches outdated FNSKU files before they propagate into the next shipment.
Frequently Asked Questions
Q: What is an FNSKU and why does it matter for Amazon prep? A: An FNSKU (Fulfillment Network Stock Keeping Unit) is Amazon’s seller-specific identifier for each unit you send to FBA. Every unit must have an FNSKU label that covers the manufacturer barcode — it’s how Amazon attributes inventory to your account rather than commingling it with other sellers’ stock. If the FNSKU is wrong, missing, or unreadable, Amazon cannot correctly receive the unit, and the error becomes an inventory problem or a receiving exception.
Q: Where does the FNSKU label go on a polybagged product? A: The FNSKU label goes on the outside of the polybag — not on the product inside the bag, and not on an interior card. Amazon’s scanning process reads what’s accessible on the outer surface. A label inside a sealed polybag is effectively not there from Amazon’s receiving perspective. The label must also be on a flat, unobstructed surface so the barcode reads correctly.
Q: When is a suffocation warning required on a polybag? A: A suffocation warning is required on any polybag or plastic bag where the opening is wider than 12.5 centimeters (approximately 5 inches). The warning must be printed directly on the bag — not on a card or insert placed inside the bag — and the font size must meet Amazon’s specification relative to the bag’s surface area. Failure to include the warning, or placing it on the inside of the bag, is one of the most common causes of Amazon prep non-compliance at receiving.
Q: What happens when an FNSKU changes for an existing product? A: You need to reconcile before sending more inventory. Freeze labeling on the affected product, quarantine any already-labeled inventory that hasn’t shipped, confirm the new FNSKU in Seller Central, relabel the quarantined units, and update your inbound plan to reflect the new identifier. Sending a shipment that mixes old and new FNSKUs for the same product creates inventory reconciliation problems inside Amazon’s system that are slow and costly to resolve.
Q: What is a carton content label and is it always required? A: A carton content label declares the ASINs and unit quantities inside each shipping carton. Amazon uses it during receiving to verify the shipment against the inbound plan. It is required for all FBA inbound shipments unless you’re using Amazon’s carton content scanning workflow, which requires a specific setup. A carton without a content label — or with a content label that doesn’t match what’s inside — triggers a discrepancy log at receiving, which can delay your inventory becoming available for sale.
If you’re setting up an Amazon prep workflow for the first time — or have had recurring labeling issues that create receiving exceptions — share the product profile and packaging format and we’ll clarify what a controlled labeling process looks like for your SKUs.