Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
Key Takeaways for Lightspeed and Kitchen CUT
- The Lightspeed–Kitchen CUT integration syncs menu items and sales data, while ingredient costs stay static until someone updates them manually.
- Initial setup requires manual mapping of each Lightspeed item to a Kitchen CUT recipe, which can take several hours to a full day.
- Recipe costs do not update automatically when supplier prices change, so reported GP figures can drift away from reality quickly.
- Operators still handle manual invoice entry and recipe maintenance, which creates recurring admin time and ongoing risk of data drift.
- For live invoice capture, automatic cost updates and supplier price alerts, book a demo with Jelly to see the workflow in practice.
Setup Time for the Lightspeed and Kitchen CUT Connection
Setup for the Lightspeed–Kitchen CUT integration follows a three-step process. A Kitchen CUT account must be active and already populated with your recipe library. Lightspeed menu items are then mapped to Kitchen CUT recipes, with each POS item matched manually to its recipe. Sales data begins flowing only after the connection is authorised and mapping is complete.
For a site with a mid-sized menu of 40 to 80 items, this mapping usually takes several hours and can stretch to a full day, depending on how complete and tidy the recipe library is. Lightspeed’s K-Series architecture, updated through 2025 and 2026, supports third-party API connections through its developer platform, which provides a stable data layer for integrations of this type. Any menu change in Lightspeed, such as new dishes, renamed items or seasonal updates, then requires fresh mapping in Kitchen CUT to keep the integration aligned.
Ongoing maintenance becomes a recurring administrative task tied directly to how often the menu changes. Teams with frequent menu updates face a steady stream of mapping work.
Assess your current workflow maturity and decide whether your team has the capacity to maintain menu mapping every time the menu changes.
Ongoing Costs for Lightspeed and Kitchen CUT
Kitchen CUT operates on a subscription model with pricing tailored to site count and feature tier. UK pricing is not published as a flat rate, and multi-site operators see costs scale per location. There are no public per-user fees, although enterprise tiers with dedicated support usually carry higher monthly commitments.
Lightspeed charges separately, so operators pay for both platforms plus any implementation or onboarding support. For a single-site operator, the combined monthly spend can feel high compared with the admin time saved, especially when recipe costs still rely on manual updates.
Jelly charges a flat £129 per month per location, with no extra fees per user or feature.
Assess your current workflow maturity and calculate the total monthly cost of your costing stack, including staff time spent on manual updates.
Operational Limits of the Lightspeed Kitchen CUT Integration
The Lightspeed–Kitchen CUT integration delivers menu syncing and sales-based GP tracking, but it does not address invoice capture or live costing. The table below summarises the main operational limits.
| Area | Lightspeed–Kitchen CUT | Impact on Operations |
|---|---|---|
| Invoice capture | Manual entry required | Staff time, higher risk of data entry errors |
| Ingredient cost updates | Static until manually updated | Recipe GP figures become inaccurate after any supplier price change |
| Real-time margin visibility | Not available, GP is theoretical based on last-set costs | Slower reaction to margin erosion |
| Supplier price alerts | Not included | Price creep goes undetected between manual reviews |
This setup shows what you sold and what it theoretically cost, but not what it actually costs today with current supplier pricing.
Assess your current workflow maturity and track how many days pass between a supplier price increase and the moment it appears in your dish costings.
Kitchen CUT and Jelly Compared for Lightspeed Operators
This comparison table sets Kitchen CUT (used alongside Lightspeed) against Jelly’s native Lightspeed integration on the metrics that matter most to finance-focused operators.
| Feature | Kitchen CUT + Lightspeed | Jelly + Lightspeed |
|---|---|---|
| Invoice capture | Manual entry | Automated scan from email or photo |
| Ingredient cost updates | Manual and static | Live, updated on every invoice |
| Lightspeed connection setup | Multi-step mapping, hours to days | API connection in about 5 minutes |
| Supplier price alerts | Not included | Included, flags every price movement |
Jelly appears on the Lightspeed marketplace, and the POS connection follows a single guided flow inside Jelly. You open Jelly, click Integrations, sign in to Lightspeed, grant permissions and select categories to sync. Jelly customers see an average GP improvement of 2 percentage points within the first three months. One operator moved from 65 percent to 72 percent GP within 12 weeks on approximately £500,000 in revenue.
See the Lightspeed integration in action and walk through the five-minute setup and live invoice scanning.
Assess your current workflow maturity and confirm whether your current integration gives you live margins or only theoretical ones.
Migrating from Kitchen CUT to Jelly While Keeping Lightspeed
Migration from Kitchen CUT to Jelly keeps Lightspeed in place, so the POS remains unchanged. The migration follows three practical steps.
You first export your existing recipe library from Kitchen CUT. Jelly’s onboarding team then supports data mapping so recipes can be rebuilt against ingredients already populated from scanned invoices. You next connect Lightspeed to Jelly through the same five-minute API flow described earlier. Finally, you begin forwarding supplier invoices to your Jelly inbox or photographing them into the platform, and ingredient costs start populating automatically.
Downtime stays low because Jelly only surfaces POS items sold after the integration connects, which keeps the dish-mapping process clean and free from legacy menu clutter. Most operators generate live GP data within their first week.
Assess your current workflow maturity and check whether your recipe library is documented clearly enough to migrate cleanly, or whether it still lives across spreadsheets and individual knowledge.
Common Problems with Static Costing Integrations
Static integrations that sync menu structure and sales while leaving cost data manual create three recurring operational problems.
Spreadsheet drift. Recipe costs set at menu launch start to diverge from reality within weeks. Ingredient prices move constantly. Without automated invoice capture feeding live cost updates, the GP figure in any costing tool becomes less accurate over time.
Delayed financial visibility. Operators who rely on monthly accountant reports or weekly manual reconciliations cannot react to margin erosion quickly. By the time a problem appears in a report, it has already cost money. Jelly’s Flash Report delivers daily GP visibility by combining invoice costs with Lightspeed sales data automatically.
Chef resistance to admin. Head chefs and kitchen teams are hired to cook and run service, not to update spreadsheets. Asking them to re-enter invoice prices or update recipe costs by hand creates friction, errors and eventual abandonment of the system. Automation removes the dependency on chef admin entirely.
See how Jelly removes manual admin by automating invoice entry and recipe updates across the costing workflow.
Assess your current workflow maturity and estimate how much of your costing accuracy depends on a specific person completing a manual task each week.
Conclusion: Choosing a Lightspeed Costing Tool That Protects Margin
When evaluating any Lightspeed-connected costing tool, focus on criteria that directly protect your margins in real time. The most important factor is whether the tool updates ingredient costs automatically when invoices arrive, because without this your GP figures will always lag behind reality. Real-time supplier price alerts matter just as much, since they allow you to react to price changes before margin erosion compounds. Connection speed and simplicity also count, because a tool that connects to Lightspeed in under ten minutes without specialist support reduces rollout friction. Pricing should stay predictable and proportionate to the admin time and margin protection the tool delivers.
The Lightspeed–Kitchen CUT integration provides clear value for menu syncing and theoretical GP tracking. Its limits are equally clear: manual invoice entry, static recipe costs and no supplier price alerts. For operators who rely on live data for margin accuracy, these limits translate into real financial risk.
Jelly connects to Lightspeed in about five minutes, automates invoice capture from day one and delivers live dish margins and supplier price alerts without ongoing manual input. At £129 per month per location, pricing stays fixed and transparent.
Ready to see live GP visibility in your own operation? Book a demo to walk through your Lightspeed setup and see how Jelly connects.
Frequently Asked Questions
Does the Lightspeed Kitchen CUT integration update dish costs automatically when supplier prices change?
No. The Lightspeed–Kitchen CUT integration syncs menu items and sales data between the two platforms, while ingredient costs within Kitchen CUT recipes stay unchanged until someone edits them. A team member must update the relevant ingredient costs in Kitchen CUT whenever a supplier invoice arrives with new prices. During periods of frequent price movement, which is now standard for UK hospitality operators in 2025 and 2026, GP data in Kitchen CUT can lag behind reality by days or weeks. Jelly addresses this by scanning every invoice line item automatically and updating live dish costs as soon as a new invoice is processed.
How does Jelly’s Lightspeed integration compare to Kitchen CUT’s for setup time?
Jelly’s Lightspeed integration is designed to complete in about five minutes. The process follows a single guided flow where you sign in to Lightspeed, grant permissions and select which POS categories to sync, with no specialist technical support required. Kitchen CUT’s integration with Lightspeed involves a more involved setup, because menu items from Lightspeed must be mapped manually to recipes in Kitchen CUT, which for a menu of 40 to 80 items can take several hours to a full day. Any later menu change in Lightspeed then requires re-mapping to keep the integration accurate. Jelly avoids legacy clutter by only surfacing items sold after the integration connects.
Can I keep using Lightspeed if I switch from Kitchen CUT to Jelly?
Yes. Jelly connects to Lightspeed independently of any other platform, so switching from Kitchen CUT to Jelly does not require changes to your Lightspeed setup. The migration involves exporting your existing recipe library from Kitchen CUT, rebuilding recipes in Jelly against ingredients populated from scanned invoices and connecting Lightspeed through Jelly’s guided API flow. Lightspeed continues to operate as before, and Jelly is listed on the Lightspeed marketplace so the two platforms are designed to work together.
What does Jelly cost compared with Kitchen CUT for a UK operator?
Jelly charges a flat rate of £129 per month per location, with no variable fees per user or feature. Kitchen CUT’s UK pricing is not published at a standard rate and is usually quoted based on site count and feature requirements, with enterprise tiers carrying higher monthly costs. When comparing total cost of ownership, operators should factor in staff time, because manual invoice entry and recipe cost updates in Kitchen CUT create a recurring admin burden that Jelly removes through automation. Jelly customers typically save 10 to 20 hours of admin per month.
How quickly can I expect to see GP improvements after connecting Jelly to Lightspeed?
Most Jelly customers begin generating live GP data within their first week, once supplier invoices start flowing into the platform. The Price Alert feature activates immediately and flags every ingredient price movement from the first processed invoice. In terms of measurable GP improvement, most customers see the uplift described earlier within their first three months, once invoice automation and price alerts are fully active. Some operators also report monthly savings of several thousand pounds through faster reactions to supplier price changes and tighter menu cost controls.