Lightspeed Hostme Integration: Automate Table Management

Lightspeed Hostme Integration: Guide for UK Restaurants

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

Key Takeaways for UK Lightspeed & Hostme Users

  • The Lightspeed Hostme integration creates a real-time sync between reservation data in Hostme and sales data in Lightspeed, eliminating manual double-entry for UK multi-site operators.
  • Accurate, automated data flow enables live dish costing, gross-profit visibility and stronger supplier negotiations without waiting for end-of-week reports.
  • Successful setup requires Administrator access in both platforms, correct floor-plan mapping and one integration instance per Lightspeed location.
  • Operators typically recover 10–20 hours of admin time per month and gain reliable revenue-per-cover figures once the sync is live.
  • Book a demo with Jelly to connect your Lightspeed data and unlock live margin intelligence from day one.

Prerequisites Before You Start the Integration

Confirm a few account and network details before you start the Lightspeed Hostme setup. Once these are in place, the connection process runs smoothly.

Lightspeed account requirements: You need an active Lightspeed Restaurant subscription. The user account performing the integration must hold Administrator-level permissions within Lightspeed. Manager-level accounts do not carry sufficient API access rights and will produce an authorisation error at the connection step.

Hostme account requirements: You need an active Hostme account with Owner or Admin role assigned. Standard staff accounts cannot initiate third-party integrations. Confirm your Hostme subscription tier includes POS integration. POS integration is available on Hostme’s Grande plan and above.

Network and API readiness: Both platforms communicate over HTTPS REST APIs. No custom API keys need to be generated manually, because the OAuth handshake between Lightspeed and Hostme handles authentication. Ensure the device used during setup has a stable internet connection and that your venue’s network does not block outbound OAuth redirects.

Multi-site note: Each Lightspeed business location requires a separate Hostme integration instance. This means multi-site operators must repeat the setup process once per venue, so three sites require three separate connections that follow the same steps outlined below.

See how Jelly handles multi-site Lightspeed data across all your locations in a single dashboard.

Why Real-Time Lightspeed Hostme Sync Matters

Manual reconciliation between reservation records and POS sales data is one of the most persistent sources of wasted time in UK multi-site restaurant operations. When a cover booked in Hostme does not automatically appear against the corresponding Lightspeed transaction, finance leads must cross-reference two separate systems to produce accurate weekly GP reports. At scale across two, three or five sites, this creates compounding delays that push gross-profit visibility weeks behind real trading conditions.

Real-time sync removes that manual reconciliation. When Lightspeed and Hostme are connected, table status, cover counts and associated sales data update without manual input. Finance managers gain accurate revenue-per-cover figures without waiting for end-of-week exports. Operations managers can identify underperforming sessions, such as a Tuesday dinner service running at 40% capacity, and adjust staffing or promotional activity in time to make a difference.

Beyond operational adjustments, the same real-time data strengthens your position in supplier negotiations. Accurate, real-time sales-mix data shows exactly which dishes are selling and at what volume. Chefs and operations managers gain the evidence needed to challenge supplier price increases or consolidate orders for better rates. Jelly’s Price Alert feature builds directly on this foundation and flags every ingredient price movement the moment a new invoice is scanned.

Discover how Flash Report and Price Alert protect your margins using your Lightspeed sales data across every site.

Step-by-Step Setup for Lightspeed Hostme Connection

Step 1: Log in to Hostme as Admin
Open your Hostme dashboard and navigate to Settings → Integrations → POS Systems. Confirm your account displays the Owner or Admin badge in the top-right profile menu before proceeding.

Step 2: Select Lightspeed Restaurant
Within the POS Systems panel, locate the Lightspeed Restaurant tile and select Connect. Hostme displays a brief summary of the data permissions it will request. Review these permissions, which cover table status reads and sales transaction reads, then select Continue.

Step 3: Authenticate via Lightspeed OAuth
A Lightspeed login window opens in a new browser tab. Enter your Lightspeed Administrator credentials. Lightspeed presents an OAuth permissions screen listing the scopes Hostme requires, including read access to orders, tables and business locations. Select Allow. The tab closes automatically when the connection succeeds.

Step 4: Select the business location
Hostme displays a list of all Lightspeed business locations associated with your account. Select the single location this Hostme instance should sync with. Multi-site operators repeat this step for each venue so that every site has its own dedicated connection.

