Since June 2024 that question has a different shape. Shift4 completed its acquisition of Revel Systems, and Revel is no longer marketed as an independent product — its own website now forwards to Shift4. If you are choosing a new POS system for a Saudi operation today, the honest starting point is that Revel is not a like-for-like candidate against actively marketed platforms, and the decision you are really making is about Shift4's roadmap for it.
You already run Revel across your branches and it is doing its job. An operating estate is not invalidated by an acquisition, and ripping out a working POS on news alone is how operators buy themselves a year of disruption. The right move is a structured review: what your contract says, what support you are actually receiving, and what the migration trigger points would be.
We do not recommend signing a new Revel deployment in Saudi Arabia. Any current capability, support or roadmap commitment now has to come from Shift4 in writing, and until it does, a new rollout rests on claims nobody can verify. Evaluators who were quoted Revel should compare actively marketed alternatives — start with our independent software comparisons, including Lightspeed vs Revel Systems, which covers this exact situation.
We deliberately do not list Revel's feature set here. The vendor documentation that would back those statements now redirects to Shift4, and a capability table nobody can source is marketing, not advice. What Revel does today, and for how long, is a question for Shift4's published materials and your contract — we help you put that question precisely.
The structural limitation is uncertainty: product direction, release cadence and regional support for Revel in the GCC are Shift4 decisions now. Before committing budget to expanding a Revel estate, get the support and roadmap position in writing and weigh it against the cost of migrating to a platform that is being actively sold in the region.
Saudi F&B and retail operators running Revel still have to meet the Kingdom's requirements — ZATCA e-invoicing obligations and VAT at 15% do not pause because a vendor changed hands. An acquisition also changes who answers when a compliance-relevant update is needed. We assess what your current setup covers, what depends on vendor updates, and where a local integration layer protects you. See how this plays out for the food & beverage sector.
We do not publish licence prices — for Revel there is currently no public Saudi price list to cite. The cost question that matters now is three-year cost of staying versus cost of moving: remaining licence and support fees, integration maintenance, the risk premium of an uncertain roadmap, and on the other side, migration, retraining and dual-running during a cutover. We build that comparison with your numbers, not ours.
For most Saudi evaluations the shortlist question is no longer "Revel or something else" but "which actively marketed platform fits the operation Revel was serving". Our comparison pages put the candidates side by side on multi-branch operation, offline behaviour, integration surface and local support — independently, because we are not compensated to steer the outcome.
We start from your operation — branch count, service model, existing systems — and score candidates against it before any vendor conversation. For Revel estates that produces one of three verdicts: stay and stabilise, stay and plan the exit, or migrate now. An impartial assessment makes that call defensible.
POS never lives alone: accounting, inventory, aggregators and payment providers all attach to it. Whether you stay on Revel or migrate, we map every integration you depend on and plan its continuity first — the integrations, not the tills, are where cutovers fail.
If the verdict is migration, cashiers and branch managers get trained on the target platform before cutover, branch by branch, and the first trading days run with support on call. If the verdict is stay, we document the support path so your team knows exactly who answers what.
We do not publish client names, counters or percentages on this page. What we can say about outcomes: the operators who navigate a vendor acquisition well are the ones who made the stay-or-move decision deliberately, on evidence, before it was forced on them. Ask us for references relevant to your sector and we will arrange direct conversations.
We do not quote durations for new Revel implementations, because we do not recommend starting one. For an existing estate, the meaningful timeline is a migration timeline, and it depends on branch count, integration surface and data volume — we size it in the assessment.
For Revel the three-year view must price uncertainty: support continuity, integration maintenance and a possible forced migration mid-window. We model stay-versus-move with your actual contract figures.
Compliance posture is configuration- and version-specific, and for Revel the update path now runs through Shift4. We verify what your installed version covers against ZATCA requirements rather than repeating a vendor claim.
Today the evaluation runs the other way: which alternatives replace it. Our Lightspeed vs Revel comparison is the published starting point; the full alternative set depends on your vertical.
Existing integrations keep working until something changes on either side. The risk to manage is maintenance: who patches the connector when an API changes. We audit that dependency chain as part of the estate review.
Because we are independent. We do not resell Revel or Shift4, we are not paid on the outcome, and the same team that would advise "stay" will advise "move" when the evidence says so. That is the entire value of the assessment.
We name clients only with their consent and in direct conversations, not on product pages. References from Saudi F&B and retail operators are available on request.
Every engagement ends in a written, evidenced recommendation — stay, stabilise or migrate — with the integration map and cost model that back it. The deliverable is yours whether or not we run the implementation.
We do not publish testimonial quotes on this page. Speak to our references directly — it is worth more than a curated pull-quote.
We hold no Revel or Shift4 reseller position — on this page that is a feature, not a gap. Our technical partnerships are listed where they are contractual; none of them binds the advice given here.
Continue with POS systems, the Lightspeed vs Revel Systems comparison, our independent software comparisons, or the food & beverage industry page.
If you run Revel in Saudi Arabia, or were quoted it, book a session. You will leave with a clear stay-or-move position and the evidence behind it. Request a session or ask for an impartial assessment.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.