Written by: JJ Tan, Founder, Jelly

Key Takeaways

  • MarketMan’s gross margin calculations rely on a fragile data chain of POS mapping, recipe accuracy, line-item invoices and weekly inventory counts that often breaks for UK multi-site operators.
  • Even when all inputs are present, the platform’s reports only become trustworthy after two to four weeks of setup per location and ongoing manual discipline that many kitchens struggle to maintain.
  • UK-specific issues such as VAT treatment, OCR challenges with local supplier invoices and dollar-denominated pricing add further friction for operators seeking reliable GP figures.
  • Jelly takes an invoice-first approach that delivers live dish costing and supplier price alerts within the first week, with POS integration completed in about five minutes.
  • Jelly is the best gross margin insights solution for growing UK restaurants, pubs and boutique hotels that want trustworthy GP without a long setup.

See Jelly In Action

How MarketMan Calculates Gross Margin

MarketMan derives gross margin by linking POS sales data, supplier invoices, inventory counts and recipe data to calculate cost of goods sold against sales. The platform uses the standard COGS formula, beginning inventory plus purchases minus ending inventory, then sets that against net sales to produce a food cost percentage. It then inverts that percentage to give gross margin. Each element in that chain is a dependency. Remove one and the GP figure stops being reliable at all.

The data chain breaks down as follows.

  • POS item mapping. Every till button must map to a named menu item. An unmapped POS item records revenue but depletes no stock, which creates a zero-cost sale and corrupts stock depletion, recipe costing, variance and menu engineering.
  • Invoice line-item capture. The price actually paid on an invoice flows into inventory values, COGS and recipe costs. Invoice-level price accuracy directly determines the reliability of downstream gross-margin figures. Invoices entered as totals rather than line items break this chain.
  • Recipe and ingredient costing. Every dish must have a current, accurate recipe. Theoretical food cost is only as good as the recipes behind it. If recipe costs have not been updated since a supplier price rise, the theoretical number becomes fiction and every comparison against it becomes equally unreliable.
  • Inventory counts. Physical counts must be taken at consistent intervals, times and units. A single overstated inventory count skews two months. Overstating one period’s ending count makes that month appear cheaper and the next month appear more expensive, with the error netting out across both periods rather than disappearing.
  • COGS and GP calculation. Beginning inventory plus purchases minus ending inventory, set against net sales, produces the actual food cost percentage. Gross margin is the complement of that figure, and it is only as accurate as every link above it.

What Gross Margin Reports MarketMan Provides

MarketMan provides three named reports that together cover the main dimensions of gross margin analysis. Each performs well when the underlying data is clean.

  • COGS and Gross Profits Report. Uses purchasing, counts and sales data to tell operators what their COGS and gross profits are. It works on purchasing and sales in aggregate and on counts, and can break revenue and COGS down by revenue centre such as kitchen and bar. Operators use it to track whether overall margin is moving in the right direction and to compare performance across locations.
  • Actual vs Theoretical Report. Compares recipe-and-POS-implied usage against invoice-and-count-derived actual usage. The variance between the two is where waste, over-portioning, theft and data errors surface. MarketMan considers a variance under 2–3% healthy and a variance of 5% or more a systemic problem worth investigating that same week.
  • Menu Profitability Report. Shows dish-level ingredient costs and margins, used to review menu pricing and sales mix. Recipe costing turns a vague sense that something is off into a specific, fixable decision. Operators can drop an item, adjust a price, or renegotiate a supplier. Outputs stay reliable only when recipe specifications and current ingredient prices stay accurate.

What Data MarketMan Needs For Accurate GP

Accurate GP from MarketMan depends on four specific inputs that teams must maintain continuously across every site.

  • Accurate POS-to-item mapping. When a POS button maps to nothing, the sale records revenue with zero cost. One multi-outlet operator traced a four-figure weekly cost variance per store to unmapped POS items, with food cost readings running past every plausible level once discounts and free-of-charge items were included.
  • Disciplined recipe accuracy. A recipe that still carries last quarter’s beef price produces a theoretical cost that is fiction. A 30-cent costing error on a dish selling 1,000 times a month produces a $300 monthly variance before labour, waste or price changes are considered.
  • Invoice line-item capture. Invoices entered as totals rather than line items prevent the platform from updating individual ingredient costs. When a supplier raises the price of a single SKU, that change must flow through the invoice into the recipe and into the GP figure. That chain breaks if invoices are summarised.
  • Regular, consistent inventory counts. MarketMan recommends weekly full stocktakes, taken after the last service and before deliveries, by the same team, in the same units. Inaccurate food cost arises even when everything has been counted. Unit-of-measure mismatches, deliveries arriving mid-count, invoices recorded in the wrong period and non-food items included in the count all distort results.

