A medical device manufacturer earning $100M in annual revenue is quietly burning $4–7M every year on the gap between its ERP and its commercial team.[1] The money shows up as written-off bill-onlys, working capital tied up in consignment nobody can see, rep selling time consumed by admin work, and a customer service team that has grown faster than revenue. It rarely shows up on a single line of the P&L — which is why most companies don’t see it until growth makes it impossible to ignore.

A $200M spine manufacturer we spoke with last week was evaluating a full ERP replacement to fix what they called “stress fractures from rapid growth.” Manual paper charge sheets. PO matching draining their distribution network. Sales reps following up on billing status. Excel-based forecasting. Field inventory scrambling for cases. Their existing on-premise ERP was running general ledger, payables, receivables, and warehouse inventory cleanly. It could not run any of the workflows actually causing the chaos.

They were ready to spend two years and seven figures replacing the ERP. The chaos wasn’t an ERP problem. None of the workflows breaking under their growth — case scheduling, bill-only matching, consignment visibility, distributor reconciliation — live in any traditional ERP. Not their on-prem system. Not NetSuite. Not SAP. Not Business Central. Replacing the ERP would have delivered the same gap with a new logo on it.

“We need something now. We’re kind of, with our growth, with the stress fractures that are happening, just due to our growth, we need something we can rely on.” — Director of financial operations, growth-stage spine manufacturer

Traditional ERPs were architected in the 1990s and 2000s for manufacturers shipping pallets of finished goods to warehouses, who billed on shipment, paid suppliers on receipt, and closed the books on a monthly cadence. That model still describes most of the economy. It does not describe a medical device commercial team, where 60–80% of inventory sits outside the four walls and billing happens after a device has already been implanted.

What every major ERP does well

Where every major ERP breaks for medical device commercial work

The gap is not a vendor problem. It’s an architectural one. We have integrated against most of the major systems and the same pattern shows up across all of them.

The way to think about it: your traditional ERP is the system of record. A commercial ERP is the system of action. The system of record stores what happened. The system of action coordinates the work that produces the data the system of record needs.

Today, the system of action is your customer service team. They sit between unstructured inputs from the field and the structured data your ERP requires. They read the email. They open the attachment. They decipher the charge sheet. They look up the contract pricing. They chase the rep for the missing lot number. Then they type it all into the ERP. That is the commercial layer — and right now it’s a person.

Field Activity

Charge sheets, POs, usage texts, hospital emails, consignment counts, loaner requests, transfer notices

→

Commercial ERP — reads inputs, structures data, coordinates workflows

→

Traditional ERP

Sales orders, invoices, inventory adjustments, GL postings, financial reporting

What lives at each layer

Both layers are necessary. Neither replaces the other. The mistake we see most often is companies trying to push commercial workflows down into the ERP by customizing it — which works until it doesn’t, and then the upgrade path turns into a rewrite.

“We brought in a category-leading inventory tool a few years back to do all of our asset tracking. It’s gotten to be pretty manual. Our reps end up coming here every time they go in and move a set.” — Owner, orthopedic distributor

Order-to-cash is the workflow most often pointed at when leaders start asking whether their ERP is the problem. It usually isn’t. The ERP can generate the invoice and post the receivable cleanly. The breakdown is upstream — in the unstructured inputs that arrive before anything reaches the ERP.

What the work actually looks like today

A surgical case ends. A nurse, a rep, or a materials manager fills out a paper charge sheet. The rep snaps a photo and texts it to the back office, sometimes the same day, sometimes a week later. A customer service rep opens the photo, deciphers the handwriting, looks up the matching PO in the hospital portal, cross-references contract pricing in the ERP, types the order in line by line, and submits it for invoicing. If the price doesn’t match, the invoice gets credited and re-billed. If a lot number is missing, the rep gets called. If the PO never arrives, someone has to chase it down through the hospital’s materials team.

Typing the order is roughly twenty percent of the work. The other eighty percent is investigation and reconciliation — reading things, looking things up, and asking people for what’s missing.[2] No traditional ERP does any of that. It can flag a PO as unmatched. It can’t read the charge sheet, find the case, check the contract price, and chase the rep for the missing lot number.

What a commercial ERP does at this layer

“There’s a cork board in the office where George just takes the bill-onlys, prints them, puts them up, and waits for the PO to come in to do the matching.” — Operations lead, orthopedic implant startup

Most medical device companies have somewhere between one and ten million dollars of finished inventory sitting outside their warehouse at any given moment — in hospital consignment closets, surgical center stockrooms, and rep vehicles. The ERP shows it as a single line item: “consignment.” Where it actually is, how much of it has expired, who used what last week — the ERP can’t tell you, because nothing has told it.

