Warehouse Inventory + SKU Mapping: preventing wrong-product restocks
These tiles are early in the restock path because the first danger is not math. The first danger is trusting the wrong product identity or ignoring stock already in the building.
Warehouse Inventory exists to answer
“What do we physically have, and is it usable for future sales?”
SKU Mapping exists to answer
“Are the Amazon listing, internal SKU, supplier item, and warehouse count all talking about the same product?”
Mistake prevented
Reordering product we already have, or ordering the wrong product because the SKU/ASIN relationship is off.
Inside Warehouse Inventory
Physical count
This is not the same as Amazon sellable inventory. It means units in Brent’s world: shelf stock, golden stock, replacements, returns, or other local states. Franz must ask whether a count is current usable stock or a historical/starting balance.
Section/location
Location matters because product in the wrong place can look unavailable even when it physically exists. Section data helps explain whether inventory can realistically feed the next restock/prep action.
Events/notes
Notes explain why the number exists. If a count changed because of a pull, return, adjustment, or shipment, the note may matter more than the raw count.
Inside SKU Mapping Validation
SKU
The internal operating identifier. If it is wrong, every downstream lookup can be wrong.
ASIN/listing
The Amazon-facing product identity. Confirming this prevents applying demand from one listing to inventory from another.
Supplier/manufacturer item
The buying identity. Restock only works if the product we order from the supplier matches the Amazon product we intend to sell.
Escalation rule
If mapping is uncertain, stop. Do not proceed to order quantity. A questionable mapping turns the restock math into false confidence.