Lightspeed Restaurant Integration: The UK Operator’s Runbook

Written by: JJ Tan, Founder, Jelly | Last updated: 7 November 2026

Key Takeaways

• Most Lightspeed Restaurant integrations fail during pre-flight checks rather than at the authorisation stage itself.
• Operators must first identify their Lightspeed series (K, L, O or U) because each has a different integration menu path.
• Admin access, finalised VAT classifications and agreed menu mappings are essential prerequisites before connecting any partner.
• Jelly connects natively via the Lightspeed marketplace in around five minutes, mapping POS items to dishes for automatic live GP updates.
• Jelly is the best back-office integration for Lightspeed Restaurant setup for getting live dish-level GP from your POS sales.

See Your Live GP in a Demo

Step 1 — Identify Your Lightspeed Series (K, L, O or U)

Series identification is the first decision that keeps your Lightspeed Restaurant integration setup on track. Lightspeed Restaurant runs across four distinct product series, each with its own interface and integration menu location. Confirm your series before clicking anything else. The table below shows how to recognise each series and where its integration menu lives.

Each series reflects a different product generation, and the integration menus are not interchangeable between them. Lightspeed K Series integration setup and Lightspeed L Series integration setup follow different click-paths even for the same partner. If you are unsure which series your account is on, check the app name or logo colour before proceeding. The wrong path produces a dead end with no error message to explain it.

Step 2 — Pre-Flight Readiness Checklist

Pre-flight is the stage where most integrations stall, even though few providers publish it as a distinct step. Work through every item below before opening the integration menu. Each check is listed with the consequence of skipping it.

• Menu items, modifiers, pricing and VAT classifications finalised in Lightspeed. Lightspeed is the source of truth for all product data. Connecting a partner before VAT classifications are set means incorrect tax data flows downstream into accounting and GP calculations.
• Ingredient and product mappings agreed before connection. Decide which Lightspeed POS categories, such as food and beverages, will sync to which back-office dishes before authorising. Mapping after the fact introduces legacy clutter.
• Floor plans and staff roles and permissions set. Incomplete floor plans and missing role assignments cause order-routing failures after go-live.
• Tablet OS and the Lightspeed Restaurant app updated. An outdated app version can block the integration handshake entirely.
• Admin access to the Lightspeed account confirmed. This is the single most common blocker. Without admin-level credentials, the authorisation step cannot be completed. Confirm this before service day.
• Peak-hour speed test and router QoS rules checked. Each integration connection introduces another point of failure, and a congested network during service is the most common cause of dropped syncs. Run a speed test before go-live. If throughput dips at peak, set QoS rules so POS traffic is prioritised over guest Wi-Fi.

Talk to the Team

Step 3 — Run the Connection Flow

Once pre-flight is complete, the connection flow follows the same structural sequence regardless of which partner you connect. The flow has five stages.

1. Log in to Lightspeed Back Office using admin credentials. Non-admin logins will not surface the integration menu.
2. Locate the integration menu for your series. K Series: Back Office → Integration Hub. L Series: Restaurant Manager → Integrations. O Series: Back Office → Discover → Integrations.
3. Search for the partner by name. Partners are grouped by category, including accounting (Xero, Sage, QuickBooks), delivery (Deliveroo, Uber Eats, Deliverect) and reservations (ResDiary, OpenTable, TheFork). If the partner does not appear, see Step 4 on native integrations versus HubRise.
4. Open the partner details page. Review the permissions the partner requests and confirm the data categories it will access.
5. Select Onboarding or Connect and authorise. Lightspeed redirects you to the partner’s own authorisation flow. Complete it there, then return to Lightspeed to confirm the connection is active.

Partner-specific quirks, particularly for delivery integrations such as the Lightspeed Deliveroo integration and reservations tools such as ResDiary, OpenTable and TheFork, are covered in dedicated guides rather than duplicated here.

Step 4 — Native Integration Hub vs HubRise: Choose the Right Route

Native integrations are the default choice when they exist for your series. Fewer moving parts mean fewer failure points and no additional connector subscription. The native Integration Hub is the right route for any partner Lightspeed has already certified for your series.

HubRise acts as a connector bridge for partners that Lightspeed does not natively support. It is a legitimate and well-documented solution for non-native partners, and the Lightspeed HubRise integration follows its own setup flow. The decision is straightforward. If the partner is in the native menu, use the native route. If it is not, HubRise is the appropriate bridge.

