Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
Key Takeaways
- A broken Lightspeed Restaurant integration immediately removes real-time item-level sales data, which makes daily GP figures disappear and pushes finance teams back to manual spreadsheets.
- The most common failure points are expired OAuth tokens, mis-mapped POS categories, insufficient admin permissions, network issues on terminals, and Xero invoice push errors.
- Each issue has a clear resolution path: re-authorise tokens with admin credentials, re-map new or renamed categories, confirm full API scopes, restore network connectivity, and fix duplicate invoice references in Xero.
- Restoring the connection with Jelly automates two to five hours of weekly manual work per site and typically delivers a two-percentage-point GP uplift within the first three months.
- Book a demo with Jelly to reconnect your Lightspeed sales data to live dish costing in minutes, not hours.
The Problem: Lost Real-Time Sales Data from Lightspeed Restaurant
Lightspeed Restaurant is a capable POS platform, and its REST API pushes item-level transaction data to connected platforms in real time. When that connection breaks, the downstream effects compound quickly. Without item-level sales data, costing platforms cannot calculate dish-level gross profit. Finance managers lose their daily Flash report. Executive chefs cannot see which dishes are underperforming. Operations managers are left waiting for a monthly accountant report that arrives too late to act on supplier price movements.
The manual reconciliation burden that follows, such as cross-referencing POS exports against invoice data in spreadsheets, typically consumes two to five hours of additional work per week per site. The root causes of these failures fall into three categories: sales sync failures, terminal connectivity problems, and accounting push errors. Each category has a distinct resolution path.
Lightspeed Not Syncing Sales
A sales sync failure means Lightspeed Restaurant is processing transactions normally at the terminal, but item-level data is not reaching the connected costing or accounting platform.
1. Verify API Credentials and OAuth Token Status
Lightspeed Restaurant uses OAuth 2.0 for third-party authentication. Tokens expire or are invalidated when a Lightspeed account password is changed, when a user role is downgraded, or when the connected application is removed from the Lightspeed account. Navigate to your Lightspeed Restaurant back office, go to Settings, then Integrations, and confirm the connected application still appears with an active status. If it has been removed, re-authorise the integration from the third-party platform.
2. Check POS Category Mapping
Most costing platforms, including Jelly, sync only the POS categories you explicitly select during setup, typically Food and Beverages. If a menu category has been renamed, split, or added in Lightspeed since the integration was first configured, new items in that category will not appear in the connected platform. Review your category list in Lightspeed and re-map any new or renamed categories in the integration settings of your costing tool.
3. Confirm API Permission Scope
The Lightspeed Restaurant API requires specific permission scopes for reading sales data. If the account used to authorise the integration has had its role changed from Manager or Owner to a more restricted role, the API token will silently lose read access to transaction endpoints. Re-authorise the integration using an account with full admin permissions.
Terminal Not Connecting to Lightspeed
A terminal connectivity failure means the Lightspeed Restaurant app on the device cannot communicate with the Lightspeed cloud. This prevents any data, including sales, from reaching connected integrations.
1. Diagnose Network Connectivity
Lightspeed Restaurant requires a stable internet connection to sync transactions to the cloud. Confirm the terminal device has an active connection by opening a browser and loading an external page. If the venue uses a guest Wi-Fi network separate from the POS network, ensure the terminal is connected to the correct SSID. A dedicated wired or 4G backup connection for POS devices is standard practice in multi-cover environments.
2. Confirm Admin Access on the Device
Certain Lightspeed Restaurant configuration changes, including re-linking a terminal to a business location, require admin-level credentials within the app. If a staff member has logged out of the admin session, the terminal may continue processing offline transactions without syncing them. Log back in with owner or manager credentials and force a manual sync from the terminal settings menu.
3. Refresh the API Token on the Integration Side
If the terminal is online and the Lightspeed back office shows normal activity but the connected platform still reports no new data, the issue is likely an expired refresh token on the integration side. In Jelly, navigate to Integrations, then Lightspeed, and use the reconnect flow to generate a fresh token. This process takes under two minutes and does not affect historical data that has already synced.
Xero Invoice Push Failing from Jelly
Jelly pushes digitised invoice data directly to Xero. When this push fails, invoices accumulate in Jelly without reaching the accounting ledger.
1. Check Xero Account Mapping
Each invoice line item must map to a Xero account code. If a new supplier or cost category has been added in Jelly without a corresponding Xero account code assigned, the push will fail silently for that invoice. In Jelly accounting settings, confirm every active supplier category has a valid Xero account code assigned.
2. Verify Xero OAuth Connection Status
Xero OAuth 2.0 access tokens expire every 30 minutes, and refresh tokens remain valid for 30 days. If the Jelly–Xero connection has not been used for an extended period, re-authorise it from the Jelly integrations panel. Xero then prompts a standard login and permission grant flow.
3. Resolve Duplicate Invoice Errors
Xero rejects invoice pushes where the invoice reference number already exists in the ledger. This occurs when an invoice has been entered manually into Xero before Jelly processes it. Identify the duplicate in Xero, void or archive the manual entry, then re-push from Jelly.
Common Lightspeed Error Codes and Resolutions
| Error / Status | Where It Appears | Likely Cause | Resolution |
|---|---|---|---|
| 401 Unauthorised | Integration platform logs | Expired or revoked OAuth token | Re-authorise the integration using a Lightspeed admin account |
| 403 Forbidden | Integration platform logs | Insufficient API permission scope | Upgrade the authorising account role to Owner or Manager in Lightspeed back office |
| 404 Not Found | Integration platform logs | Endpoint URL changed or resource deleted | Check the integration platform for an available update, then re-map deleted menu items |
| 429 Too Many Requests | Integration platform logs | API rate limit exceeded | Contact the integration platform support team to review polling frequency settings |
| Offline / No Sync | Lightspeed terminal | Network loss or admin session timeout | Restore the network connection, log back in with admin credentials, then force a sync |
Jelly Lightspeed Integration Setup and Daily Use
Having covered the common failure points and their resolutions, the next step is preventing these issues through proper initial setup. Jelly is listed on the Lightspeed Restaurant marketplace and operates as a complementary layer alongside the POS. It does not replace Lightspeed or alter how Lightspeed processes transactions.
Setup follows a consistent five-step flow: open Jelly, click Integrations, sign in to Lightspeed, grant permissions, then select which POS categories to sync. The entire process takes approximately five minutes. The only common friction point is insufficient admin access to the Lightspeed account, and Jelly flags this requirement before the authorisation step.
Once connected, Jelly real-time API mapping links each Lightspeed menu item to a costed dish in the Jelly Kitchen section. Only items sold since the integration was connected appear for mapping, which keeps the linking process clean and free of legacy menu clutter. From that point, every completed transaction in Lightspeed updates the Flash Report, Jelly daily, weekly, and monthly gross-profit view, and feeds the Sales Mix report, which shows which dishes are most popular and most profitable at the same time.
The Price Alert feature flags every ingredient price movement from incoming invoices. This gives operators the data to challenge supplier increases in the same week they occur. Book a demo, schedule a chat to see the Lightspeed integration live in a working kitchen environment.
Restored Data Flow: Concrete Operational Benefits
Connecting Lightspeed to Jelly removes hours of manual reconciliation and restores live GP visibility. 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. Cairn Lodge Hotel Head Chef Stuart Noble reduced food costs by 5% within a month of activation.
Across Jelly customer sites, the consistent pattern matches the uplift outlined earlier, supported by these specific case examples. The Price Alert feature provides the supplier negotiation leverage that makes this possible. When an ingredient price increases, the alert surfaces the exact SKU, the previous price, the new price, and the supplier name. That information gives teams enough evidence to request a credit note or switch supplier within the same week.
Comparing Manual Spreadsheets, Legacy Systems and Modern Platforms
Manual spreadsheets remain the most common approach in UK hospitality because they require no software budget and no onboarding. Their limitation is speed. A spreadsheet cost model is only as current as the last time someone updated it, which in a busy kitchen is rarely the same week a supplier changes a price. Costing a single menu item manually takes an average of 28 minutes.
Legacy systems were built for large chains with dedicated back-office teams and carry licensing costs and implementation timelines that reflect that audience. They provide more static reporting than real-time margin visibility. Modern automated platforms connect invoice data, POS sales, and dish costing in a single workflow. The main differences between them are onboarding speed and interface complexity.
Jelly is designed specifically for growing independent operators and multi-site groups up to around five locations. Pricing is a flat rate of £129 per location per month, and onboarding is measured in days rather than months.
Frequently Asked Questions
How long does it take to set up the Jelly–Lightspeed integration?
The connection follows the five-step flow described in the integration section above, taking approximately five minutes from start to finish. Dish mapping, which links each Lightspeed menu item to a costed recipe in Jelly, is an additional step that takes roughly 10 to 20 minutes depending on menu size. Only items sold since the integration was activated appear for mapping, so you avoid working through a full historical menu list.
What level of Lightspeed account access is required?
Administrative access to your Lightspeed Restaurant account is required to authorise the integration. The OAuth flow needs permission to read item-level transaction data. If the person setting up the integration does not have this access, Jelly flags the requirement before the authorisation step so the correct account holder can complete it.
Does Jelly work across multiple Lightspeed sites?
Jelly supports multi-site operators using Lightspeed. Each site is set up as a separate location in Jelly, with its own Lightspeed connection, invoice inbox, and dish cost library. Operators managing two to five sites can view GP performance per location or consolidated across the group from a single Jelly account. Pricing is a flat £129 per location per month with no per-user charges.
Is sales data from Lightspeed stored securely within Jelly?
Jelly processes item-level sales data received via the Lightspeed API and uses it solely to calculate dish-level gross profit margins within your account. Jelly shares customer data with subprocessors such as AWS, Stripe, Postmark and others solely to provide and support the service. The OAuth connection means access is governed by a token that you can revoke at any time from your Lightspeed back office.
What happens to my GP data if the Lightspeed integration drops temporarily?
If the connection is interrupted, for example due to a token expiry, Jelly will not receive sales data for the period the connection is down. Historical data that has already synced remains unaffected. Once the integration is reconnected, Jelly resumes receiving new transaction data from that point forward. For any gap period, Lightspeed reporting can be used to export sales data manually if needed for reconciliation.
Conclusion: Restore Live GP Visibility Today
A broken Lightspeed integration is more than a technical inconvenience. It removes the real-time margin data that operators need to react to supplier price changes, protect dish profitability, and make informed purchasing decisions. The troubleshooting steps above resolve the most common failure points, including expired OAuth tokens, misconfigured category mappings, insufficient admin permissions, and Xero push errors.
Operators who want to move beyond reactive troubleshooting can use Jelly as a complementary integration that keeps Lightspeed sales data permanently connected to live dish costing, automated invoice management, and daily GP reporting. The result is the time savings and margin improvements detailed above, supported by real case studies and live supplier price alerts. Book a demo, schedule a chat and restore real-time GP visibility to your Lightspeed Restaurant operation today.