Of the twelve full dashboard builds we delivered in 2025, nine encountered location code conflicts during validation. Not missing codes — duplicate codes. Two different warehouses using "DC-01" for different physical sites. A transit node sharing an identifier with a stocking location. A retail store code that matched a warehouse bay number.
None of these were discovered during the sales conversation. They surfaced in week six or seven, when live data from multiple sources was merged for the first time.
Why this keeps happening
Warehouse management systems are often deployed location by location, sometimes years apart, sometimes by different integrators. Each deployment uses whatever location naming convention made sense at the time. The ERP's location master may have been cleaned up during a migration, but the WMS instances at each site were not updated to match.
Weekly Excel reports mask the problem because each warehouse sends its own file with its own local codes. Nobody merges them until a cross-location dashboard forces the merge.
How we surface conflicts in a mapping workshop
Before any build begins, we run a location reconciliation exercise during the stock level mapping workshop:
- Export location master lists from every WMS and the ERP
- Plot them on a single hierarchy diagram
- Flag any code that appears in more than one system with a different physical meaning
- Assign temporary canonical codes for the dashboard build
- Document which source systems need permanent renaming (client's IT responsibility)
This exercise takes 60–90 minutes in a full-day workshop. It is not glamorous. It prevents the three-week delay that follows when validation reveals the same conflict with live stock data attached.
Who owns the permanent fix
We assign canonical codes for the dashboard and document the mapping. Permanent renaming in source systems is the client's IT team's task — we provide the mapping table but do not modify WMS or ERP master data as part of a dashboard build. Some clients schedule the rename during the build; others run with canonical codes in the dashboard for a quarter while IT plans the migration.
When to schedule cleanup before the build
If your mapping workshop reveals more than five conflicting codes across three or more systems, we recommend pausing the build and running a focused cleanup sprint. We have turned away two projects in 2025 where the data was not ready, and both clients thanked us six months later when they compared notes with a competitor's failed dashboard attempt at a trade event.