Lightspeed vs Revel for Restaurants: 2027 Buyer's Guide

Key Takeaways

• Revel is not a standalone product a new buyer should plan around. Shift4 bought the company and said it planned to remove duplicate restaurant products.

• Lightspeed publishes three plan prices and a kitchen display price on its own pricing page, so it is the easier of the two to budget for today.

• Neither vendor's full cost can be finished from public numbers alone. Revel's prices are quote-based, and Lightspeed's page does not state its billing period.

• Kitchen screens, processing rates and API access move the total more than the headline plan price does.

• Review-site star ratings were blocked during research, so this guide does not rank either vendor on stars.

• Get contract length, cancellation terms, setup fees and processing rates in writing from each vendor before you compare totals.

The category decision comes before the brand decision

A restaurant POS is the system that takes orders, sends tickets to the kitchen, accepts card payments and records each sale. A restaurant-specific product adds a kitchen display system (KDS) and menu tools on top of that core. The first decision is therefore whether you need the restaurant layer at all, or whether a general retail register or a reservations-only tool will do. If you need tickets on a kitchen screen and sales reporting for one venue or a small group, you are in the restaurant POS category, and both Lightspeed and Revel sell into it.

The brand question comes second, and this year it is harder than usual because one of the two is being absorbed into another company's product line.

TL;DR: Shortlist Lightspeed first because it publishes prices. Treat Revel as a question for Shift4 that needs a written answer. Do not sign with either until you have the billing period, screen count, payment rates, contract length and API terms on paper.

Revel is being folded into Shift4, which changes the decision

Shift4 Payments agreed in May 2024 to buy Revel Systems, an iPad-based POS company, for $250 million in cash. Shift4 deal value: $250 million in cash according to Payments Dive (2024). Shift4's CEO said the company would "take the best capabilities out of Revel" and move them into its SkyTab POS system, and that Shift4 would "delete the duplicative product offerings." The company cited Revel POS terminals at about 18,000 merchant locations and described them as a $17 billion payment opportunity, according to Payments Dive (2024).

Shift4's own release notes add a dated fact: SkyTab POS became Shift4 Dine on May 12, 2026, according to Shift4 (2026). That notice does not mention Revel. In the sources I could open, I found no Shift4 statement that sets out when individual Revel accounts move, so the timing for your account has to come from Shift4 directly. The SkyTab product had been in beta earlier, when Shift4 said more than 4,000 restaurants had run it, according to Digital Transactions (2022).

Revel's own pricing address redirects to Shift4's food-and-beverage page. That page returned rate-limit errors during research, so this guide has no Revel price list to print. In my reading, the practical question is not whether Revel works today but which product, under which contract, you would be on in 2027. A Revel quote is a quote for a product whose future Shift4 has described as consolidation.

How we evaluated these tools

This guide is a buyer's evaluation built from public vendor pages and independent sources. It does not rely on demo accounts or hands-on use of either system. The ranking uses six weighted criteria, each weighted by how much it changes the purchase for a restaurant owner or operations lead. Review-site ratings are not part of the weighting, because the review sites I tried returned access errors.

The two largest weights go to pricing clarity and vendor direction, because those are the points the public record shows are most in flux for these two products. Integration access carries the same weight, because a POS that cannot share data costs staff time every day.

Feature matrix on the decisions that matter

The Lightspeed plan list and the $30 kitchen display price come from Lightspeed's pricing page. Lightspeed's May 2026 results release also lists AI menu imports and a promotion engine inside its Order Anywhere product, per Lightspeed's results release. "Not verified" means I could not open a public page that states the item for Revel during research. It does not mean the feature is missing.

Pricing and cost math

Essential plan price: $189, period not stated according to Lightspeed (2026): Lightspeed's Starter plan costs $69, its Premium plan costs $399, and its kitchen display costs $30 per screen per month. The page does not say whether plan prices are per location or per register, and it does not state a billing period for the base plans. CostBench's verification page lists the same three plan prices as per location, according to CostBench (2026), and it states that it is not a vendor endorsement.

Pricing checked October 29, 2026. Revel prices are quote-based, because no Revel price list was available in the sources I could open.

Worked example: take one restaurant on Lightspeed's Essential plan with four kitchen screens. The plan is $189 and each screen adds $30 a month, so the monthly figure is $189 plus four times $30, which is $309 (Lightspeed pricing). The page does not state whether the $189 is a monthly charge, so this math assumes it is. If it is, the 12-month total is $309 times 12, or $3,708, before hardware, payment fees and add-ons. Raw API access is listed on the Essential plan, so the page shows no separate API fee, but the developer time to read a role list from /staff/v1/businessLocations/{businessLocationId}/userTypes/BACK_OFFICE/roles is a real cost you need to estimate yourself.

