Lightspeed Table Booking Integration Guide for UK Venues

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

Key Takeaways for Lightspeed, OpenTable and Jelly

• A Lightspeed table booking integration with OpenTable removes double-bookings by syncing reservations directly into the POS in real time.
• Automated data flow between OpenTable and Lightspeed K-series cuts manual errors in cover counts, deposits and VAT handling.
• Jelly connects to Lightspeed via a five-minute API setup, turning every transaction into live gross-profit visibility through Flash Reports and Sales Mix analysis.
• UK operators using the combined stack recover 10–20 hours of monthly admin time previously spent on manual reconciliation and invoice checks.
• Book a Jelly demo for your Lightspeed setup and see how the platform delivers immediate margin insights.

How Lightspeed and OpenTable Work Together with Jelly

For UK restaurant, pub and boutique-hotel operators running Lightspeed Restaurant (K-series), the gap between a confirmed reservation and a completed POS transaction is where margin quietly disappears. When front-of-house teams manually transfer booking data into the POS, errors accumulate: covers are miscounted, deposits are misapplied, and the sales data that should be driving nightly GP calculations arrives late or incomplete.

These manual workflows create a margin leak that compounds across every service. Connecting OpenTable directly to Lightspeed K-series closes that gap at the operational level. Once the integration is live, reservation data flows into the POS automatically, covers are tracked in real time, and each transaction is available for downstream reporting.

Jelly then connects to Lightspeed through the same quick API process, pulls item-level sales data the moment each transaction completes, and converts it into live gross-profit visibility, including Flash Reports, Price Alerts and Sales Mix analysis, without any manual data entry. The result is a joined-up system where the booking, the sale and the margin figure sit in a single source of truth.

Pre-Setup Checks Before You Connect

1. Confirm your Lightspeed plan. Verify that your Lightspeed Restaurant (K-series) subscription includes API access and third-party integrations. Contact Lightspeed support if you are unsure which tier you are on.
2. Check your OpenTable account type. OpenTable’s POS connectivity features are available on specific OpenTable for Restaurants plans. Confirm your plan includes the Lightspeed integration before you continue.
3. Assign admin credentials. You will need admin-level access to both your Lightspeed back office and your OpenTable account. Because the integration touches payment flows and VAT configuration, delegate this task to your operations manager or finance lead, someone with authority over financial controls, not a floor supervisor.
4. Audit your table and menu structure. Ensure table numbers in Lightspeed match the floor plan configured in OpenTable. Discrepancies here are the single most common cause of sync failures.
5. Review UK data-protection obligations. Guest reservation data, including name, contact details and dietary notes, is personal data under UK GDPR. Confirm both platforms are configured to process data under a lawful basis and that your privacy notice reflects the use of third-party reservation software.
6. Set aside 60–90 minutes. The technical steps are straightforward, and table mapping plus testing require uninterrupted time. Schedule this outside service hours.

Why Lightspeed, OpenTable and Jelly Together Matter

1. Real-time margin visibility. When reservation and sales data sit together in Lightspeed and then flow into Jelly, operators see gross-profit figures by dish and by service instead of waiting until month-end when action is limited.
2. Fewer double-bookings. A direct integration means OpenTable reads live table availability from Lightspeed rather than relying on manual updates. This reduces the risk of double-booking during peak covers.
3. Faster supplier negotiations. Jelly’s Price Alert feature flags ingredient price changes the moment a new invoice is scanned. With accurate, real-time sales-mix data flowing from Lightspeed, operators can calculate the margin impact of a price increase and approach suppliers with hard figures.
4. VAT compliance on deposits. Automated payment flows between OpenTable and Lightspeed reduce the risk of deposit VAT being recorded incorrectly. This area often triggers audits for UK hospitality businesses.
5. Reduced admin burden. The time savings are substantial. Operators consistently recover the admin hours previously spent on manual data entry, price checking and invoice reconciliation.

See how Jelly delivers live GP reporting from the moment your Lightspeed integration goes live.

