Most comparison pages age. This one changed while nobody was looking, and the honest version has to start there. In June 2024, Shift4 - in its own words the leader in integrated payments and commerce technology - completed its acquisition of Revel Systems, and as of this page's writing Revel's own web address resolves to a Shift4 page. One side of the pairing this page is named for is a currently marketed standalone product; the other is a product line inside an acquirer.
Lightspeed Retail is presented by Lightspeed as a retail POS system and payments offering - an integrated platform combining software and hardware to facilitate and manage sales transactions in retail environments, cloud-based, with a built-in inventory management system. Revel Systems was one of the established names in cloud point of sale, which is exactly why this keyword still gets searched - by buyers who shortlisted it, and by operators who already run it and are deciding what the acquisition means for them.
This page does the same two things the rest of this cluster does - decision rule first, then evidence, then genuinely invertible conditions - with one addition this pairing forces: it tells you which questions can no longer be answered from published vendor material at all, so that you put them to the vendor in writing instead of trusting a page, ours included.
Our interest, stated before the argument rather than after it. We work with point-of-sale platforms including Lightspeed's and can deliver implementations and migrations on either side of this page. That is a commercial interest in your decision and you should have it now rather than find it on a partners page afterwards. We hold no reseller or distribution agreement for either product and earn nothing from which licence you buy - but implementation revenue is an interest in its own right. Section 8.1 sets out what we do about that.
The honest first answer is that this is no longer a comparison between two like things. Lightspeed publishes current, standalone product documentation for its retail POS. Revel's vendor no longer maintains a standalone marketing presence for it - revelsystems.com resolves to Shift4's site - and Shift4's own published statement about the acquisition is an investor release, not a product roadmap. A scorecard that fills Revel's column from memory or from third-party review sites would be the exact thing this cluster exists to argue against.
Choose Lightspeed when you are buying a retail POS today and want the vendor's current published offer. What Lightspeed publishes is specific: an integrated software-and-hardware platform for retail transactions, cloud-based, with built-in inventory management, multi-location management of inventory, sales and customer data across channels and stores, ecommerce reach, and customizable reporting. Whether that matches your operation is testable - section 3 gives you the tests.
Treat the Revel side as a question for Shift4, not a column on a scorecard. If Revel is on your shortlist, or already on your counters, the decision-relevant facts - product roadmap, support commitments, contract continuity, what happens to your hardware at renewal - are answerable only by the current owner, in writing. Section 5 lists the exact questions. A yes to those questions can make staying (or even buying) rational; silence is also an answer.
Choose neither yet if what you are really deciding is bigger than a till - if the POS decision is entangled with an ERP, ecommerce or payments decision that should be made first. That is section 6.
What follows compares what is published, and says plainly where nothing is. Every claim below is drawn from the named vendor's own current published material and nothing else. On this pairing that rule has a visible consequence: most of one column cannot be built, and we show you that rather than papering over it. Verify anything that will carry weight in your decision against each vendor's current documentation and your own scripted scenarios.
| Dimension | Lightspeed | Revel Systems |
|---|---|---|
| What the vendor currently says it is | A retail POS system and payments offering - an integrated platform that combines software and hardware to facilitate and manage sales transactions in retail environments | No current standalone statement to cite: as of this page's writing, Revel's own web address resolves to a page of its acquirer, Shift4. That is a fact about the vendor's web estate, not a claim about the product's quality |
| Ownership | Lightspeed | Shift4 completed its acquisition of Revel Systems in June 2024; Shift4's release states the acquisition provides it approximately 18,000+ merchant locations |
| Multi-location, as published | Integrate and manage inventory, sales and customer data across all your sales channels and stores | Row not built: no current vendor documentation to cite. Put the question to Shift4 directly - see section 5 |
| Inventory, as published | A comprehensive inventory management system is built in | Row not built, same reason |
| Ecommerce and reporting, as published | Ecommerce reach from your site to social selling to online marketplaces; customizable reports available anywhere, anytime | Row not built, same reason |
| Offline operation | Row not built for either product. The brief for this page asked for an offline-mode comparison; no offline-operation claim appears in the material cited here for either side, and we will not fill the row from third parties. If tills that keep selling through an outage matter to you - and in most Saudi retail they should - make it a scripted scenario in section 7's evaluation and require each vendor to demonstrate it, not state it | |
| Saudi e-invoicing (ZATCA) | Neither vendor's material cited here makes a ZATCA claim, and this page makes none on their behalf. ZATCA's own position governs: taxpayers may choose any e-invoicing solution provider as long as it is compliant with the requirements, and ZATCA considers the taxpayer compliant where the requirements are met even where the provider is not on ZATCA's indicative list. At the point of sale this is not abstract - the POS is where the compliant document is born. See section 3.3 | |
Read the empty cells as information. They are the difference between what you can verify today about each side of this shortlist, and that difference is itself decision-relevant.
Six criteria decide a POS selection in Saudi retail, and the weight each carries depends on how many branches you run and who holds your payments relationship.
This section carries no price, subscription fee, processing rate or hardware figure. Neither side's cited material publishes a Saudi-market figure we could cite, and our own fee ranges are not published yet - ask, and you will have it before you talk to anyone. We publish no price for either platform and no comparative figure between them.
The lines that belong in a POS cost model, so two proposals can be compared on one template:
Lightspeed's published multi-location claim - managing inventory, sales and customer data across all your sales channels and stores - is the sourceable anchor here, and it is a claim about scale of estate, not scale of transaction volume. Test it as one: your branch count, your SKU count, your busiest hour, in a demonstration scripted by you rather than the vendor.
On the Revel side we publish no scalability statement, because there is no current vendor documentation to take one from. The scalability question that IS answerable today is organizational: which entity signs your contract, which entity supports the product in three years, and what the acquirer's published intentions for the product line are. Get those answers in writing before scale of software becomes worth testing at all.
For a point-of-sale system this criterion outranks most others, because the POS is where the tax document originates. This section states only what the regulator publishes.
ZATCA implements e-invoicing in two phases. Phase One, the Generation Phase, was enforced from 4 December 2021 for all resident taxpayers and any party issuing tax invoices on behalf of suppliers subject to VAT; invoices are issued through a compliant electronic solution and carry additional fields depending on the transaction type. Phase Two, the Integration Phase, is enforceable from 1 January 2023 in waves; in this phase the electronic solution must be integrated with ZATCA's systems and e-invoices must be generated in the required format.
ZATCA also publishes the point that reframes vendor claims: taxpayers may choose any e-invoicing solution provider as long as it is compliant with the requirements, and ZATCA will consider the taxpayer compliant where the requirements are met even if the provider is not on ZATCA's indicative list. The obligation sits with you, not with a badge on a vendor's site.
We do not state either product's current compliance status, and you should treat any page that does with caution. Require each bidder to show you, on a live till, a simplified tax invoice generated and integrated per your wave's requirements - your items, your VAT registration, your receipt format - before compliance carries any weight in your scoring.
A retail POS is never alone: it meets your ERP or accounting system, your ecommerce channel, your loyalty scheme and your payments provider. Lightspeed publishes the integration surface of its own platform as spanning physical and online channels - from your site to social selling to online marketplaces - which is a claim about breadth you can test against your actual channel list.
The test is the same one the ERP pages in this cluster prescribe: list every interface the till must serve on day one, the e-invoicing integration first; for each, establish who builds it, who owns it, what happens to it at upgrade, and what it costs to keep. On the Revel side, add: which company's engineers answer that question now.
We publish no count of certified implementers or support engineers in the Kingdom for either platform - no such figure is published by either vendor in a form we could cite, and inventing one is what this cluster exists to argue against.
What to do instead: require named individuals and response commitments in the proposal, ask what happens to the support relationship after go-live, and - on this pairing specifically - ask who legally provides support in Saudi Arabia for each product today, and confirm the answer against the contract entity you would actually sign with.
Neither side's cited material publishes an implementation duration, so this page publishes none. We publish no week or month count for either platform.
What actually moves a POS rollout: branch count and geography; data migration scope (SKUs, customers, loyalty balances); the number of integrations live at cutover; hardware logistics; and staff training across shifts. Ask both bidders for a plan with those five stated as assumptions, and compare plans rather than durations. A bidder who will not state the assumptions has not given you a date.
Written to be invertible. Each condition is specific enough that you can tell whether you are in it.
This section is different from every other section 5 in this cluster, and honesty about why is the point. We cannot list published-capability conditions for Revel, because its vendor publishes no current standalone material to cite. What we can do is name the circumstances in which the Revel side is still a rational choice, and the questions that make it one.
What we will not do is fill this section with capability claims from reviews, resellers or memory. If the conditions above do not describe you, section 4 - or section 6 - does.
Three cases.
The POS decision is downstream of a bigger one. If you are also choosing an ERP, an ecommerce replatform, or a payments provider, decide the anchor system first - the POS must integrate with all three, and choosing it first inverts the dependency. Our retail industry page sets out how these systems hang together in a Saudi retail operation.
You are a single till, not an estate. Much of what distinguishes platforms at this level - multi-location inventory, channel integration, estate reporting - is weight a single-location shop pays for and does not use. Start from the wider POS systems page and let your growth plan, not a comparison of enterprise features, pick the tier.
You arrived here for the acquisition, not the comparison. If you run Revel today and your only question is "what now?", you do not need a scorecard - you need Shift4's written answers to section 5's questions, and an exit-cost line from section 3.1 so that staying and leaving are both priced before you negotiate renewal.
A comparison page can frame a decision. It cannot weight criteria it does not know about, and yours are specific to your entity structure, your existing estate, your sector and your timetable. This is how we turn the framing into a defensible decision.
Criteria first, products second. We write and weight the evaluation criteria with you, and you sign them off, before either product is scored. Criteria written after the candidates are known tend to describe the candidate the author already preferred.
Your scenarios, your data. Both bidders are given the same scripted scenarios, built from your floor - your items, your busiest hour, your returns and exchanges, a simulated connectivity outage, an e-invoice generated per your ZATCA wave - and scored on the same sheet by the same people. A vendor demonstration shows the best path through a product with clean data, which is not evidence about your case.
The full cost, on one template. Both proposals are normalized onto a single multi-year model containing the lines section 3.1 names, with the same growth assumptions applied to each. This is where close-looking quotations separate.
A written recommendation, with the conditions that would reverse it. You get a scored comparison, a recommendation, the assumptions behind it, and an explicit statement of what would have to be true for the other answer to win.
And a genuine third option. If the evaluation concludes that your incumbent is adequate, that a tier down is right, or that the purchase should wait a year, that is what the report will say. How we evaluate impartially describes the method in full, including how conflicts are declared and how criteria are locked before scoring begins.
Fees for both are not published yet - ask, and you will have it before you talk to anyone - and how we work sets out where a selection sits among the stages of an engagement.
The honest answer has two halves, and the second is the one that should matter to you.
First, the disclosure. We are a delivery firm as well as an advisory one. We work with both platforms on this page and can implement either, which means we have a commercial interest in this decision that a pure research house does not. We hold no reseller or distribution agreement for either product and earn nothing from which licence you buy - but implementation services revenue is an interest in its own right, and pretending otherwise would be the fastest possible way to lose your trust. Assume the same is true of almost every firm publishing a comparison like this one, whether or not they say so.
Second, what is done about it, because a disclosed interest is manageable and a denied one is not. The criteria are written and weighted with you and signed off by you before either product is scored. The "choose the other one" conditions are published on this page, in sections four, five and six, rather than kept for a meeting. The evaluation is charged as a fixed fee agreed before scoring begins, so what we earn from the evaluation does not depend on which way it goes. Every recommendation ships with the conditions that would reverse it. And "keep what you have" and "buy a tier down" are outcomes we reach and record as outcomes, because they are.
Third, what you should require - of us and of everyone else. Ask, in writing, before the engagement begins, what the adviser earns under each possible outcome of the recommendation, and require the answer as a clause in the engagement letter rather than as a reassurance in an email. If you would rather the selection were run by someone with no delivery capability at all, say so - there are cases where that is the right call, and we will tell you plainly when yours is one of them.
This page is written to stay true rather than to stay fresh. Everything on it describes structural characteristics - what each vendor publishes its product to be, how the family is organized, what deployment and licensing structures are documented - because those change on a scale of years. It carries no version numbers, no release names, no feature ticks, no prices and no compliance statuses, because those change on a scale of weeks.
It also carries a rule the rest of the market does not publish: every claim on this page about a product we do not make is taken from that vendor's own current documentation, and any comparison point we could not source that way was removed rather than estimated. Several conventional rows are missing from section 2 for exactly that reason - every current Revel capability row, offline operation on both sides, any price or processing rate, any ZATCA readiness status, POS market share in the Kingdom, and any claim about the acquirer's product roadmap. The ownership facts in section 2 are cited to the acquirer's own June 2024 investor release and to what the vendor's own web address resolves to as of this page's writing, with the date recorded. Their absence is deliberate. A comparison that fills those rows from memory is the thing this page exists not to be.
So use this page for the shape of the decision, and verify the specifics that will carry weight against each vendor's current documentation, against ZATCA's own published list of compliant solutions for the e-invoicing question, and above all against your own scripted scenarios run on your own data. If something here reads as out of step with what a vendor is telling you today, tell us - we would rather correct the page than defend it.
We publish no aggregate figure here: no count of selections run, no share of programs delivered on time, no average saving, no satisfaction score. Not because there is nothing to say, but because a number of that kind is unverifiable by you, is produced by the firm it flatters, and would refute the argument the rest of this page spends fifteen sections making. A buyer evaluating advisers should discount such figures wherever they appear, this page included.
What we will do instead is both more useful and more checkable. In a first conversation we will describe comparable engagements in enough detail for you to judge the fit - sector, entity structure, scope, what the evaluation concluded, and whether that conclusion held afterwards - and where the client permits it we will put you in touch with them directly. Our published, client-approved work is on the success stories pages.
The organizations that bring us this comparison are recognizable by shape rather than by name. Multi-branch retailers whose till estate has outgrown its first POS. Operators running Revel today, deciding between renewal and migration after the acquisition. Retail groups consolidating separate front-of-house systems after a merger. And single-brand operators expanding from three stores to ten, discovering that the POS that ran three cannot see ten.
We do not publish a client list on this page. The organizations that have agreed to be named appear on our customers page, which is maintained with their permission rather than assembled to support a comparison article.
Our published project work lives on the success stories pages, where each entry is a real engagement whose client has approved the account of it. We deliberately do not write case studies for a comparison page: a case study assembled to support an argument is not evidence, it is illustration - and on a page arguing that you should discount claims whose author has an interest in them, publishing one would be self-refuting.
If you want project evidence specific to your decision, ask for it in the first conversation and be precise about what would persuade you: the same sector, the same entity structure, the same platform, the same problem, a reference call. That is a reasonable thing to require of us and of everyone else you shortlist.
We do not publish a client quote until the client has reviewed and approved the exact wording attributed to them, so this section will carry real, attributed testimonials from selection engagements as those approvals arrive - rather than a composite, a paraphrase, or a quotation drafted in-house and signed off in passing. A quote assembled by the firm it praises is worth precisely nothing, and putting one on this page in particular would quietly contradict every other section of it.
References matter to a decision of this size. Ask in the first conversation and we will connect you with a comparable client wherever confidentiality permits.
On a page that asks you to discount claims from authors with an interest in the outcome, our own interests belong in plain sight rather than in a footnote. We work with both platforms named here and can deliver either, and we hold technical relationships and certifications with a number of enterprise technology vendors. We hold them for one reason: advising on a platform without people who have actually worked inside it produces advice that reads well and fails in delivery.
Three rules govern how that interacts with this comparison, and each is something you can hold us to. Our evaluations are not restricted to products we work with. Where a relationship exists with a vendor under consideration, it is disclosed at the point of the recommendation rather than left for you to discover afterwards. And no vendor sees, funds, reviews or approves this page or any evaluation before it reaches you.
Our current certifications and technology partner network are published on the partners page.
This page settles a shortlist of two. The pages around it answer the questions on either side of it. Lightspeed Retail and Revel Systems set out what we deliver on each platform; POS systems is the wider category if the shortlist itself is still open, and the retail industry page places the POS inside the full retail systems map.
How we evaluate impartially is the method behind the criteria in section three, our other comparisons index the rest of this cluster, and how we work shows where a selection sits in an engagement. What each piece costs is not published yet - ask, and you will have it before you talk to anyone.
The comparison above is the general shape. Yours has a specific entity structure, a specific existing estate, a sector, a timetable and a set of constraints that no published page can weight. Tell us three things - what you run today, what is actually failing, and what has to be true a year after go-live - and that is enough for a first conversation and enough for us to tell you whether you need a full evaluation, a smaller piece of work, or nothing at all.
What that conversation will not be is a product pitch - and on this pairing in particular, it may end with 'stay where you are and get Shift4's commitments in writing', which no licence-seller will ever tell you. We do not sell you a licence and we earn nothing from which platform you choose, which is what makes it possible for us to tell you that your current system is adequate, or that the purchase you are planning should wait a year, or that the shortlist you arrived with is the wrong shortlist.