Put every FBA prep run through an acceptance gate

FBA prep is now a release decision, not a service selection.

Amazon confirmed that, beginning January 1, 2026, it no longer offers prep and item-labeling services for new US FBA shipments. The change also applies when inventory reaches FBA through AWD, Amazon Global Logistics, Amazon SEND, or Supply Chain Portal. Amazon’s July packaging guide then makes the execution standard plain: units need the correct barcode, scannable labels, secure packaging, and any product-specific preparation before they enter the fulfillment network.

The operator response is a SKU-level acceptance gate that can stop a bad prep run before pickup.

Convert policy into a SKU specification

Do not send a factory a generic link and call it a packaging standard.

Create one controlled specification for each sellable SKU. Identify the exact product, variation, condition, unit count, bundle structure, packaging revision, barcode path, label file, label location, warnings, inserts, and carton configuration. Add clear photographs of an approved finished unit and every face that carries a code or claim.

Amazon distinguishes individual units from case-packed products and requires unofficial sets sold as one unit to be packaged together and marked so they are not separated. Translate those rules into the physical configuration the vendor must reproduce. Give every different colorway, size, or multipack a separate line.

Version the specification and link it to the purchase order. A current approval should never depend on someone remembering which PDF was used last quarter.

Qualify the barcode path before printing

The presence of a barcode does not prove that it is the right barcode.

Document whether the SKU will use an eligible manufacturer barcode, an Amazon barcode, or a Transparency code. Amazon’s guide notes that Amazon barcodes are required for several product types and conditions, including products not tracked through manufacturer barcodes. The live account workflow and current help page should decide eligibility for the actual SKU.

When an Amazon barcode is used, the printed label must include the scannable code, FNSKU, product title, and condition. Place it on a smooth, flat surface, outside any additional wrapping, and cover competing UPC, EAN, or ISBN codes that could be scanned by mistake. Transparency codes must not be covered by another label.

Match the exported label file to the purchase-order SKU map before printing. A perfectly applied FNSKU for the wrong variation is still a defect.

Test the physical pack, not the mockup

Approve finished production units, not a design rendering.

Draw samples across cartons and work shifts after the prep run. Confirm that the unit is secure, the bundle cannot separate, loose parts cannot escape, and the protection fits the product’s actual hazard. Amazon calls for bubble wrap on sharp, fragile, ceramic, and glass items, while several loose or contaminating product types require bagging. Current category guidance should govern the method.

Handle the sample as inventory will be handled. Turn it, compress it reasonably, check closures, inspect edges, and confirm that the label stays readable after the packaging flexes. Do not treat a supplier’s drop-test claim as evidence unless the method, sample, result, and tested revision are recorded.

Photograph the accepted unit beside its SKU and lot identifier. The goal is to prove what was released, not merely what was intended.

Make every code scan before pickup

Visual inspection misses quiet barcode failures.

Use a scanner or validated scanning application to read every visible code on each sampled unit. The accepted result should resolve to the intended identifier, while obsolete or competing codes should be covered or rendered unscannable where Amazon requires it. Repeat the check through transparent bags and after bubble wrap, because reflections, curves, seams, and damaged print can change scan behavior.

Amazon’s public guide specifies black ink on non-reflective adhesive paper, labels one to two inches tall and two to three inches wide, and a 300-DPI laser printer as the best-practice output. It also rejects damaged or photocopied labels. Treat these as measurable inspection fields, then check the live help guidance for any SKU- or marketplace-specific requirement.

Reconcile sampled units, case quantities, carton labels, and the shipment plan. One correct unit cannot clear a carton built for another destination or quantity.

Close the loop with defect evidence

The gate needs a disposition path, not just pass or fail.

When a sample fails, quarantine the affected scope. Record the SKU, lot, carton range, defect class, evidence, likely cause, corrective action, owner, and retest result. Expand sampling when the defect may be systematic. Do not let a vendor relabel a few photographed units while the unverified balance moves to pickup.

Amazon says it may refuse, return, or repackage inadequately prepared inventory at the seller’s expense, and may add product-specific prep requirements after damage-related returns. Track receiving issues, untraceable inventory, damage, repackaging, and customer returns back to the prep specification. That feedback distinguishes an isolated receiving event from a repeatable packaging weakness.

Release requires a named reviewer, timestamp, approved exception record, and preserved evidence. The shipment should move only when the physical inventory agrees with the digital plan.

The Operator Read

Outsourcing prep does not outsource accountability.

Amazon’s service change moves seller-controlled prep completion upstream, where a seller, factory, or prep provider must make the unit ready before it enters the US FBA network. A checklist alone is too weak if it is not tied to an exact SKU, production run, label file, sample, and reviewer.

Write the standard at unit level. Confirm the barcode path in the live workflow. Inspect and scan finished inventory, quarantine exceptions, and authorize pickup with evidence.

The document is not the vendor’s promise that prep is complete. It is the release record showing why this shipment was ready.