Running FMCG Operations Across Pakistan, UAE, and East Africa Without Losing Your Mind
Three currencies. Four languages. Roughly 1,200 outlets spread across Karachi, Dubai, and Nairobi. That was the setup of a customer we onboarded last year, and honestly, watching their ops head try to reconcile three different Excel sheets every Monday morning is what convinced me Zivni had to get the multi-country thing right.
Because here's what most founders don't tell you: managing FMCG operations across Pakistan, UAE, and East Africa isn't a scaling problem. It's a translation problem. Translation of currency, of business rules, of what a "productive call" even means in each market.
Let me explain what I mean.
The Same Brand, Three Completely Different Field Realities
In the UAE, a field rep working modern trade in Dubai might cover 18 outlets a day. Carrefour, Lulu, Spinneys. Big trolleys, structured planograms, clean shelves. The rep's main job is shelf execution and ensuring secondary placement isn't getting eaten by a competitor brand.
In Karachi or Lahore, that same rep is covering 45+ kiranas in a day, mostly on a motorbike, mostly cash transactions, and the "shelf" is whatever the dukaandaar feels like arranging that morning. Order frequency is daily or every other day. Credit cycles are messy.
Then you go to Nairobi or Kampala. Now your rep is doing van sales through dukas, mobile money is the dominant payment rail (M-Pesa runs everything), and the route might cover 80 kilometers of dust roads. Stock-outs aren't about poor forecasting — they're about whether the van made it through traffic before 2pm.
Same brand. Same SKU list (mostly). Three completely different operating systems.
A regional FMCG management platform that treats all three the same is going to fail. I learned this the hard way in our first year — we built Zivni's beat planning module assuming UAE-style outlet density and got destroyed in Pakistan demos. Reps were laughing at us because we were suggesting 12 calls a day when their target was 40.
So we rebuilt it. Configurable per country, per distributor, per rep type.
What Actually Needs to Be Country-Specific
This is the bit I wish someone had written down for me. When you're designing or buying multi-country FMCG software, these are the things that genuinely have to differ by market — not just translate:
Currency and tax logic. Obvious one. AED, PKR, KES, UGX, TZS. But it's not just display — it's reporting, target setting, incentive calculation. A rep in Pakistan hitting PKR 8,50,000 in monthly sales and a rep in UAE hitting AED 45,000 need to show up on the same regional dashboard with comparable performance metrics. A multi-currency sales platform that just converts at end-of-month FX rates is lying to you. You need locked rates per reporting period.
Outlet classification. A "wholesaler" in Pakistan is a different animal from a "wholesaler" in Kenya. In the UAE you probably don't even have that channel — it's all modern trade and HoReCa. Your outlet master needs flexible categorization, not a fixed taxonomy.
Compliance and tax invoicing. UAE has VAT and FTA requirements. Pakistan has FBR and provincial sales tax (which varies — Sindh and Punjab don't agree on much). Kenya has eTIMS now and KRA wants real-time invoice transmission. If your sales app can't generate compliant invoices per market, your distributors will refuse to use it. We watched this happen to a competitor in Nairobi last year.
Payment methods. Cash dominates in Pakistan secondary sales. Cheques in UAE distribution. M-Pesa in Kenya. Your app needs to capture these natively, not force everything into a "cash/card/other" dropdown.
Language for the rep, not just the dashboard. Urdu for Pakistani reps. Arabic for some Gulf reps (though English works for most in UAE). Swahili for East African reps. The head office in Dubai might run in English but the guy entering an order on his phone in Faisalabad needs Urdu buttons or he'll make mistakes.
The Reporting Layer Is Where Most Platforms Break
Here's the thing — getting data into the system per country is the easy part. Getting it out in a way a regional VP can actually use? That's where most multi-country FMCG software falls apart.
I used to think a good regional dashboard meant pretty charts. I was wrong. What regional leaders actually need:
- Comparable metrics across markets (productive call rate, strike rate, lines per bill) calculated with local context but displayed in a normalized view
- Currency conversion that's transparent — show me PKR sales AND the AED equivalent, not just one
- Drill-down that respects local hierarchy. A distributor in Mombasa rolls up differently than a distributor in Sharjah
- Exception reporting that flags issues per market's norms, not against a global average
The last point matters most. If your average productive call rate is 78% in UAE and 62% in Pakistan (because the market structures are genuinely different), a regional alert that flags "anything below 70%" is useless. You're either ignoring Pakistan or pretending UAE has no issues.
Zivni handles this with per-market benchmarks that roll up to a regional view. Took us about 14 months of iteration to get right. Still not perfect.
One Platform vs Three Platforms — When Each Wins
Look, I'll be honest. There are situations where running three separate tools makes sense. If your Pakistan business is fully independent with its own P&L, its own ERP, its own distributor network, and zero shared SKUs with your UAE business — you probably don't need one platform. Just use the best local tool in each market.
But if you're a regional FMCG player — and most of our customers are — sharing brands, sharing supply chain, sharing senior leadership, and trying to apply lessons from one market to another? Then one platform wins, hard. The data fluency you build when your Karachi team can see what their counterparts in Dubai are doing with the same brand is worth more than the licensing cost difference.
The customer I mentioned at the top? They cut their monthly reporting cycle from 11 days to 2. Their Kenya GM started copying merchandising tactics from Pakistan (turns out aggressive secondary placement works in dukas too). And the CEO finally stopped getting three conflicting versions of "how many outlets did we cover this month."
That's the real win. Not the dashboard. The shared language.
If you're trying to figure out how to set this up for your business — or you've been burned by a platform that promised multi-country support and delivered three disconnected instances — drop me a line. I'd rather have a real conversation than push a demo.