Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
Check These Prerequisites Before You Start
Confirm a few basics before you configure the Lightspeed Mews integration. First, identify which version of Lightspeed Restaurant your property runs, K-Series or L-Series, because each version uses different API endpoints and mapping fields. Next, log in to your Mews back office and note the outlet IDs and sales-service IDs for every F&B point of sale you plan to connect, such as the restaurant, lobby bar, and room service. Finally, confirm you hold administrator-level credentials for Lightspeed, Mews, and Omniboost before you begin, because missing admin access is the single most common cause of failed connections.
Key Takeaways for UK Hotels
- Automatic posting of F&B charges to guest folios removes manual reconciliation and prevents lost revenue for UK hotels.
- Omniboost provides a seven-step configuration flow that maps Lightspeed outlets, payments, taxes, and items to Mews in minutes.
- K-Series and L-Series Lightspeed versions require different API mappings, and L-Series needs MFA and UUID identifiers.
- Testing with a focused checklist confirms room charges, VAT, and refunds post correctly before you go live across every outlet.
- Once the integration is live, connect Jelly to turn the same Lightspeed data into real-time gross profit visibility and supplier alerts.
Seven-Step Omniboost Setup for UK Lightspeed and Mews
The following seven steps cover the full Omniboost middleware configuration for a UK multi-outlet hotel environment.
Step 1: Create your Omniboost account and connect Mews. Register at the Omniboost portal and select Mews as your PMS. Enter your Mews Client Token and Access Token, both available under Mews > Settings > Integrations. Save and confirm that the connection status shows “Active”.
[Screenshot placeholder: Omniboost dashboard — Mews connection screen]
Step 2: Add Lightspeed as your POS source. Inside Omniboost, go to POS Connections and select Lightspeed Restaurant. Authenticate using your Lightspeed account credentials. Omniboost then pulls a list of your configured Lightspeed business locations.
[Screenshot placeholder: Omniboost — Lightspeed POS authentication screen]
Step 3: Map each Lightspeed outlet to a Mews service. For each physical outlet, such as the restaurant, lobby bar, or room service, match the Lightspeed location ID to the corresponding Mews outlet ID and sales-service ID you captured earlier. UK properties with three or more outlets should complete this mapping one outlet at a time to avoid cross-posting errors.
[Screenshot placeholder: Omniboost — outlet mapping table]
Step 4: Configure payment types. In Omniboost payment mapping, align each Lightspeed tender type, including cash, card, and room charge, to the equivalent Mews payment type. The room charge tender is the critical mapping because it instructs Omniboost to post the transaction to the guest folio instead of settling it at the POS.
[Screenshot placeholder: Omniboost — payment type mapping]
Step 5: Set tax and revenue category rules. Match Lightspeed revenue categories, such as food, beverage, and service charge, to Mews accounting categories. UK properties must keep VAT rates consistent across both systems to prevent tax discrepancies on guest folios.
[Screenshot placeholder: Omniboost — tax and revenue category configuration]
Step 6: Link POS items to Mews products. Omniboost surfaces only the menu items that have been sold since the integration was activated, which keeps the mapping list clean. Work through each item and assign it to the appropriate Mews product or accounting code. For most boutique hotel menus, this step takes under five minutes.
[Screenshot placeholder: Omniboost — POS item-to-Mews product linking]
Step 7: Activate and set the posting schedule. Choose whether charges post in real time or on a defined schedule, such as end of meal or end of day. For UK boutique hotels, real-time posting usually works best because it supports late check-outs and same-day billing queries. Save the configuration and move on to testing.
[Screenshot placeholder: Omniboost — posting schedule settings]
Key Mapping Differences for K-Series and L-Series
K-Series and L-Series use different API architectures, and this changes how Omniboost retrieves and maps data.
K-Series connects through the Lightspeed REST API. Outlet identifiers use numeric business-location IDs, and revenue categories map through K-Series “account” codes. Payment types in K-Series sit under the Payments section of the back office and must be replicated exactly in the Omniboost payment mapping table.
L-Series uses Lightspeed’s current REST API. Outlet identifiers use UUID strings instead of numeric IDs, and revenue categories are managed through L-Series “accounting groups”. The authentication flow in Omniboost also differs. L-Series requires a password plus multi-factor authentication, or OTP, rather than an OAuth 2.0 handshake. If your property migrated from K-Series to L-Series after you first configured Omniboost, rebuild the entire mapping under the L-Series connection because existing K-Series mappings do not carry over.
Checklist to Test the Room-Charge Flow
Use this checklist after completing setup to confirm charges post correctly before you go live. These seven checks verify that payment routing, VAT calculation, and duplicate prevention all work correctly across every outlet.
☐ Place a test order at each configured outlet using a test guest folio in Mews.
☐ Select “room charge” as the payment tender in Lightspeed.
☐ Confirm the charge appears on the correct Mews folio within the expected posting window.
☐ Verify the revenue category, VAT amount, and line-item description match the Lightspeed receipt.
☐ Check that no duplicate line items appear on the folio.
☐ Repeat for each outlet mapped in Step 3.
☐ Run a void or refund on one test transaction and confirm the credit posts correctly to Mews.
Common Errors and Fixes in UK Omniboost Setups
The following five errors account for most failed Omniboost configurations in UK multi-outlet properties. The table lists the cause of each error and the specific fix you can apply once.
| Error | Cause | Fix |
|---|---|---|
| Room charge not posting to folio | Room-charge tender not mapped in Omniboost payment settings | Return to Step 4 and map the Lightspeed room-charge tender to the Mews folio payment type, then re-test |
| Outlet mapping mismatch | Incorrect Mews outlet ID or sales-service ID entered | Cross-reference IDs in Mews > Settings > Integrations and update the Omniboost outlet mapping table |
| Tax discrepancy on folio | VAT rates differ between Lightspeed revenue categories and Mews accounting categories | Align VAT rates in both systems and ensure UK standard 20% and reduced 5% rates are consistently applied |
| Duplicate line items | Posting schedule set to both real time and end of day at the same time | Select a single posting mode in Omniboost and disable the conflicting schedule trigger |
| Permission error on connection | Lightspeed or Mews account lacks administrator role | Grant admin access in the relevant system’s user-management settings, then re-authenticate in Omniboost |
Connecting Jelly for Real-Time GP Margins
Once Lightspeed posts accurately to Mews, the same Lightspeed sales data can flow into Jelly and deliver live gross profit margins across every F&B outlet with no extra manual entry. Lightspeed stays the source of truth for sales, and Jelly reads item-level transaction data as each sale completes and matches it against ingredient costs from automatically scanned supplier invoices.
This setup produces a live GP margin for every dish on every outlet menu. When a supplier increases the price of an ingredient, Jelly Price Alerts flag the change immediately, and the affected dish margins update in real time. For UK boutique hotel F&B teams running room service, restaurant, and bar menus at once, this removes the need to recost dishes manually after every delivery. Jelly users see an average GP improvement of two percentage points within the first three months, and the POS connection itself usually takes under five minutes to configure.
How to Measure Success After Go-Live
After the integration is live and Jelly is connected, track a small set of metrics to quantify the operational improvement.
Reduced admin time: Night-audit reconciliation should drop from one to two hours per shift to near zero. Track weekly hours spent on manual folio corrections before and after go live so you can show the time saving clearly.
This time saving only delivers value if the automation stays accurate. Folio posting accuracy: Run a weekly audit comparing Lightspeed daily sales reports against Mews folio totals. A correctly configured integration produces a variance of zero, which confirms that the reduced admin time does not hide new posting errors.
Once accuracy is stable, you can focus on margin impact. Gross profit lift: With Jelly connected, monitor the Flash Report weekly. Operators can increase their profit margin by up to 12% in the first three months of using Jelly with a connected POS, driven by faster reactions to ingredient price changes and cleaner sales-mix data.
With margin lift visible, you can measure how well you use that data in supplier conversations. Supplier negotiation outcomes: Use Jelly Price Alert data to log every supplier price increase you challenge and every credit note you recover. Amber, a Mediterranean restaurant in East London, saves £3,000–£4,000 per month using this approach.
Next Steps and Quick FAQ
The integration is a one-time configuration that pays dividends every day. Once room-charge posting is verified and Jelly receives live sales data, the operational baseline for your F&B operation shifts permanently. Billing becomes accurate, margins stay visible, and admin time returns to the team.
FAQ
Who owns the Omniboost configuration, the hotel IT team or the F&B manager?
Either team can own it, but the person completing the setup must hold administrator access to both Lightspeed and Mews. In practice, most UK boutique hotels assign the initial configuration to the operations manager or a trusted F&B lead, with IT involved only if network or firewall settings need adjusting for the Omniboost connection.
How long does the full setup take from start to finish?
For a single-outlet property, the Omniboost configuration can usually be completed quickly, including testing. Multi-outlet properties should allow enough time to complete outlet mapping, payment-type configuration, and a full test cycle across each service point. Connecting Jelly to Lightspeed adds about five minutes.
Can the integration handle multiple outlets with different menus and VAT treatments?
Yes. Omniboost supports outlet-level mapping, so a hotel running a restaurant, lobby bar, and room-service operation can configure each outlet independently with its own revenue categories and VAT rules. Jelly mirrors this structure and displays GP margins by outlet so management can compare performance across service points without manual aggregation.
What happens to the Omniboost mapping when the menu changes?
New menu items added in Lightspeed after the integration is live appear in the Omniboost mapping interface the first time they are sold. They must be assigned manually to the correct Mews product or accounting code before charges post correctly. Jelly follows the same pattern. New items surface in the POS-to-dish linking screen only after their first sale, which keeps the mapping list current and free of legacy clutter.
Does Jelly replace Mews or Lightspeed in this workflow?
No. Jelly operates alongside both systems. Lightspeed remains the POS and the source of sales data. Mews remains the PMS and the system of record for guest folios. Jelly reads the Lightspeed sales data and combines it with supplier invoice data to produce live dish-level and menu-level GP margins, so the three systems work together and serve distinct roles.