Variable Sourcing Costs Are Quietly Destroying Your Floor Price Logic

October 2026. Your repricer is running. Your minimum price is set. You think the floor is holding. It is not. The moment you received a second lot of the same ASIN at a different landed cost, your minimum price became a fiction. One number is covering two different break-even realities. That is the floor price problem most operators never see until margin is already gone.

The Multi-Lot Problem Is Not a Reseller Problem

Retail arbitrage sellers surface this clearly. They buy two lots of the same ASIN on different trips. One came off a clearance rack at $8. One came off a standard shelf at $22. Both live in FBA under the same ASIN. The repricer sees one floor. It will sell the $22-cost unit at a price that works for the $8-cost unit. That is not a repricing problem. That is a data architecture problem. Brand-direct operators face the exact same situation through a different door: promotions, freight fluctuations, contract renegotiations, and spot buys all produce cost variation across receiving cycles. If your minimum price is not tied to lot-level landed cost, you are flying blind on at least some portion of your active inventory.

What the Top Decile Does Differently

The separation between average operators and top-decile performers on multi-SKU catalogs comes down to one discipline: cost cohort tracking. Average operators set one minimum price per ASIN and revisit it quarterly. Top-decile operators assign minimum prices at the receipt or purchase order level. When a new lot enters FBA at a different landed cost, the floor updates for that unit cohort. This requires your 3PL or warehouse team to track lot cost through to the SP-API feed, or at minimum, a reconciliation step before each repricing rule refresh. It is one extra process. It protects every unit that came in at a cost higher than your blended assumption.

Three Places Cost Variation Hides in Your Catalog

First: inbound freight. A container that landed in Q3 at $0.47 per unit does not cost the same as the air shipment you expedited in October at $1.83 per unit. Same SKU. Different floor. Second: supplier promotions. A 15% off invoice deal on a single purchase order drops that lot's landed cost below your standing minimum price assumption. You can price more aggressively on those units. You are probably not. Third: returns reprocessing. A unit that came back, was inspected, and re-entered FBA as sellable has a real cost attached to it—handling, inspection labor, storage cycle. If that cost is not captured in the floor for that unit, you are subsidizing the return economics invisibly. None of these are edge cases. All three happen across a normal operating quarter.

Three Moves to Fix It This Quarter

First, pull your last six receiving records and identify every ASIN where two or more lots entered FBA at different landed costs. That list is your priority queue. Second, for each ASIN on that list, calculate a lot-level minimum price: landed cost plus your target NetPPM floor, not a blended average. Set the stricter floor for any lot where cost was elevated. Third, build a standing rule that any expedited inbound shipment triggers an automatic minimum price review before the units go live in your repricer. Not after. Not at the next quarterly audit. Before the ASIN goes back into rotation. This is not a technology problem. Your repricer can handle multiple floor inputs. The gap is upstream data discipline.

Three Questions to Pressure-Test Your Floor Price Logic

Can you name the landed cost of the last two receiving lots for your top 20 ASINs by sell-through velocity? If not, your minimum prices are assumptions, not numbers. When your freight costs spiked this year, did your minimum prices move within the same billing cycle—or did they lag by 30 days or more? Every day of lag is a day you sold below your real floor. And finally: does the person who sets your repricer floors have direct visibility into purchase order cost data, or are they working off a SKU-level average someone else calculated? The answer tells you exactly where the fix starts. Start there.