Amazon FBA suffocation warning in one minute
If your unit is protected by a poly bag and the bag opening is 5 inches or larger when laid flat, assume you need a suffocation warning and choose a format (printed vs label) you can apply consistently. Use this fast box to decide what to do next, then follow the workflow sections for placement, barcode layout, and QC.
| Decision point | Quick rule of thumb | What to do next |
|---|---|---|
| Do I need the warning? | Opening ≥ 5 inches when the bag is laid flat | Measure once, document, then standardize the bag size per SKU |
| Printed vs label? | Printed = fewer “peel-off” failures; Label = flexible for mixed bag sizes | Pick one method per SKU and lock a layout reference photo |
| Where should it go? | Place it where sealing/folds won’t hide it | Re-check visibility after sealing, not before |
| Barcode scannable? | Barcode must be scannable through the bag or placed on the outside | Decide: clear bag scan-through vs outside FNSKU/ASIN label |
Boundary notes:
- These rules apply to the unit’s protective bag, not an outer shipping bag.
- If Seller Central shows “Prep required” for your ASIN, follow those item-level instructions first.
What counts as a poly bag in FBA prep (and why the warning matters)
Before you measure anything, make sure you’re applying the rule to the right packaging layer: the warning requirement is about poly bags used to protect units, not the carton or an outer shipping sack. In practice, the FC needs to (1) handle the unit safely and (2) scan the unit identifier without opening packaging.
Think of “poly bag” here as: a plastic bag that fully encloses the retail unit (or set) for protection, cleanliness, leak prevention, or set integrity. If you polybag because your item is loose, textile, leakable, scented, or sold as a set, you’re in the “unit protective packaging” zone where the warning and barcode layout matter most.
A helpful mindset: your goal is consistency. Once you decide how a SKU is bagged and labeled, keep it the same across batches and suppliers so you don’t create “mixed packaging” surprises later.
When the warning is required (and how to measure the opening “when flat”)
The simplest safe rule is: if the opening of the poly bag is 5 inches or larger when the bag is laid flat, you need a suffocation warning on that bag. Measurement mistakes are the #1 reason sellers think they’re compliant while the next batch isn’t—so standardize the method below.
How to measure the opening (repeatable method)
- Lay the empty bag flat on a table, smoothing wrinkles at the top opening.
- Identify the opening edge (the mouth of the bag, not the side seams).
- Measure straight across the opening, edge-to-edge (width when flat).
- If you’re on the border (close to 5 inches), treat it conservatively: standardize to a smaller opening or apply the warning so you don’t rely on “perfect” measurement.
- Record the bag size and measurement method in your SKU packaging spec so every packer measures the same way.
Quick “don’t do this” checks
- Don’t measure circumference or “around the rim.” The rule is about the opening when flat.
- Don’t measure a partially filled bag and assume it’s the same as the empty bag.
- Don’t approve one sample bag and assume the supplier won’t substitute sizes later.
Printed warning vs sticker label: which is lower-risk for your workflow?
If the warning is required, both printed warnings and applied labels can work, but the lower-risk choice depends on how stable your bag sizing and production flow are. Printed warnings usually reduce “label failure” risk, while labels give you flexibility when bag sizes or suppliers change.
Comparison table: printed vs label
| Option | Best when | Common failure modes | Practical controls |
|---|---|---|---|
| Printed warning on the bag | You can standardize bag sizes per SKU and reorder consistently | Supplier substitutes a different bag size; warning ends up too small/poorly placed | Lock bag specs (size, thickness, print location) and require a sealed-unit photo sample per batch |
| Warning sticker label | Bag sizes vary by batch/supplier or you need a fast fix without reordering bags | Label peels, wrinkles, or gets hidden by folds; inconsistent placement | Use a consistent label size, place on a flat area, and add a “placement map” photo reference |
| Hybrid (printed for core SKUs, labels for exceptions) | You have a stable core catalog plus occasional special packaging | Operators mix methods in one shipment | Add “packaging version control”: method per SKU must be stated on the carton plan / SKU sheet |
What to check before you commit (Q10 in practice)
- Can you realistically keep one bag size per SKU across suppliers and seasons?
- Do you have enough label space for both the warning and the unit identifier label without overlap?
- Can your packers follow a simple, visual placement standard (photo reference), not a paragraph?
Font size and placement that stays legible after sealing
The warning should be prominent and legible after the bag is sealed, not only when the bag is laid open on the table. That comes down to two things: (1) picking the right minimum print size based on bag dimensions and (2) placing the warning where folds, seams, and barcode labels won’t hide it.
Step 1 — Calculate your “bag size band” (so you don’t guess)
- Measure the bag’s length and width (flat).
- Add them: total length + width.
- Use that total to look up the minimum print size (Amazon provides a table; many seller guides reproduce it—verify in Seller Central for the latest version).
Reference table (commonly reproduced; verify in Seller Central)
| Total length + width (inches) | Commonly cited minimum print size (points) |
|---|---|
| 60 inches or more | 24 pt |
| 40–59 inches | 18 pt |
| 30–39 inches | 14 pt |
| Less than 29 inches | 10 pt |
Important: Treat this as a practical reference, not legal advice, and confirm the current table in Seller Central before you finalize packaging.
Step 2 — Place it so it survives real handling
- Put the warning on a flat, front-facing area that won’t be covered by the adhesive strip, tape line, or a “fold-over” flap.
- Avoid seams and corners where the bag crinkles (crinkles reduce readability and make labels peel).
- If you also apply a barcode label on the outside, keep a clear separation zone so neither blocks the other.
Step 3 — Verify after sealing (the part many teams skip)
- Seal the bag the way it will be sealed in production.
- Then check: can you read the warning in one glance without unfolding the bag?
Step-by-step polybag workflow that keeps barcodes scannable
The safest workflow is: decide the bag + warning first, then place the barcode so it’s scannable without opening the bag. If you reverse that order, you’ll keep “fixing” barcode placement after the fact and accidentally hide the warning.
The operator-proof workflow (use this as your SKU SOP)
- Choose the bag size and material for the SKU (don’t let suppliers “pick whatever fits”).
- Measure the opening (when flat) and confirm whether the warning is required.
- Choose warning method (printed vs label) and lock a placement location.
- Decide barcode strategy:
- If the barcode is visible through a clear bag, confirm it scans through the material.
- If not, apply a single, scannable unit label on the outside of the bag.
- Seal the bag the standard way (adhesive strip or tape) and avoid excess loose plastic at the edges.
- Final 2-minute checks:
- Warning is visible and legible after sealing
- Barcode is scannable (or clearly positioned on the outside)
- No extra labels cover key text or create confusion
Boundary scenarios to handle explicitly
- Opaque bags (e.g., adult products): you’ll typically need an external barcode label, and you still need to manage the warning requirement for the opening size.
- Sold-as-a-set bundles: treat the outer bag as the unit packaging and ensure the set label and warning don’t conflict.
Common mistakes + a QC checklist to catch them before shipping
Most “FBA prep problems” are not mysterious; they’re repeatable failure modes you can catch with a short QC loop. Treat this section as your prevention layer—not a guarantee that Amazon won’t ever rework something, but a way to reduce avoidable errors.
Mistake → QC check mapping (use as a pre-export gate)
- Warning missing → Spot-check sealed units from each batch/supplier; confirm warning exists when opening ≥ 5 inches.
- Warning hidden by folds/seal flap → Check the warning after sealing; don’t approve pre-seal photos.
- Warning too small / hard to read → Verify bag size band (length + width) and print size reference; reject “tiny print” on larger bags.
- Sticker label peeling/wrinkling → Rub-test one sample; check placement on a flat area (not across a crease).
- Barcode blocked or distorted → Scan-test through the bag (or confirm the outside label is the only scannable code visible).
“Before carton close” checklist (fast version)
- One sealed unit photo (front/back) per SKU, per supplier, per batch
- Warning visible in the photo without unfolding
- Barcode location consistent with your SKU layout reference
- Any exceptions documented (e.g., supplier used a different bag size)
Supplier briefing template: what to tell your China factory
If you’re sourcing from China, the fastest way to reduce packaging drift is a one-page, visual packaging spec per SKU. Your goal is to remove “judgment calls” from the factory line and replace them with a simple pass/fail standard.
Supplier spec (copy this structure per SKU)
- Bag spec: bag size (L × W), material/thickness target, and whether bag must be clear or opaque.
- Measurement method: “Measure opening when bag is laid flat, edge-to-edge.”
- Warning requirement: whether this SKU requires the warning (and where it should be placed).
- Barcode plan: “Scan-through” vs “outside label,” plus exact label placement zone.
- Placement reference: 1 layout photo or diagram showing warning zone + barcode zone.
- Acceptance criteria (pass/fail):
- Warning visible after sealing
- Barcode scannable (or correctly placed on the outside)
- No conflicting labels covering key text
Minimum photo proof to request before cartons are sealed
- 3–5 sealed-unit photos per SKU per batch (front/back)
- Close-up showing warning legibility and barcode placement
- One ruler photo demonstrating opening measurement for borderline SKUs
Factory vs China prep partner: decision table (and a practical hybrid model)
There’s no universal best answer: factory execution is fast, but a China-side prep checkpoint increases control and consistency, especially when you consolidate from multiple suppliers. Use the table below to choose based on control vs speed and how quickly you can fix problems.
| Where the warning is applied | Best when | Main advantage | Main risk | Practical best practice |
|---|---|---|---|---|
| Factory | One or two stable suppliers; packaging rarely changes | Fastest throughput | Variation across batches, hard to fix late | Enforce supplier spec + sealed-unit photo proof |
| China prep partner | Many suppliers; bag sizes/labeling vary | Higher consistency and faster rework loop before export | Adds a handoff step | Use a standard bag/label kit and a QC gate before consolidation |
| Hybrid (recommended often) | Factory does basic bagging; prep verifies and fixes exceptions | Balances speed + control | Needs clear ownership | Factory: bag + basic labeling; Prep: measurement verification + layout check + re-bag exceptions |
If you’re consolidating inventory from multiple factories, a China-side checkpoint is often the simplest way to prevent “mixed bag sizes / mixed label layouts” from reaching the port. FBABEE can help you set a single SKU packaging spec, verify sealed-unit photos, and run a consolidation QC step before cartons are finalized—especially useful for first-time FBA shipments or catalog expansions. (We’re not affiliated with Amazon; this is operational support to help you follow Seller Central guidance.)
Found late? Fix options by shipment stage (China, in-transit, destination)
If you discover missing/incorrect warnings late, the safest fix is usually the one you can verify most clearly before the inventory reaches the FC—but the realistic option depends on shipment stage.
Stage-based fix path
- Still at factory: pause packing and correct the bag/warning method; collect sealed-unit proof before re-starting.
- At China warehouse / consolidation point: re-bag or re-label under a standard layout; re-check warning visibility after sealing and barcode scannability.
- In transit: prepare a destination-side plan (3PL or partner) so you can fix immediately upon arrival; avoid waiting until the inventory is already in Amazon’s network.
- Already at destination: prioritize a controlled relabel/re-bag process and verify with photo proof before any inbound appointment.
What to prioritize (in order)
- First: meet the warning requirement (when applicable)
- Second: ensure barcode scannability (scan-through or outside label)
- Third: seal quality and presentation (avoid loose plastic, wrinkles, or label overlap)
Multi-market language planning without overcomplicating SKUs
If you sell in multiple marketplaces, the safest approach is to treat warning language as a packaging version-control problem, not a one-time design choice. Requirements can vary by marketplace and local regulations, so avoid “one-size-fits-all” assumptions and verify official guidance before standardizing.
A conservative planning framework (not legal advice)
- Single-market focus: use the marketplace’s standard warning approach and keep one packaging version.
- Multi-market with stable destinations: maintain separate packaging versions per region if language rules differ (less risk, more SKUs).
- Uncertain future destinations: consider a packaging plan that can be adapted without scrapping inventory (e.g., label-based warnings you can apply per destination).
Version control tips (prevents mix-ups)
- Assign a packaging version code per SKU (e.g., US-V1, CA-V1).
- Store the layout reference image with the SKU in your system and require it in supplier/prep handoffs.
- Don’t mix packaging versions in the same carton unless the carton plan explicitly allows it and the team is trained for it.
Bridge to close: the FAQ below answers the most common edge questions sellers ask after they understand the core workflow.
FAQ + quick recap (common edge questions sellers ask)
When do I need a suffocation warning label for Amazon FBA poly bags?
If the poly bag is used to protect the unit and the bag opening is 5 inches or larger when laid flat, you should treat the warning as required and apply it in a prominent, readable way. When in doubt, confirm the current rule in Seller Central for your marketplace and the ASIN’s “Prep required” instructions.
How do I measure a poly bag opening “when flat”?
Lay the empty bag flat, smooth the top opening, and measure straight across the mouth edge-to-edge. Don’t measure circumference or guess from a filled bag. If you’re borderline, standardize to a smaller opening or apply the warning so you’re not relying on perfect measurement.
Can the warning be printed on the bag, or can I use a sticker label?
Both approaches can work, but choose based on consistency: printed warnings usually reduce peel-off risk when bag sizes are stable, while labels are easier when suppliers change bag sizes. Whichever you choose, lock a placement location and verify legibility after sealing.
What font size and placement should I use so the warning stays legible?
Use a bag-size method (length + width total) to choose an appropriate minimum print size, then place the warning away from folds, seams, and the sealing flap. Always re-check the warning after sealing—many “compliance failures” are simply warnings hidden by creases.
What mistakes cause Amazon to re-bag or rework poly-bagged items?
Common triggers include missing warnings (when required), warnings hidden by folds, illegible text, labels peeling, and barcodes that can’t be scanned through the bag (or aren’t correctly placed outside). A short pre-export QC loop—sealed-unit photo checks plus scan/placement verification—catches most of these issues early.
Should I do warnings at the factory or through a China prep partner?
Factory application is fastest when suppliers are stable; a prep partner adds control when you consolidate from multiple suppliers or see frequent bag substitutions. A hybrid model often works well: factory does basic bagging, prep verifies measurement/layout and fixes exceptions before export.
If I discover missing warnings late, what’s the safest fix?
Choose the fix point where you can control the work and verify results: factory → China warehouse → destination. Prioritize meeting the warning requirement (when applicable), then barcode scannability, then seal/presentation. Document the fix with sealed-unit photos so the next batch doesn’t repeat the same mistake.
If I sell in multiple marketplaces, how should I plan warning language?
Treat it as packaging version control: define a packaging version per region and verify marketplace guidance and local rules before standardizing. If destinations are uncertain, plan for adaptability (labels you can apply per destination) rather than committing to a single irreversible packaging print run.
Quick recap checklist (final)
- Measure bag opening when flat (edge-to-edge)
- If opening is ≥ 5 inches, plan the warning and make it visible after sealing
- Choose printed vs label based on bag-size stability and who applies it
- Keep barcodes scannable (scan-through clear bag or label outside)
- Run a short QC loop before cartons close; keep photo proof per batch
If you’re preparing your first FBA shipment from China—or juggling multiple suppliers with inconsistent bag sizes—standardizing the packaging spec and adding a consolidation QC checkpoint can prevent a lot of late-stage rework. FBABEE supports seller workflows like pickup → consolidation → prep/QC → shipment, and can help you implement a simple “measure → apply → verify” SOP for polybag warnings and barcode layout. This isn’t legal advice, and we’re not affiliated with Amazon—always verify the latest requirements in Seller Central.

