Most retail execution software was designed for a market that looks nothing like Saudi Arabia. It assumes a small number of large chains, a single working language, mature master data, and reps who cover twelve stores a day in a dense urban grid. None of that describes the Kingdom.
Saudi Arabia asks a brand to run two operating models simultaneously. Modern trade concentrates enormous volume in a handful of banners with strict planogram discipline and their own compliance expectations. Traditional trade spreads the rest of your volume across thousands of independent groceries and convenience outlets with no data, no planogram, and no obligation to tell you anything. Software that handles one of these well often handles the other badly.
This guide is for brand managers, trade marketing leads and distribution managers evaluating retail execution software for the Saudi market. It covers what the category actually does, where the Saudi context changes the requirements, and the questions worth asking before you sign anything.
What retail execution software actually does
Strip away the positioning and the category does four things. It tells your field team where to go and what to do when they arrive. It captures what they found in a structured, comparable form. It turns that capture into a picture of your shelf that someone in head office can act on. And it closes the loop by feeding what happened back into the next cycle of planning.
Everything else is a variation on those four. Route planning, task assignment, photo capture, planogram checks, price audits, competitor tracking, out-of-stock alerts, promotion verification, KPI dashboards — all of it exists to move information between the shelf and the decision-maker with less loss along the way.
The reason the category exists at all is that the alternative does not scale. A field team reporting through WhatsApp messages and spreadsheets produces data that is late, inconsistent and unverifiable. By the time it is aggregated, the promotion has ended. We have written more on what a retail execution audit involves in practice and why the audit discipline matters more than the tooling.
Why Saudi Arabia is a distinct buying context
Four things about the Saudi market change the software requirement in ways that global vendor demos rarely address.
The channel split is genuinely bimodal
Your top ten accounts might represent the majority of your volume, and your bottom three thousand outlets represent the majority of your visits. These need different visit structures, different task lists, different frequencies and different success measures. Software that forces one visit template across both channels will produce either useless detail in traditional trade or dangerous shallowness in modern trade.
The workforce is multilingual and the head office is not
Merchandisers, promoters and van salesmen in the Kingdom commonly work in Arabic, Urdu, Hindi, Tagalog or Malayalam. The people reading the dashboards work in Arabic and English. A platform where the field app and the reporting layer must share a single language creates a permanent tax: either the field enters data in a language they are not fluent in, or head office reads reports it cannot parse.
Distribution is often not yours
Many brands in KSA reach the market through distributors who own the customer relationship, the route and sometimes the merchandising team. Your visibility ends where their system begins. Retail execution software that assumes you employ the field team directly will not survive contact with a distributor-led route to market.
Vision 2030 has raised the modern trade bar
Retail modernisation in the Kingdom has pulled compliance expectations upward. Category captains and key accounts increasingly expect brands to arrive with data, not opinions. That shifts retail execution from an internal efficiency project to a commercial requirement of doing business with the large banners.
The seven capabilities that matter most in KSA
Ranked by how often they turn out to be the thing that breaks an implementation, rather than by how prominently they appear in vendor marketing.
1. Configurable visit templates per channel and per banner
You need to define a different set of tasks for a hypermarket visit, a supermarket visit and a traditional grocery visit, and to vary that by banner where a key account has specific requirements. If templates are global, the platform will not fit.
2. Photo capture with structured verification
A photo is evidence, not data. What matters is whether the platform converts the photo into something countable — facings, share of shelf, planogram adherence, price accuracy. Image recognition can do this, though the honest answer is that its accuracy depends heavily on your catalogue quality and how the photo was taken. Our piece on how image recognition removes bias from execution reporting covers where the technology genuinely helps and where it oversells.
3. Offline-first architecture
Connectivity inside a hypermarket back-of-store or a basement grocery is unreliable everywhere, and the Kingdom is no exception. Offline-first means a rep completes a full visit with no signal and syncs later without data loss. Test this properly during evaluation, in airplane mode, on a full visit.
4. Route and territory planning that respects real geography
Riyadh, Jeddah and the Eastern Province have very different density profiles, and a route optimiser tuned for European city grids will produce schedules that ignore prayer times, mall operating hours and delivery windows. Route quality compounds: an extra visit per rep per day across a large team is a meaningful capacity gain. We covered the mechanics in smart route planning for field sales.
5. Distributor and third-party team access
If distributors or agency merchandisers touch your shelf, they need scoped access — able to submit visits, unable to see your full commercial picture. Ask specifically how the platform handles multi-organisation hierarchies. Many handle it by giving everyone a full licence, which is both expensive and a governance problem.
6. Arabic and multilingual field interface
Covered in more detail below, because it is the requirement most often treated as cosmetic and most often responsible for poor adoption.
7. Reporting your commercial team will actually open
A dashboard nobody opens is a cost centre. The test is whether a brand manager can answer a specific question — why did the promotion underperform in the Western region — without asking an analyst. Increasingly this means plain-language querying rather than filter navigation, which is the problem the AI assistant approach to retail data is designed to solve.
Like what your reading?
Take a moment to subscribe before continuing and never miss out on exclusive insights, news, and case studies.
Arabic field usability is a prerequisite, not a feature
Vendors will tell you they support Arabic. Almost all of them do, in the sense that the interface strings have been translated. That is not the same as being usable.
Things worth checking on a real device before you commit:
- Does the layout mirror properly in right-to-left, including form fields, date pickers, dropdowns and photo capture screens — or does the text flip while the layout stays left-to-right?
- Can a rep enter free-text notes in Arabic and can head office search those notes in Arabic?
- Do numbers, SKU codes and mixed Arabic-Latin product names render correctly, or do they reverse mid-string?
- Can the same deployment run Arabic for one team and English or Urdu for another, with reporting consolidated in whichever language the reader prefers?
- Are exported reports and PDFs right-to-left, or does the formatting collapse the moment someone downloads something?
The reason this matters commercially rather than aesthetically: field data quality tracks field app usability almost exactly. A rep who finds the app awkward will complete the minimum required fields and guess at the rest. You will not know this is happening, because the data will arrive looking complete.
Integration realities
Retail execution software does not sit alone. It needs product master data going in, and it needs to send execution data somewhere useful.
The three integration points that matter:
- Product and price master. Usually from your ERP. The question is not whether integration is possible but how often it syncs and what happens to in-flight visits when a SKU is discontinued mid-cycle.
- Sales and sell-out data. Execution data is far more valuable next to sell-out. Without it you can prove the display was built; you cannot prove it worked. If your distributors provide sell-out data at all, find out in what format and at what lag before you assume it can be joined.
- BI and reporting stack. If your commercial team lives in Power BI, the platform needs to export cleanly into it rather than insisting everyone log into another tool.
Master data quality is the silent determinant of success here. Duplicate SKUs, inconsistent outlet naming and stale store lists will degrade every downstream report regardless of how good the software is. Our guide to retail product management covers the catalogue hygiene this depends on.
Pricing models and what actually drives cost
Retail execution platforms are typically priced per active field user per month, sometimes with a platform fee and module-based add-ons for capabilities like image recognition or advanced analytics.
The variables that move the total more than the headline rate:
- Whether distributor and agency users count as full licences. This can double the seat count on a distributor-led model.
- Image recognition volume. Often priced per image or per scene. A large team photographing every visit generates a lot of both.
- Implementation and master data cleanup. Frequently underestimated. If your outlet list has not been audited in two years, budget for that work.
- Training and change management. Particularly relevant with a multilingual field team, where training material has to exist in more than one language.
- Contract term against pilot flexibility. A twelve-month commitment before you have validated adoption is a poor trade.
Ask for pricing modelled on your actual structure — your channel split, your distributor arrangement, your visit frequency — rather than a per-seat rate. The per-seat rate is rarely the number you end up paying.
Questions worth asking before you sign
These are the ones that tend to separate vendors who understand the region from vendors who have translated their interface.
- Show me a live Arabic field app on a mid-range Android device, completing a full visit offline.
- How do you handle a distributor-owned merchandising team that also services my competitor?
- What happens to my historical data if I leave, and in what format do I get it?
- Which of your current customers run both modern and traditional trade in the Gulf, and can I speak to one?
- What is your image recognition accuracy on my actual catalogue, measured on my photos, not your demo set?
- How long from contract to first usable report — not to go-live, to a report my brand manager trusts?
- Who cleans my outlet master data, and is that in scope or a change request?
A practical 30-day evaluation
Vendor demos are optimised environments. A short structured pilot tells you more than any number of presentations.
- Week 1 — scope narrowly. One city, one channel, one team of six to ten reps, three or four tasks per visit. Resist the urge to pilot everything.
- Week 2 — run it in Arabic. If your field team works in Arabic, the pilot runs in Arabic. Testing in English and deploying in Arabic tells you nothing about adoption.
- Week 3 — break it deliberately. Full offline visits, a mid-cycle SKU change, a rep with a cracked screen and an old device, a store that has closed down.
- Week 4 — measure the output, not the input. Can a brand manager answer a real commercial question from the pilot data without help? That is the only test that matters.
Two metrics to track through the pilot: visit completion rate and time per visit. If completion is high and time per visit is falling, adoption is real. If completion is high and time per visit is very low, reps are probably skipping fields.
Modern trade and traditional trade need different playbooks
The most common structural mistake in a Saudi retail execution deployment is applying one operating model to both channels. They reward completely different behaviour.
Modern trade: depth over frequency
In a hypermarket or large supermarket, a single visit carries high stakes. The planogram is defined, the space is negotiated, the category manager has expectations, and the volume concentration means an error costs real money. Visits should be less frequent and far more thorough: full planogram verification, share of shelf, competitor pricing, promotional compliance, stock cover in the back room, and a conversation with the store manager.
The measurement that matters here is compliance against an agreed standard, because you have an agreed standard to measure against.
Traditional trade: frequency over depth
In an independent grocery there is no planogram and no category review. What matters is whether you are present, whether you are visible, whether you are in stock, and whether the shopkeeper is willing to give you more space than your competitor. Visits should be short, frequent and focused on a small number of things done consistently.
The measurement that matters is coverage and availability, not compliance, because there is nothing formal to comply with. Asking a rep to complete a twenty-field planogram audit in a small grocery produces fabricated data and wastes the visit.
The implication for software
The platform has to let you run both without compromise. In practice that means channel-specific visit templates, channel-specific KPIs, and reporting that does not average the two into a meaningless national figure. A brand with 85% compliance in modern trade and 40% availability in traditional trade does not have a 62% problem — it has two separate problems requiring two separate responses. The five-step approach to field team management we use covers how to structure the team around that split.
Implementation mistakes that cost the most
Patterns that recur across deployments in the Kingdom, roughly in order of how expensive they turn out to be.
- Going live nationally at once. A phased rollout by region lets you fix template and master-data problems on a small population. A national go-live turns every problem into a crisis and permanently damages field team confidence in the tool.
- Skipping master data cleanup because it delays launch. Every downstream report inherits the quality of the outlet and product master. Launching on dirty data means the first reports are wrong, and the commercial team stops trusting the system before it has proven anything.
- Building the reporting layer last. If field data collection goes live months before anyone can read a useful report, the field team correctly concludes the extra work has no purpose. Adoption drops and does not recover easily.
- Too many fields per visit at launch. The instinct is to capture everything while you have the chance. The result is longer visits, lower completion and guessed answers. Start with the minimum that answers your priority question and add later.
- No supervisor layer in the system. If supervisors cannot see their team’s activity in the platform, they will manage through WhatsApp and the platform becomes a reporting obligation rather than a management tool.
- Treating the distributor as an afterthought. If distributors execute your shelf, their access model needs designing before launch, not bolting on afterwards.
The pattern underneath all of these: retail execution software fails for organisational reasons far more often than technical ones. The platform selection matters less than most buyers assume, and the rollout design matters far more.
Where to start
If you are early in this process, the most useful thing you can do before speaking to any vendor is to write down what you currently cannot answer. Not what you would like to automate — what question your commercial team asks that nobody can answer with confidence today.
That list becomes your evaluation criteria, and it is far more useful than a feature matrix. Feature matrices favour whichever vendor has the longest list. Your unanswered questions favour whichever vendor can actually answer them.
Shelvz is built for this market specifically: Arabic-first field apps, distributor-scoped access, and modern and traditional trade handled in one deployment. If you want to see it against your own outlet list and your own catalogue, book a walkthrough and we will run it on your data rather than ours.