Lightspeed: best fit, limits and implementation

Fiscal 2026 revenue: $1,227.0 million according to Lightspeed (2026). That figure covers the whole company, not restaurants alone, so it tells you about Lightspeed's scale rather than its restaurant product. The same release says Lightspeed sold Upserve after the quarter, and its fiscal 2027 outlook excludes Upserve revenue, so Upserve should not be on your shortlist.

Best fit: Lightspeed suits a restaurant that wants a published starting price, a kitchen display and reporting in one account, and that expects to connect data out through an API later. The official pricing page lists Advanced Insights reporting, multi-location management and raw API access on all three priced plans. Lightspeed's May 2026 release says a 19-restaurant UK chain chose "Lightspeed Restaurant with KDS and Advanced Insights" to replace a legacy system (Lightspeed results). That is a European example, and it is a vendor-published win, not an independent measure of service quality.

Limits: Several costs sit outside the headline plan. Third-party delivery integrations are an add-on on every plan, reservations integrations are an add-on, and Lightspeed Tasks is an add-on on Starter. The pricing page does not mention loyalty features, and it states no contract length, cancellation terms or setup fee. The Enterprise tier is quote-based and includes a personalized software and hardware package.

Implementation: Before you sign, ask for the billing period, whether prices apply per location or per register, the kitchen display hardware price, processing rates for the Essential and Premium plans (which the page marks "Custom"), and the API terms. Lightspeed's K-Series API reference lists groups including Online Ordering, Staff, Items and Financial APIs, with the Online Ordering group documented at Lightspeed's Order and Pay reference. Start integration with the one export your bookkeeper already requests by hand, and name the person who holds the API credentials before anyone builds anything.

Revel: best fit, limits and implementation

Best fit: Revel suits an existing Revel customer who is being asked to sign a new term and has a written commitment from Shift4 about the product and its support path. Payments Dive described Revel as an iPad-based POS for restaurants and specialty retailers, a product line Shift4 planned to fold into SkyTab (Payments Dive).

Limits: Revel is the weaker choice for a new buyer who wants a standalone roadmap. Shift4's 2024 statements pointed toward removing duplicate products, and its 2026 rename moved SkyTab to Shift4 Dine. Pricing is quote-based, and I could not verify Revel's API, webhook or processing terms from an open page. Revel's developer reference pages returned 404 errors during research, so this guide makes no claim about Revel's endpoints.

Implementation: Get these items in writing: the product name you would sign for (Revel or Shift4 Dine), the contract length, the date your account would move if you are already on Revel, a full export of historical sales and staff data, and the processing rate. If you migrate, plan a parallel period, because the public record gives no migration timeline for individual accounts.

Moving POS data into the books and staff rules

The two workflows below are proposed, configurable designs for a buyer's team. They do not describe a live customer, a measured result or a current deployment. Each one needs API access on the chosen plan and a named owner before it can run.

The first workflow starts when the POS sends an order notification. Lightspeed's API reference groups an Online Ordering API with Order and Pay webhook notifications, so the trigger is a closed-order notification from that API. The action is that US Tech Automations would map each notification's total, tax and tender fields into one daily summary row per venue for the bookkeeper's sheet, using a field list the buyer confirms with Lightspeed first. The output is one summary row per venue per day, plus an error record for any notification that fails to post. Prerequisites are API credentials on a plan with raw API access, a confirmed payload field list (the portal page I opened did not show payload fields), and a named data owner. The human review point is the bookkeeper, who checks any day where the POS total differs from the card processor's report by an amount the owner sets in advance.

The second workflow handles staff access. The trigger is a new back-office hire approved in the HR system. The action is that the workflow reads the back-office role list through the Staff API path /staff/v1/businessLocations/{businessLocationId}/userTypes/BACK_OFFICE/roles, which Lightspeed's API changelog quotes as a GET request, and compares it with the role the hire was approved for. The output is a manager approval task that shows both roles. US Tech Automations could configure this check so that it never changes a role on its own. Prerequisites are API access on the plan, the businessLocationId for each venue, and a written approval rule. The human review point is a manager, who approves every role change.

Zapier, Make, n8n or an in-house build

