Every food distributor we have ever worked with has, at some point, lived through a bad ERP project. The pricing tier didn't sync. The orders went to a queue nobody monitored. The customer master ended up split across two systems. There is a particular kind of Tuesday morning panic that comes with realising the integration you signed off six months ago has been quietly losing orders the whole time.
The good news is that the mistakes are remarkably consistent. Seven we see again and again, and what to do about each one.
1. Treating the ERP as the source of truth for everything
Your ERP is great at being the system of record for invoices, GL, AP, and anything an auditor cares about. It is usually terrible at the last mile. Customer-facing pricing, real-time inventory, the catalog as the buyer sees it. Distributors who try to make the ERP do all of it end up with brittle integrations and a sales team waiting on overnight batch jobs.
Better approach: let the ERP own what only it can own. Push live catalog and pricing to a customer-facing layer that's designed for read-heavy traffic, and reconcile back to the ERP on a sensible cadence.
2. Letting “real-time” mean “every API call hits the ERP”
Most ERPs in food are not built to take a hit every time a customer opens their phone. We have seen distributors take down their own production ERP because a popular new ordering app was hammering the pricing endpoint. “Real-time” in food distribution usually means “within 60 seconds,” not “synchronous.” Cache aggressively. Invalidate when prices change.
3. Not deciding who owns the customer master
This one will eat you alive if you don't deal with it on day one. If your CRM, your ordering app, and your ERP all think they own the customer record, you will end up with three slightly different versions of every account. Pick one master, write it down, and have every other system follow.
Half of all bad ERP integrations are actually customer master integrations in disguise.
4. Skipping the pricing rules edge cases
Food distribution pricing is genuinely complicated. Customer specific prices. Volume tiers. Promo overrides. Contract pricing with end dates. “Whatever Joe got last week.” If your integration doesn't have a written specification covering each of those cases, the first time a customer is overcharged it is going to be a long phone call.
Spend a day with your top sales rep going through their oddest accounts. Document every special. Then sign off on the integration spec.
5. Treating order errors as the integrator's problem
When an order fails to land in the ERP (bad SKU, missing customer, credit hold), what happens? In a lot of distributors, the answer is “nobody knows for a few hours.” The order sits in a queue, the customer thinks it is placed, and your driver shows up empty-handed.
Insist on visible, alerted error queues from the day you go live. Every failed order should ping a person in under five minutes.
6. Underestimating units of measure
Cases, pieces, pounds, kilos, bunches, half-pans, full-pans, eaches. The same SKU might be sold by case wholesale and by pound to one special account. The conversion lives in three different fields in most ERPs and four different places in the catalog. Get it wrong and you have either dramatically over or under charged. Get a unit of measure matrix written and validated before any data flows.
7. Going live without a rollback plan
Every cutover should have a documented “turn it off tomorrow” plan. Run the new integration in shadow mode for a week. Compare every order, every invoice, every inventory move against what the ERP would have done on its own. Then flip the switch.
Distributors who skip the shadow week always pay for it twice. Once in the cutover weekend, and again in the months that follow when they are still finding edge cases that broke quietly.
The pattern
The common thread under all seven mistakes: people treat the integration as a technical project when it is really an operational one. The ERP is the heart of how you take cash. Treat the connection like you would treat a new warehouse opening, with rehearsals, dry runs, and people on call.
What to ask any vendor
- How many distributors do you have live on my exact ERP version?
- Show me the error queue. Who watches it? What is the SLA on response?
- What happens to in-flight orders during your weekly deploy?
- If we want to leave you, how do we get our data out?
- Will you run shadow mode for a week before cutover?
If a vendor flinches at any of those, walk. The cost of getting an ERP integration wrong is much, much higher than the cost of getting it right the second time.