These four inputs are the operational reality of any recipe-and-inventory-led system, not a MarketMan quirk. The quality and timeliness of COGS reporting depend on how reliably physical counts are completed and how deeply sales data synchronises with the POS. A CSV-only POS link or missed counts directly degrade gross margin accuracy regardless of which platform is used.

MarketMan Gross Margin Limits For UK Operators

Two-to-five site UK operators face specific constraints when they rely on MarketMan for GP reporting.

Setup effort and time to first trustworthy GP. MarketMan states that implementation takes two to four weeks for a single location. Across multiple sites with central commissary setups, modelling central kitchens, transfers and per-location pricing requires significant setup effort. GP figures only become trustworthy once recipes, POS mappings and invoice capture are all complete and verified, which often takes longer than the implementation window suggests.

Ongoing discipline requirement. The Actual vs Theoretical report requires four live data streams, recipes, POS sales, invoices and inventory counts, maintained simultaneously. Manual recipe entry is a recurring limitation, described by reviewers as tedious. Some operators report running MarketMan for years without a working POS integration, which leads to manual workarounds that undermine the GP figures the platform should produce.

UK VAT treatment. UK gross profit must be calculated on net selling prices. Operators must strip 20% VAT from the menu price before calculating GP. The complication for UK operators is that not all food and drink carries the same VAT rate. Under HMRC Notice 709/1, eat-in meals and hot takeaway food are standard-rated at 20%, while cold takeaway food is generally zero-rated, and alcohol is always standard-rated. A GP figure calculated on gross, VAT-inclusive till sales is overstated by several percentage points, which is a material error on a 65–70% food GP target.

UK supplier invoice formats. OCR invoice accuracy is uneven on handwritten produce slips and on small local distributors with chaotic invoice formats. A manual review queue is recommended for the first 60 days while the system learns vendor layouts. UK operators using local and regional suppliers, common outside London, face more OCR friction than those using national distributors.

Pricing transparency. MarketMan’s published pricing lists Starter at $249/month and Growth at $299/month, with final pricing and contract terms settled on a demo call. For UK operators, the dollar-denominated pricing introduces currency exposure. The pricing page does not state whether plan prices are per location, which creates a material ambiguity for multi-site operators budgeting COGS reporting costs.

Those five constraints share a root cause. Each one comes from GP being calculated backwards from inventory. Jelly starts from the other end, the invoice.

Chat To The Jelly Team

A Faster Route To Live GP With Jelly’s Invoice-First Gross Margin Insights

Jelly bases its approach on a different starting point, the supplier invoice. Jelly does not wait for recipes, POS mappings and inventory counts to be complete before GP becomes meaningful. It begins producing live cost insights the moment invoices start arriving, whether photographed by kitchen staff or forwarded by email from suppliers.

The core workflow stays straightforward from day one. Jelly scans every line item of every invoice, including quantity, SKU, price and tax, and uses that data to keep dish costs live. Because dish costs are live, a supplier price rise flows straight through to every recipe containing that ingredient. The Price Alert feature then flags the change with the supplier name, the ingredient and the exact movement so a chef can challenge the increase or claim a credit note before it reaches the monthly report.

The Flash Report provides a daily, weekly or monthly view of gross profit margin, calculated from invoice costs and POS sales data. Connecting any of Jelly’s four supported POS systems, Square, EPOS Now, Lightspeed and Toast, takes about five minutes. Users open Jelly, click Integrations, sign in to the POS, grant permissions and select which categories to sync. Jelly’s POS-to-dish linking only surfaces items sold since the integration was connected, which keeps the mapping clean and free of legacy menu clutter.

Dish costing that previously took 28 minutes in a spreadsheet takes about 3 minutes in Jelly’s Kitchen section. Chefs build recipes by clicking on ingredients already populated from scanned invoices. Jelly handles all unit conversions and maths automatically. Customers consistently see meaningful results. 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.

The platform costs a flat £129 per month per location. There are no per-user or per-feature charges, and pricing is in pounds rather than dollars. Jelly states it saves customers 10–20 hours of admin every month, alongside a 2 percentage point GP improvement in the first three months and a 3% food cost reduction. Onboarding generates initial value in the first week.

