FBA Commingling Ends in 12 Days. Amazon Rufus Has Been Reading the Mess.

The March 31 FBA commingling deadline is being covered as an operations story. FNSKU requirements, repackaging workflows, inventory transition logistics. That's real work.

But there's an Amazon Rufus angle nobody's connecting to it.

How Commingling Created a Review Problem

Commingling meant Amazon could fulfill your order with any unit from the same product catalog — yours or another seller's. High-volume, competitive products especially. The buyer got what they ordered. You might ship the unit, or a third party might.

When a counterfeiter introduced bad units into that shared pool, those units shipped as your product. Buyers received them, had bad experiences, left reviews on your product page. Amazon Rufus read those reviews.

Rufus synthesizes review sentiment by use case and attributes it to your product. It doesn't know the review came from a counterfeit unit — it just sees a 1-star that says "product quality was poor" or "received damaged item," attached to your ASIN. That's the data it uses when a shopper asks "is this worth buying?"

This is the signal pollution problem. And it's been accumulating for years.

The Categories Where It Hit Hardest

Not every product was equally exposed. Supplements, electronics accessories, batteries, personal care — high-volume, easy-to-replicate products where counterfeits moved volume. Brands in these categories faced the worst review data contamination.

At Envision Horizons we've audited dozens of supplement brands on Amazon and run systematic Rufus queries against them. Some brands with clean manufacturing and strong quality control showed quality and authenticity complaints in Rufus responses that didn't match their actual return rates or customer service patterns. The reviews were there. The complaints were documented. Rufus cited them.

One plausible explanation for that mismatch: commingling-era counterfeit reviews that never got addressed.

What Changes After March 31

Brands enrolled in Brand Registry with Brand Representative status have another option. They can opt out of FNSKU requirements entirely — Amazon recognizes them as the originating brand and doesn't pool their inventory. That's been available for a while. The March 31 deadline makes it the default for everyone without it.

Ending commingling stops new contaminated reviews from entering the pool. It doesn't remove the historical ones.

The Timing Problem

Sponsored Prompts — the paid ads inside Amazon Rufus conversations — go live with CPC billing on March 25. Six days before the commingling deadline.

Brands will start paying for Rufus impressions on March 25. Reviews that include commingling-era contamination will still affect what Rufus says in paid prompt responses. Ending commingling on March 31 stops the bleeding. It doesn't retroactively clean the wound.

So: you're paying for Rufus impressions while the review data is still partially contaminated, then cutting off the source of new contamination six days later. That's the sequence most brand teams don't have in view.

What to Do Before Both Deadlines

Before March 25 (Sponsored Prompts start):

Pull the last 90 days of your 1–3 star reviews. Look for patterns that don't match your product's actual performance. Quality complaints on products with clean manufacturing. Authenticity concerns. Damage claims on products you pack carefully.

If the volume is significant and the pattern suggests counterfeit units, file a brand protection claim. Commingling-era reviews from documented counterfeits can be removed — but only if you make the case. Brand Registry makes that process faster.

Also run a Rufus query on your product. Ask "is [your product] high quality?" or whatever the relevant sentiment question is in your category. What Rufus says is the signal you're about to pay to amplify on March 25. If the answer includes complaints from counterfeit reviews, that's what your Sponsored Prompts spend is working against.

Before March 31 (commingling ends):

Set up FNSKUs for all active ASINs. Or confirm Brand Representative status and opt out of the requirement.

For health monitors and cameras, this is urgent. Amazon Rufus fields accuracy and durability queries constantly in both categories. If your review corpus has commingling-era complaints about accuracy or build quality from counterfeit units — not your actual product — Rufus is citing those to shoppers right now. After March 31, at least the new reviews will reflect real product performance.

See the health monitors comparison guide for what Rufus-ready content looks like in that category specifically.

The Org Chart Problem

Nobody is connecting commingling to Amazon Rufus because it crosses two separate parts of most brand organizations. Operations handles commingling transitions. Brand or marketing handles Rufus optimization. They don't typically share the same review data analysis.

That's the gap. Two deadlines in the same week — March 25 and March 31 — both affecting what Rufus says about your products. One team is tracking the operations deadline. The other is (maybe) starting to look at Rufus. Neither has the full picture.

If you want to see what Rufus is actually saying about your products right now — before you start paying for Sponsored Prompts — that's what AgentBuy tracks. Including the review sentiment Rufus is synthesizing now, which may still have commingling-era noise in it.

March 31 stops new contamination. But the review data Amazon Rufus has been reading? That's been accumulating since the program started.