Packaging rules that get enforced: polybags, suffocation warnings, sets, and unit protection
Packaging Rules That Get Enforced: Polybags, Suffocation Warnings, Sets, and Unit Protection
Amazon’s packaging requirements are not a style guide. They are enforced at receiving — and enforcement means rejected shipments, non-compliance fees, or units that arrive in Amazon’s system in the wrong state. The practical task is not memorizing the full specification document. It is identifying which requirements apply to each product in your catalogue, then building a repeatable process that executes them correctly under normal operating conditions.
What goes in wrong comes out expensive. A packaging non-compliance caught at the fulfillment center costs more than the prep work that would have prevented it. The removal fee, the investigation time, and the delayed inventory availability add up quickly for a problem that a controlled workflow resolves at the prep stage.
Polybag Requirements: Where Most Prep Operations Trip
Polybagging is one of the most frequently misunderstood requirements in Amazon prep — not because the rules are complex, but because teams treat it as a simple step and skip the verification controls that keep it consistent.
Polybag: A clear polyethylene bag used to contain and protect a unit for FBA inbound. Required by Amazon for products that could scatter loose parts, that are textile or fabric items, that could be damaged by moisture or handling, or that Amazon’s product type classification specifies must be polybagged. The bag must be sealed (not left open), made from transparent material that allows the FNSKU label to be read through or on the surface, and must include a suffocation warning for bags with an opening wider than 12.5 centimeters.
The requirement that consistently generates receiving exceptions is the suffocation warning. It must be printed on the bag — not on a card inside the bag, not on the product box, not on a sticker that isn’t on the exterior surface of the polybag itself. Amazon’s receiving process checks this visually. A bag with the warning on an internal card fails the check.
The second failure mode is sealing. A polybag that isn’t fully sealed — with a flap left open, a clip instead of a heat seal, or a seal that’s partly adhered — is a non-compliant bag even if the warning is correct and the unit inside is correctly labeled. The bag is supposed to protect the unit through Amazon’s inbound handling and fulfill center pick process. An open bag doesn’t do that.
The third failure mode is transparency. A polybag made from opaque or heavily tinted material may obscure the FNSKU label, which needs to be readable by Amazon’s scanners — either because the label is on the outside of the bag, or because the bag is transparent enough that a label on the product inside can be read through it. Opaque bags require the label on the exterior surface.
What you see when this isn’t working is a pattern of receiving exceptions across a shipment — not one or two units flagged, but a percentage of the batch failing the same check. That pattern is a signal that the polybagging step is not a controlled process: different team members sealing differently, bag stock that predates the warning requirement mixed with compliant stock, or a spec that was set up once and never verified against the actual bags being used.
Suffocation Warning Specifications
The suffocation warning requirement is specific enough that executing it correctly means knowing what the specification is, not just that one is required.
The threshold is 12.5 centimeters — any polybag with an opening wider than 12.5cm needs the warning. Below that threshold, the requirement does not apply. Above it, the warning must appear on the bag itself, with font size tied to the total surface area of the bag. Larger bags require larger text. The standard minimum font size for average bags is typically 10 points or larger, but the operative rule is proportionality: a warning that looks adequate on a small bag may be too small on a larger one.
Suffocation warning text (standard English): “WARNING: To avoid danger of suffocation, keep this plastic bag away from babies and children. Do not use this bag in cribs, beds, carriages or playpens. This bag is not a toy.” Minor variations in exact wording exist; the requirement is that the warning communicates the suffocation risk and child safety message.
The practical setup for a prep operation is to determine the correct font size for each polybag size used and verify it on the physical bag stock before use. A warning printed at 8 points on a large bag fails the spec. The check takes less than a minute per bag format and prevents a shipment-level rejection.
Where this gets operationally interesting is in multi-SKU operations that use several different polybag sizes. Each size may require a different font size for the warning. If the prep team is pulling bags from a shared stock without distinguishing by required warning size, units in large bags may receive warnings sized for small bags. Version control on polybag stock — separate bins for different sizes, each labeled with the required warning font size — is the low-friction solution.
Set Rules and Bundle Configuration
Products sold as sets — two or more units that must arrive together and be sold together — have specific packaging requirements beyond the individual unit requirements.
Sold as set: A product designation indicating that the units inside a shipment or package are intended to be sold together and should not be separated. Required labeling: the outer packaging of the set must include “Sold as Set” or “Do not separate” language, and the FNSKU on the outer packaging must correspond to the set ASIN — not the individual component ASINs.
The failure mode for sets is a familiar one: a prep operation that packages the components correctly but labels the set with the individual component FNSKUs instead of the set FNSKU. This creates receiving exceptions because Amazon scans the outer package label and attributes the inventory to the set ASIN, but the actual unit inside may contain components with individual labels that don’t match. The outcome is a receiving discrepancy and potentially incorrect inventory attribution.
The second set failure mode is incomplete packaging — components that should be in a shared outer packaging arriving in separate bags or boxes, with no indication that they’re a set. A receiving team sees individual units, not a set. The set ASIN receives no inventory; the individual component ASINs may receive unplanned units.
A shelf of sets assembled for an inbound shipment should, at completion, look like a shelf of identically packaged units — each with a visible “Sold as Set” indicator and the correct FNSKU on the outer surface. If the units look like individual items that happen to be near each other, the assembly step wasn’t completed.
Unit Protection: Fragility, Liquids, and Sharp Edges
Unit protection requirements vary by product type, but the principle is consistent: the unit that arrives at the fulfillment center must be in the same condition as the unit that would be acceptable to a customer. Amazon’s receiving checks for visible damage; customer delivery generates feedback that feeds account health metrics.
For fragile items — glassware, ceramics, electronics with exposed screens — the outer packaging must protect the item from impact during Amazon’s inbound handling and the pick-and-pack process. Amazon’s inbound handling is not delicate. Cartons are stacked, sorted, and conveyed mechanically. A wine glass in a polybag without padding is not protected. A glass storage jar with a lid that’s not secured will arrive with the lid loose or broken.
Bubble wrap / protective packaging requirement: Fragile items that could break during handling must be packaged such that they pass a “five-foot drop test” — the packaging holds and the item survives a drop from five feet onto a hard surface without damage visible to the customer. This is not a test Amazon administers to every shipment; it is the standard that receiving inspections and customer returns are compared against.
For liquids, the requirement is double-sealing: the primary container must be sealed, and the outer packaging must contain the liquid if the primary seal fails. A bottle of lotion in a polybag is not double-sealed. A bottle of lotion in a sealed polybag that would contain a leak is. The standard is whether a customer-ready unit could survive a container failure during fulfillment without contaminating other inventory.
Sharp or exposed edges — items with exposed metal, glass edges, or rigid protrusions that could puncture packaging or injure a customer — require packaging that contains the hazard. This is less about Amazon’s receiving process and more about the end-to-end handling through the fulfillment center, including other inventory nearby in the bin.
The expert observation worth making here: unit protection failures tend to cluster on new SKUs entering the prep workflow for the first time. A product that’s been running for months has had its packaging requirements validated by the receiving history. A new SKU is going in fresh. The right moment to verify protection adequacy is the first inbound, not after a cluster of damage complaints comes back from customers.
Standardizing Execution: Isolating Variability
The principle that holds packaging compliance together across a prep operation is isolating variability. The goal is not to train the team to remember every rule for every product — it’s to build a setup where the correct materials and steps are specified per SKU, and the execution is a matter of following the spec rather than recalling it from memory.
Practically, this means a per-SKU packaging spec that records: polybag required (yes/no), polybag dimensions and warning requirement, fragile handling flag, set configuration (yes/no) and “Sold as Set” indicator requirement, liquid double-seal requirement, and any additional protection materials required. When a SKU enters the prep workflow, the team pulls the spec, not the memory.
The exception-handling part of this principle is equally important. When a unit arrives at the prep station that doesn’t fit the existing spec — damaged packaging that changes the protection requirements, a new variant that uses a different bag size, a product shipped with a different primary container than specified — the correct response is to stop and flag, not to improvise. Improvised solutions to spec edge cases create compliance gaps that don’t surface until the shipment arrives at Amazon and the exception is logged.
The steady-state of a well-run prep operation is boring. Units come in, get packaged to spec, get labeled, get verified, go into cartons. The interesting moments are the exceptions, and those are the moments that define whether the system holds or creates drift.
Frequently Asked Questions
Q: What Amazon packaging requirements are most commonly enforced? A: The most consistently enforced requirements at Amazon’s receiving centers are polybag suffocation warnings (must be printed on the bag itself, not inside), polybag sealing (must be fully sealed, not open or clipped), fragile item protection (must withstand handling through the fulfillment process), and set/bundle labeling (outer packaging must carry the set ASIN, not individual component ASINs). Each of these generates receiving exceptions that delay inventory availability and can result in rework fees.
Q: Does every product sold on Amazon need to be polybagged? A: No. Polybag requirements apply to specific product types: items that could scatter loose parts during handling, textile and fabric products, items susceptible to moisture or contamination, and anything Amazon’s category classification specifies must be bagged. Many products ship without polybagging — in their original manufacturer packaging or in a box. The correct starting point is verifying whether polybagging is required for each specific SKU, not applying bags universally.
Q: What is the suffocation warning requirement for Amazon polybags? A: Any polybag with an opening wider than 12.5 centimeters requires a suffocation warning printed directly on the exterior of the bag. The warning must be in a font size proportional to the bag’s surface area. It cannot be on a card inside the bag, on the product box, or on a sticker that isn’t part of the bag surface. A correctly worded warning in a compliant location on the wrong surface — inside instead of outside — still fails the requirement.
Q: What does “Sold as Set” mean for Amazon packaging? A: “Sold as Set” is a required label on the outer packaging of any multi-unit product sold as a single ASIN. The outer packaging must make clear that the contents are a set and should not be separated — typically with printed “Sold as Set” or “Do not separate” language. The FNSKU on the outer packaging must be the set ASIN’s FNSKU, not the individual component FNSKUs. Failing to package correctly means Amazon’s receiving team may not identify the units as a set, leading to inventory attribution errors.
Q: What is the fragile item packaging standard for Amazon FBA? A: Fragile items must be packaged to survive Amazon’s inbound and fulfillment handling, which includes mechanical sorting and stacking. The informal standard is a “five-foot drop test” — the packaging should protect the item through a drop from five feet. Practically, this means fragile items need protective cushioning inside the outer packaging, and containers with lids (jars, bottles) need their closures secured. Damage that occurs inside Amazon’s network before a customer receives the item creates returns and account health signals.
Q: How do I set up a repeatable packaging compliance process for multiple SKUs? A: The most reliable approach is a per-SKU packaging specification document that records every requirement for that SKU: polybag required and size, suffocation warning requirement, fragile handling flag, set configuration, and any special protection materials. The prep team follows the spec for each SKU rather than recalling requirements from training. Exceptions — units that arrive differently than the spec anticipates — are flagged rather than improvised. This isolates variability and prevents specification gaps from accumulating across a large catalogue.
If you’re setting up prep for a new product or troubleshooting recurring packaging exceptions on an existing SKU, share the product format and we’ll clarify what the correct spec looks like.