Why traditional ERP can’t run this

What the commercial ERP layer adds

“The way our ERP does it, it’s like you’ve sold the unit to them, which you really haven’t. Then it just disappears. This trips up our auditors — they’re like, you bought 115 units this year? And we’re like, no, we really only bought 20.” — Owner, durable medical equipment company

A surgical case is the most complicated transaction in your business and the one your ERP knows the least about. A single case ties together a surgeon, a procedure, a hospital, a rep, a billing arrangement, a kit of instruments, a loaner set, and a consignment location. Today, the orchestration of all of that happens in group texts, email chains, phone calls, surgery scheduling portals, sticky notes on the back office whiteboard, and one or two shared spreadsheets.

No traditional ERP has the concept of a case as a first-class object. It has sales orders. It has invoices. It has inventory movements. It does not have a structured record that says “Dr. Patel, ACDF, Tuesday at 7am, Mercy Hospital, Rep Singh, Loaner Set 47, bill against PO-7821.” All of that context lives in the heads of three or four people who have to stay in sync across a week.

What breaks today

“We have a lot of stuff sitting out there. There’s a lot of volume. There’s a lot of cases. There’s a lot of scrambling to make sure that every case can be supported.” — Director of financial operations, growth-stage spine manufacturer

What a structured case object changes

Every case becomes a single record that pulls together the rep, the facility, the procedure, the surgeon, the inventory committed to the case, the loaner set assigned, the billing arrangement, and the documents required. Updates from any party flow to all parties. The back office sees the case as it’s scheduled, not after surgery’s done. The CFO sees the revenue forecast accurately because scheduled cases are visible weeks before they hit the ERP as invoices.

Medical device commercial work is rarely a two-party transaction. A typical structure has a manufacturer, one or more independent distributors, a 3PL, a network of 1099 reps, and a set of hospital customers. Each party has a different ERP, a different set of spreadsheets, and a different view of what’s happening. Reconciliation happens monthly, in Excel, and is usually wrong.

What each side needs to see — and rarely does

Today, every one of those data points lives in someone’s ERP — just not in the ERP of the person who needs it. The monthly reconciliation calls happen because the data exists, it just isn’t shared. EDI integrations between manufacturer and distributor ERPs solve part of this for purchase orders and invoices. They don’t solve it for the field activity in between, which is where most of the disagreement lives.

What the commercial ERP layer makes possible

A shared system of action that both parties write to and both parties read from. The manufacturer’s ERP and the distributor’s ERP each remain the system of record on their side. The commercial layer in between holds the live working data — cases in motion, inventory in the field, bill-onlys in process — with role-based visibility so that each party sees what they’re entitled to see.

The reconciliation call doesn’t need to exist. The data was never in disagreement — it was just in different buildings.

The shorthand: traditional ERP owns money. Commercial ERP owns motion. Where they overlap is the handoff — structured records flowing from the layer that captured the work to the layer that books it.

That’s the objection in the buyer’s own words. It’s a reasonable instinct. It’s also the same instinct that has been getting medical device companies to commit to two-year, seven-figure ERP projects for the last two decades, and it has not yet delivered the commercial layer.

Four reasons the “one ERP” path doesn’t close the gap

The faster path: keep your traditional ERP, layer a commercial ERP on top, get to value in 4–6 weeks. If a full ERP replacement still makes sense afterward, you’ll go into that project knowing exactly which workflows the ERP needs to handle and which it doesn’t.

Not every company needs a commercial ERP layer today. Below ten million in revenue, with a small team and a handful of facilities, a strong customer service operation can absorb the coordination load. Past that, the math shifts quickly. The signals below tell you whether you’re still in the absorbable range or whether the work has already outgrown the people doing it.

The growth-stage maturity model

The four-question diagnostic

Three or more “yes” answers means the commercial ERP gap is already costing you more than it would cost to close.

How to estimate each line for your business

The integration architecture is the part that makes the layered model work. Done well, the two systems behave as one to your team. Done badly, they behave as two of everything — two customer masters, two inventory counts, two pricing lists, two places to look for the same data. The pattern below is what we run with most customers.

What flows from the ERP to the commercial ERP

What flows from the commercial ERP to the ERP

How the connection is made

The commercial ERP integrates through whatever your traditional ERP supports: REST or OData for Business Central and most cloud platforms, SuiteTalk for NetSuite, Service Layer or RFC for SAP, or a custom API tunnel into an on-premise system. For on-premise installs, a secure VPN tunnel into your network is standard. There is no data migration, no rip-and-replace, and no change to your accounting close.