Why prep and labeling exist in the first place

Amazon's fulfillment network moves something like 15 billion units in and out of its warehouses every year. Nobody opens every box to check what is inside. The system assumes every unit arrives scannable, correctly labeled and prepped the way its category requires, because the alternative is a warehouse full of people squinting at shampoo bottles to work out whether they belong to you or the next seller.

Sellers who treat prep and labeling as box-ticking tend to miss this. An FNSKU label is how a robotic pick system and a human associate both know, in under a second, which listing a unit belongs to. A poly bag on a loose-fitting item is the only thing protecting it from whatever gets stacked on top of it in a bin. Skip the step and you send in a unit the system cannot handle correctly. Further down the line that turns into a miscount, a lost unit, a damaged return, or a customer complaint that had nothing to do with your product's quality.

WHY THIS COSTS MORE THAN IT LOOKS LIKE IT SHOULD

A single mislabeled case pack can hold up a whole shipment plan, beyond the units in that one box. Amazon does not always receive part of a shipment and move on. Depending on the issue, the entire shipment can sit in "problem" status, with inventory that is neither sellable nor recoverable, which is the worst place for stock to be.

The mistakes that actually get shipments flagged

Most rejections come from a short list of repeat problems. If you have been doing FBA for a while, you have probably hit at least two of them.

  • FNSKU label placement. The label goes over the manufacturer barcode when the item should keep it visible, or fails to cover it when the rule says it must, and the scanner reads the wrong barcode or finds two competing barcodes on one unit.
  • Missing poly bags or bubble wrap. Items with loose parts, sharp edges, liquids or small parts that pose a choking hazard each carry a specific prep requirement, and Amazon lists it at ASIN level. Ship one in bare retail packaging when it needs a poly bag and it is either held at receiving or, worse, received and then damages a neighbouring unit in the bin.
  • Box weight or dimensions that do not match the shipment plan. You build the plan with estimates, pack the real boxes and never go back to correct the plan before it ships. Amazon catches the mismatch at the receiving dock, and the discrepancy has to be resolved before those units count as received.
  • Mixed SKUs in a box without the right labeling. Some shipment types allow mixed-SKU cases, some need case-level labels stating exactly what is inside, and some do not allow mixing at all. Pack every case the same way across shipment types and sooner or later one gets rejected.
  • Expiration-dated goods without proper date labels. Supplements, food and cosmetics with a shelf life need the expiration date printed in a specific format and location. Miss it and the units are usually flagged before they are put away.

None of these are unusual. They are the five or six things that come up in almost every seller forum thread about a stuck shipment, because they are what Amazon's automated systems are built to catch.

The fastest way to see what Amazon expects for a given ASIN is inside the shipment workflow itself. In Seller Central, start a shipment with Send to Amazon (from Inventory, then FBA Inventory or the Shipments page). When you choose the SKUs to send, each one shows its prep category and who is responsible for prep and labeling, and you can open the prep guidance from there. Check it every time; do not rely on what the listing needed last year.

How you find out something's wrong

There is a good version of this and a bad one. In the good version, your shipment sits in "working" status noticeably longer than your other shipments to the same fulfillment center, or Seller Central's Shipping Queue shows a problem notification naming the issue, such as an FNSKU mismatch or a missing prep category. That is your cue to look straight away.

The bad version is a partial receive with no obvious explanation. You sent 500 units, Amazon confirms 460, and nothing tells you what happened to the other 40. Sometimes it is a simple miscount on the warehouse floor. Sometimes those 40 units were flagged for a labeling issue and routed to a separate problem-resolution queue that does not show up clearly in your shipment summary. Either way, you are reconciling after the fact when you could have caught it beforehand.

Worst of all is not noticing until an inventory reconciliation weeks later turns up a gap you cannot explain, by which time the paper trail, if there ever was one, has gone cold. High-volume sellers check the Shipping Queue daily during an active inbound for this reason.

When the received count is short, open the shipment and look at its reconcile view, which compares units shipped with units received and lets you research the gap or request an investigation once Amazon has finished receiving. Have your packing list, box contents and carrier proof of delivery ready before you start, because Amazon will ask for them. Our guide to FBA receiving discrepancies walks through that process in detail.

The pre-shipment checklist that actually prevents this

Most of this friction can be avoided with a five-minute check before the shipment leaves the warehouse. Run it on every shipment, including ASINs you have shipped a hundred times before.

  • Pull the current prep requirements for each ASIN. Category prep rules live in Seller Central and they do change. A product that did not need a poly bag six months ago might need one now, so do not work from memory or last quarter's packing instructions.
  • Check that FNSKU labels are placed correctly and scan cleanly: flat, not wrinkled or curling, positioned exactly where the prep guidance says, and covering (or leaving visible) the original barcode as that item requires. Scan a few with a phone or handheld scanner before sealing.
  • Weigh and measure each packed box before sealing it, and correct the shipment plan if the real numbers differ from the estimates you used when you built it.
  • Give date-sensitive and near-hazmat categories their own extra pass. Anything with an expiration date, or that is flammable, pressurized or borderline hazmat, has the least room for error and the most specific documentation requirements.
  • Confirm the case-pack labeling suits the shipment type. If you are mixing SKUs in a box, make sure the shipment type allows it and that the case labels list exactly what is inside.

If a 3PL or prep center handles this for you, the checklist should already be part of their standard procedure. If it is not, raise it with them.

A worked example

