Amazon FBA Labeling Requirements and Where They Break in 2026

The symptoms show up in your Seller Central reports before anyone in the chain says the word label:

• One SKU sits at Receiving for days while everything else on the same pallet goes live.
• The reconcile tab shows one SKU short and a near-identical SKU long by roughly the same count.
• A review says the wrong item arrived, and the unit comes back with two barcodes on it.

Each of those traces back to a barcode that a scanner could not resolve, or resolved into the wrong record. A label is the smallest object in the shipment, and it is the only thing about your unit that a fulfillment center actually reads.

A label gets about a second of attention at an Amazon fulfillment center. An associate aims a scanner, the beam either resolves a barcode or it doesn't, and that is the whole conversation your product has with the building. Nobody turns the item over looking for a better side.

Three people can catch a bad label, and only one of them is cheap

Every labeling defect gets caught by someone. The only question is where, and each step costs more than the one before it.

• You, at your own table. The label gets peeled and redone. Cost: a label and a few seconds.
• Your prep contractor, at receiving or labeling. A warehouse that scan-verifies each unit catches it before the truck leaves. Cost: a line on an invoice and a message about the SKU that keeps doing it.
• Amazon, at check-in. Cost: delayed check-in, inbound defect charges, units unsellable while you file a case, and at worst a shipment returned or disposed of at your expense.

That third line got heavier at the start of 2026, when Amazon stopped labeling and prepping units inside its US fulfillment centers. Resellers felt that one first, since commingling ended in the same move.

The print that dies in transit, and the print that was never right

Same defect, two different origins. In the first, the label was crisp when you applied it, and weeks later, after a container and a hot dock, the black has gone gray-brown, the ink has smeared, or the toner has rubbed off where cartons ground together. In the second, the barcode is narrower than the one Seller Central generated, because a PDF got printed with scale-to-fit on or somebody rebuilt the label in a design tool.

Neither fails at your table. Both fail at check-in, on the other side of the country, where you cannot reprint. Amazon asks for a barcode that scans and makes no allowance for how good it looked the day you printed it.

Print the label at the size it was generated, on stock built for it, and leave the human-readable line under the bars alone: that is what an associate types when the scan fails. The accepted dimensions and print settings come with the label file itself. After that, media decides how long the label lives.

• Inkjet is the worst option for barcodes. The ink smears under moisture and handling.
• Direct thermal has no ink at all; the media darkens under heat, and it keeps darkening in a hot warehouse until the bars merge.
• Thermal transfer lays resin or wax onto the label and survives freight far better. It is what most prep floors run, for exactly this reason.
• Laser works if the toner is properly fused and the stock is matte. Glossy stock throws glare back at the scanner.

Neither version fails your own check, because your check happens on day one and the defect matures in week three. The only test at home that helps is a scan of a finished unit, not a look at it.

A second barcode still facing out

Your FNSKU sits neatly on the front of the box and the manufacturer's UPC is still fully visible next to it. Either the scanner takes the manufacturer barcode and the unit is received as something else, or a verification step flags the mismatch and the unit stops. Inventory that checks in under the wrong identity surfaces weeks later as a phantom shortage of one SKU and a phantom surplus of another.

The rule is one scannable barcode per unit. Every other code gets covered: a UPC, an EAN, a retail price sticker, an old FNSKU from a previous plan. Covering means opaque and complete, since a corner of a UPC peeking out is still two barcodes to a scanner. With commingled inventory closed to the large majority of products, the FNSKU is no longer the optional path it once was.

Multipacks and sets are the same defect wearing a costume. Leave component barcodes showing and the fulfillment center treats the components as separate sellable units. A set ships sealed, marked on the outside with wording such as "Sold as set," and showing one barcode: its own.

Transparency is the sanctioned exception: a second code carried on purpose, close to the product barcode, on a face the scanner sees. Combined label formats print both at once.

Caught by: your prep contractor, if they scan-verify. Otherwise Amazon, and the bill arrives as a mystery.

The label placed where a barcode cannot be read

The label bends over the edge of a carton. It lands across the seam where two flaps meet, or over the perforation on a tear-open pack. Or it wraps a bottle so the code reads around the curve.

At a fold, the bars distort and the scanner gets two half-images and no match. On a seam, the label splits when tape shifts in transit. On an opening, an associate chooses between destroying the label and destroying the packaging. On a curve, the outer bars stretch and the inner ones compress, so the code reads for you and not for them.