The difference comes down to what each platform needs before it can produce a number you can trust, and how often that work repeats. Jelly needs only supplier invoices before it can produce a GP figure and usually delivers one within the first week. MarketMan needs recipes, POS mapping, invoices and inventory counts all complete first, which typically takes two to four weeks per location. Jelly surfaces live supplier price changes on every invoice line through Price Alerts, while MarketMan surfaces price shifts later through reports. Jelly’s ongoing discipline centres on invoice capture, which it automates. MarketMan’s discipline centres on recipe maintenance, POS mapping and weekly inventory counts. For UK operators, Jelly offers a clear £129 per month per location price, while MarketMan prices in dollars with per-location details agreed on a call.

Get Your First GP Figure This Week

MarketMan Or Jelly For Your Sites

MarketMan suits food-led groups with dedicated back-of-house resource, an appetite for full inventory and purchasing control, and the operational discipline to sustain weekly counts, current recipes and complete POS mappings across every site. Its broader all-in-one suite, covering supplier ordering, purchase orders, receiving reconciliation and multi-location purchasing controls, is genuinely capable for operators who can staff and maintain it. For those operators, the setup investment is justified by the depth of control available. You can read an independent assessment of how MarketMan performs for UK pub operators at Marketman Review: Is It Right For Your UK Pub? and a detailed look at its menu costing approach at Marketman Menu Costing: A UK Guide To Costs And Limitations.

Jelly suits growing UK restaurants, pubs and boutique hotels that want live, trustworthy GP without heavy setup. The invoice-first approach means GP figures are meaningful from the first week, without months of recipe entry and count discipline first. For operators whose kitchens are busy, whose chefs are not spreadsheet users and whose supplier prices are moving faster than monthly reports can track, Jelly delivers practical margin control with far less operational overhead.

Conclusion

Trustworthy GP depends on the quality of the data behind it. For a two-to-five site UK operator, sustaining the recipe accuracy, POS mapping and weekly counts that MarketMan’s reports require is a significant ongoing commitment. When any link in that chain breaks, the GP figure becomes a data artefact rather than a reliable signal. The trust question, “can I believe this number?”, matters most, and features alone cannot answer it.

Jelly is the best gross margin insights solution for growing UK restaurants, pubs and boutique hotels that want trustworthy GP without a long setup, because it automates invoice capture into live dish costing, alerts you to every supplier price change and connects to your POS in about five minutes. At £129 per month per location, with onboarding value in the first week and documented outcomes of 2 percentage points GP improvement in the first three months, Jelly provides a faster, simpler route to a GP figure you can act on.

Book A Demo

Frequently Asked Questions

Does Marketman Show Live Gross Margin?

Marketman provides near-real-time COGS tracking when its data inputs are current, but “live” depends on how recently invoices were entered, when the last inventory count was taken and whether POS sales are syncing correctly. The platform does not produce a live GP figure in the way that an invoice-first system does, because its GP calculation requires a completed inventory count to close the period. Between counts, the COGS figure is an estimate based on the last count plus purchases. For operators who count weekly, this means GP is meaningfully current once a week. For those counting monthly, the figure can be four weeks out of date before it is reliable.

How Quickly Can I Get Trustworthy GP Figures With Jelly?

Jelly generates initial value in the first week. As soon as suppliers start sending invoices to a dedicated Jelly email address, or kitchen staff photograph invoices into the app, Jelly begins scanning every line item and producing live cost insights. The Price Alert feature is active from the first invoice, flagging every supplier price movement immediately. Connecting a POS system takes about five minutes, after which the Flash Report shows gross profit margin from invoice costs and live sales data. Dish costing through the Kitchen section takes around 3 minutes per menu item once ingredients are populated from invoices. Customers typically see the GP uplift described earlier within the first three months.

Which POS Systems Does Jelly Integrate With?

Jelly integrates natively with four POS systems via real-time API: Square, EPOS Now, Lightspeed and Toast. Each integration delivers item-level sales data the moment a transaction completes. Setup follows the five-minute process described above. The only common friction point occurs when the user lacks admin access to their POS account, and Jelly flags this requirement upfront. Jelly is listed on the Lightspeed marketplace, and the EPOS Now integration is particularly relevant for independent and single-site UK operators. Jelly plans to add further POS partners in the future for operators using other systems.

Is Jelly Suitable For A 2–5 Site UK Operator?

Yes. Jelly is designed specifically for growing restaurants, pubs and boutique hotels at the tipping point of expanding to multiple locations, with annual revenue of £500,000 or more. The flat £129 per month per location pricing means costs scale predictably with the business. The invoice-first approach removes the dependency on kitchen staff maintaining recipe data and running weekly inventory counts, which is exactly the operational discipline that becomes harder to sustain as sites are added. Management and finance teams have direct access to Jelly’s insights dashboard and Flash Report across all locations, providing a central source of truth without requiring physical presence on every site. The platform integrates with Xero for accounting, and Sage integration is coming soon.