8-Step Checklist to Connect Lightspeed and OpenTable

1. Log in to Lightspeed Restaurant back office. Navigate to the integrations or marketplace section. Lightspeed’s integration marketplace lists OpenTable as a supported reservation partner for K-series.
2. Locate the OpenTable integration tile. Select it and start the authorisation flow. You will be redirected to OpenTable to grant Lightspeed permission to read and write reservation data.
3. Authenticate your OpenTable account. Use your OpenTable admin credentials. Once authenticated, OpenTable confirms which restaurant profile is being linked. If you operate multiple venues, select the correct profile before you move on.
4. Map your floor plan. In the Lightspeed back office, match each table number to its corresponding OpenTable section. This step is critical. Mismatched table IDs cause reservations to appear in the wrong section or fail to sync.
5. Configure VAT and payment handling. In Lightspeed, confirm that deposit payment types received from OpenTable are mapped to the correct VAT rate, either 20% standard or the applicable reduced rate for your venue. Incorrect mapping here creates reconciliation errors in Xero and potential VAT liability.
6. Sync your menu and covers data. Ensure that the menu items and course structures in Lightspeed reflect what guests will order against their reservation. Configure pre-set menus or tasting menus as Lightspeed combos so they appear correctly in sales reports.
7. Run a test reservation. Create a test booking in OpenTable and confirm it appears in the Lightspeed floor plan in real time. Complete a test transaction and verify the cover count, payment type and VAT split are all recorded correctly in Lightspeed reporting.
8. Connect Jelly to Lightspeed. Open Jelly, navigate to Integrations, sign in to Lightspeed and grant permissions. Select the food and beverage categories to sync. The connection process is complete in minutes. From this point, each Lightspeed transaction feeds Jelly’s Flash Report and Sales Mix automatically.

Best Practices for Ongoing Mapping and Data Hygiene

After you complete the eight steps, the reliability of your Lightspeed reservations integration depends on keeping table and menu data aligned across both platforms.

1. Maintain a single source of truth for table numbers. Designate Lightspeed as the master floor plan. Make any changes to table layout, including seasonal rearrangements and private dining additions, in Lightspeed first, then mirror them in OpenTable.
2. Update menu items in Lightspeed before OpenTable. If you add or retire dishes, update Lightspeed first. Jelly’s POS-to-dish linking only surfaces items sold since the integration was connected, so new items appear cleanly in Jelly’s Sales Mix without legacy clutter.
3. Review cover counts weekly. Cross-reference OpenTable’s reservation report against Lightspeed’s covers data each week. Discrepancies of more than 2–3% indicate a sync issue that you should investigate before it compounds across a full trading period.
4. Use Jelly’s Flash Report as a daily reconciliation tool. Use the Flash Report to catch data inconsistencies early. Because Jelly calculates GP from both invoice costs and Lightspeed sales data, a sudden drop in the Flash Report GP percentage often signals a menu mapping error or an unrecorded price change, not an actual margin decline.

Common Issues and How to Fix Them

1. Double-bookings persisting after integration. This almost always indicates that OpenTable is not reading live availability from Lightspeed. Check that the API connection is active in both platforms and that no firewall or network restriction is blocking the webhook.
2. Menu items not appearing in Jelly’s Sales Mix. Jelly only surfaces items sold since the integration was connected. If a dish was sold before the Lightspeed–Jelly connection was established, it will not appear until it sells again. This behaviour is intentional and keeps mapping clean.
3. VAT split errors on deposits. If OpenTable deposits appear in Lightspeed without a VAT code, the payment type has not been mapped correctly. Return to the Lightspeed payment types configuration and assign the correct tax rate.
4. Admin access errors during setup. Both the Lightspeed and OpenTable integrations require admin-level credentials. Jelly flags this requirement upfront during its own setup flow. If a team member without admin access attempts the connection, the authorisation fails silently.
5. UK GDPR compliance gaps. Guest data flowing from OpenTable into Lightspeed creates a data-sharing arrangement between two processors. Ensure both platforms are listed in your data processing register and that your privacy notice is updated to reflect this.

