How to Run a Merchandising Team Across Multiple GCC Countries From One Dashboard

By Sufyan · 2026-07-14 · 5 min read

Last Tuesday I was on a call with a regional merchandising head based in Dubai. He manages 84 merchandisers spread across five GCC countries. He told me he spends the first three hours of every morning just figuring out who showed up to work.

Three hours. Before he's even looked at a shelf photo.

And honestly, that's the story for most FMCG merchandising Middle East operations right now. WhatsApp groups per country. Excel trackers that never match. A supervisor in Riyadh saying everything's fine while a supervisor in Muscat says the opposite. Nobody's lying. They just have no shared view.

So let's talk about what it actually takes to run a merchandising team across UAE, Saudi Arabia, Oman, Bahrain, and Kuwait from one screen. Not the pitch-deck version. The real one.

Start with the messy truth about multi-country ops

Each GCC country has its own rhythm. Saudi has Nitaqat and Saudization quotas that affect who you can hire as a merchandiser. UAE trade is dense and vertical — Carrefour, Lulu, Union Coop, Al Maya all within 40 minutes of each other. Bahrain and Kuwait are compact enough that one supervisor can physically cover most of the country in a week. Oman is spread out, and driving from Muscat to Sohar to Salalah is a real thing you have to plan around.

If your dashboard treats these as identical, you'll get bad data. I got this wrong at first. We built Zivni's early merchandising module with a single country template and assumed clients could just duplicate it. Turned out the SKU list, planogram compliance rules, and even the store visit frequency were different in every market. We had to rebuild it.

The fix wasn't more automation. It was letting each country configure its own beat plans and audit forms while rolling everything up to one parent view. Country-level autonomy, group-level visibility. That's the model that works.

What the dashboard actually needs to show

Here's the thing — most "dashboards" are just report libraries in disguise. A regional head doesn't need 40 charts. They need maybe six numbers, refreshed live, that tell them where to look.

For a multi-country merchandising software setup, this is what I'd argue actually matters on the main screen:

Everything else — the deep dives, the trend charts, the SKU-level analysis — sits one click deeper. The main screen is for triage.

One of our clients, a personal care distributor operating in UAE, Saudi, and Bahrain, cut their morning review meeting from 55 minutes to 12 minutes after we set this up. Same information. Just structured for decisions instead of discussion.

The operational bits nobody talks about

A few things I've learned watching merchandising management GCC teams try to unify:

Time zones aren't the problem. Workweeks are. Saudi and UAE now share Sunday-Thursday. But your dashboard still needs to handle public holidays that hit different countries on different days. National Day in Saudi is not National Day in Kuwait. Your "missed visit" alerts will scream false positives if you don't build this in.

Currency and reporting. If your sales ops team reports in USD but merchandisers log incidents tied to product value, you need FX handled at the dashboard layer, not in someone's spreadsheet later. Small thing. Huge time saver.

Language at the field level, English at the top. Merchandisers in Jeddah, Manama, and Salmiya are more comfortable in Arabic. Supervisors often want reports in English. The app has to do both without anyone thinking about it. If your merchandiser has to translate a form in their head, your data quality drops. I've watched it happen.

Photo quality standards. This one's underrated. A shelf photo from a Lulu in Sharjah and a shelf photo from a Danube in Dammam need to be judged by the same AI model with the same lighting tolerance and the same planogram reference. Otherwise your compliance scores are meaningless when compared across countries.

Supervisor workload. A supervisor managing 8 merchandisers across Abu Dhabi is not the same job as one managing 8 across Oman. Distance, drive time, and store density change everything. Your dashboard should show supervisor coverage load, not just merchandiser output. Otherwise you'll promote the wrong people and burn out the good ones.

Who actually looks at the dashboard

Quick reality check. The regional merchandising head looks at it maybe 4 times a day. Country managers look at it 8-10 times. Supervisors live inside the mobile version. The GM looks at a weekly digest and nothing else.

Build for the country manager first. They're the ones who'll either love the tool or quietly go back to WhatsApp. If they trust the numbers, everyone above and below them will too.

And trust takes about six weeks. That's roughly how long it takes for a country manager to stop double-checking the dashboard against their own spreadsheet. We've seen it consistently — with clients in Dubai, Riyadh, Muscat, doesn't matter. Six weeks, give or take.

So if you're two weeks into a rollout and the country team is still keeping their own tracker, don't panic. That's normal. What matters is whether the dashboard is telling them things their spreadsheet can't.

If it's not, you don't have a merchandising platform. You have a more expensive spreadsheet.

What would you want to see on that morning screen — assuming you had 84 merchandisers spread across five countries and 12 minutes to make sense of it?

© 2026 Zivni. All rights reserved.