A manufacturer we work with had a rep promise a customer a ship date based on what the CRM showed as available inventory. The ERP had already allocated that inventory to a different order two days earlier. Nobody had synced the two systems in between, so the rep wasn't wrong about what she saw. She was wrong about what was true.
Two Systems, Two Versions of the Same Order
In most manufacturing sales operations, the ERP is where the order actually lives: inventory, pricing, production schedule, ship date. The CRM is where the relationship lives: account history, the open quote, the next call. Both are supposed to describe the same customer. In practice they describe two slightly different, slightly out of sync stories, and whichever one a rep happens to have open becomes the version they act on.
Why the ERP Almost Always Wins the Argument
When the two disagree, the ERP is usually right, because it's tied to production and finance, and nobody wants a shipment that doesn't match what was actually built. That's exactly the problem. The CRM keeps losing the argument, so sales teams learn not to trust it for anything that matters and go around it: a call to the shop floor, a text to someone in fulfillment, a spreadsheet a planner keeps on the side. The CRM turns into a contact list. The real source of truth lives in someone's head.
What Sales Actually Loses
A rep quotes a lead time that was accurate a month ago, before a supplier delay pushed the ERP's schedule back, because nothing told the CRM. An account manager doesn't know a customer's last three orders came in under spec, because that data sits in the ERP's quality module and never reaches the account record. A renewal call happens without the rep knowing the account is 45 days past due, because that's a finance field nobody thought to surface. None of these are CRM failures. They're gaps between two systems that were never told to agree with each other.
The Sync That Never Got Built
Most manufacturers we talk to have some integration between ERP and CRM, usually a one-way batch export that runs overnight on a schedule someone set up years ago and nobody's revisited since. That keeps the CRM from being completely blind, but it means every order status, ship date, and past-due balance a rep sees during the day is already stale by the time they see it. Ad-hoc fixes cover the gap for a while. Someone exports a report and cross-references it against the CRM by hand. That works until the account list gets too big to check manually, which is usually right around the time it starts to matter most.
What Actually Works
Real-time or near real-time sync in both directions, not a nightly batch job that's already a day behind by nine in the morning. Order status, inventory, and payment terms flowing from the ERP into the CRM automatically, so a rep never has to ask someone in operations what's actually true. Quote and relationship data flowing back the other way, so production knows a big renewal is at risk before it turns into a canceled order instead of after. And one owner for that sync who treats it as infrastructure to maintain, not a project that shipped once during implementation and got left alone.
Our Take
We don't start a manufacturing CRM engagement by redesigning the sales process. We start by finding out how far apart the ERP and the CRM actually are, and they're almost always further apart than the client expects going in. Close that gap and the sales team stops working from memory and starts working from the same record everyone else in the building is already using.