Flat surface, clear of seams, corners, and openings, with margin between the barcode and the edge of the panel, because scanners need quiet space around the bars. Where the surface has to be curved, turn the code so it reads up the bottle rather than around it, bars stacked like the rungs of a ladder. The beam then crosses each bar along a straight axis instead of sliding down a stretched one. Label people call it ladder orientation, and it is what makes round products behave.

The flat-panel versions you can catch by hand, if anyone at your table is looking. The curved one travels: an intermittent read passes a spot check at home and fails on a dock where nobody tries twice.

The label that lets go

A unit arrives with a clean rectangle of adhesive residue where the FNSKU used to be, or with the label loose in the bottom of the carton. The barcode was fine. The surface was wrong.

Label stock is rated for what it sticks to, and cheap stock assumes smooth, dry, room-temperature cardboard. Textured kraft, rough recycled corrugate, powder-coated metal, silicone-lined pouches, shrink film that keeps relaxing, and anything cold or faintly oily give a permanent adhesive less to hold; dust off a cutting table does the same. The label survives your table and lets go between the trailer and the belt, which reads downstream as a unit that was never labeled.

Press the whole label rather than the middle of it: a thumb tacks the center and leaves the corners proud, and a proud corner catches on every carton it passes. On difficult surfaces, ask your stock supplier for a high-tack or freezer-grade adhesive instead of buying by sheet count. Where the product refuses to hold a label at all, the bag becomes the labeling surface.

The label under the bag

A poly bagged unit with the FNSKU on the product and the bag over the top of it. Sometimes the code reads through the plastic. Sometimes the film is printed, wrinkled, or hazy and it does not. An associate then decides whether the bag is worth opening, and that unit either ships in a torn bag or gets set aside as unsellable.

The label goes on last, on the outside of whatever the customer receives. Bag first, then label the bag, and the same order for shrink wrap, bubble wrap, and any opaque overbox. Sequencing is why bagging and labeling usually share one station on a prep floor: split them across two shifts and somebody eventually runs them backward. The bag has its own list to answer to, from the suffocation warning to how much of a barcode survives the film (poly bagging requirements).

The right label on the wrong unit

This one looks like nothing, which is what makes it interesting. The label is crisp, correctly placed, correctly sized, and belongs to a different ASIN. Amazon receives the unit as the SKU on the label. A customer orders one thing, gets another, says so in a review, and the return comes back into inventory under an identity nobody can trust.

It comes from two lookalike variations labeled at the same table, a returned unit still carrying its old FNSKU under the new one, or a print run that started one label off. Color, size, and scent are the classic traps. The fix is a process rule: one SKU on the table at a time, a scan comparing what you applied against what you meant to apply, and old labels off before new ones go on.

Caught by: nobody, until a customer does. Longest fuse in the gallery.

An expiration date the receiver cannot see

A dated product inside a poly bag with the date printed on the bottle and nothing on the outside. A date written by hand in marker. A date in a format the receiving process does not accept. In dated categories each of those stops the unit at check-in, because Amazon treats the date as a receiving requirement rather than a paperwork detail.

The labeling half of the answer is short: printed rather than handwritten, in an accepted format, readable on the outer surface as the unit arrives, and repeated on each inner container of a case pack. A format Amazon does not take gets covered with one that it does. Category rules decide which products count as dated, and the accepted date formats are narrow enough to check before a run.

Caught by: your contractor, when dates are one of the lines on the inspection report you get back. Otherwise Amazon.

The defects that live above the unit

Unit labels get the attention. The two levels above them cost as much and get far less.

A box label doing a unit label's job, or one box label copied onto every carton

Both failures come from one confusion about levels. A box label identifies one carton in one shipment; a unit label identifies a product. Every carton gets a unique box ID, so copying one across the shipment hands the fulfillment center many copies of a single carton against one manifest line. Cartons carry a carrier shipping label as well, a third thing again. All of them go on flat panels, never across seams, and never on the top face of a carton bound for a pallet, since the next carton up hides it.

The version that catches experienced sellers is timing. Box labels belong to a shipment ID, and that ID moves when a plan is split, deleted, or rebuilt after a placement change. Labels printed before the split are correct labels for a shipment that no longer exists. Print them last, once the plan is final, and reprint the whole set rather than the cartons you think were affected. Box content information rides at the same level and travels with the box label, either through the shipping workflow or as a 2D barcode on the carton.

