Direct store delivery lives or dies on what happens at the back of a van at eleven in the morning, forty kilometres from the depot. Repzo is a cloud sales and field-force platform built for that moment: the rep's route, the order, the stock on board, the invoice and the settlement. Whether it fits you depends less on its feature list than on how your routes, your stock discipline and your invoicing obligations actually work today.
You run reps or vans against planned routes, you sell to outlets rather than to a warehouse, and the gap you feel is visibility: which visits happened, what was sold, what came back, and why the van's stock does not agree with the depot's. Distributors and manufacturers with their own field teams are the clearest case, and the value shows up fastest where the current answer is a messaging group and a spreadsheet.
We do not recommend it when the problem is upstream. If depot stock is wrong before the van is loaded, field software will report your inaccuracy faster, not fix it — sort warehouse accuracy first. We also do not recommend it for pre-sell-only operations with a handful of reps and no van stock, where a CRM and a good order form are cheaper and sufficient. And we would not commit before the field test in section 2.2. Start with an impartial assessment.
One clarification first, because it will come up in your first vendor call: the vendor does not sell a product called "Repzo DSD". Repzo describes itself as a cloud-based sales and field force management solution, and direct store delivery appears in its own materials as Sales Orders and Van Sales (DSD) — one solution within the platform, beside merchandising and maintenance and services. We keep the name on this page because that is what Saudi operators search for, and we tell you the truth about it because you will be quoting from a different name sheet than the vendor. What Repzo publishes on its own site: route planning and optimisation, real-time location tracking of field reps, visit scheduling with adherence tracking, sales orders and van sales, merchandising, inventory transfers, customer-specific pricing, configurable data-capture forms for the field, and real-time reporting; it names FMCG, pharmaceutical and field services among the industries it serves.
The limitation we care most about is the one nobody writes down: what the application does when the van has no signal. Saudi routes leave coverage regularly, and the difference between queuing a transaction cleanly and losing it is the difference between a working rollout and a mutiny in week three. We do not restate an offline claim here, because the vendor's own published pages do not make one that we could cite — so we tell every client to put it in writing and then prove it, in a live field test on a real route, before signing. Two more: adoption is a field-discipline problem before it is a software problem, and location-based visit verification changes the relationship with the sales team, which needs handling openly rather than sprung on them at go-live.
Three things make Saudi DSD its own problem. First, e-invoicing: an invoice raised at the back of a van is still an invoice, and ZATCA's e-invoicing obligations apply to it with VAT at 15%. How the field application produces a compliant invoice — and what happens to that invoice when connectivity drops — is a question to settle in procurement, not after go-live. Second, route geography: dense urban routes in Riyadh and Jeddah behave nothing like regional distribution across long distances, and a route-optimisation engine tuned for one will disappoint on the other. Third, the field team itself: reps and supervisors need the application in the language they work in, and a rollout that ignores that produces beautiful dashboards fed by invented data. We assess all three against your operation, alongside the wholesale and distribution sector context these projects sit in.
We publish no prices. For field platforms the licence is rarely the largest line over three years. The rest is device provisioning and replacement for people who work outdoors, mobile data, the integration into ERP and accounting so that orders and invoices reconcile without re-keying, the master-data cleanup that integration exposes, training that has to reach every rep rather than a room of managers, and the supervision capacity to actually use what the system reports. We build that model with your numbers and you keep it.
The shortlist usually has three shapes: a specialist field-sales platform like this one, a field module bolted onto the ERP you already run, and the regional alternatives that compete for the same Saudi accounts. They differ most on offline behaviour, on how honestly they handle van stock reconciliation, and on the quality of support you can actually reach from the Kingdom. Our independent software comparisons show how we score them; the shortlist is assembled per client, because route profile decides it.
We start from the operation — route count, van versus pre-sell mix, outlet types, what currently breaks — and score candidates against it before any vendor demo. We are not paid on which platform wins, which is why "your problem is depot accuracy, not field software" is an answer we are free to give. The wider asset, maintenance and field operations category shows where this sits.
A field platform that does not reconcile with ERP creates a second set of books. We map the order-to-invoice flow, the stock movements between depot and van, the customer and pricing master data, and the settlement path — then decide who owns each mismatch before one happens, and prove the round trip on real data in a pilot region before the national rollout.
Reps, supervisors and back office learn different things, and reps learn them on the route rather than in a classroom. We train by region, run the first cycles with support on call, and watch the adoption numbers in the first weeks — a rep quietly reverting to paper is the failure mode, and it is visible early if anyone is looking.
We publish no figures here. What we agree with you before go-live, and report against afterwards, is a short list: visit completion against plan, order accuracy at the outlet, van stock variance at settlement, invoice exceptions per cycle, and how long a rep actually spends on the application. Those tell you whether the rollout worked. Somebody else's percentage does not.
We do not quote a duration before seeing the route count, the ERP integration surface and the state of the customer master. A single-region pilot and a national rollout are different projects, and we size both in the assessment rather than guessing on this page.
Section 4 lists the components. The two most often missed are device replacement for people working outdoors and the master-data cleanup the ERP integration forces into the open.
We do not certify a third party's compliance on a marketing page. We put the questions in procurement: how the field application produces a ZATCA-compliant invoice, what happens to an invoice raised without connectivity, and where customer and transaction data is stored and processed. We hold the written answers to the contract.
Whichever fit the route profile, including the ERP-module option in section 5, which is often right for an operator already deep in one ERP. We show the scoring, not just the conclusion.
That is the normal shape — it sits alongside the ERP rather than replacing it. Whether it integrates cleanly with yours is an evaluation question we answer by testing, before commitment rather than after.
The heading is the brief's; we publish no numbers here. A project counter with no denominator is decoration, and in field rollouts the only relevant question is whether we have done one shaped like yours — same route profile, same ERP, same scale. Ask us directly and we will answer specifically.
We name clients only with their consent and in direct conversation, never on a product page. Organisations that have agreed to be named publicly are on our customers page; the rest are available as references on request.
Outcomes belong to the operators who achieved them. We will walk you through comparable rollouts under an appropriate confidentiality arrangement and introduce you to the people who ran them, which is worth more than a paragraph we wrote about ourselves.
We publish no quotes on this page. A conversation with an operations director who has lived through a field rollout is worth more than a curated pull-quote, so we arrange the conversation.
We claim no certification for this platform and hold no reseller position with its vendor. On a page whose entire value is independence that is the point rather than a gap. Where we do hold technical partnerships they are contractual and listed as such, and none of them binds the advice given here.
Continue with the asset, maintenance and field operations category, our independent software comparisons, the wholesale and distribution sector page, or an impartial assessment.
If you run vans or field reps in Saudi Arabia, start with a conversation rather than a demo. You will leave with a fit verdict, an integration map, a three-year cost picture and a written list of the questions to put to the vendor — starting with what happens when the signal drops. Book a session or ask for an impartial assessment.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.