How to Integrate POS with Inventory for Real-Time Food Costs

Written by: JJ Tan, Founder, Jelly | Last updated: 22 July 2026

Key Takeaways for Jelly POS Integration

• UK operators over £500k revenue lose margin when they rely on outdated spreadsheets that trail real supplier price changes by weeks.
• Connecting POS with inventory through Jelly gives live ingredient costs, automatic recipe mapping and theoretical GP after every sale.
• The six-step workflow covers POS connection, invoice scanning, recipe building, waste logging and weekly Flash Report reviews to keep variance under 3%.
• Operators usually save 2–5 hours weekly on admin and see around a 2-percentage-point GP lift within the first three months.
• See real-time food cost in a Jelly walkthrough and watch live data appear in your account from day one.

Before You Begin: Access, Invoices and Roles

A smooth integration depends on having the right access, documents and responsibilities in place before you connect anything.

POS admin access. Jelly integrates natively with Square, EPOS Now, Lightspeed and Toast via real-time API. Each system sends item-level sales data the moment a transaction completes. The main friction point is insufficient permissions. You need full admin access to your POS account at the start, and Jelly flags this requirement clearly during the connection flow.

Invoice readiness. Supplier invoices form the cost foundation. Set up a simple way to capture them, either by forwarding supplier emails to your dedicated Jelly inbox or photographing paper invoices in the app. Jelly then scans every line item automatically.

Staff roles. Assign responsibility for two ongoing tasks before go-live. Recipe building in the Cookbook needs someone who understands exact ingredient quantities and preparation methods, usually the head chef or sous chef. Daily waste and non-sales movement logging should sit with the kitchen team during service, with a manager reviewing entries weekly so gaps do not distort variance reports.

Confirm your POS compatibility with a Jelly specialist. The conversation takes under 15 minutes and covers all prerequisites.

Why Fast, Accurate Costing Matters Now

UK food price inflation pushes supplier prices up and down week to week, so static spreadsheet recipe costs become outdated within months. A recipe costed in January using January prices is inaccurate by March. Many UK operators have seen food cost increases linked to Brexit-era supply chain disruption, driven by delivery surcharges and the loss of negotiated volume pricing. Supplier price increases not passed to the menu, such as chicken breast rising from $2.80/lb to $3.40/lb, can push food cost percentage upward by 2 percentage points on affected dishes.

Connecting POS with inventory through Jelly turns this volatility into clear, usable data that drives better decisions.

• Manual spreadsheet costing disappears, and work that once needed tedious manual updates now refreshes automatically with every new invoice.
• Price Alert shows supplier price changes as they happen, so you can react before they erode margin.
• Teams reclaim 2–5 hours of weekly admin time that previously went into margin and sales mix reporting.
• Operators typically see an average 2-percentage-point GP lift within the first three months as they act on this data.

The six-step integration checklist below explains the full workflow in detail and shows how each part supports those outcomes.

Walk through the full workflow in a live Jelly account and see how each step looks in practice.

Step-by-Step Process for Connecting Jelly and Your POS

The following sections walk through each of the six steps in the integration checklist.

Step 1: Confirm POS Compatibility and Admin Access

Objective: Confirm that your POS is supported and that you hold the permissions needed to authorise a third-party integration.

Actions: Check that your POS is one of Jelly's four supported systems: Square, EPOS Now, Lightspeed or Toast. Log in to your POS back office and confirm that your account role shows full admin or owner-level permissions. If another team member manages the POS account, request a temporary admin login or ask them to be present for the connection step.

Success criteria: Admin login confirmed and POS version confirmed as supported.

Step 2: Connect the POS Through Jelly

Objective: Create a live API connection so every completed transaction sends item-level sales data to Jelly in real time.

Actions: Open Jelly, go to Integrations, select your POS, sign in using your POS admin credentials, grant the requested permissions and choose which POS categories to sync, such as food, beverages or both. The process is the same across all four supported systems and usually takes only a few minutes.

Success criteria: Jelly's Integrations screen shows the POS as connected, and test transactions appear in the sales feed within minutes.

Step 3: Scan Supplier Invoices for Live Ingredient Costs

Objective: Build a live ingredient price database that updates automatically with every delivery.

Actions: Forward supplier invoice emails to your dedicated Jelly inbox or photograph paper invoices using the Jelly app. Jelly digitises every line item, including quantity, SKU, price and tax, without manual data entry. Instruct your team to capture every invoice at the point of delivery rather than catching up later.

Success criteria: All active suppliers have at least one processed invoice, and the ingredient list in Jelly reflects current delivery prices.

Step 4: Build Digital Recipes and Map Them to POS Items