Step 5: Map floor plans
Hostme prompts you to match its reservation sections, such as Main Floor or Terrace, to the corresponding table sections configured in Lightspeed. Accurate mapping here determines whether a reservation in Hostme correctly updates the right table in Lightspeed in real time. Take two minutes to verify each section name matches before saving.

Step 6: Confirm the connection
Select Save and Activate. Hostme runs a test ping to Lightspeed and displays a green Connected status indicator. Make a test reservation in Hostme and confirm the corresponding table status updates in Lightspeed within 30 seconds. This real-time update confirms a successful setup.

Connect Lightspeed to Jelly in minutes and start receiving live dish-cost data as soon as your POS sync is active.

How Lightspeed Hostme Sync Behaves in Service

Once the Lightspeed Hostme integration is active, data flows in both directions on a near-real-time basis.

Reservation-to-table updates: When a booking is confirmed, modified or cancelled in Hostme, the corresponding table in Lightspeed updates its status, such as available, reserved or seated, without any manual input from floor staff. This prevents the common scenario where a table appears available in the POS while a reservation exists in the booking system.

Sales-to-reservation matching: When a Lightspeed order is opened on a table linked to a Hostme reservation, the cover count and spend data attach to that reservation record. Hostme’s reporting then reflects actual spend per booking rather than estimated covers.

Report formats: Within Hostme, the Reservations Report and Revenue by Section views incorporate Lightspeed transaction data once the integration is live. Within Lightspeed, the standard Sales Summary and Table Activity reports keep their existing format while automatically reflecting reservation-sourced cover data.

Update frequency: The sync is event-driven rather than scheduled. There is no fixed polling interval, because updates trigger on reservation creation, modification or cancellation in Hostme and on order open or close events in Lightspeed. During high-volume service periods, both platforms handle concurrent events without queuing delays under normal network conditions.

See how Jelly layers live GP reporting on top of Lightspeed to deliver gross-profit margins by dish, by session and by site.

Lightspeed Hostme Troubleshooting Guide

Error: “Authorisation failed” during OAuth
Cause: The Lightspeed account used does not hold Administrator permissions. Resolution: Log out of Lightspeed, log back in with an Administrator account, and restart from Step 3.

Error: Table status not updating in Lightspeed after a Hostme reservation
Cause: Floor plan sections were not mapped correctly in Step 5, or the Hostme section name contains a trailing space or special character that does not match the Lightspeed section name exactly. Resolution: Return to Settings → Integrations → Lightspeed → Floor Plan Mapping in Hostme and re-verify each section name character by character.

Error: “Location not found” when selecting business location
Cause: The Lightspeed account authenticated in Step 3 does not have access to the intended business location. This occurs when a staff account was used instead of the account that owns all locations. Resolution: Re-authenticate using the Lightspeed account that holds Administrator access across all business locations.

Error: Sync active but cover counts are incorrect
Cause: The party size entered in Hostme at booking time differs from the covers manually entered by floor staff in Lightspeed. Resolution: Train floor staff to accept the Hostme-sourced cover count rather than overriding it in the POS. Alternatively, enable the Hostme setting that locks cover count on table open.

Error: Integration shows “Connected” but no data appears in Hostme reports
Cause: The Lightspeed location selected during setup is a test or sandbox environment. Resolution: Disconnect, return to Step 4 and select the live production location.

Get help from Jelly’s onboarding team. The team supports Lightspeed connections and can help resolve integration issues during your first week.

How to Measure Integration Success

Three practical metrics confirm that the Lightspeed Hostme integration is delivering operational value.

Admin time saved: Track the hours your operations or finance team previously spent reconciling Hostme reservation records against Lightspeed sales exports each week. A successful integration eliminates this task entirely and reduces reconciliation time to zero. For multi-site operators, this time saving multiplies across every location and recovers significant admin hours that can be redirected to higher-value work.

Revenue-per-cover accuracy: Compare Hostme’s revenue-per-cover figures before and after integration. Pre-integration, these figures rely on manual cover entry and are frequently understated. Post-integration, they reflect actual Lightspeed transaction values and become reliable enough to inform menu pricing decisions.

