Why Amazon Keeps Rejecting Your FBA Shipments (And How to Stop It)

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 is opening every box by hand to check what's inside. The entire system runs on the assumption that every unit arrives scannable, correctly labeled, and prepped the way its category requires, because the alternative is a warehouse full of people eyeballing shampoo bottles to figure out whether they're yours or the next seller's.

That's the part a lot of sellers miss when they treat prep and labeling as bureaucratic box-checking. It isn't. An FNSKU label is how a robotic pick system and a human associate both know, in under a second, which listing that unit belongs to. A poly bag on a loose-fitting item is the only thing standing between your product and a puncture wound from whatever gets stacked on top of it in a bin. Skip the step and you're not breaking a rule for its own sake, you're introducing a unit that the system can't handle correctly, and somewhere down the line that shows up as a miscount, a lost unit, a damaged return, or a customer complaint that was never really about your product quality.

The Mistakes That Actually Get Shipments Flagged

Most rejections trace back to a short list of repeat offenders. If you've been doing FBA for a while, you've probably hit at least two of these.

• FNSKU label placement errors: the label goes over the manufacturer barcode when the item needs "Sell on Amazon" barcode covering, or it doesn't cover it when the rule says it should, and now the scanner picks up the wrong barcode or two competing barcodes on the same unit.
• Missing required poly-bagging or bubble wrap: anything with loose parts, sharp edges, liquid contents, or small parts that pose a choking hazard has a specific prep requirement attached to it, and it's listed at the ASIN level, not guessed at. Ship it in bare retail packaging when the category calls for a poly bag and it either gets held at receive or, worse, gets received and then damages a neighboring unit in the bin.
• Box weight or dimensions that don't match the shipment plan: you build the plan with estimated numbers, then pack the actual boxes and never go back and correct the plan before it ships. Amazon catches the mismatch at the receiving dock, and now you've got a discrepancy that has to get resolved before those units count as received inventory.
• Mixed SKUs in a box without the right labeling: some shipment types allow mixed-SKU cases, some require case-level labels identifying exactly what's inside, and some don't allow mixing at all. Treat every case pack the same way across different shipment types and you'll eventually hit one that rejects it.
• Expiration-dated goods without proper date labeling: supplements, food, cosmetics with a shelf life, anything in that bucket needs the expiration date printed in a specific format and location. Miss it and the units usually get flagged before they're ever put away.

None of these are exotic. They're the five or six things that show up on almost every seller forum thread about a stuck shipment, because they're the five or six things Amazon's automated systems are specifically built to catch.

How You Find Out Something's Wrong

There's a good version of this and a bad version. 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 direct problem notification naming the specific issue, like an FNSKU mismatch or a missing prep category. That's your cue to go look immediately.

The bad version is a partial receive with no obvious explanation. You sent 500 units, Amazon confirms 460, and there's no note telling you what happened to the other 40. Sometimes that's a straightforward miscount on the warehouse floor. Sometimes it's 40 units that got flagged for a labeling issue and routed to a separate problem-resolution queue that doesn't show up cleanly in your shipment summary. Either way, you're stuck reconciling it after the fact instead of catching it before it became a problem.

The worst version is the one where you don't catch it at all until an inventory reconciliation weeks later turns up a gap you can't explain, and by then the paper trail (if there ever was one) is cold. This is why sellers who ship high volume treat the Shipping Queue as something to check daily during an active inbound, not something you glance at once and forget about.

The Pre-Shipment Checklist That Actually Prevents This

Most of this friction is avoidable with a five-minute check before the shipment leaves the warehouse, not after. Here's what that check should cover, every time, no exceptions for "we've shipped this ASIN a hundred times before."

• Pull current prep requirements per ASIN: category-specific prep rules live in Seller Central and they do change. A product that didn't need poly-bagging six months ago might need it now. Don't rely on memory or last quarter's packing instructions.
• Verify FNSKU labels are correctly placed and scannable: flat, not wrinkled, not curling at the edges, positioned exactly where the prep guidance says, and covering (or not covering) the original barcode as required for that specific item.
• Confirm actual box weight and dimensions before sealing: weigh and measure the packed box, not the estimate you used when you built the shipment plan, and correct the plan if there's a mismatch before the carrier picks it up.
• Check date-sensitive and hazmat-adjacent categories separately: anything with an expiration date, anything flammable or pressurized, anything that reads as borderline hazmat gets its own extra pass. These categories have the least room for error and the most specific documentation requirements.
• Confirm case-pack labeling matches the shipment type: if you're mixing SKUs in a box, make sure the shipment type actually allows it and that case labels reflect exactly what's inside.

If you're running this through a 3PL or prep center, this checklist should be part of their standard operating procedure, not something you have to ask for. If it isn't, that's worth a conversation.

What to Do When a Shipment Gets Held Anyway

First step: find the actual named reason, not the generic status. Seller Central's Shipping Queue and the shipment's problem log will usually tell you the specific requirement that wasn't met, whether that's a prep category, a labeling issue, or a discrepancy in received quantity. Don't waste time guessing when the system will tell you directly if you look in the right place.

Second step: figure out where the shipment physically is. If it hasn't been picked up yet or is still in transit, you may be able to fix the issue and resubmit before it ever reaches the fulfillment center. If it's already arrived and been flagged during receiving, you're now in a different process entirely, usually a case with Seller Support or a removal/disposal decision for the affected units, and trying to treat that like a pre-shipment fix wastes time you don't have.

Third step: decide whether this is a one-off or a pattern. If you've had one flagged shipment in the last year, fix it and move on. If you're seeing repeat issues across multiple shipments, that's usually a process problem at your warehouse or your in-house team, not bad luck, and it's the point where bringing in a prep service or 3PL that contractually guarantees compliance starts to pay for itself. You're not paying them for the poly bags. You're paying them to not have this conversation again.

Why This Matters More as Q4 Gets Closer

The mechanics of a flagged shipment don't change between July and November. The resolution timeline does, dramatically. A labeling issue that gets sorted out in two or three days during a slow month can take two or three weeks once fulfillment centers hit peak volume, because every queue involved, receiving, problem resolution, Seller Support case review, is backed up with everyone else's inbound freight at the same time.

That gap is the entire argument for getting prep right the first time as the calendar tightens. In June, a shipment stuck for a few days is an annoyance. In late October, that same delay can mean inventory that arrives after your best selling window has already started, which is a lost-sales problem, not just a logistics headache. Build in a real buffer for your Q4 shipments and treat every prep check as non-negotiable in the two months before peak, because the cost of a mistake scales with how backed up the system already is.

The Bottom Line

Prep and labeling problems are, honestly, one of the more embarrassing categories of FBA friction to fall into, because they're entirely preventable. This isn't Amazon changing the rules on you without warning or an algorithm making an unpredictable call. The requirements are documented, sometimes buried a few clicks deeper in Seller Central than they should be, but documented, and they don't change without notice often enough to excuse skipping the check. Every shipment that gets held over a missing poly bag or a mismatched box weight was a five-minute check away from shipping clean.

Get in the habit of running the checklist every time, keep your prep records current, and treat peak season as the time to tighten up, not loosen up. That's the whole game.