Lightspeed TheFork Integration Guide for UK Restaurants

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

Key Takeaways for UK Operators

• UK restaurants turning over £500k+ can remove double-bookings and manual reservation friction by connecting Lightspeed Restaurant to TheFork Manager.
• The integration creates a live, two-way data flow that updates table availability in real time and returns guest spend to TheFork’s CRM automatically.
• Accurate table mapping and consistent cover capacities between both platforms are essential to prevent post-integration seating conflicts.
• Automated seating and order creation remove manual steps between guest arrival and bill opening, while VAT-compliant data return supports accurate back-office reconciliation.
• Adding Jelly on top of your Lightspeed data delivers live gross-profit visibility and price alerts, and you can book a demo to see how Jelly protects your margins.

Account-Level Lightspeed TheFork Integration Setup

The first step is linking Lightspeed and TheFork at account level before you touch tables or seating rules. Follow these steps in order.

1. Log in to Lightspeed Back Office. Navigate to Settings → Integrations → Marketplace. Search for TheFork in the marketplace listing. [Screenshot placeholder: Lightspeed marketplace listing showing TheFork tile]
2. Enable the TheFork integration. Click Connect on the TheFork tile. Lightspeed displays your Restaurant ID. Copy this value because you will need it in TheFork Manager.
3. Open TheFork Manager. Go to Settings → POS Integration. Select Lightspeed from the provider list and paste your Restaurant ID into the designated field.
4. Enter API credentials. TheFork Manager prompts for your Lightspeed API key. Generate this key inside Lightspeed Back Office under Settings → API Access, then paste it into TheFork Manager.
5. Save and verify the connection. TheFork Manager confirms a successful handshake. If the status shows an error, re-check that the API key has the correct permissions scope, including read and write on reservations and orders.

Inputs required: Lightspeed admin credentials, TheFork Manager admin credentials, Restaurant ID, API key.
Output: Active two-way connection between Lightspeed and TheFork.

Table Mapping Best Practice for Accurate Seating

Exact table mapping between Lightspeed and TheFork prevents double-bookings and seating confusion after you go live.

1. Audit your Lightspeed floor plan. In Lightspeed Back Office, open Floor Plans and note every table number, section name and cover capacity.
2. Replicate the floor plan in TheFork Manager. Under Restaurant Settings → Tables, create tables using identical names and numbers to those in Lightspeed. Keep naming consistent in both systems.
3. Assign cover capacities consistently. If a table seats four in Lightspeed, set the same capacity in TheFork. Mismatched capacities cause TheFork to offer covers that Lightspeed cannot accommodate.
4. Map sections to service areas. If your venue has separate dining rooms or terraces, create matching sections in both systems and assign tables to the correct section in each.
5. Run a test booking. Make a test reservation in TheFork for a specific table and confirm it appears on the correct Lightspeed floor plan in real time.

Inputs required: Current Lightspeed floor plan, TheFork Manager table editor access.
Output: Identical table structure across both platforms, which removes mapping conflicts.

Automated Seating and Order Flow Between Systems

Once table mapping is confirmed, the integration automates the journey from reservation to open bill with no manual steps.

1. Enable automated seating in TheFork Manager. Under POS Settings → Seating Automation, toggle the feature on. This setting instructs TheFork to push a seating event to Lightspeed the moment a guest is marked as arrived.
2. Confirm real-time table status updates. When a table is opened in Lightspeed, TheFork Manager marks it as occupied and removes it from available inventory. Because TheFork can no longer see that table as available, it cannot accept a second booking for the same slot.
3. Verify order creation on seating. Lightspeed should automatically open a new order ticket linked to the TheFork reservation reference. Check that the guest name and cover count transfer correctly to the ticket header.
4. Test a full-cycle scenario. Seat a test booking, add a menu item in Lightspeed, close the bill, and confirm the table returns to available status in TheFork Manager within 60 seconds.

Output: No manual intervention required between a guest arriving and an order ticket opening in Lightspeed.

CRM and Loyalty Data Returned to TheFork

The integration sends guest spend data from Lightspeed back to TheFork Manager so your CRM and loyalty records stay accurate.

1. Enable data return in TheFork Manager. Under POS Settings → Data Return, confirm that bill total, itemised spend and visit date are selected for sync.
2. Link guest profiles. TheFork matches returning guests by email address. Ensure your front-of-house team collects and enters guest email addresses at the point of booking, not at the table.
3. Review historical bill details. After each service, TheFork Manager guest profiles display spend per visit, average cover value and visit frequency. Use this data to shape loyalty offers and marketing campaigns.
4. Set loyalty triggers. Use TheFork Manager loyalty tools to create automated rewards based on visit count or cumulative spend thresholds, now populated automatically from Lightspeed bill data.

Output: Enriched guest profiles in TheFork Manager with accurate spend history and no manual data entry.

Back-Office Data Handling and UK VAT Checks

1. Confirm VAT codes are mapped correctly in Lightspeed. UK operators should ensure that food and beverage items carry the correct VAT rate, such as 20% standard or 0% for qualifying food items.
2. Check that TheFork passes net and gross values. In TheFork Manager POS settings, verify that the data return includes both net revenue and VAT amounts so your back-office reconciliation reflects accurate taxable turnover.
3. Reconcile daily Z-reports. After each service, cross-reference Lightspeed end-of-day reports with TheFork Manager revenue summaries. Discrepancies usually indicate a table that was seated manually rather than through the automated flow.
4. Push to accounting software. Once your back-office reconciliation is complete, you have accurate transaction data flowing through Lightspeed, which forms the base for your accounting and margin analysis.

