Policy is boring until it costs you a launch
Amazon's prep policy reads like a glossary. None of it is hard to follow if you set up SOPs around it on day one. All of it is expensive to fix once a shipment is in transit.
I run SunPort Prep Center, a 2,500 sq ft FBA prep and 3PL operation in Dania Beach, Florida. We see thousands of units a week move through receiving, prep, and outbound, and the same six policy mistakes keep showing up — usually from sellers who built their process around a YouTube video instead of the actual policy pages. None of these are exotic. Each one has a clean operational fix. Here is the violation pattern we see, and the SOP we run against it.
1. Hazmat and dangerous-goods misclassification
The violation pattern: a seller lists a product as a plain consumer good when Amazon classifies it as a dangerous good. Lithium batteries (loose or built into a device), aerosols, anything flammable or pressurized, magnetized items, and certain supplements and cosmetics all get pulled into the dangerous-goods review program. The seller doesn't realize it, ships it in, and the units sit in a hazmat hold for weeks or get destroyed. Worse, repeated misdeclaration is the kind of thing that gets a category gated.
The SOP fix: classify before you buy, not after the PO ships. We check every new ASIN against its hazmat status and request the supplier's safety data sheet (SDS) and an exemption sheet for any battery, liquid, gel, powder, or pressurized item. If a product is flagged, we hold it in our warehouse until the dangerous-goods review clears, then ship — instead of letting Amazon discover it at their dock. Slower on paper, far faster in practice.
2. Suffocation warnings on poly-bagged units
The violation pattern: poly bags over Amazon's size threshold (it's on the larger end — think a bag big enough for a child to get a head into) require a printed suffocation warning, and the warning has to be legible and sized appropriately to the bag. We routinely see bags missing the warning entirely, warnings printed too small to read, the bag not transparent, or the bag sealed in a way that blocks the existing barcode. Any of those gets the unit flagged as unsuitable.
The SOP fix: we use clear poly bags with the suffocation warning pre-printed at a size that scales with the bag, and we keep the opening sealed flush so there's no loose trailing plastic. The scannable barcode — whether it's on the product or our applied label — stays visible through the bag, with no print or seam crossing it. If the bag is below the warning threshold we skip the warning, but the default is: if in doubt, the warning goes on.
3. Master-carton weight and size limits
The violation pattern: a master carton that's too heavy or too large for standard FBA handling, shipped without the required heavy-or-oversize labeling. Amazon caps standard carton weight (the common limit for a mixed/standard carton sits around the 50 lb mark, with a higher single-SKU allowance), and any carton exceeding the standard threshold needs a "Team Lift" or heavy-package marking on the top and side. Skip the label and the carton can be refused or hit with a non-compliance fee at the fulfillment center.
The SOP fix: every outbound carton gets weighed and measured at the pack station, and the system flags anything over the standard limit before it's taped shut. Overweight cartons either get split or get the heavy/oversize markings applied to the correct faces. We'd rather pack two clean cartons than gamble one heavy one through receiving.
4. Expiration-dated and lot-controlled goods
The violation pattern: consumables, supplements, and topicals need the expiration date printed in the required format and clearly visible, and Amazon expects meaningful shelf life remaining on arrival — short-dated stock gets refused. The other half of the failure is internal: sellers ship newer lots before older ones, so the oldest stock is the last to sell and ages out in the warehouse.
The SOP fix: we verify the expiration date is printed in a readable MM-DD-YYYY or MM-YYYY style on both the unit and the carton, and we confirm enough shelf life remains to clear Amazon's minimum before we ship. Internally we sequence by FIFO — oldest lot picks and ships first — and we won't blend lots in a single shipment without explicit instruction. Lot numbers are recorded at receiving so a recall or a date question is a lookup, not an archaeology project.
5. Bundles and "sold as set" units
The violation pattern: a multi-pack or bundle that isn't labeled as a single sellable unit. The components arrive loose, the fulfillment center separates them, and now you've got orphaned pieces and a customer who ordered a set and got one item. This is one of the most common — and most avoidable — sources of negative reviews on bundle listings.
The SOP fix: bundles get assembled into one unit, secured together, and labeled with a clear "Sold as Set — Do Not Separate" marking, with a single FNSKU applied to the bundle (never one barcode per component showing). The whole unit reads as one item at receiving. If a kit has loose parts, they go inside one outer bag or box so nothing can be split off in handling.
6. Box content and barcode commingling errors
The violation pattern: two related failures. First, shipments arriving without accurate box-content information — Amazon needs to know what's in each carton, and missing or wrong manifests trigger fees and slow check-in. Second, and more damaging, barcode commingling: leaving the manufacturer barcode (UPC/EAN) on a unit instead of applying your FNSKU. When you don't use a unique FNSKU, Amazon may commingle your stock with other sellers' identical units — so a buyer can receive someone else's (possibly counterfeit or damaged) product against your account.
The SOP fix: we apply your FNSKU to every unit and cover the manufacturer barcode so only one scannable code is visible. Box content is captured per carton during pack-out and submitted with the shipment, so nothing arrives as a mystery box. The standing rule on our floor is one unit, one barcode, one truth — no commingling, ever.
The pattern behind the pattern
Notice what all six have in common: the fix happens at receiving and pack-out, before anything moves. Once a non-compliant unit is in Amazon's network, you're looking at removal orders, destruction, fees, or — at the bad end — a category or account flag. The cost of catching it at our dock is a few minutes per SKU. The cost of catching it at theirs is your launch.
If you want a prep partner who runs these checks as standard SOP rather than as a surprise, contact us. We're in Dania Beach, open Monday through Friday, 9 to 6 ET, and we'd rather catch this stuff at our dock than let you find it at Amazon's.