Objective: Link every dish sold through the POS to its exact ingredient quantities so each sale triggers automatic theoretical cost depletion.

Actions: In Jelly's Kitchen section, open the Cookbook and create a recipe by selecting ingredients already populated from scanned invoices. Jelly handles unit conversions and cost calculations automatically. Start with prep items such as sauces, portioned proteins and pre-cut vegetables, then build finished dish recipes on top of them. When a recipe is complete, map it to the corresponding POS menu item. POS integration reads sales data as transactions occur, and when a dish is sold the system calculates ingredient consumption based on the recipe and deducts it from theoretical stock. Jelly only shows POS items sold since the integration went live, which keeps the mapping list clear of legacy menu clutter.

Success criteria: Every active menu item has a mapped recipe, and live dish GP% is visible in the Cookbook with no unmapped items left.

Step 5: Record Waste, Staff Meals and Other Non-Sales Movements

Objective: Capture every inventory deduction that does not come from a POS sale so theoretical food cost stays accurate.

Inventory management software connected to POS enables real-time stock depletion on every sale, but it still needs digital logging of non-sales deductions such as waste and complimentary items to keep theoretical food costs correct. The table below shows the main movement types to log every day.

Movement Type	Examples	Reason Code	Frequency
Prep waste	Vegetable trim, portioning offcuts	Preparation trim	Daily, per service
Spoilage	Expired produce, damaged stock	Spoilage / expiry	Daily, at stock check
Staff meals	Team food consumed on shift	Staff consumption	Per shift
Complimentary items	Amuse-bouche, manager comps	Complimentary / goodwill	Per service

Record waste daily as it happens and tag it with a reason so spoilage and over-prep become visible in the system. Unrecorded complimentary items and staff meals create significant variances, and one bar found a 4% spirits variance caused by inconsistent pours and failure to log free items.

Success criteria: Non-sales movements logged every service and no unexplained variance spikes at week-end review.

Step 6: Run Variance Audits and Use the Flash Report

Objective: Use Jelly's Flash Report to read live theoretical GP after every sale and spot variances between theoretical and actual usage.

Actions: Open the Flash Report daily or weekly to review GP% by period. Compare theoretical food cost, calculated from recipe-mapped POS sales, against actual cost from scanned invoices. Variances of 2–3% between actual and theoretical usage are common in well-run hospitality operations. Consistently higher variances need fast investigation into waste, theft, poor portion control or receiving errors. Use Jelly's Price Alert to see which ingredient price changes drive cost movement, then respond by negotiating with the supplier, substituting an ingredient or repricing the dish.

Success criteria: Flash Report reviewed at least weekly, variance held below 3% and GP% moving toward target.

Common Mistakes and How to Fix Them

• Missing admin rights at connection: The integration fails at the permissions step when the user lacks admin access. Fix this by logging in with the POS owner account or requesting a temporary admin role before you start.
• Unmapped POS items: Dishes sold without a linked recipe create no theoretical cost depletion and inflate variance. Audit the Cookbook weekly and map any new menu items as soon as they go live on the POS.
• Unlogged waste and staff meals: Restaurant groups lose 4–10% of ingredient spend to untracked waste before a dish leaves the kitchen. Assign a named team member to log non-sales movements every service and avoid leaving it as a shared task.
• Stale invoice data: When a supplier changes prices mid-month and the new invoice is not scanned quickly, recipe costs in Jelly understate the true food cost. Scan every delivery note or invoice on the day it arrives.
• Incorrect portion sizes in recipes: Accurate recipe definitions need realistic portion sizes, such as 150g pasta and 80g sauce, instead of idealised quantities. Check portion weights against actual kitchen practice when you set up recipes.
• POS category sync too broad or too narrow: Syncing non-food categories, such as retail merchandise, pollutes the sales mix. During setup, select only the POS categories that relate to food and beverage costing.

How to Measure Success After Integration

Four core metrics show whether the POS and inventory integration is delivering real value.

• Food cost %: Calculate this as food and drink cost divided by net revenue, multiplied by 100, with a combined target of 28–32% for UK restaurants and pubs; figures above 35% usually signal portion control issues, outdated menu pricing or waste.
• Gross profit %: Target 63–68% combined food and drink GP for UK operators. Jelly's Flash Report shows this figure after every sale without manual calculation.
• Theoretical vs actual variance: Keep variance below 3%. Higher variance points to unlogged waste, portion drift, theft or receiving discrepancies that need investigation.
• Weekly P&L review cadence: Weekly tracking improves margin metrics faster than monthly review, because teams catch and correct issues within the same trading week instead of a month later.

View all four metrics in a single Jelly Flash Report and see how they move day by day.