That same native-versus-bridge rule applies to the back-office leg. Connecting Lightspeed to Jelly does not require HubRise, because Jelly is listed on the Lightspeed marketplace as a native connection. It follows the standard Integration Hub flow described in Step 3, so no bridge is needed.

Step 5 — Menu Mapping and Test-Order Verification

Lightspeed remains the source of truth for products, modifiers, pricing and VAT after authorisation. Mapping happens once the connection is live. Match each Lightspeed POS item to the corresponding category or dish in the partner system.

Verify end-to-end before service with three tests: a test ticket to the kitchen display, a test to the printer and a test transaction into accounting. The real failure mode at this stage is a connected integration that produces no kitchen tickets. If tickets are not printing, check printer and KDS mapping in the Lightspeed Back Office rather than the integration settings. VAT misclassification is the other common cause of incorrect data in accounting. Recheck classifications in Lightspeed if figures look wrong after the test.

For deeper troubleshooting guidance, the Lightspeed integration troubleshooting guide covers the most common failure patterns in detail.

Step 6 — The Back-Office Leg: Connect Lightspeed Restaurant To Jelly For Live GP

The Jelly connection uses the same five-minute sequence as every other supported POS. Open Jelly, click Integrations, sign in to Lightspeed, grant permissions and select which POS categories, such as food and beverages, to sync. Jelly is listed on the Lightspeed marketplace. The integration uses a real-time API connection, so item-level sales data arrives in Jelly the moment a transaction completes at the till.

The only common friction point is lacking admin access to the Lightspeed account, and Jelly flags this requirement upfront before the connection attempt. POS-to-dish linking only surfaces items sold since the integration was connected. That approach keeps the mapping clean and free of legacy menu clutter.

Once connected, the back-office leg turns those POS sales into live margin data. Invoices scanned by photo or forwarded by email are processed line by line. That updates ingredient costs, so every dish’s GP margin stays live. Price Alert flags every supplier price movement, so the team can negotiate credits or switch suppliers before margins erode. Flash Report gives a daily, weekly or monthly GP view calculated from invoice costs and POS sales. Sales Mix shows which dishes are most popular and which are most profitable, which supports data-driven menu decisions. Invoices push one-click into Xero, with Sage integration coming soon.

The results operators report are consistent. One operator moved GP from 65% to 72% within 12 weeks on approximately £500,000 in revenue, and Populu lifted GP from 68% to 72% across 16 locations. Across the customer base, that typically shows up as a 3% cut in food costs within the first three months. Connecting a POS automates 2–5 hours of weekly work that would otherwise go on manual margin calculations. Jelly charges a flat £129 per month per location, so costs stay predictable as your team grows.

For multi-site operators connecting more than one Lightspeed site, the Lightspeed multi-site integration architecture guide covers the additional configuration steps.

See Jelly in Action

Common Mistakes and Troubleshooting Triage

• Integration not showing in the back office. Likely cause: wrong series menu, or the partner is not native to that series. Check your series first, then verify whether the partner requires HubRise.
• Authorisation fails. Likely cause: no admin access to the Lightspeed account. Confirm admin credentials before retrying.
• Connected but no sales data appearing. Likely cause: POS categories were not selected during setup, or no transactions have occurred since the connection was made. Return to the integration settings and confirm category selection.
• Tickets not printing. Likely cause: printer or KDS mapping is incomplete in Lightspeed Back Office. Check routing rules rather than the integration itself.
• Margins look wrong in Jelly. Likely cause: POS items are not yet mapped to Jelly dishes, or VAT classifications in Lightspeed are incorrect. Recheck both before assuming a data error.

For partner-specific issues, the Lightspeed integration support guide covers the POS-to-Xero connection in detail.

How to Measure Success

Once the failure modes above are ruled out, a completed Lightspeed Restaurant integration setup should produce a handful of observable outcomes. Before service begins, the integration is live and a test order has been verified across the kitchen display, printer and accounting system. Shortly after go-live, POS items are mapped to back-office dishes or categories, live GP is visible in Jelly’s Flash Report, Price Alerts are being generated and actioned, and admin hours spent on manual margin calculations are measurably reduced. Customers consistently see that same reduction in food costs within the first three months of connecting a POS to Jelly.

