Why SAP Alone Isn't Enough for FMCG Field Operations
A distributor in Jeddah called me last March. His IT head had just spent 14 months rolling out SAP S/4HANA. Beautiful implementation. Finance loved it. Supply chain loved it. The 87 field reps? They were still using paper order books and a WhatsApp group called "Orders Daily."
He asked me a question I've heard maybe 40 times now: "We paid for SAP. Why do my reps still not use it?"
Here's the thing. SAP is incredible at what it was built for. It's just that field sales wasn't really what it was built for.
The mismatch nobody warns you about
SAP runs on structure. Master data, GL codes, approval workflows, MRP runs. It assumes the person using it is sitting at a desk, has stable internet, and has 20 minutes to complete a task properly.
Now picture Adnan. He's a pre-seller in Karachi covering 32 outlets a day on a motorbike. It's 43 degrees. The shopkeeper at outlet number 19 is yelling at him to hurry up because three customers are waiting. Adnan has maybe 90 seconds to take an order for 14 SKUs, check the credit limit, confirm the next delivery date, and snap a shelf photo.
Ask Adnan to do that inside SAP Fiori on a 4-inch screen with patchy 3G? Won't happen. He'll write it on paper. He'll send it on WhatsApp. He'll call the office. Anything but the "system."
And this isn't an Adnan problem. It's a tool-fit problem.
SAP was designed for back-office certainty. Field sales is front-line chaos. Trying to force one into the other is how you end up with a $400K SAP rollout and a separate Excel sheet that the sales manager actually trusts.
What SAP genuinely can't do well (and shouldn't have to)
Let me list the stuff I've watched SAP-only setups struggle with, again and again:
- GPS-tracked attendance and beat adherence. SAP doesn't know if your rep actually visited the outlet or just marked it visited. There's no geo-fence logic baked in.
- Voice order entry in Urdu, Arabic, or Hindi. Reps in our markets aren't typing 18 SKUs per outlet. They speak them. SAP's mobile interface isn't built for that.
- Shelf photo analysis. You can store a photo in SAP. Sure. But can it tell you share-of-shelf vs competitor brands across 12,000 outlets? No.
- Gamification. Leaderboards, streaks, points — the stuff that actually moves rep behavior. SAP wasn't built to gamify anything.
- Offline-first mobile. This one's huge. Half the outlets in Oman's interior or Punjab's rural belts have terrible signal. Reps need apps that work fully offline and sync later. SAP's mobile layer is online-dependent in most real-world setups.
- Distributor secondary sales visibility. SAP handles your primary sales (factory to distributor) beautifully. But secondary sales (distributor to retailer)? That's where most FMCG brands go blind. And that's the data the brand actually needs to plan trade promotions.
I used to think a strong SAP consultant could custom-build all of this. I was wrong. I watched a brand in Dubai spend 9 months and roughly $180,000 trying to build a custom SAP mobile order app. It worked. Sort of. Adoption stayed below 30%. They eventually layered a specialist tool on top.
The two-layer model that actually works
Here's what the smartest FMCG operations leaders I work with have figured out. They stopped trying to make SAP do everything. They run a two-layer stack instead.
Layer 1 — SAP (or Oracle, or Microsoft Dynamics): the system of record. Finance, inventory, procurement, master data, primary sales invoicing, GL. The stuff that needs to be airtight, audited, and integrated with the rest of the business.
Layer 2 — A field sales platform: the system of action. Beat plans, rep tracking, mobile order capture, photo audits, retailer onboarding, gamification, secondary sales analytics. Built for the phone in the rep's pocket, not the desktop in HQ.
The two talk to each other through an integration layer. SKU master, pricing, credit limits, customer master — all flow from SAP into the field app. Orders, visits, photos, and secondary sales data flow back from the field app into SAP.
This is what we've built Zivni to do. We're not trying to replace SAP. Honestly, we'd lose that fight, and we shouldn't be fighting it anyway. SAP is excellent at being SAP. We're the layer that sits between SAP and the 200 reps on motorbikes who'd never log into Fiori willingly.
When people search for an "SAP alternative FMCG" tool, they usually don't actually want to replace SAP. They want to stop forcing field reps to use SAP for things SAP was never built for. Those are very different problems.
What good SAP FMCG integration actually looks like
A few things I've learned about getting SAP field sales integration right, after doing it with brands in Riyadh, Lahore, Manchester, and Houston:
Keep SAP as the single source of truth for master data. Don't let reps create customers in the field app and have them magically appear in SAP later. That's how you end up with 4 versions of the same kiryana store and a finance team that wants to quit.
Use middleware or direct APIs. SAP PI/PO, CPI, or even a clean REST API layer. Avoid flat-file dumps if you can. They break. They always break.
Sync the right things at the right frequency. Customer master and pricing — daily or on-change. Orders — real-time or near-real-time. Stock — hourly is usually enough. Don't try to sync everything every minute. You'll bankrupt your API quotas and slow everyone down.
And please, get your SAP consultant and your field sales vendor in the same room early. Not after the contract is signed. I've seen 6-week delays because nobody asked whether the SAP environment had API access enabled until week 9 of the project.
So if you've got SAP and your reps still aren't using it for daily field work — that's not a failure of SAP. And it's not a failure of your reps either. It's a missing layer. The question is whether you keep patching around it with WhatsApp groups and Excel, or whether you actually build the second layer properly.
What would your CFO say if she knew how much of your secondary sales data still lives in a paper register?