Lightspeed Multi-Site Integration: UK Restaurant Guide

Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026

Key Takeaways

• Lightspeed multi-site integration centralises sales reporting and menu access but does not resolve dish-level costing or real-time margin visibility.
• Multi-site operators need three layers, POS, inventory and profitability, to prevent margin leaks as they scale from one location to several.
• Without automated invoice capture and live ingredient pricing, UK restaurants and pubs risk outdated costs and hidden delivery commission losses.
• Jelly complements Lightspeed by mapping sales data to recipes, scanning supplier invoices and delivering daily GP reports per site in minutes rather than hours.
• Talk to Jelly about closing your profitability gap across your Lightspeed locations and protecting margins as you grow.

What Is Lightspeed Multi-Site Integration?

Lightspeed multi-site integration is the configuration of Lightspeed Restaurant POS across two or more physical locations so that sales reporting and account access are managed centrally rather than independently per site. Lightspeed multi-location setups allow sharing of menu items and central management of modifiers/products from a master account, but menus must be created and edited separately per location. Each location processes transactions locally while data flows to a shared back-office view. The table below shows which multi-site scenarios Lightspeed handles natively and which require an additional layer to close the profitability gap.

Scenario	Supported by Lightspeed Multi-Site	Requires an Additional Layer
Centralised sales reporting across locations	Yes	No
Menu management from one account	Limited	Yes
Inventory sync between sites	Limited	Yes
Delivery menu with commission factored in	Yes via Deliverect	No
Dish-level GP margin per location	No	Yes
Composite/batch recipe costing	No	Yes

The Three Layers Behind Profitable Multi-Site Operations

Multi-site operations work best when you treat them as three distinct layers, each with a clear job.

• POS layer: Lightspeed Restaurant handles transaction processing, menu configuration and centralised sales data across all locations.
• Inventory layer: This layer covers stock counts, supplier invoices and ingredient-level price tracking. Lightspeed provides a foundation here, but fluctuating UK ingredient prices and multi-supplier complexity mean this layer needs dedicated tooling.
• Profitability layer: This layer delivers real-time dish costing, GP margin visibility, price alerts and delivery commission modelling. It sits above the POS and inventory layers and is where operators either protect or lose margin.

Most operators invest heavily in the POS layer and underinvest in the profitability layer. That imbalance leaves accurate sales data sitting next to invisible costs.

See how Jelly closes the profitability gap in a 15-minute walkthrough of your Lightspeed setup.

How Inventory Control Changes When Lightspeed Scales Across Sites

A single-site operator can manage supplier relationships informally. A chef knows roughly what beef costs this week because they placed the order themselves. At two or more sites, that informal knowledge breaks down.

Supplier negotiations become fragmented. Site A may be paying a different price per kilo for chicken than Site B because the orders were placed separately and no one compared invoices. Finance visibility suffers because invoice data arrives from multiple suppliers across multiple locations and lands in different inboxes or, worse, in a pile on a desk.

Chef workflows change too. A head chef overseeing two kitchens cannot physically be in both. They rely on sous chefs to manage ordering, but those sous chefs are not tracking ingredient price movements against dish costs. By the time a margin problem surfaces in a monthly report, the damage is already done.

Lightspeed’s inventory tools give operators a starting point for stock management, but the sync between what was ordered, what was invoiced and what a dish now costs in real time is not automatic. That gap is where margin leaks.

How Jelly Extends Lightspeed Across Multiple Locations

Knowing what Lightspeed does well across multiple locations makes it easier to plan the extra tools that complete the picture.

• Cost vs control: Centralising menus and sales reporting reduces admin cost per site. Jelly works alongside Lightspeed to provide clear dish-level costing workflows.
• Speed vs accuracy: Lightspeed processes transactions quickly and reliably. Jelly complements this by matching transaction data against live ingredient costs.
• Single vs multi-location complexity: Reporting that works well for one site becomes easier to interpret across three or four sites when Jelly normalises costs and margins per location.
• Manual vs automated reporting: Jelly automates the process of pulling sales exports from Lightspeed and matching them against supplier invoices, which reduces the time spent on spreadsheets.

