Revel's current position in one minute

Shift4 announced on 14 June 2024 that it had completed the acquisition of Revel Systems. Shift4 said Revel had more than 18,000 merchant locations in the United States and internationally and that Revel's sales and dealer network could help distribute Shift4's SkyTab offering.

For a buyer, the practical questions are:

• Is Revel still the recommended product for this UK deployment?
• Which Shift4 or Revel company signs the software, support and payment agreements?
• Are UK acquiring and supported payment integrations unchanged?
• What is the migration path if the product strategy changes?
• Are existing and new customers offered the same hardware and contract?

Do not infer answers from the acquisition announcement. Put them in the tender and contract.

Who should consider Revel?

Multi-site restaurant groups

Central menu changes, group reporting and consistent permissions can save managers from editing each site separately. The value grows with the number of locations, but so does rollout risk. Pilot one representative venue before signing an estate-wide order.

High-volume quick service

Kitchen displays, modifiers, order routing and speed matter when a queue forms. Measure order entry and kitchen hand-off with the actual menu. A feature list cannot reveal whether staff need six taps or sixteen.

Complex retail or hospitality concepts

A bakery that sells weighed products, prepared food, subscriptions and wholesale orders has more demanding data than a standard counter. Confirm which workflows are native and which rely on paid integrations or manual workarounds.

Businesses that may be too small

A one-site café with a short menu may not recover the implementation and support cost. Start with our EPOS systems for small business guide and compare Square POS, Shopify POS and Lightspeed before committing to enterprise-style complexity.

Pricing: build a complete ownership model

Revel's current public UK material does not provide a universal price that safely covers software, hardware, implementation and payments. Treat every number in a sales conversation as one component.

Ask for these rows separately:

• recurring software per location and per register
• implementation, menu build and data migration
• iPads, stands, printers, cash drawers, routers and kitchen displays
• delivery, installation and on-site training
• online ordering, loyalty, inventory and API modules
• third-party integration subscriptions
• payment terminal, acquiring and gateway charges
• replacement hardware and enhanced support
• minimum term, annual increases, renewal and exit

The right denominator is not “per terminal per month”. It is the total cost across the intended term divided by the sites, orders or gross margin the system supports.

Worked three-year example

Assume a two-site restaurant group needs four registers, two kitchen displays and central reporting. It receives an illustrative proposal with:

• software at £95 per register per month
• two additional modules at £80 per site per month
• hardware and installation of £12,000 excluding VAT
• implementation and training of £4,000 excluding VAT
• integration subscriptions of £180 a month
• support upgrade of £120 a month

Monthly recurring cost is £840: £380 software, £160 modules, £180 integrations and £120 support. Across 36 months that is £30,240. Adding £16,000 upfront gives a three-year technology cost of £46,240 excluding VAT, before card processing.

That is about £642 per site per month across the term. The group should decide what the system must save or earn. If it cuts waste by £350 per site, saves 18 manager hours worth £270 and improves order capture by £200, the modelled benefit is £820 per site. If those gains are plausible and measured, the cost may be rational. If they are sales assumptions, it is not.

Card payments can change the answer

An integrated POS normally sends the sale amount to the card terminal and returns approval to the order. This reduces re-keying, but it can tie software and payments together commercially.

Assume the group processes £180,000 of cards a month. One quote is 1.25% blended and another is 1.10%, with otherwise identical fees. The difference is £270 a month or £9,720 across 36 months.

That saving is larger than many software negotiations. It is also incomplete unless the card mix is genuinely priced the same. Compare consumer debit, credit, commercial, Amex, non-UK cards, authorisation fees, PCI charges, refunds, chargebacks and minimums.

Ask whether payment processing is mandatory, optional or linked to a software discount. Get the software price with and without the proposed acquirer so the subsidy is visible.

Restaurant workflow test

A proper demonstration should use your menu and a realistic service. Ask staff to:

1. Open a table and add drinks.
2. Add a meal with modifiers, allergy notes and a delayed course.
3. Move an item to another seat.
4. Send drinks to the bar and food to the correct kitchen station.
5. Apply a manager-approved discount.
6. Split the bill three ways, including a tip.
7. Void one item after it has reached the kitchen.
8. Refund part of yesterday's order.
9. Continue after broadband is disconnected.
10. Reconcile till, card batch and bank payout.

Time the routine and note every manual step. A powerful system that slows ordinary service is the wrong configuration.

Offline and local-network resilience

Older Revel material promoted an “Always On” approach using local network components. Do not assume the current UK configuration behaves the same way. Ask the supplier to demonstrate three separate failures:

• internet unavailable but local Wi-Fi and router working
• local router unavailable
• payment service or terminal unavailable

The till may keep taking orders while card authorisation cannot complete. Understand which functions continue, how transactions synchronise and who carries the risk of offline card payments. Set value limits and give managers a cash, QR or payment-link fallback.

Inventory and food-cost controls

Ingredient-level inventory sounds valuable, but it depends on accurate recipes, yields, wastage and purchase records. A system cannot fix inconsistent inputs.

Pilot ten high-value or high-waste products. Compare theoretical usage from sales with actual stock counts for four weeks. Investigate portion variation, staff meals, spoilage and unrecorded waste. Expand only when the process produces decisions.

For retail, test variants, bundles, serial or barcode needs, stock transfers, purchase orders and returns. Confirm whether historical cost and margin reports match the accounting treatment.

Online ordering, delivery and integrations

Every extra channel creates menu, availability and reconciliation questions. Ask whether the connection is native, partner-built or connected through an aggregator.

Test a price change, sold-out item, modifier, refund and cancelled delivery order. Find out where the source of truth lives. If staff must edit four menus, the integration has not solved the operational problem.

Record each third-party contract, subscription and support owner. When an order disappears, staff need to know whether Revel, the delivery platform, the integration provider or the internet connection owns the incident.

Multi-location control without blocking local managers

Head office may want standard menus and reporting while venue managers need local stock and staffing decisions. Design permissions before rollout.

Check who can change prices, issue refunds, reopen bills, export customer data, edit tax settings and view wages. Test how a central menu update affects location-specific availability and promotions. An audit trail should show who changed what and when.

Data, reporting and exit risk

Request sample exports before signing. Finance should be able to connect gross sales, discounts, service charges, tips, tax, refunds, payment types and net settlements.

Ask which data can be exported in a machine-readable format, how often, at what cost and for how long after termination. Clarify ownership of customer, menu and transaction data. A POS becomes expensive to leave when the only usable history is trapped in a dashboard.

The Shift4 acquisition makes roadmap questions especially relevant. Request written commitments for support life, security updates and notice of material changes. Avoid relying on a salesperson's prediction about future products.

Alternatives to compare