ERP Integration for FMCG Sales: What Actually Happens When You Connect SAP, Oracle, or Dynamics to Your Field App

By Sufyan · 2026-08-22 · 5 min read

A distributor in Jeddah once told me his reps were placing 340 orders a day into a field app, and his accountant was re-typing every single one into SAP the next morning. Three people. Full-time. Just for data entry.

That's the problem ERP integration is supposed to solve. And honestly? Most of the time it doesn't solve it as cleanly as the sales deck promises.

So I want to walk through what actually happens when you connect a field sales tool like Zivni to SAP, Oracle NetSuite, or Microsoft Dynamics 365 Business Central. What the connectors really do. Where they break. And what to ask before you sign anything.

What an ERP connector actually does (and doesn't do)

Let's get the basics out of the way. An ERP connector is a middleware layer — sometimes a set of APIs, sometimes a scheduled sync, sometimes a file drop — that moves data between your ERP and your field sales app.

The stuff that usually flows from ERP → field app:

And from field app → ERP:

Sounds simple. It isn't. Here's the thing — every ERP treats these objects slightly differently, and every FMCG business has customized their ERP over the years. Your SAP isn't my SAP. The Oracle in a Karachi biscuit company doesn't look like the Oracle running in a Dubai beverage distributor.

So when a vendor says "we integrate with SAP," the real question is: which SAP, which version, which modules, and who's writing the mapping?

SAP, Oracle, and Dynamics — the honest differences

I've now done integrations with all three across GCC and Pakistan clients. Here's what I've actually seen.

SAP (ECC and S/4HANA)

The big one for enterprise FMCG. If you're a Unilever distributor, a Nestlé bottler, or a major regional player, you're probably on SAP. Integration usually happens through SAP PI/PO, CPI (Cloud Platform Integration), or increasingly BAPI/OData calls.

The good news: SAP is well-documented and predictable. The bad news: nothing about SAP is fast. A typical SAP field sales connector project runs 6-10 weeks even with a solid partner. Expect to spend real time on order type mapping, pricing procedures, and the customer hierarchy (sold-to, ship-to, payer, bill-to — yes, all four).

Watch out for: pricing conditions. FMCG pricing in SAP is a beast. Volume discounts, scheme discounts, free goods, off-invoice, bill-back. If your reps see the wrong net price on their tablet, you'll hear about it within 48 hours.

Oracle (NetSuite and E-Business Suite)

NetSuite is where the mid-market FMCG guys live, especially in the UK and USA. The REST and SOAP APIs are genuinely good. SuiteScript lets you build custom endpoints when the standard ones don't fit.

Oracle EBS is older, chunkier, and mostly integrates through Oracle Integration Cloud or straight DB-level connectors. Slower to work with but stable once it's running.

With NetSuite specifically, the gotcha is subsidiaries and multi-book accounting. If a distributor operates across UAE and KSA with separate legal entities in NetSuite, your field app has to know which subsidiary each order belongs to. Miss that and reconciliation becomes a Friday night activity.

Microsoft Dynamics 365 (Business Central and F&O)

Business Central is genuinely pleasant to integrate with. The APIs are modern, OAuth-based, and the object model makes sense. Most of our Dynamics integrations at Zivni take 3-4 weeks, which is roughly half the SAP timeline.

Dynamics 365 Finance & Operations (the bigger sibling) is closer to SAP in complexity. Data entities are powerful but you need someone who knows what they're doing.

The questions nobody asks (but should)

When you're evaluating a sales ERP connector, most buyers ask about "features" and "support." Fine. But these are the questions that actually save you from a bad go-live:

  1. Is the integration real-time, near-real-time, or batch? A rep placing an order at 11am shouldn't wait until midnight to see it in SAP. But also — do you actually need real-time credit checks, or can you cache credit limits and sync every 15 minutes? The answer changes your architecture and your cost.

  2. Who owns the mapping document? This is the single most important artifact in an ERP integration. It lists every field, every transformation, every default value. If your vendor doesn't produce one, walk away.

  3. What happens when the ERP is down? Because it will be. SAP maintenance windows, Oracle patching, network issues in the Riyadh data center. Your field reps in Muscat still need to book orders. A decent connector queues transactions locally and replays them when the ERP is back. A bad one just fails silently.

  4. How do you handle master data conflicts? A rep creates a new outlet on Tuesday. Accounting creates the same outlet in SAP on Wednesday under a slightly different name. Now you have duplicates. Who wins? What's the dedupe logic?

  5. Can I see the logs? If a rep says "my order didn't sync," you need to open a dashboard and see exactly what happened. Not open a support ticket and wait 6 hours.

One last thing on cost

Most vendors quote the integration as a one-time fee. That's misleading. The real cost is the ongoing maintenance — every time your finance team adds a new pricing condition in SAP, or Dynamics releases a breaking API change, or you open a new market with a different tax regime, someone has to update the connector.

At Zivni we typically bundle a maintenance retainer into the ERP integration module because I got tired of clients being surprised. Budget for it either way. A connector isn't a fridge. You don't plug it in once and forget.

Happy to dig into any specific ERP if you're mid-evaluation — the pricing procedure conversation for SAP alone could be its own post. What's the ERP you're trying to connect?

© 2026 Zivni. All rights reserved.