Introducing Jelly: Profitability Layer on Lightspeed–TheFork Data

With reservations and seating now automated, the next challenge is protecting the margin on every cover you serve. The Lightspeed–TheFork integration solves the operational problem. Jelly solves the financial one. Once Lightspeed is live, Jelly connects to it via a real-time API, using the same data stream that powers your TheFork seating flow, and turns every sale into a live gross-profit calculation.

[Screenshot placeholder: Jelly integration screen showing Lightspeed connection active]

Jelly Flash Report gives a daily view of your GP margin calculated from invoice costs and Lightspeed sales data. The Price Alert dashboard flags every ingredient price change from every supplier the moment a new invoice is scanned, so a margin-eroding price increase never sits unnoticed for weeks.

[Screenshot placeholder: Jelly Price Alert dashboard showing flagged supplier price increases]

Operators using Jelly alongside Lightspeed see measurable improvements in gross profit. For a site turning over £500,000 annually, this can represent significant recovered margin each year. Amber, a Mediterranean restaurant in East London, saves £3,000–£4,000 per month using Jelly invoice automation and price alerts, which delivers roughly a 68× return on the platform cost.

Jelly is listed on the Lightspeed marketplace, and connecting the two platforms takes under five minutes: open Jelly, click Integrations, sign in to Lightspeed, grant permissions, then select which categories to sync.

See how Jelly transforms your Lightspeed sales data into real-time dish costing and margin alerts by booking a guided demo.

Common Lightspeed TheFork Integration Issues

Double-bookings appearing after integration: The most common cause is a table name mismatch between Lightspeed and TheFork Manager. Return to the table mapping section and confirm every table ID is identical in both systems. Also check that automated seating is enabled, because without it TheFork does not receive real-time occupancy updates from Lightspeed.

Missing loyalty or CRM data in TheFork Manager: This usually means guest email addresses are not being captured at the booking stage, which prevents TheFork from matching the bill return to a guest profile. Implement a front-of-house process to collect emails at reservation, not on arrival.

Table-mapping conflicts after a floor plan change: Any physical change to your dining room, such as adding a table or splitting a section, requires an update in both Lightspeed and TheFork Manager at the same time. Updating only one system breaks the mapping and can cause seating errors.

UK VAT handling discrepancies: If your Lightspeed Z-report and TheFork revenue summary show different totals, check whether TheFork is receiving gross or net values. Confirm the VAT code configuration in the Lightspeed product library matches HMRC requirements for each item category.

Success Metrics and Multi-Site Rollout

Operators who complete the full Lightspeed–TheFork–Jelly workflow can achieve clear operational and financial gains.

• Removal of double-bookings and manual reservation entry
• Weekly admin time recovered through automated seating and order creation
• Live GP margin visibility per dish, updated with every new supplier invoice
• Faster supplier negotiations backed by Price Alert data instead of end-of-month spreadsheet reviews
• Xero reconciliation time reduced through Jelly accounting integration

For multi-site operators, Jelly supports separate location profiles under a single account at £129 per location per month, using a flat rate with no per-user charges. Each site maintains its own invoice stream, dish costing and Flash Report, while management retains a consolidated view across all locations. Lightspeed multi-site architecture supports the same structure, so the combined stack is straightforward to replicate at each new site.

Frequently Asked Questions

Who owns the integration data?
Each platform retains ownership of the data it generates. Lightspeed holds transaction and order data. TheFork holds reservation and guest CRM data. Jelly holds invoice, costing and GP margin data. The integration creates a shared data flow between them, but no single platform takes ownership of another record set. UK operators should review their data processing agreements with each provider to confirm GDPR compliance, particularly regarding guest email data passed between TheFork and Lightspeed.

How long does the full setup take?
The Lightspeed–TheFork account connection and table mapping can take a few hours, depending on the complexity of your floor plan. Jelly Lightspeed connection uses the same quick setup process described earlier. Many operators complete the full three-platform workflow, including Lightspeed, TheFork and Jelly, within a working day and begin receiving GP data after their first invoice is scanned.

What happens with multi-site configurations?
Each site requires its own TheFork Manager account linked to its corresponding Lightspeed location. Table mapping must be completed separately for each site. In Jelly, each location operates as a distinct profile, so dish costs, supplier invoices and GP margins are tracked independently. Management-level users can access all site profiles from a single Jelly login, which provides a consolidated view without mixing site-level data.

How are supplier price changes handled after integration?
Supplier price changes do not affect the Lightspeed–TheFork integration directly, because that integration handles reservations and order flow rather than procurement. Within Jelly, every new invoice is scanned automatically and any price change triggers a Price Alert. The alert shows which ingredient has changed, by how much and from which supplier. This gives chefs and operations managers the data needed to renegotiate rates, switch suppliers or adjust menu pricing before the margin impact compounds.

Conclusion: Protect Margins from Day One

Connecting Lightspeed Restaurant to TheFork removes the manual friction between reservations and service. You avoid double-bookings, manual ticket creation and disconnected guest records. The steps above cover the complete workflow, including account setup, table mapping, automated seating, CRM data return, VAT reconciliation and troubleshooting.

Adding Jelly to the same Lightspeed data stream takes the integration further by converting every sale and every supplier invoice into live gross-profit intelligence. Operators at Amber achieve the savings mentioned earlier through automated invoice processing and real-time price alerts. The Howard Arms reached 80% gross profit. Populu lifted GP from 68% to 72% across 16 locations. The integration creates the data, and Jelly turns that data into profit.

Ready to protect your margins? Schedule a 30-minute demo to see the full Lightspeed–Jelly workflow in action.