Zapier, Make and n8n can connect a POS notification to a spreadsheet, a ledger or a chat message. When a builder configures them, they can keep run histories, retry failed steps and route errors to a separate branch. The buyer still has to design and own the parts that make an automation trustworthy: idempotency so a retried webhook does not post the same sale twice, escalation to a named person, access controls on credentials, and maintenance when the POS changes its fields. An in-house build gives the most control and also the most upkeep.

A proposed US Tech Automations design would put those pieces in one place: a retry policy, a duplicate-check key on each sale, an error queue that a manager clears each day, and credential scopes limited to the reports or staff roles the workflow needs. The prerequisites are the same as for any build: API credentials on a plan that includes API access, a named data owner, and a written list of fields allowed to leave the POS. No workflow in this guide posts to accounting without the human check.

When a simpler setup wins

A simpler setup wins in three cases. If you run one venue and need only tickets, card payments and the POS's built-in reports, the vendor's reports are enough, and an extra workflow adds cost without supporting a decision. If you only need a weekly CSV for your bookkeeper, a scheduled export or a no-code connector does the job. If nobody on your team can own credentials and clear exceptions, the vendor's managed reports will serve you better than any custom workflow. US Tech Automations is the wrong choice in all three cases, and the POS's own reporting should be your starting point.

Glossary

• Kitchen display system (KDS): A screen in the kitchen that shows orders sent from the POS. Lightspeed prices its KDS per screen.

• Raw API access: Direct access to the vendor's API. Lightspeed lists it on its priced plans, and you should confirm the terms in writing.

• Integrated payments: Card processing built into the POS. Lightspeed marks it "Default" on Starter and "Custom" on Essential and Premium.

• Webhook: A message the POS sends to another system when an event happens, such as a new order.

• Idempotency: The property that a retried message does not create a duplicate record.

• Billing period: Whether a price is charged monthly, annually or on another schedule.

• Quote-based: The vendor does not publish a price, so the figure exists only in a sales quote.

• Total cost of ownership: Software, screens, processing and add-ons over the full contract term.

Decision checklist

• Ask each vendor for the billing period, the per-location or per-register basis, and the contract length.

• Count kitchen screens before you compare plan prices, because screens change the monthly bill.

• Get processing rates in writing for the plan you would buy.

• Confirm that API access is included in that plan, not sold separately.

• Get a written statement of the product name and support path, including whether Revel customers move to Shift4 Dine.

• Name the person who will own API credentials and clear automation errors.

• Confirm that historical sales and staff data can be exported before you migrate.

Who should choose which vendor

Choose Lightspeed if you want published plan prices, a kitchen display and reporting in one account, and API access you can confirm on the plan you buy. Choose Revel only if you are already a Revel customer with a written path from Shift4, or if Shift4 gives you a written quote that names the product you would receive.

Who this is for: An owner or operations lead who must pick a restaurant POS within a few months and can get written answers from each vendor.

Red flags: a vendor that will not state the billing period or processing rate in writing, a plan whose API access you cannot confirm, and no named person to own credentials and exceptions.

Frequently asked questions

Is Revel still a standalone restaurant POS?

Not in a way a new buyer should plan around, because Shift4 owns Revel and its own release notes show SkyTab renamed Shift4 Dine on May 12, 2026. Get the product name and support path in writing before you consider it.

Which is cheaper, Lightspeed or Revel?

You can read Lightspeed's plan prices from its pricing page, but Revel publishes no price list in the sources I could open, so a direct comparison needs a written Revel quote.

Does Lightspeed have a free plan?

The pricing page I opened lists no free plan, so budget from its lowest priced tier and confirm the billing period.

Do I need API access for a restaurant POS?

Only if you want order, staff or accounting data to move without re-keying it. Lightspeed lists raw API access on its three priced plans, so confirm the terms before you assume it.

Can a non-developer set up these workflows?

Partly, since no-code tools can handle the trigger and action steps. Someone still has to own credentials, error handling and the review queue.

Should a single-location owner pick Lightspeed?

Possibly, if the kitchen display and reporting are your priorities, because it publishes a starting price. Confirm the billing period and screen count before you decide.

Bottom line

For restaurant buyers comparing these two in 2027, Lightspeed is the vendor you can price and plan around from public information. Revel needs a written answer from Shift4 about the product, the contract and the processing rate before it is a serious option. Get those answers in writing, then compare totals. If you want the data flows described above, see how US Tech Automations configures this in a proposed design before you commit.