The pallet labeled on one side

An LTL pallet takes a label on each of its four sides, in the upper half of the load, facing outward, over the stretch wrap rather than under it, because a forklift driver approaches from whichever direction the trailer allows. Pallet labels do not replace box labels; every carton still carries its own. A pallet label under three turns of wrap is the same as no label, and it usually happens at the end of a long day.

Where each defect gets caught, and what it turns into

What you see	Who usually catches it	What it becomes if Amazon catches it
Faded, smeared, or rubbed-off print	Amazon	Exception handling, inbound defect charges
Label resized or redrawn in a design tool	You, with a scan off the print run	No read at all
FNSKU applied while the UPC still shows	Contractor, if scan-verified	Wrong identity received, two SKUs out of sync
Label over a corner, seam, or opening	You	Failed scans and torn labels at check-in
Barcode reading around a curve	Amazon	Intermittent reads, disputed counts
Label peeled off in transit	Amazon	Unidentified unit, no reimbursement path
Label under a poly bag or wrap	Contractor	Bag opened at receiving or unit set aside
Multipack with component barcodes exposed	Amazon	Set broken into singles, wrong quantity live
Right label, wrong SKU	The customer	Wrong item shipped, returns, defect metrics
Expiration date not visible from outside	Inspection	Dated units held at check-in
Box labels from a shipment ID that changed	You, if you reprint last	Cartons that scan into nothing
Pallet labeled on one side	Carrier or Amazon	Delays at the dock, reworked freight

None of this replaces the pass over a finished shipment, where unit, carton, pallet, and paperwork get checked in order. The 2026 shipment checklist runs that pass end to end. The habit that catches most of the table above is smaller: scan one finished unit off the top of the run and one off the bottom. Label defects rarely arrive one at a time. They arrive as a whole SKU.

When to stop doing this yourself

The quality question moved upstream this year. With the fulfillment centers out of the labeling business, the last hands that can catch any defect above belong either to your operation or to your contractor's.

Watch two places for it. The Inbound Performance dashboard surfaces prep and labeling defects by shipment, and the same defect repeating on the same SKU is a process problem rather than bad luck. The reconcile tab is the other: units that check in short, late, or as the wrong SKU are usually a labeling story before they become a counting story.

If you run arbitrage volume, lookalike variations, or anything dated, labeling is where the hours go. A warehouse that scan-verifies each unit as it labels catches most of this gallery before the truck leaves, and that is the argument for handing it over: not the labor rate, the catch rate. Our FNSKU labeling service runs in the same pass as receiving and inspection, and what that costs per unit is on the price list.

Label problems we get asked about

Do I still need an FNSKU on every unit?

For most sellers, yes. With commingling closed to the large majority of products, the unit needs a barcode that identifies your inventory rather than the product in general. A few categories and programs still work differently, and eligibility sits in Seller Central under FBA product barcode requirements.

Can I print FNSKU labels on sheet labels from an office printer?

Within limits. Matte white stock in the size the label file is built for, full scale with fit-to-page off, a laser printer rather than an inkjet, and one label scanned off the sheet before the rest go onto product. Thermal transfer still holds up better over months of storage and freight.

What actually happens if a unit arrives with no readable label?

It becomes an unidentified unit, and since the start of 2026 nobody downstream will finish it for you. Expect a stalled check-in and an inbound defect charge whose amount Seller Central will show you long before you ever trigger one. Expect a weak position afterward too: Amazon's wording is that units with missing or defective labels may not be traceable in its facilities, and untraceable inventory is not eligible for reimbursement.

Do I have to cover the manufacturer's barcode if I use an FNSKU?

Yes, and completely: UPCs, EANs, retail price stickers, old FNSKUs from an earlier shipment. Partial coverage is worse than none, because it produces reads that work some of the time, and intermittent failures are the hardest to trace.

Are box labels and pallet labels part of labeling requirements, or something separate?

Amazon treats them as separate steps in the shipping workflow, which is exactly why they get missed. Unit labels tell the building what a product is, box labels and box contents tell it what arrived, pallet labels tell a forklift driver where to take it. A shipment can be perfect at one level and fail at another, and the charges attach independently.