Amazon Ends FBA Commingling: The Reseller's Complete FNSKU Labeling Guide (2026)

On March 31, 2026, Amazon closed a system that had been running for more than a decade. The stickerless commingled inventory model - which let resellers ship products under manufacturer barcodes and have their units pooled with other sellers' identical stock - ended for resellers. What replaced it is mandatory FNSKU labeling: a seller-specific identifier that ties every unit to the account that sent it. Amazon announced the change at its annual Accelerate seller conference in September 2025, giving sellers roughly six months to build the workflows they would need. That window has now closed. If you were running commingled stock and are still sorting out what this means for your business, this guide covers every dimension of the change: who it hits, what the labels require, how to move a large catalog through the transition, and why - under the right conditions - seller-specific inventory is actually better for your bottom line.

What Changed on March 31, 2026: The End of Stickerless Commingled Inventory

Under the commingled system, if two sellers both stocked the same product with the same UPC, Amazon treated those units as interchangeable. A unit from Seller A could fulfill an order placed with Seller B. Returns came back into a shared pool. Neither seller's inventory was truly their own once it crossed into the fulfillment center. That arrangement ended for resellers on March 31, 2026.

One thing many sellers got wrong during the lead-up: the deadline is an arrival deadline, not a creation deadline. A shipment created in Seller Central before March 31 but physically received at the fulfillment center after that date still had to carry FNSKU labels. If you rushed to create shipping plans in late March assuming that timestamp protected you, but the trucks arrived in April, those units needed labels. Amazon's enforcement point is the inbound receiving scan, not the timestamp on your shipping plan.

The policy has been confirmed for US and European fulfillment centers, both of which require FNSKU-only labeling for resellers on new inbound shipments. Sellers using other Amazon marketplaces - including Japan, Canada, India, or Australia - should verify current FNSKU requirements for those regions directly with Amazon, as rollout details for additional markets may differ.

A question that comes up constantly from sellers with existing commingled stock: do I need to recall it? The answer is no. Inventory already inside Amazon fulfillment centers before March 31 is grandfathered. It sells through under the old rules with no action required on your end. Creating a removal order for that stock is unnecessary. The new requirements apply only to units entering the fulfillment network after the deadline.

Who Must Switch: Resellers vs. Brand Representatives and the Brand Registry Trap

The exemption from FNSKU labeling is narrower than most sellers realize, and the confusion around it is producing real compliance failures.

Only sellers holding the 'Brand Representative' role in Amazon Brand Registry are exempt. If you own or officially represent the brand on Amazon under that specific role, you may continue shipping under manufacturer barcodes - UPCs, ISBNs, EANs - without FNSKU labels.

Here is the trap. Being enrolled in Brand Registry does not automatically mean you hold the Brand Representative role. Amazon has a second role within Brand Registry called 'Reseller.' Authorized resellers - even those formally enrolled in Brand Registry by the brand owner to sell authentic goods - are assigned the Reseller role, not the Brand Representative role. Sellers with the Reseller role in Brand Registry are not exempt. They must apply FNSKU labels exactly like any other reseller who has no Brand Registry enrollment at all.

This distinction is causing widespread confusion because sellers assume that Brand Registry membership equals an exemption. It does not. If you are uncertain about your role, check it directly in your Brand Registry account settings before making any labeling decisions. Acting on a mistaken assumption here has direct financial consequences, because the penalties for non-compliant inbound shipments are severe and have no clearly documented appeals path.

For the majority of FBA resellers - those selling other brands' products through wholesale purchasing, retail arbitrage, or online arbitrage - FNSKU labeling is now required without exception.

What Is an FNSKU and How It Differs from a UPC, EAN, or ASIN

FNSKU stands for Fulfillment Network Stock Keeping Unit. It is a barcode identifier generated by Amazon specifically for your seller account and a specific product listing. Every FNSKU begins with 'X00' followed by a string of alphanumeric characters - for example, X001ABC123. The barcode format used is Code 128.

The critical distinction between an FNSKU and a UPC or EAN is what each identifier is tied to. A UPC or EAN belongs to the product itself. Any seller offering that product shares the same code. That is exactly what made commingling possible - one barcode, many sellers' units pooled together in the same bin. An FNSKU, by contrast, is tied to your seller account. Two sellers stocking the exact same product have different FNSKUs. When Amazon scans your FNSKU, it knows the unit belongs to your inventory specifically, not to a shared pool.

An ASIN (Amazon Standard Identification Number) is a different identifier again. An ASIN identifies a product listing within Amazon's catalog, and multiple sellers can list under the same ASIN. The FNSKU connects your account to that ASIN - it is your account's version of the product, not the product in the abstract.