These capabilities show how Jelly extends the functionality of Lightspeed to meet the needs of growing multi-site operators.

Lightspeed One Account, Multiple Locations: Readiness Checklist

Operators gain smoother multi-site rollouts when they work through this checklist before connecting sites under one Lightspeed account and adding a profitability layer.

• Data quality: Menu item names must be consistent across sites. Inconsistent naming creates mapping problems when linking POS items to dish recipes, which means the profitability layer cannot accurately track costs per dish.
• Supplier invoice processes: Once dish mapping is in place, the system needs current ingredient prices to calculate margins. Each site needs a clear process for capturing invoices, either by forwarding supplier emails to a dedicated address or photographing paper invoices on receipt.
• POS admin access: Admin-level access is required before any configuration can begin. The person connecting the integration must have this access, which is the single most common friction point during setup.
• Team tech comfort: Chefs do not need to be technical, but they do need to be willing to photograph an invoice or click through a simple recipe builder. Tools that demand more effort than this will not be used consistently.
• Delivery menu separation: Sites using a delivery platform need a plan to model delivery commission overheads separately so that delivery dish margins are not confused with dine-in margins.

Lightspeed POS Multi-Site Setup: A Phased Approach

A phased rollout reduces risk and builds team confidence before you expand to every location.

1. Phase 1, Lightspeed multi-site configuration: Confirm all locations are operating under the correct account structure in Lightspeed Restaurant. Standardise menu item names across sites.
2. Phase 2, POS-to-dish mapping: Connect Jelly to Lightspeed via the integrations tab, a process that takes approximately five minutes (see FAQ for step-by-step details). Map each POS item to a Jelly dish recipe. Only items sold since the integration connected appear in the mapping queue, which keeps the list clean.
3. Phase 3, Invoice automation: Direct supplier invoices to Jelly via a dedicated email address or photograph them on arrival. Jelly scans every line item, quantity, SKU, price and tax, then updates ingredient costs automatically.
4. Phase 4, Margin reporting rollout: Activate Flash Reports for daily GP visibility per site. Enable Price Alerts so any ingredient price movement triggers an immediate notification. Build delivery menu variants with commission factored in using Jelly’s Delivery Menu Creation tool.

Walk through the setup process with a Jelly specialist for your specific Lightspeed configuration.

Common Multi-Site Challenges Without a Profitability Layer

Multi-site operators running Lightspeed without a profitability layer consistently encounter the same set of problems.

• Inconsistent data capture: One site photographs invoices on the day of delivery, another batches them weekly. Ingredient costs in the system are always slightly out of date at one location.
• Delayed price updates: UK ingredient prices shift frequently. Chicken, dairy and cooking oils have all seen significant price volatility in recent years. A dish costed in January may be loss-making by March if the recipe cost has not been updated.
• Spreadsheet drift: Finance managers maintain a master spreadsheet that gradually diverges from reality as new suppliers are added, portion sizes change and seasonal menus rotate. By the time the monthly management accounts arrive, the spreadsheet and the accounts tell different stories.
• Poor cross-site visibility: Without a centralised profitability view, an owner cannot see at a glance which site is performing well on GP and which is not. Problems at Site B stay invisible until they appear in the quarterly figures.
• Delivery commission overheads: Operators using Deliveroo, Uber Eats or Just Eat face commission rates that can reach 30–35% of the order value. Without a separate delivery menu model, the commission erodes margins that look healthy on the Lightspeed sales report but are not.

What Profitable Multi-Site Operators Have in Common

Operators who maintain strong GP margins across multiple sites share four operational characteristics.

