Written by: JJ Tan, Founder, Jelly | Last updated: 7 November 2026
Key Takeaways
- Lightspeed splits support across separate help centres by product line (K-Series, O-Series, R-Series, Ecom), so identifying your series first prevents being bounced between teams.
- For partner-built connectors, the integration provider owns the connection, so always check the partner’s marketplace listing before raising a ticket.
- While waiting for support, operators lose live margin visibility, which is costly given how many UK restaurateurs rank profitability as their top concern.
- Jelly connects to Lightspeed Restaurant (K-Series) in about five minutes via the marketplace and delivers live dish-level gross profit without a support queue.
- Jelly is the fastest route from a broken Lightspeed integration to working margin reports for UK operators who need live data now.
Skip the support queue — see live margins
Route Your Lightspeed Integration Issue By Product Line
The single most common reason operators spend a day being bounced between Lightspeed and a third party is that they open a ticket with the wrong party. The routing depends entirely on which Lightspeed product line you run. The breakdown below maps each series to its typical integration failure and the party you should contact first.
- K-Series (Lightspeed Restaurant). Typical problems include unprovisioned API credentials, financial data not syncing and OAuth errors. Go first to your Lightspeed Account Manager for API access, or kseries.api@lightspeedhq.com for issues with an existing API client.
- O-Series (Restaurant Legacy/Kounta). Typical problems include OAuth token expiry and developer credential setup. Go first to the O-Series developer documentation, then the O-Series back office for OAuth credentials.
- R-Series (Lightspeed Retail). Typical problems include a third-party connector not syncing or a partner app not connecting. Go first to the integration provider. R-Series partner integrations are supported by the provider rather than by Lightspeed, so check the partner’s marketplace listing for contact details.
- Ecom. Typical problems include online store sync failure and inventory not updating. Go first to Lightspeed support via in-app chat or +44 20 3695 9599, then confirm whether the connector is Lightspeed-native or partner-built.
Before opening any ticket, identify your product line. The help centre, the API route and the responsible support party all differ by series. Operators who skip this step are the ones who spend a day being redirected.
The Official Lightspeed Integration Support Channels For Each Series
Once you know your product line, the next step is choosing the right official channel. Lightspeed documents several contact routes, and you only need the ones that match your series, so save those into your support notes today.
In-App Text Chat. For Lightspeed Restaurant (K-Series), 24/7 live text-based chat support is available in all languages from the Back Office by clicking Help and selecting Chat with support. Other Lightspeed products have more limited chat hours. For example, O-Series chat runs 6 AM to midnight AEST.
UK Phone Number. +44 20 3695 9599 is the number Lightspeed publishes across its UK pages, including its partner and product pages. It appears alongside the advertised 24/7 support for Lightspeed Payments. Use it for account-level issues, billing queries and hardware problems on any product line.
Remote Access Code Path. On Lightspeed Restaurant POS, navigate to POS Settings > Support to generate a 6-digit remote access code. Give this code to the support agent so they can view your session directly. This avoids lengthy back-and-forth descriptions of the problem.
K-Series API Support Email. For issues with an existing K-Series API client, such as adding a redirect URI, kseries.api@lightspeedhq.com is the documented route. Quote your Client ID in the first line. Provisioning a new K-Series API client sits with your Lightspeed Account Manager, and setup can take up to 48 hours.
O-Series Developer Documentation. The O-Series developer portal at o-series-support.lightspeedhq.com covers OAuth 2.0 setup and the “Developers: Create Your First Add-On” guide. OAuth credentials for O-Series are created inside the back office and require Developer or Partner-level permissions.
Integration Hub. The Lightspeed UK integrations directory lists third-party integrations with their compatible product line, and each partner entry includes the partner’s website link and contact email. This directory is the correct starting point for any third-party connector issue.
Who Actually Supports A Third-Party Lightspeed Integration?
Support ownership for third-party integrations causes most of the redirection pain. The answer depends on which product line you run and who built the connector.
Lightspeed’s UK integrations directory describes each listed integration as a service provided by an integrated partner. For R-Series in particular, third-party integrations are supported by the integration provider rather than by Lightspeed, which explains the redirect from Lightspeed support. The same principle applies to any partner-built connector on any product line. Lightspeed supports the POS, the API connection and the account. The partner supports the connector itself, including the mapping, the sync logic and the credentials on their side.
The practical escalation path is:
- Identify the integration provider, which is the named partner on the Lightspeed marketplace listing.
- Check whether the integration is marketplace-listed. If it is, the listing publishes the partner’s contact route. Lightspeed’s eviivo listing is a documented example and names eviivo’s support email as the contact route for partner-side issues.
- Raise the ticket with the party that owns the broken layer. When the Lightspeed POS is processing sales normally but the data does not reach the third-party tool, the fault usually sits on the partner side.
Before re-opening a Lightspeed ticket, check the partner’s listing on the Lightspeed marketplace and confirm you are contacting the party that owns the connection. For further context on how third-party connectors behave in practice, the Lightspeed POS Third-Party Integrations: A UK Guide covers the integration ecosystem in detail.
Does Lightspeed Have An API?
If you have confirmed the connector is partner-owned and still need to know whether you can build your own route, the answer depends on your product line and tier. K-Series exposes a documented REST API using OAuth 2.0, covering orders, financial data, items, allergens and reservations. However, K-Series custom API access is a paid add-on requested through your Lightspeed Account Manager. It is not self-serve for merchants. Once approved, Lightspeed provisions a Client ID and Client Secret. The dedicated K-Series API support email is kseries.api@lightspeedhq.com.
For O-Series, OAuth credentials are created inside the back office and require Developer or Partner-level permissions. For Lightspeed Restaurant more broadly, raw API access is restricted to the Premium tier, listed at $399/month (USD). Operators on Starter or Essential plans are therefore limited to pre-built connectors. Publishing a Marketplace add-on requires Developer Certification and Partnerships review regardless of product line.
Confirm which Lightspeed product line and tier you are on before requesting API access. The answer determines both the route and the cost.
What To Do While You Wait For Lightspeed Integration Support
A stalled integration costs real money. 48% of UK restaurateurs say improving profitability is the biggest issue on their minds, and a broken POS-to-margin connection means pricing decisions rely on last month’s numbers. Every day without live sales data brings blind margins, delayed gross profit visibility and supplier negotiations without evidence.
For operators whose real need is margin and cost visibility rather than the specific connector, Jelly is listed on the Lightspeed marketplace and connects in approximately five minutes. The connection flow is:
- Open Jelly and click Integrations.
- Sign in to your Lightspeed account.
- Grant permissions.
- Select which POS categories to sync, such as food and beverages.
Two things often trip people up during setup. The first is permissions: you need admin access to your Lightspeed account, and Jelly flags this before you start if it is missing. The second is scope: POS-to-dish linking only surfaces items sold since the connection date, which keeps the mapping clean of legacy menu clutter but means you will not see historical dishes. For a full walkthrough of the setup process, the Lightspeed Restaurant Integration: Complete Setup Guide covers every step.
Once connected, Lightspeed sales flow into Jelly’s Flash Report as live dish-level gross profit. Ingredient costs update with every new invoice scan, so the GP margin for every dish stays current. Connecting a POS automates 2–5 hours of weekly work and delivers real-time margins and sales mix data. Lightspeed remains the POS, and Jelly reads its data to produce live margin reporting.
Can I Integrate Shopify And Lightspeed?
Shopify sits in the eCommerce and retail scope, so it is relevant to Lightspeed Retail (R-Series and X-Series) rather than to Lightspeed Restaurant K-Series. However, Lightspeed Restaurant O-Series has its own separate Shopify integration. Lightspeed Retail’s multichannel selling syncs inventory across in-store, ecommerce and social selling channels, and Shopify connectivity sits within that retail scope. If you run Lightspeed Restaurant K-Series, a Shopify integration does not apply to your product line and will not resolve a restaurant data or margin problem.
If you run Lightspeed Restaurant K-Series and are chasing a Shopify connection, route your issue using the product-line breakdown above instead. For everyone else, the wait for a working connection is often the real problem, and the next section focuses on how to handle that delay.
When To Stop Troubleshooting And Change Approach
Repeated failures on the same integration signal a decision point. If the same connection has failed several times and the data the business actually needs is margin and cost visibility, removing the dependency is more efficient than re-opening tickets. Toast’s UK POS guide advises operators to ask how many outages a system had in the past year. The same counting logic works for integrations: if you have opened more than two tickets on the same connection, the connection itself is the bottleneck, not the ticket.
Jelly is the Lightspeed marketplace partner that turns POS sales into live dish-level gross profit without a support queue. The outcomes are documented. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue, and Populu lifted GP from 68% to 72% across 16 locations. Jelly onboards and generates initial value in the first week. If you have been troubleshooting the same connection for more than two ticket cycles, connect Lightspeed to Jelly instead. For guidance on what to do when data has already been lost or corrupted during a failed integration, the Lightspeed Integration Troubleshooting: Restore GP Data guide covers the recovery steps.
Conclusion: The Fastest Route To Live Margin Data
The routing rule is simple. Match your product line to the right channel, and when a partner-built connector fails, go to the partner first. Everything else in this guide follows from those two moves.
When the business needs live margin data, Jelly provides a direct route. It is listed on the Lightspeed marketplace, connects in about five minutes via Jelly > Integrations and turns Lightspeed sales into live dish-level gross profit without a support queue. That path is the fastest way to move from a broken integration to a working margin report.
Frequently Asked Questions
Which Lightspeed Product Lines Does Jelly’s Integration Support?
Jelly integrates with Lightspeed Restaurant, specifically the K-Series product, via a real-time API. The integration delivers item-level sales data the moment a transaction completes, which Jelly uses to calculate live dish-level gross profit margins. Jelly does not currently integrate with Lightspeed Retail (R-Series or X-Series) or Lightspeed Ecom.
How Long Does The Lightspeed-To-Jelly Connection Take, And What Access Do I Need?
The connection takes approximately five minutes and follows the four-step flow described above. The only common friction point is admin access to your Lightspeed account, which Jelly flags upfront if it is missing. The connection is user-led, with no separate developer setup described on the Jelly side.
Is Jelly Listed On The Lightspeed Marketplace?
Yes. Jelly is listed on Lightspeed’s integrations marketplace as a partner compatible with Lightspeed Restaurant POS (K-Series), and Lightspeed announced the integration as a new partner in July 2026, indicating it has been through Lightspeed’s partner process. Its listing publishes the contact route for integration support. Lightspeed remains the POS, and Jelly reads its data.
What Happens To Menu Items Sold Before The Integration Was Connected?
POS-to-dish linking in Jelly only surfaces items sold since the integration was connected. Items sold before the connection date are not surfaced, which keeps the mapping clean and free of legacy menu clutter. This behaviour is by design and prevents historical menu data from cluttering current dish costing and GP calculations.
Does Jelly Replace Lightspeed?
Lightspeed remains the POS system, and Jelly reads its sales data via the API. Jelly adds the margin and cost visibility layer, including automated invoice scanning, live dish costing, Flash Reports and Sales Mix, which sits on top of the POS data Lightspeed generates. The two systems work together.
What Should I Do If Lightspeed Support Redirects Me To The Partner?
Raise the ticket with the party that owns the connection. Find the integration provider’s contact details on its Lightspeed marketplace listing, because each listed partner publishes its own support route there. Lightspeed support is correct to redirect you when the POS itself is working.
Does Jelly Work Alongside Other POS Systems?
Yes. In addition to Lightspeed Restaurant, Jelly integrates natively with Square, EPOS Now and Toast via real-time API. Each integration delivers item-level sales data and follows the same five-minute connection flow. Jelly holds marketplace listings or integrations with multiple POS systems, including Square, Lightspeed, ePOSnow and Toast, not Lightspeed alone. Lightspeed remains a key POS partner for Jelly.
