The 90% Business Delivery-Rate Mandate: What Self-Ship Sellers Across EU Marketplaces Must Prove by September 30
21.07.2026
Amazon Business’s New Fulfilment Standards Are Coming for Third-Party Sellers — Is Your 3PL SLA Ready?
22.07.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
A reseller ships three cartons of the same branded item to different FCs across Germany and France. Half arrive labeled under the manufacturer barcode, half under a generic FNSKU sticker applied in a rush the week before. Under the old commingling model, that inconsistency rarely mattered because Amazon pooled matching inventory and shipped whichever unit was closest to the buyer. That pooling is going away. Amazon has been phasing out commingled inventory, and the practical result for multi-SKU sellers and resellers is that every single unit now needs its own FNSKU label, checked and applied before it reaches an FC. This changes how prep gets planned, who checks labeling accuracy, and what happens when a batch arrives without it. The rest of this piece walks through what is confirmed, what remains an operational judgment call, and where labeling responsibility should sit inside a seller’s inbound workflow.
What Commingling Actually Meant and Why Amazon Is Retiring It
Commingled inventory let Amazon treat identical products from different sellers as interchangeable, tracked only by manufacturer barcode rather than a seller-specific FNSKU. A buyer order could be fulfilled from any seller’s stock of that ASIN sitting in the network, not necessarily the unit the original seller sent in. For sellers confident in product authenticity and condition, this reduced prep costs since manufacturer barcodes could sometimes ship as-is.
The trade-off was traceability. If a counterfeit or damaged unit entered the pool from one seller, it could be shipped against another seller’s order, creating returns disputes and account health issues that were hard to unwind. As counterfeit complaints and reseller conflicts grew across EU marketplaces, Amazon has moved toward requiring stickered FNSKU labeling on virtually all inbound units, closing the commingling pathway. For resellers running Amazon FBA Prep services in Europe, this means barcode strategy is no longer optional at the SKU level; it is now a per-unit labeling decision.
What Sellers Must Confirm Before Shipment
Before cartons leave a prep facility, a seller needs a confirmed answer on labeling method for every ASIN in the shipment, not just the fast-moving ones. Mixed-source inventory, where the same ASIN is sourced from more than one supplier or batch, is where labeling gaps most often appear.
Practical checks include confirming FNSKU assignment status in Seller Central for each ASIN, verifying that stickered labels are readable and scannable at carton level, and reconciling supplier packaging against Amazon’s current labeling requirement rather than a policy version from a year or two earlier. Reseller inventory tracking Amazon relies on becomes far weaker if a batch of units skips this check and gets treated as generic stock.
What Breaks Without a Clear FNSKU Check
When FNSKU labeling is inconsistent, the first failure point is usually FC receiving: mislabeled or unlabeled units can be refused, quarantined, or logged as unfulfillable, which stalls sellable status until the discrepancy is resolved. That is inventory the seller has already paid for and shipped, sitting outside the sales flow.
A second failure shows up downstream in returns and reseller disputes. Without a unique FNSKU tying a unit to a specific seller’s batch, a defective or counterfeit item can be harder to trace back to its source, which slows account health investigations and can trigger stricter scrutiny of future shipments from that account.
Who Owns the Labeling Decision Inside the Inbound Workflow
The end of commingling shifts labeling from a cost-optimization choice into a fixed step that needs an owner. In practice, that owner is whoever controls the prep station before cartons are sealed, whether that is an in-house team, a third-party prep center, or a reseller’s own repackaging line.
This matters most for sellers who source the same ASIN from multiple suppliers or buy from liquidation and wholesale channels, since those units often arrive with inconsistent or missing manufacturer barcodes. FNSKU labeling rules now require that every one of those units gets its own scannable seller-specific label applied before it enters Amazon’s network, not applied selectively based on which units looked cleanest. Sellers using external prep should confirm in writing whether FNSKU application is included by default or billed as an add-on, since assuming it is covered is a common planning gap.
Confirm before the next shipment:
- FNSKU status assigned in Seller Central for every ASIN in the batch, not just top sellers
- Supplier packaging reviewed against current Amazon labeling requirements, not last year’s rule set
- Mixed-source ASINs flagged separately so no unit defaults to manufacturer barcode by mistake
- Carton-level label scan test completed before dispatch, not assumed from a sample unit
Check at the prep or FC handoff:
- Prep center contract explicitly states who applies FNSKU labels and at what stage
- Label placement matches Amazon’s current carton and unit label positioning
- Removal or repackaging jobs re-verify FNSKU rather than reusing old stickers
- Inbound shipment plan confirms FC destination before labeling is finalized, since label content can depend on routing
Watch for cost and margin impact:
- Per-unit labeling cost added to prep invoices where it was previously bundled or skipped
- Storage days accumulating on units held at receiving pending relabel
- Removal order costs triggered if unlabeled stock is rejected and needs return-to-seller handling
- Reseller margin recalculated where manufacturer-barcode shipping was previously assumed free
Assign follow-up ownership:
- A named person or team confirms FNSKU compliance before each shipment is booked
- Exception process defined for units arriving without correct barcodes mid-batch
- Regular review of Seller Central labeling requirement pages, since Amazon updates these periodically
- Escalation path agreed with the prep partner if a batch is rejected at FC receiving
Deciding Whether to Adjust Your Prep Workflow Now
The practical decision for most resellers is not whether FNSKU labeling matters, it clearly does, but when to rebuild the workflow around it. Waiting until a shipment gets rejected at FC receiving is the expensive way to learn the new rule; auditing labeling practice before the next inbound batch is the cheaper one.
A reasonable sequence is to first confirm current FNSKU assignment status across the full ASIN catalogue, then check whether prep is happening in-house or through a partner, then align that partner’s process with the per-unit labeling requirement rather than assuming their existing service already covers it. Sellers running high SKU counts or frequent restocks from multiple suppliers carry the highest exposure here, since inconsistent sourcing is exactly where old commingling habits are hardest to unlearn. Building this check into a standard pre-shipment routine, rather than a one-off fix, is what keeps sellable status intact as Amazon tightens enforcement across EU marketplaces.
Responsibility Owner
Whoever seals the carton owns the FNSKU check. Name this person or team explicitly in the prep contract, not as an assumed default.
Document Checkpoint
Confirm FNSKU assignment in Seller Central per ASIN before dispatch. This is the checkpoint most batches skip under time pressure.
Exception Escalation
If units arrive without correct barcodes mid-batch, pause that portion and escalate to the prep partner rather than shipping as-is.
What to Lock Down Before Your Next Inbound Shipment
The end of commingling does not change what sellers sell, but it changes how much labeling discipline is required to keep that inventory moving through FC receiving without delay. The decision in front of most resellers is narrow but consequential: confirm which ASINs still rely on manufacturer barcodes, close that gap with proper FNSKU labeling rules applied at the unit level, and assign a clear owner for that check before the next shipment is booked.
Sellers running FBA prep through a third party should treat this as a contract conversation, not an assumption. Ask directly whether FNSKU application is included, how mixed-source batches are handled, and what happens if a carton is rejected at the FC. Sellers prepping in-house should build the same check into their pre-shipment routine rather than relying on habits formed under the old pooled-inventory model. Either way, this is a workflow fix, not a one-time cleanup, since sourcing patterns and Amazon’s labeling requirements can both shift again.
Labeling policy sits with Amazon, and sellers should verify current FNSKU requirements directly in Seller Central rather than relying solely on third-party summaries, including this one. Where the operational question is how to build per-unit FNSKU checks into an inbound workflow across multiple EU FCs, FLEX. supports that layer of prep, carton labeling, and handoff coordination. If your current setup was built around commingled or manufacturer-barcode shipping, it is worth a conversation before your next shipment moves.