Invoice discrepancy rate: When sales data is accurate and real-time, finance leads can cross-reference supplier invoices against actual dish sales volumes with confidence. Operators using Jelly alongside Lightspeed consistently identify invoice discrepancies, such as incorrect quantities or unapplied credits, that were previously invisible in manual workflows. Jelly’s Price Alert feature flags every supplier price movement and gives finance leads the data to challenge discrepancies before they compound.

See how Jelly quantifies GP improvement from week one of your Lightspeed integration.

Next Steps: Connect Lightspeed to Jelly

Once the Lightspeed Hostme integration is stable and data is flowing cleanly, the next step is connecting Lightspeed to Jelly. Jelly’s native Lightspeed integration uses a real-time API connection that delivers item-level sales data the moment each transaction completes. The architecture mirrors the Hostme sync but focuses on dish costing and margin reporting rather than table management.

Connecting Lightspeed to Jelly is a short process. Open Jelly, navigate to 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, which confirms the connection is a supported, maintained integration rather than a workaround.

Once connected, three Jelly features activate immediately and build on your Lightspeed sales data to protect margins. The Flash Report delivers a daily view of gross-profit margin calculated from your Lightspeed sales and your scanned supplier invoices, with no spreadsheet or accountant required. This real-time margin visibility is then protected by the Price Alert feature, which flags every ingredient price movement from every supplier invoice and gives chefs and operations managers the evidence to negotiate credits or switch suppliers before margin damage accumulates. Finally, the Sales Mix report shows which dishes are selling at volume and which are most profitable, enabling data-driven menu engineering decisions that refine the menu based on actual performance across every site.

Operators who connect Jelly to Lightspeed consistently recover meaningful margin. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue. Populu lifted GP from 68% to 72% across 16 locations. Jelly’s real-time costing supports faster supplier negotiations and tighter menu controls.

Connect your Lightspeed data to Jelly and switch on live dish costing, Price Alerts and Flash Reports today.

FAQ: Lightspeed Hostme and Jelly

Does the Lightspeed Hostme integration work across multiple UK sites simultaneously?
Yes, and each Lightspeed business location still requires its own Hostme integration instance as outlined in the prerequisites. The setup process, which takes only a few minutes per site, is identical for each location. There is no technical limit on the number of locations you can connect, and Hostme’s reporting consolidates data across all connected sites in its multi-location dashboard view.

Who owns the data that flows between Lightspeed and Hostme?
The data generated in each platform remains owned by the operator. Lightspeed’s OAuth integration grants Hostme read access to specific data scopes, including orders, tables and business locations, without transferring data ownership. You can revoke Hostme’s access at any time from within your Lightspeed account under Connected Applications, which immediately terminates the sync without deleting historical data in either platform.

How frequently does the sync update during a busy dinner service?
The integration is event-driven, not scheduled on a fixed polling interval. Updates trigger on specific actions, such as a reservation confirmed in Hostme or an order opened or closed in Lightspeed, and typically propagate within 15–30 seconds under normal network conditions. During high-volume service, both platforms process concurrent events without queuing delays, so a fully booked Saturday dinner service does not degrade sync performance.

What happens to historical reservation and sales data when the integration is first activated?
The Lightspeed Hostme integration syncs data from the point of connection forward. Historical records in Lightspeed and Hostme are not retroactively linked. This behaviour matches Jelly’s Lightspeed integration, where POS-to-dish linking only surfaces items sold since the integration was connected, which keeps the mapping clean and free of legacy menu clutter.

Can Jelly work with Lightspeed if we do not use Hostme for reservations?
Yes. Jelly’s Lightspeed integration is independent of any reservation platform. Jelly connects directly to Lightspeed Restaurant via the Lightspeed API and pulls item-level sales data in real time regardless of which reservation tool, or no reservation tool, the venue uses. The Hostme integration and the Jelly integration operate as complementary layers that can be deployed together or independently.

Conclusion: Turning Synced Data into Margin Control

The Lightspeed Hostme integration removes the manual reconciliation that sits between front-of-house reservations and back-of-house sales data. With table status, cover counts and transaction values flowing automatically between the two platforms, UK multi-site operators recover 10–20 hours of admin per month and gain the accurate, real-time sales data that margin management requires. Jelly extends that foundation further by connecting to Lightspeed in minutes and delivering live dish costing, Price Alert notifications and daily Flash Reports that turn synced POS data into gross-profit visibility across every site, every day.

See how Lightspeed Hostme and Jelly work together to give your operation complete margin control from reservation through to gross profit in real time.