• Simplicity: The tools chefs use must require minimal admin. If costing a dish takes 28 minutes in a spreadsheet, it will not be done consistently. Jelly reduces that to approximately three minutes by building recipes from ingredients already populated via scanned invoices.
• Timeliness: Price alerts need to surface on the day a supplier invoice arrives, not at month end. Jelly’s Price Alert feature flags every price movement, up or down, the moment an invoice is processed.
• Visibility: Owners and finance managers need a single view across all sites. Jelly’s Flash Report delivers daily, weekly or monthly GP margin per location, calculated from live invoice costs and Lightspeed sales data.
• Repeatability: The workflow must be the same at every site so that a new sous chef or a new location can be onboarded without rebuilding the system from scratch.

Jelly is built specifically for UK restaurants, pubs and boutique hotels at the £500k+ revenue stage expanding to two to five sites. It integrates natively with Lightspeed Restaurant via a real-time API and is listed on the Lightspeed marketplace. Operators using Jelly report a 90% reduction in bookkeeping time, an average 2 percentage point improvement in gross margins within three months, and average food cost reductions of 3% in the same period. Pricing is a flat £129 per location per month with no per-user charges.

Populu lifted GP from 68% to 72% across 16 locations. The Howard Arms reached 80% gross profit after the owner had been told 60% was the ceiling. Amber saves £3,000–£4,000 per month through faster reactions to supplier price changes.

Frequently Asked Questions

Can Lightspeed Restaurant manage multiple sites from one account?

Yes. Lightspeed Restaurant supports multi-location management from a single account, which allows operators to centralise menu configuration and sales reporting. Each location processes transactions independently while data is aggregated at the account level. The account structure does not, however, automatically calculate dish-level GP margins or track ingredient price changes across sites. Those functions require a dedicated profitability tool connected to the POS.

Does Lightspeed sync inventory across multiple locations in real time?

Lightspeed provides inventory management tools that can be configured across locations. Jelly works alongside Lightspeed to deliver real-time synchronisation of ingredient-level costs, particularly as supplier invoices arrive at different times from different suppliers. Jelly scans invoices automatically and updates recipe costs the moment a new price is captured.

How much does it cost to add Jelly to a Lightspeed multi-site setup?

Jelly charges a flat rate of £129 per location per month. There are no per-user fees and no variable charges based on invoice volume or feature usage. For a three-site operation, the total cost is £387 per month. Given that operators typically save 10–20 hours of admin per month per site and see average GP improvements of 2 percentage points, the platform typically pays for itself within the first month of use.

How long does it take to connect Jelly to Lightspeed?

Connecting Jelly to Lightspeed Restaurant takes approximately five minutes. The process involves opening Jelly, navigating to the Integrations tab, signing in to the Lightspeed account, granting the necessary permissions and selecting which POS categories to sync. The only common delay occurs when the user does not have admin-level access to their Lightspeed account. Jelly flags this requirement before setup begins. POS-to-dish mapping only surfaces items sold after the integration is connected, so there is no legacy menu clutter to work through.

What happens to delivery menu margins in a multi-site Lightspeed setup?

Lightspeed records delivery orders as sales, but it does not automatically factor in the commission charged by delivery platforms such as Deliveroo or Uber Eats. Without a separate model, delivery GP appears higher than it actually is. Jelly’s Delivery Menu Creation feature allows operators to duplicate existing menu items and apply a commission percentage, which produces a separate, accurate margin figure for delivery sales at each site.

Conclusion

Lightspeed multi-site integration gives UK restaurant, pub and boutique hotel operators a reliable foundation, with centralised sales data, consistent menu management and a single account across locations. That foundation is necessary but not sufficient for margin control at scale.

Operators who grow profitably beyond two sites add a profitability layer on top of their POS. That layer automates invoice capture, updates dish costs in real time, alerts the team to supplier price movements and delivers a daily GP view per location. Jelly is built to be that layer for Lightspeed users, with a five-minute setup, a flat monthly fee and results that appear within the first three months.

See your real margins across every Lightspeed site in a short Jelly walkthrough.