Advanced Tips for Scaling Jelly Across Your Business

Multi-site rollout. Once the workflow runs smoothly at one site, you can repeat it across additional locations using the same quick POS connection per site. Sushi Revolution used Jelly to achieve gross profits 2–3% higher on average across multiple sites, with consistent recipes and cost data centralised in one platform. Jelly's flat £129 per site monthly pricing keeps costs predictable as you grow.

Xero integration for automated bookkeeping. Jelly pushes digitised invoices straight into Xero with one click, which removes manual AP data entry and cuts bookkeeping time by around 90%. This links kitchen cost data directly to the management accounts your finance team or accountant uses.

Delivery menu costing. Jelly lets operators set separate target gross profits on dine-in and delivery menus, reflecting third-party delivery commissions of up to 30%. Duplicate existing Cookbook recipes and apply the commission overhead to build a correctly priced delivery menu.

Price Alert negotiations. Every supplier invoice processed by Jelly feeds the Price Alert feature, which highlights every price increase or decrease by ingredient and supplier. Use this data in supplier meetings to challenge unjustified increases, request credit notes and compare alternative suppliers using hard invoice evidence instead of estimates.

FAQ

How do you calculate food cost after POS integration?

Once your POS is connected and every menu item is mapped to a recipe in Jelly's Cookbook, food cost calculates automatically. Each time a dish is sold through the POS, Jelly multiplies the recipe's ingredient quantities by their current invoice prices and accumulates the total cost of goods sold. Food cost percentage then appears as total ingredient cost divided by net revenue, multiplied by 100. Because invoice prices update with every scanned delivery, the figure reflects current supplier pricing rather than a static snapshot from menu launch. The Flash Report shows this calculation daily, weekly or monthly without manual input.

How do you manage variance between theoretical and actual food cost?

Variance is the gap between what the system calculates you should have used, based on POS sales and recipes, and what you actually used, based on physical stock counts and invoices. The 2–3% variance threshold mentioned in Step 6 is the benchmark for well-run operations. To manage variance, log all non-sales movements such as waste, staff meals and complimentary items every service using Jelly's movement logging. Review the Flash Report weekly and investigate any variance above this by checking for unmapped POS items, unlogged waste events, portion drift or receiving discrepancies. Consistent variance above 5% usually points to a systemic issue such as theft, over-portioning or a supplier short-delivering on invoiced quantities.

What is the difference between inventory data and POS data in this workflow?

POS data records what was sold, including dish name, quantity, price and time of transaction. Inventory data records what stock exists and at what cost, based on scanned supplier invoices and physical counts. Jelly connects the two. POS sales trigger theoretical ingredient depletion based on mapped recipes, while invoices keep the cost of each ingredient up to date. The result is a live theoretical food cost figure that combines both data sources. Neither dataset alone produces accurate real-time GP. POS data without recipe costs gives revenue only, and inventory data without sales gives stock levels only. The integration makes the margin calculation live and automatic.

How long does it take to see a return after connecting Jelly to a POS?

Most operators see actionable data within the first week. Price Alert notifications start as soon as the first invoices are processed, giving chefs and owners immediate visibility of supplier price movements. Live dish GP% appears in the Cookbook as soon as recipes are mapped to POS items, which usually takes a few hours for an active menu. Meaningful GP improvement is typically observed within the first three months, matching the 2-percentage-point lift mentioned earlier, as operators use Price Alert data to negotiate with suppliers, adjust menu pricing and reduce untracked waste.

Does Jelly work for operators with multiple POS systems across sites?

Yes. Each site connects its own POS to Jelly independently using the same quick integration flow. A multi-site operator running Lightspeed at one location and EPOS Now at another can connect both, with each site's sales data feeding into its own Flash Report and Cookbook. Recipes and ingredient costs can be managed centrally, giving head office a consolidated view of GP across all locations while each site's kitchen team works within their own operational data. Jelly's £129 per site monthly pricing applies per location with no per-user charges.

Conclusion: Turning POS Data into Live GP

The workflow in this article, covering POS access, connection through Jelly, invoice scanning, recipe mapping, non-sales movement logging and Flash Report review, replaces the manual spreadsheet cycle that costs UK operators margin every week. Chef-Owner Murat Kilic at Amber saves £3,000–£4,000 per month using this exact approach. The Howard Arms reached 80% gross profit after moving from manual costing to Jelly's automated system. Cairn Lodge Hotel cut food costs by 5% within a month of going live.

Jelly is priced at a flat £129 per site per month with no per-user fees and no variable charges, and it delivers initial value within the first week. The POS connection is the starting point that unlocks live theoretical food cost and GP.

Start your Jelly setup and see live GP in your own operation within days.