How to Track Results from Your Integration

1. Admin time recovered. Track hours spent on manual reservation-to-POS reconciliation before and after integration to quantify the time recovered.
2. GP percentage via Jelly Flash Report. Monitor your daily and weekly GP percentage in Jelly. A stable or improving GP figure confirms that sales data flows correctly and that ingredient costs are being captured accurately from invoices.
3. Invoice discrepancy rate. Measure the number of invoice queries raised per month. Jelly’s automated invoice scanning and Price Alert feature reduce discrepancies by surfacing price changes immediately rather than at month-end.
4. Double-booking incidents. Log any double-booking complaints before and after integration. A functioning Lightspeed–OpenTable connection should reduce these to near zero within the first trading week.

See Flash Reports and Price Alerts in action with your own Lightspeed data.

Next Steps to Get More Value from Jelly

1. Scale to multi-site. Jelly charges a flat rate of £129 per location per month. Once the Lightspeed–OpenTable–Jelly stack is proven at one site, replicating it across additional venues adds a consolidated GP view across all locations without extra complexity.
2. Add Jelly’s Cookbook for live dish costing. With Lightspeed sales data flowing into Jelly, build your recipes in Jelly’s Cookbook section. Ingredient costs update automatically with every new invoice, so your dish GP margin stays live and you avoid spreadsheets.
3. Use Sales Mix to engineer your menu. Jelly’s Sales Mix report, powered by Lightspeed item-level data, shows which dishes are most popular and most profitable. Use this insight to retire low-margin items, promote high-margin dishes and plan your next menu cycle.
4. Push invoices to Xero automatically. Jelly’s one-click Xero integration pushes digitised invoices directly into your accounting software, cutting bookkeeping time by up to 90% and keeping your accounts payable current without manual entry.

FAQ

Does Jelly work directly with Lightspeed Restaurant (K-series)?

Yes. Jelly is listed on the Lightspeed marketplace and integrates with Lightspeed Restaurant via a real-time API. The setup process is quick, typically complete within one short session. Once connected, Jelly receives item-level sales data the moment each transaction completes in Lightspeed, which feeds the Flash Report, Price Alerts and Sales Mix automatically.

Will connecting OpenTable to Lightspeed affect how Jelly receives sales data?

No. Jelly connects directly to Lightspeed at the POS level, not to OpenTable. The OpenTable–Lightspeed integration handles reservation and cover data. Jelly handles the sales and margin layer. The two connections operate independently and complement each other without conflict.

How does Jelly handle VAT when pulling sales data from Lightspeed?

Jelly reads the sales figures as recorded in Lightspeed, including any VAT codes applied at the point of sale. Configure VAT rates correctly in Lightspeed, particularly for deposits received via OpenTable, before connecting Jelly so that GP calculations in the Flash Report reflect accurate net revenue figures.

How long does it take to see profitability data in Jelly after connecting Lightspeed?

Sales data appears in Jelly in real time from the moment the integration connects. GP figures in the Flash Report become meaningful within the first trading day, provided invoices have been uploaded or emailed into Jelly so that ingredient costs are available for the calculation.

Conclusion: Turning Bookings into Protected Margin

Connecting OpenTable to Lightspeed Restaurant (K-series) is a repeatable, eight-step process that removes manual reservation-to-POS workflows, reduces double-bookings and creates a clean stream of item-level sales data. In 2026, that data stream only delivers value when it feeds clear profitability insight.

Jelly connects to Lightspeed in minutes and converts each transaction into live gross-profit visibility, with Flash Reports updated daily, Price Alerts triggered by every invoice change, and Sales Mix analysis that shows exactly which dishes earn their place on the menu. Operators consistently see the admin time savings described earlier and achieve meaningful GP improvements within the first three months.

The integration stack stays straightforward. The profitability gains arrive quickly. Protect your margins from day one and see how Jelly works alongside your Lightspeed setup from the moment the first reservation lands.