Here is how one bad label plays out, with illustrative numbers. A seller sends 6 boxes of 80 units each, 480 units in all. On the last box, the packer applies FNSKU labels from a different variation (the blue instead of the green). The blue labels scan, so nothing stops at the dock, but 80 green units are now recorded as blue. The blue listing shows more stock than exists, the green listing shows less, and the first customers to order blue receive green. The fix (a removal, relabel and resend, plus handling the complaints) costs far more than the minute it would have taken to scan one unit from each box against the shipment plan before sealing.

What to do when a shipment gets held anyway

Start by finding the named reason behind the generic status. Seller Central's Shipping Queue and the shipment's problem log usually state the specific requirement that was not met, whether a prep category, a labeling issue or a discrepancy in received quantity. The system will tell you if you look in the right place, so there is no need to guess.

Next, work out where the shipment physically is. If it has not been picked up or is still in transit, you may be able to fix the problem and resubmit before it reaches the fulfillment center. If it has already arrived and been flagged at receiving, you are in a different process, usually a Seller Support case or a removal or disposal decision for the affected units. Treating that like a pre-shipment fix wastes time you do not have.

Then decide whether it is a one-off or a pattern. One flagged shipment in the last year: fix it and move on. Repeat issues across several shipments usually mean a process problem at your warehouse or with your in-house team. At that point a prep service or 3PL that contractually commits to compliance starts to pay for itself. What you are buying is the end of these conversations; the poly bags are incidental.

Amazon can also prep or label noncompliant units itself when they arrive, charging you for the work. That keeps inventory moving, but the fees add up on every unit, and repeated issues can affect your inbound performance. Treat any unplanned prep charges on your statement as a signal to fix the cause at source.

KEEP A PER-ASIN PREP RECORD

Every time you check prep requirements for an ASIN, save a dated screenshot or note. Requirements change without much notice, and a record of what was required on the day you shipped makes any dispute with Amazon much faster to resolve, because you are not arguing from memory.

Why this matters more as Q4 gets closer

The mechanics of a flagged shipment are the same in July and November. The resolution time is not. A labeling issue that takes two or three days to sort out in a quiet month can take two or three weeks once fulfillment centers hit peak volume, because receiving, problem resolution and Seller Support case review are all backed up with everyone else's inbound freight at once.

Sellers who ship inbound freight during Q4 routinely report inbound processing and problem-resolution timelines running two to three times longer than off-peak months, simply from fulfillment center volume.

That gap is the strongest reason to get prep right first time as the calendar tightens. In June, a shipment stuck for a few days is an annoyance. In late October, the same delay can mean inventory arriving after your best selling window has started, and the cost becomes lost sales. Build a real buffer into Q4 shipments and run every prep check without exception in the two months before peak, because the cost of a mistake grows with how backed up the system already is. Our Q4 readiness playbook covers how to schedule inbound work around those cut-offs.

The bottom line

Prep and labeling problems are among the more frustrating kinds of FBA friction because they are preventable. The requirements are documented in Seller Central, sometimes a few clicks deeper than they should be, and they do not change so often that skipping the check is reasonable. Nearly every shipment held over a missing poly bag or a mismatched box weight was a five-minute check away from going through cleanly.

Run the checklist on every shipment, keep your per-ASIN prep records current, scan a sample of labels before sealing, and tighten the routine in the run-up to peak season.

Frequently Asked Questions

Why did Amazon flag my FBA shipment for a prep or labeling problem?

Most rejections trace to a short list of repeat offenders: FNSKU label placement errors, missing poly-bagging or bubble wrap where the ASIN requires it, box weight or dimensions that don't match the shipment plan, mixed SKUs without the right case labels, and expiration-dated goods missing proper date labeling. Amazon's automated systems are built to catch exactly these.

Amazon only received 460 of the 500 units I sent. What happened to the rest?

A partial receive with no explanation is usually one of two things: a straightforward miscount on the warehouse floor, or units flagged for a labeling issue and routed to a separate problem-resolution queue that doesn't show up cleanly in your shipment summary. Check Seller Central's Shipping Queue and the shipment's problem log for the named reason.

How long does a stuck FBA shipment take to resolve during Q4?

Far longer than off-peak. A labeling issue sorted out in two or three days during a slow month can take two or three weeks once fulfillment centers hit peak volume, because receiving, problem resolution and Seller Support case review are all backed up at once. Sellers routinely report inbound timelines running two to three times longer.

Do prep requirements change for an ASIN I've already shipped many times?

They do, which is why shipping an ASIN a hundred times before is no reason to skip the check. Category-specific prep rules live in Seller Central and a product that didn't need poly-bagging six months ago might need it now. Pull current requirements per ASIN each time and save a dated screenshot as your record.

Where do I see the prep requirements for a specific ASIN?

In the Send to Amazon workflow. When you select SKUs for a shipment, Seller Central shows each one's prep category and whether you or Amazon is responsible for prep and labeling, with a link to the guidance for that category. Save a screenshot each time so you have a dated record.

Can I fix a labeling mistake after the shipment has left?

If the boxes have not reached the fulfillment center, contact your carrier or prep center first; it is sometimes possible to recall or relabel. Once Amazon has received and flagged the units, work through the shipment's problem notifications in Seller Central, which will offer the available options, often Amazon-applied prep or labeling for a fee, or a removal.

Tired of inbound shipments getting stuck over prep and labeling issues?

SellerVine's fulfillment team builds compliance checks into every shipment plan before it leaves the warehouse, so you're not finding out about a problem after your inventory is already stuck in a queue.

Get a free FBA audit →