Combine inventory across every warehouse into one table. Flag every SKU below its reorder point so procurement reorders before stockouts hit.
I want to consolidate inventory across my CHI and NYC warehouses. Build me a flow that combines both into one table and flags any SKUs where total available inventory falls below their reorder point.
1. Pull inventory from each warehouse. WMS export, 3PL portal, or ERP feed per location.
2. Standardize the SKU and quantity fields. One row per SKU per warehouse with the same column structure.
3. Sum to a total available position. SKU-level rollup across every warehouse.
4. Compare against the reorder point. Reorder points live in the ERP or a reference table.
5. Output the table. Full consolidated inventory plus a flagged view of SKUs below reorder.
Multi-warehouse consolidation combines the stock positions of every location into one table, so a SKU has a single total available quantity across the network rather than a separate number per building.
The network view is what reorder decisions actually need. A SKU can look healthy at one warehouse and be nearly out everywhere else, and the reorder point applies to the total, not to whichever location someone happened to open first. Getting there means reconciling SKU codes and quantity definitions that differ by site.
Procurement and planning read it daily, and every new location makes it harder: another system, another export format, another naming convention for the same product.
The brand opens a second warehouse. Then a third. Each new location adds its own WMS, its own export format, and its own way of naming the same SKU. Procurement is responsible for keeping the brand in stock across all of them, and procurement is doing the math by pulling one CSV per warehouse every morning and stitching them into a workbook.
The cost of the workbook is not the time. It is the lag. The CSVs are stale by mid-day. The reorder points are accurate as of last quarter. The SKU that needs a PO today does not get one until the workbook gets rebuilt next week. By then the brand is short.
The right answer is one table fed by every warehouse on a schedule, with reorder logic that compares total available to a current reorder point and surfaces the SKUs that need attention now.
