Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
Key Takeaways for UK Lightspeed Operators
- Lightspeed has discontinued its native Loyalty module, so UK operators now connect a third-party loyalty app through the Lightspeed marketplace.
- Popular marketplace options include Marsello, 5loyalty, Loyale and Lynked, and each connects via OAuth with multi-location support.
- Integration steps stay simple: log into Lightspeed, install the chosen app from the marketplace, grant permissions, then map revenue categories.
- Common pitfalls such as single-site API keys, legacy menu items and misclassified discounts can be avoided with a short pre-launch checklist.
- Pairing your loyalty app with Jelly turns the same POS data into real-time gross-profit reporting, so you protect margins from day one.
Why Lightspeed Removed Its Native Loyalty Module
Lightspeed discontinued its native Loyalty module as part of a broader platform consolidation. The company shifted toward an open marketplace model where specialist third-party providers handle loyalty, gifting and CRM instead of a single bundled product. Lightspeed issued guidance directing existing Loyalty users to migrate to a marketplace partner. For UK operators, this created a window to select a replacement, complete the technical migration and avoid any gap in customer reward data. The marketplace integrations are faster to configure than the legacy native module, and they give multi-site operators more flexibility.
Comparing Marsello, 5loyalty, Loyale and Lynked for UK Sites
The table below covers four criteria that matter most to UK multi-site operators. All pricing figures are indicative list prices as of June 2026. Confirm current rates directly with each provider before purchasing.
| Provider | Starting Price (per month) | Multi-Location Sync | Online/Offline Parity |
|---|---|---|---|
| Marsello | From $60 USD | Yes, centralised dashboard | Yes, unified earn and burn online and in-venue |
| 5loyalty | £75 | Yes, location-level reporting | Yes, POS and web redemption |
| Loyale | Contact for pricing | Yes, multi-site campaigns | Yes, omnichannel earn and burn |
| Lynked | Contact for pricing | Yes, group-level controls | Yes, digital and in-person |
None of the four providers currently publish a UK allergen-linked rewards feature as a standard offering. If allergen-aware menu personalisation is essential, confirm this directly with your shortlisted provider before committing.
Not sure which loyalty app fits your operation? Book a demo or schedule a chat and a Jelly specialist will walk through the options with you. Once you have selected a provider, the technical connection usually completes in under five minutes, and the steps below show you how.
Connecting a Loyalty App to Lightspeed Restaurant
Lightspeed Restaurant, the cloud-based product used by most UK hospitality operators, supports marketplace integrations through a standard OAuth flow. The steps below apply to all four loyalty providers listed above.
- Log in to your Lightspeed Restaurant back office with an account that has Manager or Owner permissions.
- Navigate to Marketplace and search for your chosen loyalty app, such as Marsello, 5loyalty, Loyale or Lynked.
- Click Install and follow the OAuth prompt to grant the loyalty app read access to transaction data and write access for discount or reward line items.
- Inside the loyalty app dashboard, map your Lightspeed revenue categories, such as food and beverages, to the earn rules you want to apply.
- Run a test transaction on a non-live terminal to confirm points are awarded and that the redemption discount appears correctly on the Lightspeed receipt.
To connect Jelly at the same time, repeat the same Marketplace search for Jelly, click Install and grant identical read permissions. Jelly does not require write access to Lightspeed. It only reads item-level sales data to calculate gross-profit margins.
Connecting a Loyalty App to Lightspeed R-Series
Lightspeed R-Series, the retail-origin product sometimes used by hotel gift shops and hybrid F&B or retail venues, uses a separate API endpoint from Lightspeed Restaurant. The marketplace-style interface looks similar, but two important differences affect setup.
- Log in to your Lightspeed R-Series back office. Confirm you are in the R-Series environment, not the Restaurant environment, by checking that the URL path includes /retail/.
- Navigate to Apps, not Marketplace, and search for your loyalty provider. Not all four providers listed above are available on R-Series, so verify compatibility on the provider documentation before you start.
- Complete the OAuth grant as above. R-Series uses a product-based data model rather than a menu-item model, so map your loyalty earn rules to R-Series product categories instead of Restaurant menu categories.
- If you run a hybrid site that uses R-Series for retail and Restaurant for F&B, set up two separate loyalty app connections, one per Lightspeed environment. Confirm with your loyalty provider that their platform supports dual-environment accounts under a single brand.
- For Jelly, the connection process on R-Series follows the same quick flow described above. Open Jelly, click Integrations, sign in to Lightspeed, grant permissions and select which product categories to sync. Jelly flags upfront if the account lacks admin access, which is the most common friction point.
Common Multi-Location and Shopify Integration Pitfalls
UK operators running two or more sites, or combining Lightspeed with a Shopify online ordering channel, tend to hit the same issues during loyalty migration. Use the checklist below to avoid the most frequent problems.
- Single-site API keys used across multiple locations. Each Lightspeed business location requires its own API credential, because Lightspeed uses the key to identify which site generated each transaction. Using one key for all sites causes transaction data to merge under a single location ID, which breaks both loyalty earn calculations and Jelly per-site GP reporting. Generate a separate key for every location to keep attribution accurate.
- Legacy menu items polluting the data feed. Jelly POS-to-dish linking only surfaces items sold after the integration connects, which keeps the mapping clean. Many loyalty apps also pull historical SKUs, so archive discontinued menu items in Lightspeed before connecting a new loyalty app.
- Shopify and Lightspeed running separate loyalty instances. If you use Lightspeed in-venue and Shopify for online orders, confirm your loyalty provider supports a unified member wallet across both channels. Without this, customers build two separate point balances and redemption becomes inconsistent.
- Discount line items misclassified as revenue. When a loyalty redemption applies a discount in Lightspeed, some configurations post it as a negative revenue line instead of a discount category. This inflates your net sales figure and distorts Jelly Flash Reports. Set loyalty discounts as a dedicated Lightspeed discount type, not a product override.
- Insufficient permissions at go-live. Both the loyalty app and Jelly require Manager or Owner-level Lightspeed credentials during initial setup. Installation attempts with a staff-level account often fail and delay launch.
How Jelly Uses Loyalty Data for Real-Time Margin Protection
Once your loyalty app and Jelly both connect to Lightspeed, the data flow runs automatically. Every time a transaction completes at the POS, including loyalty redemptions, the Lightspeed API sends Jelly item-level sales data. Jelly maps each POS item to a costed dish in its Kitchen section, where ingredient costs stay updated from scanned supplier invoices.
This connection produces three live reports that protect margins in real time.
- Flash Report. View daily, weekly or monthly gross-profit margin calculated from actual invoice costs and actual POS sales. Loyalty redemption discounts appear as a separate line, so you can see their precise GP impact without manual reconciliation.
- Price Alert. Track every ingredient price movement from supplier invoices. If a loyalty promotion drives volume on a dish whose ingredient costs have just risen, Price Alert highlights the conflict immediately.
- Sales Mix. See which dishes are most popular and most profitable. Many operators run loyalty double-points promotions on low-margin dishes, and Sales Mix makes this risk visible before it compounds.
Across Jelly customers, operators consistently see an average two percentage-point GP lift within the first three months. One head chef at a UK hotel reported a five percent food cost reduction within a month of connecting Jelly, thanks to live dish costs. Another independent pub operator moved from a projected 60 percent gross profit to 80 percent after implementation and now reviews margins in Jelly instead of waiting for month-end accounts.
Frequently Asked Questions
Who owns the customer data collected by a third-party loyalty app connected to Lightspeed?
The operator owns the customer data. Third-party loyalty apps act as data processors under UK GDPR, which means they handle data on your behalf and under your instructions. You should confirm this in the data processing agreement provided by your chosen loyalty provider before go-live. Jelly does not collect or store customer identity data. It only processes anonymised item-level sales figures from Lightspeed to calculate costs and margins.
How quickly does loyalty transaction data appear in Jelly Flash Reports?
Jelly receives item-level sales data from Lightspeed in real time through the API, usually within seconds of a transaction completing at the POS. The Flash Report updates continuously throughout the day, with no batch processing or overnight delay. If Lightspeed experiences an API outage, transactions queue and sync automatically once connectivity returns.
How should I map loyalty discount line items to the correct category in Jelly?
During the initial POS-to-dish linking step in Jelly, you select which Lightspeed categories to sync, such as food and beverages. Configure loyalty discounts in Lightspeed as a dedicated discount type rather than a product category. This setup ensures they appear as a cost line in Jelly reporting instead of being subtracted from gross sales, which gives you an accurate view of revenue and the cost of your loyalty programme. If you have already connected Jelly and find discounts misclassified, update the discount type in Lightspeed and the correction will flow through on the next transaction cycle.
Can Jelly cost a delivery menu that includes loyalty-discounted items?
Yes. The Jelly Kitchen section includes a Delivery Menu Creation feature that lets you duplicate existing menu items and layer in delivery commission overheads, such as the percentage charged by Deliveroo or Uber Eats. This produces a separate, accurately costed delivery menu. If a loyalty promotion applies to items that also appear on your delivery menu, you can model the combined impact of the commission and the discount against live ingredient costs before launch.
Next Steps for Replacing Lightspeed Loyalty and Protecting Margins
Replacing Lightspeed Loyalty has two stages. First, select and connect the right third-party app for your customer programme. Second, ensure the resulting sales data feeds directly into a margin-protection layer. The loyalty apps covered in this guide, Marsello, 5loyalty, Loyale and Lynked, each connect to Lightspeed Restaurant and, where compatible, Lightspeed R-Series using the same OAuth process. Jelly connects through the same approach and immediately begins converting that POS data into live Flash Reports, Price Alerts and Sales Mix analysis.
Operators who complete both stages gain a single, automated view of how every loyalty promotion affects gross profit, without waiting for a monthly accountant report. At £129 per location per month with no per-user fees, Jelly adds the margin intelligence that loyalty apps alone do not provide.