

![]()
A carton lands at Cergy with apparel polybagged in clear film, small parts loose in a poly sleeve, and no suffocation warning printed anywhere. The seller assumed polybagging was one rule applied the same way across the whole shipment. It is not. Amazon’s requirement is triggered by bag-opening size first, then layered with category-specific rules that apply on top, and missing either layer is one of the most common reasons an otherwise-ready shipment gets pulled aside during FBA Prep in France.
The practical decision for a multi-category seller is not whether to polybag. It is knowing which SKUs cross the bag-size threshold that requires a suffocation warning, which categories carry their own separate polybagging obligation regardless of bag size, and what the warning label itself has to say before a shipment reaches Amazon.fr. This article walks through what FLEX.’s Cergy hub actually checks on the floor, so the gap gets caught before dispatch rather than after a hold notice.
The first thing to separate is that the suffocation warning is not a category rule. It is a bag-geometry rule. Amazon’s general FBA guidance ties the requirement to the size of the bag’s opening — commonly referenced around a 5-inch threshold, though the exact figure should always be checked against current Seller Central policy rather than assumed from memory, since Amazon updates packaging requirements without much warning.
What this means operationally: two units in the same product line can trigger different outcomes if one ships in a snug-fit bag and the other in a looser one sized for a bulkier variant. A prep team working from a single blanket instruction ('polybag everything the same way') will misjudge a portion of the run. The check has to happen bag-by-bag, or at minimum SKU-variant by SKU-variant, not once per product category.
This is also why sellers who prep at home or through a lower-cost freelance packer often arrive at Cergy with a partially compliant batch. The bag choice was made for cost or fit, not against the suffocation-warning threshold, and nobody flagged the mismatch until receiving.
Before inventory leaves the supplier or home base, the seller should know the actual bag-opening measurement for each polybag being used, not just the product category. This is a five-minute check with a tape measure against the bag as manufactured, not the product inside it.
Category exceptions also need confirming separately. Some product types (certain apparel, for instance) carry polybagging obligations independent of the suffocation-warning threshold, while other categories may be exempt from polybagging entirely under Amazon’s current packaging and prep requirements. Assuming last year’s rule still applies without checking Seller Central is a weak habit that shows up at receiving.
When a bag-size or label gap isn’t caught before the carton reaches a prep facility, the shipment doesn’t just get a warning note. It gets pulled into a rework queue, relabeled or rebagged on-site, and depending on volume, that can add a day or more to the prep timeline before the unit is released for FC handoff.
For a seller running a tight restock cadence into Amazon.fr, that delay compounds. A shipment that was supposed to land in the FC ahead of a promotion window instead sits in exception processing, and the seller finds out the size of the problem only after Cergy opens the cartons — later than most sellers would like.
Meeting the bag-size threshold is only half the requirement. The warning text has to appear on the bag in a specific way — legible font size, correct placement relative to the opening, and wording that matches Amazon’s required suffocation-warning language rather than a paraphrased version a supplier assumed was close enough.
For Amazon.fr specifically, sellers should confirm directly with current Amazon policy whether the warning text needs to appear in French, bilingually, or whether Amazon’s standard English-language warning is accepted as-is for shipments into the French marketplace. This detail changes depending on current policy, so it is not something to assume from a prior shipment or from what worked on another marketplace.

Multi-category catalogues make this harder because polybagging obligations don’t stop at bag size. Apparel frequently carries its own polybagging requirement tied to protecting the garment, independent of whether the bag opening crosses the suffocation-warning line. Small parts and choking-hazard items often carry separate labeling obligations layered on top of, not instead of, the suffocation rule. Some categories are exempt from polybagging altogether under current Amazon guidance, which means bagging them anyway can create unnecessary prep work rather than protecting the shipment.
The operational risk is treating the catalogue as one uniform SKU set. A seller shipping apparel, small electronics accessories, and packaged consumables in the same load is really managing three separate rule sets that happen to travel in the same carton. Each product line needs its own polybagging decision, confirmed against current category guidance, before the shipment is packed for Amazon FC forwarding.
This is where a documented prep instruction per SKU, not per shipment, prevents the kind of gap that only surfaces once units are already on the receiving floor.

On the floor, the check sequence at Cergy runs in a fixed order: confirm the bag-opening measurement against the suffocation-warning threshold, confirm the category-specific polybagging requirement for that SKU, then verify the warning label itself — text, placement, and font size — before the unit is sealed into its shipping carton.
Units that fail any one of these three checks get flagged and corrected on-site rather than pushed forward with a note. That correction loop is what keeps a labeling gap from turning into a hold once the shipment reaches Amazon’s FC, but it only works because the check happens before carton close, not after.
Measure the bag opening against the current suffocation-warning threshold per Amazon policy, not per assumption from a prior shipment or another marketplace.
Confirm whether the SKU’s category carries its own polybagging obligation or exemption, separate from the bag-size rule, before packing.
Verify warning text, font size, and placement, and confirm current language requirements for Amazon.fr before dispatch.
The operational decision here isn’t whether polybagging matters. It’s whether the seller confirms bag-size thresholds and category rules for every SKU in the catalogue before goods leave for prep, or whether that check gets left to whoever is packing cartons on the day. The second approach is where correctable gaps turn into shipment holds.
A practical next step: pull the current bag specifications for each active SKU, check them against Amazon’s latest suffocation-warning and category guidance in Seller Central, and flag anything close to the threshold or ambiguous on exemption status. That list is what a prep partner needs in hand before the shipment arrives, not after cartons are opened.
For sellers running multiple categories through FBA Prep in France, this is exactly the kind of gap that a documented, SKU-level prep instruction closes — and it’s the difference between a shipment that clears Cergy on schedule and one that sits in a rework queue while the promotion window passes.
If your catalogue spans apparel, small parts, and general merchandise, don’t wait for a hold notice to find out which SKUs are missing a compliant suffocation warning. Send FLEX. your current product and packaging list ahead of your next shipment into the Cergy hub, and get a straight answer on which units need rebagging, relabeling, or nothing at all — before they’re sitting in a queue instead of on the shelf.
Contact FLEX. before your next Cergy shipment to check which SKUs need rebagging, relabeling, or nothing at all.
