What Commingling Actually Is
When you send stock to FBA, Amazon has to know which unit belongs to whom. There are two ways to do that, and the choice sits in a settings page most sellers configure once during setup and never revisit.
The first option is the Amazon barcode, usually called an FNSKU. Every unit gets a label that is unique to you and to that listing, so the warehouse tracks your units as distinctly yours. The second option is the manufacturer barcode, the UPC or EAN already printed on the retail packaging. Choose that and your units join a pool with every other seller of the same product who made the same choice. Amazon calls this stickerless commingled inventory, and it exists because it is genuinely more efficient. Nobody has to apply a label, and the warehouse can ship whichever unit is closest to the customer.
The efficiency is real. So is the catch. In a commingled pool, the unit that leaves the warehouse under your order number is not necessarily the unit you sent in. Amazon treats the products as interchangeable because the barcode says they are. The customer, and therefore your account health, does not treat them as interchangeable at all.
How Another Seller's Unit Becomes Your Problem
Picture a popular kitchen gadget sold by fourteen sellers, nine of whom are stickerless. Those nine have poured their inventory into one shared bucket. Eight of them source properly from the brand. The ninth buys grey market stock of uncertain provenance, or older packaging, or units that have been returned, reboxed and sent back in.
A customer orders from you. The fulfilment centre nearest that customer picks from the pool. The unit that ships is the ninth seller's. It arrives with a faded box, a broken seal, or a manual in the wrong language. The customer does what customers do and reports that the item was not new, or that they believe it is not genuine.
That complaint lands on your account, because you were the seller of record on the order. Your account health page shows the issue. Your Voice of the Customer data degrades. If enough of these accumulate on the ASIN, Amazon may ask you for invoices proving authenticity, and the invoices you produce will be genuine and will not explain the unit the customer received, because that unit was never in your supply chain.
This is the part sellers underestimate. In a normal inauthentic complaint you defend yourself with supplier invoices. In a commingled complaint your invoices are perfect and irrelevant, because the defect belongs to a unit you never touched. The strongest evidence you have does not address the actual event.
Returns make the pool worse over time. A unit that goes out, comes back, gets assessed as sellable and returns to inventory rejoins the same shared pool. Every restocked return from every participating seller is in there with your stock. The longer a commingled ASIN has been trading, the more mixed the pool tends to be.
The Complaint Pattern to Watch For
Commingling damage has a recognisable signature, and spotting it early saves the listing. Look for these together rather than in isolation.
- Condition complaints that contradict your process. Reports of scuffed boxes, missing parts, opened seals or expired dates on a product you know ships factory sealed from a single supplier.
- Reviews describing packaging you do not use. Customers mentioning a different box design, an older logo, or a language variant you have never stocked is close to diagnostic.
- Complaint rates that ignore your changes. You improve prep, switch carriers, tighten inspection, and the complaint rate does not move, because your handling was never the variable.
- Problems concentrated on your commingled SKUs. If the FNSKU labelled half of your catalogue is clean and the stickerless half is not, that is not a coincidence about product categories.
Check the barcode setting before investigating anything else. Sellers routinely spend weeks auditing their own prep quality on a problem that a settings page would have explained in thirty seconds. The Voice of the Customer dashboard will tell you which ASINs are generating negative customer experiences, and the inventory settings will tell you which of those are stickerless. The overlap is your answer.
The Fix: Amazon Barcodes
The remedy is not complicated. In Seller Central, under the Fulfilment by Amazon area of your account settings, there is a barcode preference. Set it to Amazon barcode. From that point, units you send in are labelled with an FNSKU that ties them to you, stored as yours, and shipped as yours. The pool no longer applies.
A few practical notes on making the switch:
- The setting is account level, with per SKU overrides. You can change the default for everything and still handle individual SKUs differently, which is useful if you have a genuine commodity line where commingling makes sense.
- Someone has to apply the labels. Either you or your prep partner labels units before they ship, or you use Amazon's labelling service and pay a per unit fee. Both cost something. Neither costs as much as a suppressed ASIN.
- It changes nothing retroactively. Stock already in the network stays in the pool. Only new receipts are labelled.
- Some products are excluded from commingling anyway. Various categories, including many consumables and topicals, require Amazon barcodes, so parts of your catalogue may already be labelled without you having decided it.
Brand owners should also look at Transparency, which puts a unique code on every unit and lets Amazon verify authenticity at the point of fulfilment. It is a heavier lift than a settings change, since it involves applying codes during manufacturing, but for brands that are repeatedly targeted it addresses the problem at the source rather than downstream.
Cleaning Up Stock You Already Sent In
Changing the setting solves tomorrow. The stock sitting in the pool today still ships under your orders, and if the ASIN is already generating complaints, waiting for natural sell through means accepting more damage in the meantime.
You have two options, and the right one depends on how much harm the ASIN is taking. The passive route is to leave existing commingled units to sell through while all new receipts arrive labelled, which gradually dilutes the exposure. It costs nothing and it is slow, and it is reasonable when the complaint rate is low and the product is not brand critical.
The active route is a removal order. You pull the commingled units back, inspect them, relabel them with FNSKUs, and send them in as clean stock. This costs removal fees, inbound shipping and handling time, and it is the right answer when the ASIN matters and the complaints are mounting. One useful side effect is that you finally see what is actually in the pool, and sellers are frequently surprised by what comes back, which is itself an argument for the switch.
Whichever route you take, sequence it properly. Change the barcode preference first, then handle the legacy stock. Doing it the other way round means the replacement shipment arrives stickerless and rejoins the pool you just paid to escape.
Defending a Complaint You Did Not Cause
If the listing is already under pressure, you still need to respond, and the response has to acknowledge reality rather than protest innocence. A plan of action that simply asserts your stock is genuine will not be persuasive when the complaint describes a unit that does not match your stock.
The stronger structure is to name the root cause honestly and show that you have removed it. Your supplier invoices establish that your sourcing is legitimate. Your explanation identifies commingled fulfilment as the mechanism by which units outside your control reached your customers. Your corrective action is the barcode change, with the date you made it, plus the removal order if you placed one, plus whatever inspection or Transparency step you have added. That reads as a seller who diagnosed a systems problem, which is what account health reviewers are looking for.
Keep the evidence tight. Invoices from an authorised source covering the relevant period, with quantities that plausibly support your sales volume, are worth more than a large pile of documents. Screenshots showing the barcode setting now reads Amazon barcode, and the removal order confirmation, do real work here because they are proof of a change rather than a promise.
Where a specific complaint is clearly about a unit you did not supply, say so plainly and briefly, then move on to the fix. Reviewers see a lot of blame shifting, and the way to be believed is to pair the explanation with a structural change you have already made.
When Commingling Is Genuinely Fine
It would be dishonest to say nobody should ever use it. Commingling exists because for some inventory it is the correct trade. If you are selling a genuine commodity where units are functionally identical, unbranded, low value, hard to counterfeit and rarely returned, the labelling saving is real and the downside is small. Plenty of sellers run this way for years without incident.
The decision turns on one question: what happens if a customer receives a unit that is not yours. For a pack of generic cable ties, the answer is a shrug and a refund. For a supplement, a cosmetic, an electrical item, anything for children, or any product carrying your own brand, the answer is a complaint that can take the ASIN offline and put your account under review. Those are not comparable risks, and they should not get the same setting.
Brand owners in particular should treat this as close to non negotiable. You spend money building a brand so that the name means something to a customer. Commingling hands the quality control of that promise to strangers with no interest in protecting it, in exchange for a fee measured in pennies per unit. That trade does not make sense, and the sellers who discover it during a suspension invariably say they had no idea the setting was there.
Frequently Asked Questions
Commingled, or stickerless, inventory is FBA stock stored by manufacturer barcode rather than by a seller specific label. Units of the same product from every participating seller are pooled together, and when a customer orders from you, Amazon may ship any unit from that pool, including one another seller sent in.
Change your barcode preference in Seller Central from manufacturer barcode to Amazon barcode, found under the Fulfilment by Amazon section of your account settings. From that point new shipments receive a seller specific FNSKU label, so your units are tracked and shipped as yours rather than pooled.
No. Changing the setting only affects stock sent in afterwards. Units already stored as stickerless remain in the shared pool until they sell through or you create a removal order and send them back in labelled.
If your inventory is commingled, the unit the customer received may not have been yours. Returns that were restocked without proper inspection, and units from sellers with weaker sourcing, sit in the same pool and ship under your order. The complaint attaches to the seller on the order, not to whoever supplied the unit.
Slightly, because you avoid a per unit labelling fee and some prep time. For a low value, high volume, unbranded commodity that saving can be rational. For any branded product where an inauthentic complaint could suspend the ASIN, the saving is trivial against the risk.
