The multi-site visibility gap
In a single-plant manufacturer, inventory analytics is straightforward. The ERP holds the full picture: what is on hand, what is on order, what is consumed in production, and how those numbers translate into days on hand for every stocked item. The reports are accurate. The decisions are grounded in complete data.
In a multi-plant or multi-OpCo manufacturer, each plant's ERP picture is equally accurate and equally incomplete. Plant A's ERP tells the story of Plant A. Plant B's ERP tells the story of Plant B. Neither system tells the story of the network.
The consequence is predictable. A critical component runs to a stockout at Plant A while Plant B holds eight months of supply of the same part under a different item number. The purchasing team at Plant A places an emergency order with premium freight. The operations team at Plant B does not know a transfer opportunity exists. The network pays twice: once for the excess carrying cost at Plant B, and again for the premium freight at Plant A. Neither ERP report surfaces the problem because neither ERP knows what the other is holding.
This is not a data quality problem. Each plant's ERP data is accurate. It is a data consolidation problem: the network-level view that would surface the transfer opportunity does not exist in any single ERP system, and multi-site manufacturers typically have no mechanism for creating it without a cross-ERP analytics layer.
The item master fragmentation problem
The root cause of the multi-site visibility gap is item master fragmentation. In a company that has grown by acquisition, each plant typically manages its own item master. The same physical component receives a different item number in each plant's ERP, because each plant was set up independently and assigned its own local identity to every part it stocked.
A hydraulic seal kit that costs $180, is sourced from the same supplier, and performs the same function at three plants might appear as SEAL-HYD-220 in one ERP, Part 44-7891-B in a second, and 220-HSK-A in a third. To each plant's ERP, these are three distinct items with no relationship to each other. Without a normalization step, cross-plant comparison of days on hand for that part is structurally impossible.
Solving this does not require plants to rename or re-code their items in their own ERP systems. What is needed is a mapping layer at the analytics level that recognizes the equivalence between SEAL-HYD-220, Part 44-7891-B, and 220-HSK-A, and presents that relationship in the cross-plant view. That mapping is the unified item master, and it is what makes cross-plant days on hand analysis possible.
Transfer opportunity identification
Once the item master is unified and cross-plant days on hand is calculable, transfer opportunities surface automatically. A transfer opportunity exists when the same physical item is below its stockout threshold at one plant and above its excess threshold at another plant in the same network.
The economics are straightforward. Moving stock from Plant B to Plant A costs freight, handling, and coordination time. Purchasing the same stock from a supplier for Plant A while Plant B holds excess costs all of that plus the full purchase price of the new stock and the premium freight for an emergency order, and the excess at Plant B continues to accumulate carrying costs. For purchased components where material cost is significant, the savings per transfer incident can be substantial.
The transfer opportunity is only visible when two conditions are true simultaneously: the item master is unified across plants, and the DOH calculation is current at all locations. Neither condition can be met by plant-level ERP reports alone. The cross-plant view requires a data consolidation layer that connects to all plant ERPs and presents a unified inventory picture updated at the same frequency.
Consolidated slow-mover detection
Slow-mover identification is standard practice in plant-level inventory management: items above a days-on-hand threshold get flagged, and a buyer reviews whether to adjust the reorder quantity, return stock to a supplier, or write down obsolete inventory. The problem is that plant-level slow-mover flags tell you about the plant's situation, not about the item across the network. The pattern across plants changes both the interpretation and the required response.
A plant-level slow-mover report showing Plant A at 128 days DOH triggers a local review. A cross-plant view showing all four plants at 100 to 142 days DOH on the same item triggers a product-level review. These are materially different responses requiring different decisions from different people. The distinction is only visible from the consolidated network view.
Multi-ERP analytics for PE-owned portfolio companies
Private equity portfolio manufacturers face the multi-site visibility problem in its most complex form. Plants within a single OpCo sometimes run different systems. OpCos acquired from different companies typically bring entirely different ERP platforms: Dynamics at one, Epicor at another, Sage or NetSuite at a third. Each platform uses its own data model, its own item numbering conventions, and its own export format.
Multi-ERP inventory analytics does not require consolidating the ERP systems. ERP standardization is a multi-year, high-cost program with significant operational disruption risk. What it requires is consolidating the data at the analytics layer, above the ERP layer, in a way that normalizes item master data, translates each platform's data model into a common format, and maintains a live connection to each source system so the analytics reflect current stock levels rather than last month's manual export.
The data consolidation work compounds across use cases. The item master normalization and ERP connector work done to enable cross-plant inventory analytics also enables cross-plant procurement spend visibility, cross-plant pricing analytics, and the working capital view your board expects. The foundation serves every analytical use case, not just inventory. See the data consolidation framework for acquired manufacturers for how this layer is built and maintained.
The distinction also matters for the operating cadence at portfolio level. A PE operating partner running a 4-6 year hold needs inventory visibility across OpCos to identify working capital release opportunities, benchmark DOH performance across the portfolio, and monitor whether post-acquisition operational improvements are holding. None of that is possible from individual OpCo ERP reports. It requires the same cross-plant, cross-ERP consolidated view that enables the plant-level transfer opportunity and slow-mover analytics described above, applied at the portfolio level.
How Inventory IQ delivers multi-site inventory analytics
Inventory IQ connects directly to each plant's ERP, normalizes the item master across all sites, calculates days on hand per SKU per plant using the appropriate demand denominator, identifies transfer opportunities when cross-plant imbalances exist, and surfaces the consolidated slow-mover view across the network. For PE-owned portfolio companies with multiple ERP platforms, it maintains a live connection to each platform independently so the analytics layer stays current without requiring ERP standardization.
Inventory IQ connects to each plant ERP, normalizes the item master across all sites, calculates daily SKU-level DOH per plant, and surfaces the cross-plant views your operations and procurement teams need to act on imbalances before they become emergency orders. In multi-ERP environments, it handles each platform's data model independently without requiring standardization at the ERP layer.