Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
As of June 2026, no native integration exists between Lightspeed Restaurant POS and ResDiary. Connecting the two systems requires a middleware layer that maps reservation data, such as covers, deposits and prepayments, to POS transaction records. The goal is a single automated data flow that removes manual re-entry and gives you live spend visibility for every booking.
The 7-Step Checklist at a Glance
- Confirm API access on both Lightspeed and ResDiary accounts
- Select and configure a middleware tool (for example Zapier, Make, or a dedicated hospitality iPaaS)
- Map ResDiary booking fields to Lightspeed table and cover data
- Configure deposit and prepayment handling with correct VAT codes
- Enable live spend sync so POS sales post against the open reservation
- Run end-to-end tests with live and sandbox bookings
- Connect Lightspeed to Jelly for real-time menu profitability on the synced sales data
Key Takeaways for Lightspeed and ResDiary Users
- UK restaurants using Lightspeed and ResDiary must rely on middleware to bridge the lack of native integration, which can remove 10–20 hours of weekly manual data entry.
- This seven-step checklist covers API access, middleware configuration, field mapping, VAT-compliant deposit handling, live spend sync, testing and Jelly integration.
- Correct VAT code mapping on deposits is essential for HMRC compliance, because leaving fields blank can create discrepancies in VAT returns.
- Once synced, Jelly ingests real-time Lightspeed sales data and delivers live dish-level gross profit, Price Alerts and Flash Reports without spreadsheets.
- Connect Lightspeed to Jelly today to turn synced reservation and sales data into actionable, same-day margin visibility.
Before You Begin: Access, Accounts and VAT Details
Confirm these prerequisites before you start the technical setup. When everything is ready, the initial configuration usually takes under 60 minutes.
- Lightspeed account role: You need Owner or Manager-level access to generate API credentials. Lightspeed Restaurant operates on two architectures, K-Series (the legacy on-premise-adjacent stack) and L-Series. Both Lightspeed O-Series and K-Series use OAuth 2.0 for API authentication, but they use different endpoint URLs and token handling. Because the middleware configuration depends on the correct series, confirm which version your venue runs before you proceed.
- ResDiary account role: You need Administrator access to reach the ResDiary API settings and generate a client ID and secret.
- Middleware account: You need a Zapier, Make (formerly Integromat), or hospitality-specific iPaaS account on a plan that supports webhook triggers and multi-step automations.
- VAT registration details: Keep your VAT registration and tax codes to hand so you can map deposits correctly in Step 4.
Why Lightspeed–ResDiary Sync Affects Margin and Compliance
Manual booking-to-POS entry creates a margin visibility problem, not just a time drain. When reservation data and sales data sit in separate systems, gross profit figures always arrive late. By the time a finance manager reconciles the two, supplier prices may have already moved and the chance to negotiate credits has passed.
Two UK-specific compliance points also apply. Under HMRC rules, deposits collected at the point of booking are treated as advance payments and are liable for VAT at the point of receipt, not at the point of dining. Any middleware mapping deposits from ResDiary to Lightspeed must therefore apply the correct VAT code when it creates the deposit record in the POS. Syncing customer names, email addresses and booking history between platforms also counts as personal data processing under UK GDPR. Lightspeed acts as a data processor and your venue is the data controller. Check that your privacy notice covers POS-to-reservation data sharing and that any middleware provider appears as a sub-processor in your data processing agreements.
Step-by-Step Process to Connect ResDiary and Lightspeed
Step 1 — Confirm API Access
Log in to Lightspeed with Owner credentials. For O-Series, go to Account, then API Access, and create a new OAuth application, then note the client ID and secret. For K-Series, go to Configuration, then API, and copy the static key. In ResDiary, go to Admin, then API Settings, and generate a client ID and secret. Store all credentials in a password manager before you continue.
Step 2 — Configure Your Middleware Tool
Create a new automation in your chosen middleware platform. Set the trigger to a new or updated booking event in ResDiary, using its webhook or polling connector. Set the action to create or update a reservation or table record in Lightspeed through its REST API.
Step 3 — Map Booking Fields Between ResDiary and Lightspeed
Match ResDiary fields to their Lightspeed equivalents so bookings stay aligned. Map booking reference to POS order reference, covers to guest count, table ID to Lightspeed table number, and arrival time to reservation start time. Mismatched table IDs are the most common cause of duplicate bookings. Standardise table naming conventions in both platforms before you save the field map.
Step 4 — Configure Deposit and Prepayment Handling for VAT
When ResDiary records a deposit, the middleware must post a matching payment line to the Lightspeed order with the correct VAT code. The rate depends on what the deposit covers. For standard-rated food and drink, apply the 20% VAT code. For zero-rated items, apply the 0% code. Do not leave the VAT field blank, because Lightspeed will default to no-tax and that behaviour creates discrepancies in your VAT return. Map prepayments for set menus as partial payments against the open order, not as separate orders, so reporting stays accurate.
Step 5 — Enable Live Spend Sync Back to ResDiary
Set up a second automation that runs each time a POS order linked to a reservation is updated. Configure this automation to post the running spend total back to the ResDiary booking record. Front-of-house staff then see live spend for each table without leaving the reservations screen.
Step 6 — Test the End-to-End Flow
Create a test booking in ResDiary and confirm that it appears in Lightspeed within your target latency, which is typically under 60 seconds for webhook-based middleware. Process a test payment in Lightspeed and confirm that the spend figure updates in ResDiary. Test a deposit scenario and verify that the VAT code is correct in the Lightspeed order. Log all results and fix any issues before you go live.
Step 7 — Connect Lightspeed to Jelly for Profitability Insights
With reservation and sales data now syncing between ResDiary and Lightspeed, the next step is to turn that data into clear profitability insights. Open Jelly, click Integrations, sign in to Lightspeed and grant permissions. The setup usually takes under five minutes. Jelly then ingests item-level sales data in real time, matches each POS item to a costed dish in your Jelly Cookbook, and surfaces live gross profit margins, Price Alerts and Flash Reports, all without further manual input.
Schedule a live walkthrough of Jelly’s Lightspeed integration to see the setup in action.
Common Mistakes and Troubleshooting for Your Integration
| Symptom | Likely Cause | Fix |
|---|---|---|
| Duplicate bookings in Lightspeed | Middleware firing on both “created” and “updated” ResDiary events | Filter the trigger to “created” only, or add a deduplication step using booking reference |
| Deposits posting with no VAT | VAT code field left blank in middleware field map | Hard-code the VAT code in the middleware action step |
| Sync fails after Lightspeed update | O-Series OAuth token expired | Enable token refresh in the middleware configuration |
| Missing line items in Jelly | POS category not selected during Jelly integration setup | Return to Jelly Integrations, edit the Lightspeed connection and include all relevant categories |
| Table IDs not matching | Table names differ between ResDiary and Lightspeed | Standardise table naming in both platforms, then re-run the field map |
| K-Series vs O-Series API errors | Using O-Series endpoint URLs with a K-Series account | Confirm your series in Lightspeed Account settings and use the correct base URL for that series |
How to Measure Success After Go-Live
Track three metrics in the first four weeks after go-live to confirm that the integration delivers both operational efficiency and financial visibility. First, measure manual re-entry hours, because the target is zero hours spent transferring booking data between platforms. That time saving only matters if the data is accurate, which makes GP accuracy the second metric. Flash Reports in Jelly should reflect actual sales within the same trading day, not the following week. Finally, measure Price Alert response time. With Jelly scanning every invoice line item, price increases from suppliers should trigger an alert within 24 hours of the invoice arriving, giving chefs and operations managers time to negotiate credits or adjust menu pricing before the next service.
Advanced Tips for Multi-Site Groups and Xero Users
Multi-site operators should replicate the middleware automation for each venue rather than building a single multi-branch flow. This approach isolates failures to one site and makes debugging faster. Each Jelly location connects independently to its own Lightspeed account, so GP reporting remains site-specific while the owner or finance manager still sees a consolidated view.
To extend the data flow further, use Jelly’s one-click Xero integration to push digitised invoices directly into your accounting software. This setup closes the loop from reservation deposit through to supplier invoice reconciliation with no manual touchpoints. No reduction in bookkeeping time is reported for Jelly users using Xero integration.
FAQ
Does ResDiary have a direct integration with Lightspeed in 2026?
No. The two platforms require middleware to connect, using tools such as Zapier or Make to pass booking, deposit and spend data between their APIs. This guide explains the full setup process.
What is the difference between Lightspeed K-Series and O-Series for this integration?
Lightspeed Restaurant K-Series APIs use OAuth2 authentication with access tokens that have a limited lifespan and expire. K-Series and O-Series both use OAuth 2.0, as noted in the prerequisites, but they differ in token lifespan and refresh requirements. O-Series tokens expire and must be refreshed periodically, which is why the middleware needs a token refresh mechanism to prevent sync failures. The API endpoint URLs also differ between the two series, so confirm which version your venue runs before you configure the middleware connection.
How are deposits handled for UK VAT purposes when syncing ResDiary to Lightspeed?
Deposits count as advance payments under HMRC rules, so VAT is due at the time of receipt, as explained in the compliance section above. When the middleware posts a deposit from ResDiary to a Lightspeed order, it must apply the correct VAT code at that point. Leaving the VAT field blank causes Lightspeed to record the deposit as tax-free, which creates discrepancies in your VAT return. Always hard-code the appropriate VAT rate in the middleware field map for deposit transactions.
How often does data sync between the systems, and who owns the data?
Sync frequency depends on the middleware configuration. Webhook-based triggers usually deliver data within 60 seconds of a booking event. Polling-based setups check for changes at intervals you define. Your venue is the data controller for all customer and transaction data passing between ResDiary, Lightspeed and any middleware tool. Lightspeed acts as a data processor. Any middleware provider must appear as a sub-processor in your data processing agreements to remain compliant with UK GDPR.
What does Jelly do with the Lightspeed data once the sync is live?
Jelly ingests item-level sales data from Lightspeed in real time through a direct API integration. Each POS item is mapped to a costed dish in Jelly’s Cookbook, where ingredient costs update automatically every time a new supplier invoice is scanned. This setup produces a live gross profit margin for every dish on the menu, a daily Flash Report showing overall GP, and Price Alerts that flag ingredient cost changes as soon as a new invoice arrives. Setup usually takes under five minutes and requires no manual data entry after the initial dish mapping.
Conclusion: Turning Synced Data into Same-Day Decisions
Connecting Lightspeed and ResDiary is a configuration project, not a roadblock. A correctly built middleware flow delivers automated seating, accurate deposit handling with the right VAT codes and live spend data, all without manual re-entry. Once that data flows reliably into Lightspeed, Jelly turns it into the margin visibility that operations managers, finance managers and head chefs need to make decisions the same day, not the same month.
The operators seeing the strongest results, such as Amber Restaurant saving £3,000–£4,000 per month or The Howard Arms reaching 80% gross profit, are the ones who closed the gap between their systems and their profitability data. This seven-step process provides the foundation. Jelly adds the profitability layer on top.
Book a demo to see how Jelly works with your Lightspeed setup and delivers real-time menu profitability from day one.