Written by: JJ Tan, Founder, Jelly | Last updated: 10 October 2026
Key Takeaways
- The Lightspeed TheFork integration connects reservations to open checks in Lightspeed Restaurant (K-Series). Silent failures usually come from table-number mismatches or missed seated-status triggers.
- Exact table-number matching between TheFork Manager and Lightspeed is essential. Any discrepancy stops reservations from opening checks automatically.
- The seated-status trigger in TheFork Manager fires the API call that opens an order in Lightspeed. Reservation time alone does not open a check.
- Regular checks after table plan changes, menu updates or token expiry keep the integration reliable as a live operational system.
- Jelly turns Lightspeed sales and reservation data into real-time margin visibility, automating invoices, inventory and dish profitability.
Start turning your Lightspeed data into margin insight
Before You Begin: Prerequisites for the Lightspeed TheFork Integration
Confirm these requirements before you connect Lightspeed and TheFork:
- Admin access to Lightspeed Back Office
- Admin access to TheFork Manager
- The restaurant’s table plan and table numbers documented in both systems
- Confirmation that the venue uses Lightspeed Restaurant (K-Series), not a legacy Lightspeed product
- A TheFork Manager account in good standing with the Lightspeed connection tile available
The owner, operations manager or GM usually owns the setup process, and the head chef or finance lead may help if table plans or menu structures change during setup. Whoever leads the work should treat the integration as a one-off configuration with ongoing sync behaviour that needs occasional checks rather than daily management.
Table plan changes, menu updates and token expiry can all affect the connection without triggering an obvious error, so a quick review after each change protects service. For a broader walkthrough of connecting Jelly to Lightspeed, see the Lightspeed Restaurant Integration: Complete Setup Guide.
See how Jelly supports your Lightspeed setup
Why the Lightspeed TheFork Integration Matters
The integration matters because it removes manual work and improves data accuracy at the point of service. Getting it right has direct operational consequences:
- Reservations arriving as orders reduce manual re-entries at the pass during service
- Covers and spend history visible against the booking give GMs a clearer picture of service performance
- A cleaner link between reservations and revenue cuts reconciliation time at month-end
- The seated-status trigger, when working correctly, opens the check at the moment the guest sits instead of when a server remembers to start one
TheFork’s POS API operates a two-way flow. Reservation details are made available to the POS, and TheFork calls a POS-configured API endpoint to open the order when the restaurant marks the diner as ARRIVED or SEATED in TheFork Manager. This mechanism converts a booking into a live check and only fires when the status change is made correctly in TheFork Manager.
Improve how you use Lightspeed reservation data
How to Connect TheFork to Lightspeed
Use these steps for the Back Office → Integration Hub → TheFork connection flow. TheFork Manager linking often causes issues, so the sequence below focuses on that side.
- Access Lightspeed Back Office. Log in with admin credentials. A successful result shows the left-hand navigation menu with Integration Hub accessible.
- Open Integration Hub. From the left-hand navigation, select Integration Hub, then search or browse for TheFork. A successful result shows the TheFork tile as visible and clickable.
- Retrieve the Connection Token. Click the TheFork tile and retrieve the connection token provided during setup. A successful result displays a token string that you can copy.
- Link Consoles in TheFork Manager. In TheFork Manager, open the Lightspeed connection tile. Paste the token into the prompt and click “Proceed with linking.” A successful result confirms that TheFork Manager has established the link.
- Sync Devices. Update your POS terminals to recognise the new integration by tapping the reload icon on your iPad app, or by going to POS > Devices in Back Office and selecting the reload button. A successful result shows the POS with the integration status as active.
Once the consoles are linked, table numbering becomes the most common point of failure. Exact table-number matching is critical. Table numbers assigned in TheFork Manager must precisely match the table numbers on your Lightspeed Restaurant floor plan. If TheFork Manager has “Table 12” and Lightspeed has “T12” or “12A,” the reservation will not open a check. Before going live, export your table list from both systems and reconcile them line by line.
TheFork Manager’s redesigned Floor Plan forms part of its autumn 2026 update, with the interactive drag-and-drop floor plan rolling out to partners from November 2026. It lets operators spot free tables instantly, create reservations directly from the floor plan, and track booking status in real time using dynamic colours and table countdowns, which makes accurate table numbering easier during service.
For troubleshooting Jelly’s own Lightspeed connection, see Lightspeed Integration Troubleshooting: Restore GP Data.
Get help connecting Lightspeed and Jelly
What Syncs Between Lightspeed and TheFork
Knowing what syncs in each direction helps you diagnose where failures occur. Here is what moves between TheFork Manager and Lightspeed Restaurant (K-Series).
Reservation → POS: When a guest books on TheFork, reservation information such as party size, time, table assignment and guest notes becomes available to Lightspeed Restaurant (K-Series). Reservations are only shared after being marked seated or arrived in TheFork, or 15 minutes before the start of service, depending on settings. The reservation appears against the assigned table.
Seated Status → POS: When the restaurant marks the diner as ARRIVED or SEATED in TheFork Manager, TheFork calls an API endpoint on the POS to open the order. This trigger starts the in-restaurant service flow. In TheFork Manager, “seated” means the guest has physically arrived and been seated. In Lightspeed, this action opens a check against the assigned table.
Order Close → TheFork: After the bill is paid, the POS closes the order, frees up the table, and sends updated order details, including the total amount and items, back to TheFork. TheFork then updates the reservation status in TheFork Manager to LEFT.
Spend History → POS: The outbound data documented in TheFork’s POS API is final order information tied to a specific reservation. This feed covers the total amount and items for that visit only. Operators should not expect TheFork Manager to display a guest’s lifetime spend across all visits based on this integration alone.
Yums and Loyalty Visibility: TheFork’s POS API documentation does not show that the Lightspeed–TheFork integration synchronises loyalty points, rewards or broader guest-profile history into TheFork Manager. Treat Yums visibility as separate from the POS integration.
Use synced data to improve your margins
Troubleshooting: Why TheFork Reservations Are Not Opening Checks in Lightspeed
Most failures trace back to a small set of causes. Work through these checks in order before escalating to support.
Why Is My TheFork Reservation Not Opening a Check in Lightspeed?
Check three things in order:
- Table-number mismatch: The table number in TheFork Manager does not exactly match the table number in Lightspeed. As noted earlier, this is the most common cause, so reconcile the table lists in both systems before service.
- Seated-status not triggered: The reservation has not been marked as ARRIVED or SEATED in TheFork Manager. The check only opens when this status change occurs, so the team must action this step.
- Integration token expired: The connection token linking the two systems has expired or been revoked. Check the Integration Hub in Back Office to confirm that the connection remains active.
What Happens When a Seated Reservation Never Creates an Order?
If a guest is seated but no check appears in Lightspeed, follow this sequence:
- Confirm that the table number in TheFork Manager matches the floor plan in Lightspeed exactly.
- Re-seat the reservation in TheFork Manager by marking it as seated again to re-trigger the API call.
- If that fails, manually open the check in Lightspeed against the correct table.
- Verify the connection in Integration Hub and, if the token has expired, re-link the consoles using the setup steps above.
Do TheFork Deposits Work with Lightspeed?
TheFork Manager supports card-hold and prepayment features for no-show protection. However, the Lightspeed Restaurant (K-Series) API documentation does not show any endpoint, property or field for reservation deposits, prepayments or deposit reconciliation. Operators should reconcile deposits within TheFork Manager and treat deposit handling as a separate workflow from the POS integration.
How Do Multi-Table Bookings Behave?
On TheFork Manager, when you use automatic table assignment mode on Performance or Enterprise plans, the system assigns bookings to tables based on priority and combinations, which allows a single reservation to span multiple tables. The Lightspeed Restaurant (K-Series) API documentation does not document any mechanism for linking multiple tables to a single reservation. In practice, operators should test how large-party bookings appear in Lightspeed and be ready to split or merge checks manually. Confirm behaviour with Lightspeed or TheFork support if multi-table bookings are common in your venue.
Get troubleshooting support for your Lightspeed data
How to Disable the Lightspeed TheFork Integration Cleanly
Disabling the integration requires action in both Lightspeed and TheFork. Current documentation from TheFork and Lightspeed does not confirm that disconnecting one side automatically removes the other.
On the Lightspeed Back Office side:
- Log in to Back Office with admin credentials.
- Navigate to Integration Hub.
- Locate the TheFork connection and select the option to disable or remove the integration.
- Confirm the action when prompted.
On the TheFork Manager side:
- Log in to TheFork Manager.
- Navigate to the Lightspeed connection tile.
- Remove or deactivate the connection.
Follow this operational sequence before disconnecting:
- Pause new reservations or service changes.
- Export and record all active and future bookings.
- Disconnect the integration in Lightspeed Back Office.
- Ask TheFork Manager support or your account administrator to deactivate the corresponding Lightspeed connection.
- Test that new TheFork reservations no longer create or update Lightspeed records. If you also run other reservation platforms, apply the same table-mapping checks when you review those integrations.
Where This Sits Alongside OpenTable and SevenRooms
UK operators running multiple reservation partners should treat each platform as using the same basic rule. A table number in the reservation system must match a table number in the POS floor plan. The mismatch issues that affect TheFork apply in the same way to OpenTable and SevenRooms connections.
Multi-platform operators should standardise table numbering across all systems and audit the mapping whenever the floor plan changes. For operators also using Hostme alongside Lightspeed, see the Lightspeed Hostme Integration: Guide For UK Restaurants.
How Jelly Turns Lightspeed Data into Margin Visibility
Once reservation and POS data flows cleanly through Lightspeed, the next step is using it to protect margin. Jelly is listed on the Lightspeed marketplace and integrates natively with Lightspeed via real-time API, delivering item-level sales data the moment a transaction completes.
Jelly’s Menu Engineering (Sales Mix) uses Lightspeed sales data to show which dishes are most popular and most profitable. This view supports clear decisions about menu pricing and placement.
Jelly’s Flash Report builds on that by giving a daily, weekly or monthly view of gross profit margin calculated from invoice costs and POS sales data. You see the impact of your reservation mix on profitability without waiting for month-end accounts.
Behind both features, Jelly automates invoice scanning, price alerts and live dish costing, which saves operators 2–5 hours of weekly work. The results speak clearly: one operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue, while Populu lifted GP from 68% to 72% across 16 locations.
Jelly charges a flat rate of £129/month per location with no variable charge per user or feature.
See how Jelly turns Lightspeed data into margin visibility
FAQ
Who Typically Owns the Lightspeed TheFork Integration Setup?
The owner, operations manager or GM usually owns the process, and admin access to both Lightspeed Back Office and TheFork Manager is required. The head chef or finance lead may help if table plans or menu structures change during setup, for example when floor plan numbering is revised or new menu items need mapping in downstream tools.
How Often Should I Check the Lightspeed TheFork Connection?
Check the connection after any menu or table plan change and periodically during service on high-volume nights. The integration behaves as a live operational system, and a brief check at the start of each busy service period is a sensible precaution.
What Happens When the Menu or Table Plan Changes?
If table numbers change in Lightspeed, update TheFork Manager to match before the next service. Mismatched table numbers silently prevent checks from opening, with no error message in either system. If menu items change, verify that the POS-to-dish mapping in downstream tools, including Jelly, remains accurate so that sales mix and margin data stay clean.
Does the Lightspeed TheFork Integration Work Across Multiple Sites?
The Lightspeed Restaurant (K-Series) TheFork integration is configured in Back Office, with the connection token and table numbers set up per venue. For Lightspeed Restaurant (K-Series), each business location needs its own TheFork account and pro plan subscription.
Table numbers in TheFork Manager must also match that location’s Lightspeed floor plan exactly, since floor plans and tables are managed separately per site. Multi-site operators should standardise table numbering across locations where possible to reduce mapping errors when staff move between sites. Jelly also operates on a per-location basis at £129/month per site, which makes it straightforward to scale margin visibility across a growing group.
What Should I Do If the Connection Drops Mid-Service?
Check the Integration Hub in Back Office to confirm the connection status. If the token has expired, re-link the consoles using the setup steps in this guide. During service, manually open checks in Lightspeed against the correct tables and note which reservations were affected.
After service, reconcile those checks against TheFork Manager so that covers data and order totals stay accurate. Handle this reconciliation immediately after service to reduce the risk of missing a booking.
Protect your GP with cleaner Lightspeed data
Conclusion
The Lightspeed TheFork integration delivers clear operational value when it works correctly. Reservations arrive as open checks, covers data stays clean, and the team stops re-entering bookings at the pass.
Reliable performance depends on exact table-number matching between TheFork Manager and Lightspeed, a clear process for using the seated-status trigger, and a simple routine for checking the connection when something breaks mid-service. Table plan changes, token expiry and unmatched table numbers cause most silent failures, and each has a direct fix.
For operators who want deeper insight, Jelly turns the sales and reservation data flowing through Lightspeed into real-time margin visibility. It automates invoices, dish costing and GP reporting so you can make faster, better-informed decisions every service.
See Jelly in action with your Lightspeed data
