Written by: JJ Tan, Founder, Jelly
Key Takeaways
- Marketman menu costing links supplier invoices to recipes for live plate cost and food cost percentage updates, but it usually needs weeks of data entry before it delivers value.
- UK operators face extra setup work around VAT-exclusive pricing, pack-size unit conversions, and multi-site licensing that scales per location.
- Marketman’s pricing typically ranges from about $199–$429 per month per site plus a $500 onboarding fee, so first-year costs often sit well above the headline subscription.
- Marketman automates price cascades and alerts, yet the two-to-four-week configuration window and ongoing manual invoice uploads on lower tiers limit its practicality for many UK operators.
- UK restaurants, pubs, and boutique hotels that want faster time-to-value can see Jelly’s live menu costing in days, not weeks.
How Marketman Menu Costing Works
Marketman menu costing follows a structured setup sequence before it delivers live plate costs:
- Set up ingredients with pack sizes and units of measure
- Build recipes and sub-recipes, assigning ingredient quantities and wastage percentages
- Connect suppliers and configure vendor catalogues
- Scan or upload supplier invoices so prices flow into the ingredient database
- Let costs cascade automatically from ingredients to every recipe that uses them
- Set target food cost percentages per dish or across the menu
- Review plate cost and GP per dish in the reporting dashboard
- Sync recipe and price data across multiple sites
Because each step depends on the one before it, the system only becomes useful once ingredients, recipes, and supplier connections are fully configured. That dependency is where the real time investment sits.
Live Price Updates
When a supplier invoice is processed in Marketman, ingredient costs update and cascade to every recipe containing that ingredient. Marketman automates recipe cost updates when invoice prices change, which separates it from lower-cost tools that require manual re-entry.
For UK operators, the key issue is how invoices enter the system. Email invoice scanning appears as an Enterprise-tier feature on Marketman’s published plan structure, so operators on lower tiers may need to upload invoices manually. UK full VAT invoices must show the net cost and VAT separately. They state the amount payable excluding VAT for each item, the gross total excluding VAT, and the total VAT chargeable. Only simplified invoices for supplies of £250 or less may show a single VAT-inclusive total. Operators must confirm whether Marketman reads ingredient costs as VAT-exclusive figures, which is the correct basis for food cost percentage calculations, or whether that separation needs manual configuration. Food cost percentage uses the ex-VAT selling price as the basis for the ratio.
Portion And Sub-Recipe Tracking
MarketMan’s recipe costing supports batch recipes and sub-recipes and handles unit conversions within the same UOM family. A sauce built as a batch sub-recipe can be costed per 100ml and then pulled into multiple dishes at the correct portion size. Wastage percentages sit at the ingredient level, so a 10% trim loss on a protein feeds into the plate cost.
UK supplier pack sizes vary widely: a 5kg bag of flour, a 10-litre drum of oil, a case of 24 tins. Each one requires accurate pack-size configuration at setup. Marketman’s unit-of-measure handling allows ingredient updates to propagate to item and menu costing, but this only works correctly when pack sizes and yields are entered consistently from the start. Inconsistent item naming or unit conventions break the cascade.
Profitability Insights
MarketMan calculates plate cost by pulling live ingredient prices from purchase orders and inventory records, then calculating the cost per portion for each recipe. The food cost percentage for an individual dish is derived by dividing the ingredient cost for that dish by the revenue charged to the customer. Total restaurant Food Cost Percentage uses Cost of Goods Sold divided by Total Sales. Operators can set target food cost percentages, and the system flags dishes that breach those targets as ingredient prices move. The alert mechanism compares actual food cost percentage against a defined maximum target and fires when a price update pushes a dish above it. This gives operators a live signal instead of a month-end surprise.
Multi-Unit Sync
For UK groups running two to five sites, Marketman’s multi-site capability means a recipe change or supplier price update at group level flows to all connected locations. Marketman’s Professional tier adds multi-location support and advanced analytics on top of the base Operator tier.
Softabase’s March 2026 review states that MarketMan’s pricing is charged per location. A three-site group on the Professional tier therefore pays for three separate location licences, not a single group-wide fee. The cost structure scales linearly with site count.
A Worked UK Dish Example
This worked example shows how Marketman-style costing behaves for a classic pub burger using UK supplier pack prices. All ingredient costs are ex-VAT, which matches the correct basis for food cost percentage calculations.
| Ingredient | Pack Price (ex-VAT) | Pack Size | Portion Cost |
|---|---|---|---|
| Beef mince (80/20) | £12.00 | 2kg | £1.80 (300g portion) |
| Brioche bun | £4.80 | 12 buns | £0.40 |
| Cheddar slice | £3.60 | 20 slices | £0.18 |
| Lettuce, tomato, onion | £2.50 | 10 portions | £0.25 |
| Burger sauce (batch) | £1.50 | 10 portions | £0.15 |
Total plate cost: £2.78. Selling price ex-VAT: £9.17 (£11.00 inc. 20% VAT). Food cost percentage: £2.78 ÷ £9.17 = 30.3%.
Inside Marketman menu costing, the same calculation runs automatically once each ingredient links to a supplier invoice. If the beef mince price rises from £12.00 to £13.50 per 2kg, the plate cost updates to £3.08 and the food cost percentage moves to 33.6%. That shift triggers an alert if the target sits at 30%. On a spreadsheet, that recalculation only happens when someone notices the invoice and updates the cell manually.
How Much Does Marketman Cost UK Operators?
Total cost of ownership for a UK operator extends beyond the headline subscription price.
On published plan pricing, PriceTrack lists Marketman’s plans as of June 2026 at Starter ($199/month), Growth ($249/month), and Enterprise (custom pricing). Softabase’s March 2026 review lists different tiers. Operator is $239/month per location, Professional is $329/month per location, and Ultimate is $429/month per location. Third-party sources do not agree exactly on live rates, and Marketman’s pricing has changed multiple times in the past 12 months.
Beyond the monthly subscription, Marketman charges a one-time $500 onboarding fee at sign-up. For a single location, first-year cost is estimated at about $3,400 including that fee, dropping to about $2,900 annually thereafter. For a two-to-five-site group, MarketMan costs are estimated at $478 to $1,195 per month depending on tier and site count.
The less visible cost is setup time. Third-party sources report that MarketMan requires weeks of active recipe and ingredient data entry, with one source specifying two to four weeks, before its food cost reporting becomes meaningful. During that window, the subscription runs but the menu costing feature does not yet deliver value. Some restaurants abandon the tool before seeing ROI because they underestimate the data entry burden at purchase. UK operators should also verify whether their POS integrates natively or needs a third-party connector, as some POS integrations carry their own monthly fees.
Compare Jelly’s flat-rate pricing and one-week onboarding to see how the numbers stack up.
How The 30/30/30 Rule Relates To Marketman
Before comparing Marketman against a spreadsheet, it helps to know what food cost target the platform supports.
The 30/30/30 rule is a restaurant budgeting benchmark that allocates roughly 30% of revenue to food cost, 30% to all-in labour cost, and 30% to operating expenses, leaving about 10% as net profit. It works as a benchmark to compare against rather than a precise engineering target.
The 30% food cost target acts as a pricing guardrail. Menu price equals plate cost divided by target food cost percentage, so a £2.78 plate cost at a 30% target yields a £9.27 ex-VAT menu price. Marketman menu costing acts directly on this bucket. It tracks ingredient costs, calculates food cost percentage per dish, and alerts when a dish breaches its target. The labour and operating expense buckets sit outside Marketman’s scope.
Quick-service restaurants often run 25–28% food cost, casual dining typically lands at 28–32%, and fine dining regularly runs 33–40%. The 30% food cost figure in the rule is a blended average across the full menu including beverages, not a per-dish target. Marketman’s target food-cost-percentage alerts work best when set at the dish level and calibrated to the actual cost history of each item.
For UK operators, Marketman menu costing therefore supports the food cost bucket of the 30/30/30 framework. Hitting the labour and operating expense buckets needs separate systems and disciplines.
Marketman Menu Costing Vs A Spreadsheet
For a single-site operator with a short, stable menu and a supplier list that barely changes, a spreadsheet can still be workable because re-keying a handful of costs is genuinely quick. Dedicated software becomes more attractive as complexity, site count, or price volatility grows.
Marketman menu costing adds clear value over a spreadsheet in three specific situations. When a supplier price changes, 70% of recipes carry an out-of-date cost after a supplier price change in a spreadsheet-based system. Marketman cascades the update to every affected recipe automatically. Invoice capture without manual typing removes the re-keying step entirely. Multi-site consolidation gives a group operator one source of truth instead of separate spreadsheets that drift to their own ingredient names and cannot be compared without a manual reconciliation job every month.
The admin burden shifts rather than disappears with Marketman. Instead of re-keying prices, operators must maintain consistent ingredient names, pack sizes, and recipe structures inside the platform. Marketman’s value drops when recipes, item names, and units are inconsistently maintained.
Marketman Menu Costing Template And Platform Build
A Marketman menu costing template gives operators a way to test their costing approach before they commit to full platform setup.
The worked burger table above functions as a simple template. Operators can enter their own pack prices, portion sizes, and selling prices to produce a real food cost percentage for top sellers. That exercise highlights missing recipes, unclear yields, or inconsistent portion sizes.
Building the same costing inside Marketman turns the static template into a live system. The plate cost updates when invoices arrive, not only when someone re-opens the file. The trade-off is setup time. Every ingredient, pack size, and recipe must be entered correctly before the platform delivers accurate figures. Any stock system is only as good as its setup. Ingredients with correct pack sizes and yields and recipes that match what the kitchen actually does require real work. Skipping that groundwork produces confident, precise, wrong numbers.
The template works as a diagnostic. The platform becomes the operational system. Operators evaluating Marketman can use the template phase to clean recipe data before they begin platform configuration.
Where Marketman Menu Costing Falls Short For UK Operators
The setup burden is the most consistently reported limitation. Entering every recipe with exact ingredient quantities, setting up vendor catalogues, and training staff on receiving and count procedures takes weeks of data entry, and some restaurants abandon the tool before seeing ROI. For a single-site operator without a dedicated operations manager, that setup window is a real cost in time and attention.
For UK operators specifically, VAT treatment needs careful configuration. As the HMRC rule quoted earlier explains, net cost and VAT must appear separately on full VAT invoices. Food cost percentage must use ex-VAT figures. Whether Marketman handles this separation automatically or needs manual setup is a question operators should confirm directly with Marketman before signing a contract, because the answer affects the accuracy of every plate cost the system produces.
Unit conversions must be configured correctly at the ingredient level. A 5kg bag, a 10-litre drum, and a case of 24 all need their own conversion rules. Multi-location rollups require disciplined item mapping, and standardising recipe structure takes time for teams with many ad hoc prep methods. In practice, the quality of Marketman’s output tracks directly with the quality of the data entered, which is easy to underestimate during a sales demo.
Email invoice scanning sits on the Enterprise tier, so operators on lower tiers must upload invoices manually, with no automated capture. And Marketman requires regular physical counts to maintain accurate food cost data. Ongoing staff time therefore becomes a hidden operational cost beyond the subscription fee and onboarding charge.
Why Jelly Is The Best Solution For UK Operators
The three questions UK operators raised earlier, setup time, VAT handling, and per-location cost, are where Jelly’s approach differs most from Marketman’s.
Jelly gives growing restaurants, pubs, and boutique hotels a simpler way to manage food and beverage operations. It automates invoices, inventory, and real-time menu profitability without a long configuration phase.
In Jelly’s Kitchen section, chefs build a dish recipe by clicking on ingredients already populated from scanned invoices. All unit conversions and maths happen instantly. A task that took 28 minutes in a spreadsheet now takes about 3 minutes to cost a menu item. There is no separate ingredient setup phase because the invoice scan performs the setup.
As invoices update ingredient prices, dish costs and GP margins update in real time. A red percentage indicator appears if a dish drops its margin, and a green one appears if it improves. Jelly users add 2 percentage points to gross margins on average in the first 3 months. The Price Alert feature flags every supplier price increase or decrease, giving chefs concrete evidence for supplier negotiations, similar to Marketman’s price tracking alerts but without weeks of prior configuration.
Jelly’s pricing is a flat £129/month per location with no variable charge per user or feature. Check Jelly’s flat-rate pricing and free trial. Jelly does not charge an onboarding fee or require an annual commitment, and all new accounts start with a 14-day free trial with no credit card. Onboarding and initial value arrive in the first week. Operators gain access to price alerts and spending insights as soon as suppliers send invoices to a dedicated email address, or within 24 hours of photographing invoices into the app.
Jelly integrates natively with Square, EPOS Now, Toast, and Lightspeed via real-time API, and with Xero for accounting. These tools feed item-level sales data into Jelly the moment a transaction completes and enable the Flash Report, a daily, weekly, or monthly view of GP margin calculated from invoice costs and POS sales. Jelly users cut food costs by 3% on average in the first 3 months.
Stuart Noble, Head Chef at Cairn Lodge Hotel, put it directly: “Price hikes were crushing our margins — I felt helpless. With Jelly, every dish cost is up-to-date at my fingertips. We slashed food costs by 5% in a month.”
See Jelly’s live dish costing in action and compare it to your current process.
Frequently Asked Questions
How Do I Calculate The Cost Of A Menu In Marketman?
The process runs in sequence. First, build your ingredient library with correct pack sizes and units of measure for each supplier product. Second, build recipes and sub-recipes by assigning ingredient quantities and wastage percentages to each dish. Third, connect your suppliers and configure vendor catalogues so invoice prices can flow into the ingredient database. Once invoices are processed, either by upload or, on the Enterprise tier, by email scanning, ingredient costs update and cascade to every recipe that uses them. Marketman then displays plate cost and food cost percentage per dish and fires alerts when a dish breaches its target food cost percentage. The system only produces accurate figures once ingredients, recipes, and supplier connections are all correctly configured.
What Food Cost Percentage Should A UK Restaurant Target?
General industry ranges vary by concept type. Fast casual operations typically target a food cost percentage of around 28–35%. According to the National Restaurant Association’s 2025 Restaurant Operations Data Abstract (2024 data), full-service restaurants generally land in the 28–35% range, with a median food cost of 32.0% of sales. Fine dining concepts often run around 33–40% food cost. These figures act as directional benchmarks. The right food cost percentage for a specific operation depends on selling prices, labour model, and occupancy costs. A dish with a 38% food cost that sells in high volume and carries a strong contribution margin may be more valuable than a 25% food cost dish that barely moves. The 30/30/30 rule uses 30% as a blended food cost benchmark across the full menu including beverages, which works as a useful P&L sense check rather than a per-dish target.
How Long Does It Take To Set Up Marketman Menu Costing?
As noted in the pricing section, setup typically takes two to four weeks before food cost reporting becomes meaningful. That window covers building the ingredient library with correct pack sizes, entering recipes and sub-recipes, configuring vendor catalogues, and training the team on invoice receiving and stock count procedures. The subscription runs during this period, so the effective cost of ownership in the first month sits above the headline plan price. Operators with large menus, multiple suppliers, or complex batch recipes should budget toward the longer end of that range.
Does Marketman Handle UK VAT On Supplier Invoices?
Food cost percentage is calculated on the ex-VAT selling price for the ratio to be meaningful. As the HMRC rule quoted earlier states, net cost and VAT must appear separately on full VAT invoices. Operators evaluating Marketman should confirm directly with Marketman how UK VAT invoices are handled at upload or scan, and whether ex-VAT extraction is automatic or needs manual configuration. Incorrect handling overstates every plate cost and food cost percentage the system produces.
Is Jelly Suitable For A Single-Site UK Pub Or Restaurant?
Yes. Jelly is built for established restaurants, pubs, and boutique hotels at the £500k+ revenue level, whether they run a single site or expand to multiple locations. Single-site operators benefit from the same invoice automation, live dish costing, and Price Alert features as multi-site groups, without per-location cost scaling that makes some competitors expensive for smaller operations. At £129/month per location with no onboarding fee and a one-week time to value, Jelly is designed to deliver a return from the first month.
Conclusion
Marketman menu costing links supplier invoice prices to recipes and delivers live plate costs and food cost percentage alerts. For UK operators, the evaluation rests on three practical questions. Total cost of ownership must include setup time, onboarding fees, and per-location pricing. The platform’s handling of UK-specific requirements around VAT invoices and pack-size unit conversions must be clear. The two-to-four-week setup investment must feel proportionate to the size and complexity of the operation.
For operators where those trade-offs feel acceptable, Marketman offers a full-featured platform. For operators who need live menu costing without a multi-week configuration phase, a simpler alternative often fits better. Talk to Jelly and compare it directly with Marketman to decide which approach suits your operation.