To generate an FNSKU label in Seller Central, navigate to Manage FBA Inventory, find the relevant product, open the Edit dropdown, and select Print Item Labels (the exact menu path may vary if Amazon has updated the interface - check Seller Central's current help documentation if the path differs). Amazon generates the label file from there. This process runs at the ASIN level, which becomes a meaningful workflow consideration when you are working across a large catalog.

Why Amazon Ended Commingling: Counterfeits, Brand Damage, and the Scale of the Problem

Amazon's decision was not reactive or sudden. The commingling system had a known structural flaw: because any seller's units under a given UPC were treated as interchangeable, a counterfeit or inferior product carrying the right barcode could enter the shared pool and fulfill a buyer's order placed with a completely different, legitimate seller. The buyer who expected an authentic product received something counterfeit. Neither seller could prevent it once both sets of stock hit the fulfillment center.

A Wall Street Journal investigation in 2014 documented exactly this pattern. Tovolo kitchenware saw counterfeit products surface in Amazon search results when authentic inventory ran low, because counterfeit units carrying matching UPC barcodes had mixed freely into the commingled pool. Johnson and Johnson withdrew many of its consumer products from Amazon the year prior, citing quality concerns that included expired and damaged items linked to commingled inventory practices.

The financial scale of the downstream damage was significant. Amazon stated at its 2025 Accelerate conference that brand owners collectively spent approximately $600 million in a single year on re-stickering costs alone - a consequence of commingled returns, where a seller's return slot received inferior or counterfeit units from another seller's stock rather than the original items. A seller who sent in authentic product could be credited with receiving a counterfeit upon return.

There is also an infrastructure factor. When Amazon first introduced commingling, one practical justification was delivery speed: pooling inventory across sellers meant units were distributed across more fulfillment centers, reducing transit time to customers. Amazon's network has since expanded substantially, with more centers positioned closer to end customers. The speed rationale weakened considerably, making the counterfeit risk no longer an acceptable tradeoff.

The Real Cost of Non-Compliance: Defective Classifications, Unplanned Fees, and Denied Reimbursements

If you send units to a fulfillment center after March 31, 2026 without required FNSKU labels, the consequences arrive in two distinct forms - and they stack on top of each other.

First, Amazon classifies unlabeled units arriving after the deadline as defective. Defective units are ineligible for reimbursement under FBA policies. That means if Amazon loses, damages, or cannot account for those units, you have no claim. The reimbursement path that exists for compliant inventory does not apply. The financial loss is permanent per unit, with no documented appeals process for the classification.

Second, if Amazon steps in and applies a missing label on your behalf - which it may do rather than immediately discarding or returning the stock - it charges an unplanned prep fee per unit on top of standard fulfillment fees. This creates a double penalty: you pay Amazon for the prep service, and the defective classification that blocks reimbursement still stands. A handful of unlabeled units in a small shipment is a manageable mistake. A pallet of several hundred units arriving without labels creates a per-unit cost exposure that accumulates fast with no offsetting return.

The calculation worth doing before your next inbound shipment: take your average unit value and multiply it by the number of units in a typical shipment. That is your maximum exposure if the labeling workflow breaks down. Against that figure, the per-unit cost of labeling at a prep center or in-house is a small fraction. Non-compliance is not a gray area with a manageable downside - it is a loss mechanism with no recovery route.

FNSKU Label Technical Specifications: Format, Paper, Print Resolution, White Space, and Placement

Printing compliant FNSKU labels means meeting specific technical requirements on multiple dimensions. A failure on any one of them - wrong paper finish, wrong print scale, wrong placement - can produce scan failures at the fulfillment center or route units into manual review.

A common label sheet format used with Seller Central's Print Item Labels workflow is the standard 30-labels-per-sheet layout (1 inch by 2-5/8 inches per label, a size commonly associated with the Avery 5160 layout). Many sellers use sheets in this format to print directly from Seller Central. Labels must be printed in black ink only, on white non-reflective paper. Glossy paper is not acceptable. The adhesive must be removable rather than permanent, because permanent adhesive creates packaging damage during returns processing. Note that the Avery 5160 itself uses permanent adhesive - the removable-adhesive equivalent from Avery is the 6460, and many generic label sheets in the same 1 inch by 2-5/8 inch format are available with removable adhesive. Confirm the current adhesive specification against Amazon's official FBA prep requirements before ordering label stock, as requirements can be updated.

Resolution has a minimum threshold. Amazon's official FBA label specifications document the exact requirement - pull that figure from Seller Central's current prep requirements rather than relying on any third-party source, since this is the kind of technical detail that can be updated. Thermal printers and laser printers reliably meet the requirement when configured correctly. Inkjet printers are not recommended; they do not consistently produce barcode quality that fulfillment center scanners read without errors.

The barcode requires specific white space clearances on all four sides. Amazon's label prep standards specify these clearances exactly - use that documentation as your reference, not an approximation. When printing from Seller Central, set your printer to 'Actual Size' or 100% scale. Scaling labels up or down even slightly shifts barcode dimensions enough to cause read errors at receiving.

Placement is not a judgment call. The FNSKU label must completely cover any existing manufacturer barcode on the packaging - UPC, EAN, or any other. If both barcodes remain visible at the fulfillment center, the scanner may read the wrong one, routing the unit incorrectly or triggering a commingling conflict. On shrink-wrapped products, the label goes on the shrink wrap itself and must cover the underlying manufacturer barcode through the wrap. Partial coverage is not sufficient.

The Transition Workflow: Generating, Printing, and Applying Labels Across a Multi-SKU Catalog

For a reseller with a handful of ASINs, the FNSKU transition is a workflow adjustment. For a reseller with hundreds of SKUs across multiple suppliers and inbound shipments arriving weekly, it is an operational change that needs a deliberate system behind it.

The first bottleneck is label generation. Because FNSKUs are generated per ASIN in Seller Central, a large catalog cannot be batched in a single pull. The standard workflow - Manage FBA Inventory, Edit dropdown, Print Item Labels - runs at the ASIN level. The practical solution for high-SKU operations is building a local label library: as you generate each FNSKU, save the label file organized by ASIN. You are then printing from a stored library rather than re-generating from Seller Central every time the same SKU ships. This eliminates repeated manual steps and reduces the risk of pulling the wrong file at the print stage.

Batching by shipment before product arrives is the step that makes the difference. When you know what is inbound, map each unit to its corresponding FNSKU before the product hits the receiving table. Print labels in advance, sorted by SKU. Trying to identify, generate, and print labels after product is already on the floor creates errors and slows throughput significantly on high-volume shipment days.

Multi-supplier inbound shipments - where a single delivery might contain product from three wholesale sources across fifteen different ASINs - require a receive-and-sort step before labeling begins. Units need to be sorted by ASIN and confirmed against shipment plan quantities before any labels are applied. Catching count discrepancies at this stage, before labeling, is far less costly than discovering them after product has been labeled and boxed for the fulfillment center.

For sellers transitioning from fully commingled operations, the first few shipments under the new system will take longer than steady-state will. The workflow becomes faster once the label library is built, processes are documented, and whoever runs the prep is practiced in the sort-label-verify sequence.

The Underrated Upside: How Seller-Specific Inventory Improves Returns Accuracy and Reimbursement Success

Most of the coverage around this policy change has focused on the compliance burden. The positive downstream effect for resellers is being missed almost entirely.

Because an FNSKU is tied to your seller account, every return that comes back to Amazon is credited to the account that originally sent the unit. If a customer returns a product you sold, that return goes back into your inventory - not into a shared pool where you might receive another seller's inferior or counterfeit unit as your credit. Your unit comes back to you, or Amazon processes a reimbursement against a clean record of what the unit was and who it belonged to.

This directly improves reimbursement claim accuracy. Under commingled inventory, disputed reimbursements were harder to substantiate because ownership history was murky - any unit in the shared pool could have passed through multiple sellers before the loss occurred. With FNSKU labeling, the record is clean from the moment of inbound receiving: your unit, your account, your claim if something goes wrong in the fulfillment center. Sellers who actively pursue reimbursement recovery will find that FNSKU-tracked inventory produces cleaner documentation and fewer rejected claims.

For resellers who were previously receiving counterfeit or expired units as commingled returns - a real pattern when other sellers in the pool had lower-quality or mislabeled stock - that exposure is structurally eliminated. What goes into your return slot is yours.

How a Prep Center Handles FNSKU Labeling for Resellers: Workflow, Turnaround, and Coordination

For resellers who do not want to run an in-house labeling operation - or those moving from commingled to FNSKU labeling at volume - a third-party prep center handles the full workflow per unit.

When product arrives at a prep center, the receiving team logs each unit against the seller's shipment manifest and sorts by ASIN. The seller must provide FNSKU label files in advance, generated from their own Seller Central account. A prep center cannot generate FNSKUs on a seller's behalf - these identifiers are account-specific. With label files in hand, the prep center prints compliant labels and applies them per Amazon's placement and coverage requirements: black ink, non-reflective white paper, correct print scale, manufacturer barcode fully covered.

For multi-SKU inbound shipments, a competent prep center runs a sort-verify-label-verify sequence. Units are sorted by ASIN first, then quantities are confirmed against the shipment plan, then labels are applied per SKU, then counts are verified again before units are boxed for the fulfillment center. That second count catches discrepancies before they become receiving errors on Amazon's end, which are significantly harder to resolve after the fact.

Per-unit fees for FNSKU labeling are separate from other prep services such as poly bagging, bundle assembly, or inspection. Check with your specific prep center for current pricing, as rates vary. Turnaround time depends on shipment volume and what other prep services the units need, but the labeling step itself - once product is received and sorted - moves quickly for experienced teams operating with organized label files.

The coordination requirement that matters most on the seller's side: send FNSKU label files before the shipment arrives, not after. Prep centers that receive product without label files ready sit on units while waiting. Those delays compound against your restock lead times and can push inbound shipments past your target windows. The simplest fix is making label file delivery part of your shipping confirmation process - when you notify the prep center that a shipment is on the way, attach the label files at the same time.