Written By
Share This Article
Every ops leader watches field inventory closely during M&A integration. Almost none of them are watching during the window that actually matters — the six months after the ERP goes live, when leadership exhales, the legacy system goes offline, and your reps' workarounds quietly harden into the way you operate.
On February 1, 2003, Space Shuttle Columbia broke apart as it re-entered Earth's atmosphere. The cause traced back to a piece of foam that had broken off the external tank during launch seventeen days earlier — striking the shuttle's left wing and breaching its heat shield.
NASA engineers knew about the foam for more than twenty years. They had documented it shedding from the external tank on dozens of prior flights without catastrophic failure. By the time Columbia lifted off, engineers who raised concerns were told the issue was already classified as acceptable risk.
Sociologist Diane Vaughan spent years studying NASA's decision-making after both Columbia and Challenger. She called what she found normalization of deviance: the gradual process by which a known problem stops triggering alerts because it hasn't yet produced a catastrophe. The risk wasn't highest the first time the foam shed. It was highest after years of uneventful flights had made the problem invisible.
The same pattern shows up in MedTech after an acquisition. Except instead of ignoring foam on a heat shield, teams ignore field inventory.
The Real Risk Window Opens After Go-Live, Not During Integration
The first six months after a merger closes are consumed by the ERP. Two systems need to become one. Item masters, pricing structures, finance — all of it has a go-live date attached and a team accountable to it. Field inventory sits outside that priority stack. Not forgotten. Just not the crisis in front of anyone right now.
So the reps adapt. They build workarounds. They reconcile across two systems the way they figured out how. They request stock they already have because they can't see what's out there. Nothing catastrophic happens in week one. Nothing happens in month three. The ERP goes live and the integration is declared done. And by the time anyone turns their attention back to field inventory, the workarounds have hardened into the operating model. It's not a problem anymore. It's just how you operate.
Most ops leaders treat the M&A integration period as the window of maximum field inventory risk. The chaos is visible: two item masters, two field databases, reps running on different systems. Everyone knows the data is unreliable.
That awareness is actually protective.
The real risk window opens six months after the ERP goes live.
The spreadsheets are gone. The legacy system is offline. Leadership exhales. And field inventory visibility, already fractured by the merger, quietly hardens into whatever your reps decided to do while nobody was watching.
What Calcifies in the Silence After the ERP Goes Live
Here's what that looks like. Reps from the acquired company tracked consignment stock their way. Your reps had theirs. The new ERP absorbed the master data, but it didn't absorb the behavior. Cycle counts run on different schedules. Kit configurations get reconciled differently. Nobody standardized case scheduling during the integration crunch because there wasn't time.
Your system of record says coverage is high. But the demand signal is inflated because reps are requesting stock they already have. The traceability gaps from the integration period never got cleaned up. You don't have a bad ERP. You have a field ops model that was never standardized, and now it's baked in. That inflated demand signal means working capital tied up in product that isn't turning. The traceability gaps become your next audit problem. The regulatory exposure compounds quietly — consignment instruments with unclear chain-of-custody, implantable devices with documentation gaps that only surface during a recall or an FDA inquiry.
None of this shows up in an integration status report. It shows up twelve months later in a write-down, a failed audit, or a compliance finding that traces back to a process nobody ever formalized.
Kotter called it the premature victory celebration — declaring the war won a little too soon is what kills momentum.
The ERP go-live announcement is the premature victory celebration. What calcifies in the silence that follows is yours to own.
How the Companies That Avoid This Build It Into the Integration Plan
The companies that don't have this problem didn't fix it six months after go-live. They brought field inventory into the integration plan before the ERP project started — before the reps had a chance to adapt and their workarounds became the operating model.
Here's what that looks like operationally. Both rep populations — the acquiring company's and the acquired company's — launch on the same system from day one. There's no "their way" to fall back on because there's no gap to fill. Cycle count schedules are standardized from the first week, not negotiated over twelve months of competing practices. When a rep requests stock, the system surfaces what's already in their territory — so the inflated demand signal never forms. Traceability runs continuously from case one, which means when audit season arrives, there's nothing to reconstruct.
Movemedical integrates in 6–8 months — well within a typical M&A integration timeline. Companies that brought it in at the start of their integration have seen 20% reductions in days inventory on hand and 60% less time on audit prep. Those numbers aren't the result of fixing a broken field ops model. They're the result of never having to.
If you're already past go-live, the window is narrower — but it's not closed. The longer the workarounds run, the more expensive they are to unwind.
If your acquisition closed in the last 18 months, it's worth a conversation.