Conclusion: Run The Runbook In Order

Running the steps in order keeps your Lightspeed Restaurant integration setup predictable. Series first, pre-flight second, connect third and back-office leg last. Skipping any stage, particularly pre-flight, is the primary reason integrations fail before service. The connection flow itself is straightforward once the readiness checks are complete and the correct series menu is confirmed.

Jelly is the best back-office integration for Lightspeed Restaurant setup for getting live dish-level GP because it connects in around five minutes, is listed on the Lightspeed marketplace and keeps every dish margin live from invoice data. Every POS transaction updates ingredient-level costs automatically, so GP is always current without manual effort.

Book a Demo With the Team

Frequently Asked Questions

How Do I Know If I’m on Lightspeed K, L, O or U Series?

Check the name and logo colour of the Lightspeed Restaurant app on your device. The K Series is identified by a white logo on a red background, and its app is labelled “Lightspeed Restaurant POS (K)”, and the L Series app features a red logo on a white background, and the iOS app is labelled “Lightspeed Restaurant POS (L)”. If you are unsure, log in to your Back Office and look at the top-level navigation. K Series shows an Integration Hub option, while L Series shows an Integrations option inside Restaurant Manager. If neither matches, you may be on O Series or U Series, and Lightspeed’s help centre has series-specific identification guidance.

Why Isn’t My Lightspeed Integration Showing in the Back Office?

The most common cause is navigating to the wrong series menu, because each series has a different path to its integration settings and the menus are not interchangeable. The second most common cause is that the partner you are looking for is not natively supported in your series and requires a HubRise connector bridge instead. Confirm your series first, then check whether the partner appears in the native Integration Hub before assuming a technical fault.

Do I Need HubRise to Connect Lightspeed Restaurant to My Other Tools?

You only need HubRise if the partner you want to connect does not appear in your series’ native integration menu. HubRise is a connector bridge for non-native partners and works well for that purpose. If the partner is already listed in the Lightspeed Integration Hub for your series, use the native route, because it involves fewer moving parts. Jelly, for example, is listed on the Lightspeed marketplace and connects natively without requiring HubRise.

How Long Does It Take to Connect Lightspeed Restaurant to Jelly?

The connection takes approximately five minutes once pre-flight checks are complete and admin access to the Lightspeed account is confirmed. The flow is simple. Open Jelly, click Integrations, sign in to Lightspeed, grant permissions and select which POS categories to sync. POS-to-dish mapping begins immediately after connection and only surfaces items sold since the integration went live, which keeps the mapping clean.

Do I Need Admin Access to Lightspeed to Connect Jelly?

Yes. In Lightspeed Retail, authorising a third-party integration requires an Admin-level user, because Retail POS Admins approve app connections and only users with the “Admin” role can authorise the connection. Some integrations require higher permissions such as “Owner” or “Master” Admin with full location permissions. As noted in Step 2, admin access is the usual sticking point. Jelly flags the admin access requirement upfront before the connection attempt so there are no surprises mid-flow. Confirm with your Lightspeed account holder that you have admin access before starting.

Which Sales Data Does Jelly Pull from Lightspeed?

Jelly pulls item-level sales data via real-time API, so each transaction is sent to Jelly the moment it completes at the till. You select which POS categories, typically food and beverages, sync during setup. Jelly maps each POS item to a dish in its Kitchen section, which then drives live GP calculations using ingredient costs from scanned invoices. Only items sold after the integration was connected are surfaced for mapping, so there is no legacy menu clutter to clean up.

Can I Connect Multiple Lightspeed Sites to Jelly?

Yes. Jelly supports multi-site operators and charges a flat £129 per month per location with no per-user fees. Each site connects independently through the same five-minute flow described in Step 6, and GP, Flash Reports and Sales Mix data are available per location. For architecture guidance on connecting multiple Lightspeed sites, the Lightspeed multi-site integration guide covers the configuration in detail.

What Should I Check Before Going Live?

Run through the pre-flight checklist in Step 2. Finalise menu items, modifiers, pricing and VAT classifications in Lightspeed. Agree ingredient and product mappings, set floor plans and staff permissions, update the tablet OS and app, confirm admin access and complete a peak-hour speed test with QoS rules applied. Then complete the test-order verification in Step 5 with a test ticket to the kitchen display, a test to the printer and a test transaction into accounting before the first cover of service.