Procure Wizard Recipe Costing: A Guide for UK Operators

September 13, 2026

Written by: JJ Tan, Founder, Jelly

Key Takeaways

UK hospitality operators are moving away from spreadsheets because of volatile supplier prices, multi-site complexity, and the admin burden of maintaining accurate recipe costing and gross profit figures.
Access Procure Wizard is an enterprise procurement and recipe costing system that updates dish costs and GP when supplier prices change, and it needs clean data, accurate recipes, and dedicated admin resource to work reliably.
The platform distinguishes between centrally managed administrative recipes and site-level local recipes, which creates governance and consistency challenges for growing multi-site operators.
Procure Wizard is priced and structured for larger estates with central procurement teams, so smaller or early multi-site operators often find the implementation scope and ongoing maintenance commitment disproportionate to their needs.
For growing restaurants, pubs, and boutique hotels, invoice-driven recipe costing can deliver live GP without enterprise overhead.

What Is Procure Wizard Recipe Costing?

Access Procure Wizard is The Access Group’s procurement and recipe costing system for hospitality. Its recipe costing module links recipes to supplier prices so that, when connected to purchase-to-pay, dish costs and gross profit update automatically as supplier prices change. Access Procure Wizard Evo’s recipe management module is used across more than 9,700 UK hospitality sites, according to Access Group’s own site count. That connection removes the need for manual recalculation.

The core framework follows a clear sequence: supplier price file → recipe build (portion, yield, wastage) → live dish cost → GP calculation → menu decisions.

See how a lighter approach handles the same sequence automatically.

How Recipe Costing Works In Procure Wizard

Recipe costing in Procure Wizard runs through a connected chain of data, and each step depends on the accuracy of the previous one.

Recipes link to supplier price files. Each ingredient in a recipe is mapped to a supplier SKU. When a supplier updates a price, that change flows through to every recipe containing that ingredient without manual intervention, provided the price file is current and correctly mapped.
Portion, yield, and wastage factors are applied. Recipe costing software multiplies the quantity of each ingredient by its current purchase price, accounting for yield loss such as trim and cooking reduction. A yield factor per recipe node translates raw purchase weights into usable edible portions. Defaulting yield to 1.0 when real trim loss exists overstates theoretical margin across every affected dish.
Live price updates flow through to dish costs. Access Procure Wizard Evo displays live cost per portion and gross profit as each ingredient is added or portion adjusted. This view shows the GP impact before a dish is launched. The system also tracks recipe audit history, recording who created and approved each recipe and when it was last updated.
GP is derived from sales and cost data. The system summarises cost per portion, price per portion, target GP, actual GP, and profit per portion at a glance. Menu performance analysis uses the Star, Plow Horse, Puzzle, and Dog classification system based on units sold, revenue, profitability, and popularity.

GP accuracy depends entirely on the quality of the price files and recipe data feeding the system. If supplier prices are not updated regularly, food costing software cannot produce reliable food cost or margin figures, because recipe costs will not reflect current purchasing costs. A mid-sized restaurant group running manual reconciliation processes can run at an inflated food cost for weeks before the discrepancy surfaces.

How Local And Administrative Recipes Work In Procure Wizard

Access Procure Wizard Evo uses an unrestricted tiering system for menus, supporting simple single-level menus or multi-levelled structures for groups, regions, and sites. This structure allows central and site-level recipe structures to coexist. In practice, this creates two governance modes: administrative recipes managed centrally by head office or a dedicated admin team and pushed out across sites, and local recipes created or adjusted at site level.

The distinction carries real operational implications. Administrative recipes deliver consistency and cost control across an estate and require a dedicated team to build, maintain, and update them as supplier prices and menus change. Local recipes give kitchen teams flexibility and introduce variability that can undermine group-level GP reporting. For a growing operator moving from two to five sites, the admin resource required to maintain administrative recipes accurately is a material commitment, and vendor pages rarely quantify that commitment.

How Much Procure Wizard Typically Costs

Access Group does not publish standard pricing for Procure Wizard and directs buyers to contact the vendor directly. No list price, pricing calculator, or free trial is publicly available. The product is structured across three tiers: Essential+, Professional+, and Premium+. Each tier covers progressively broader scope from purchase-to-pay through to enterprise and bespoke end-to-end procurement.

Several factors drive the total cost of ownership beyond the headline licence fee. Procurement software quotes are commonly shaped by several factors: the modules selected, the number of sites or entities, integration requirements, implementation complexity, support and professional services, and contract term. Implementation and configuration should be budgeted at one to three times the first-year licence fee. Data migration, including cleaning and mapping SKU, supplier, and location master data, is consistently the most underestimated cost line in enterprise software projects.

Procure Wizard is positioned and priced for multi-site estates with centralised procurement and dedicated admin resource. The platform is best suited to multi-site hospitality operators such as restaurant groups, hotel groups, and pub companies using centralised procurement, with businesses handling high invoice volumes across many sites and suppliers benefiting most. Single-site or early multi-site operators may find the commercial model and setup burden heavier than expected relative to the GP visibility they actually need. That commitment is also reflected in the commercial model.

Explore a lighter commercial model with Jelly.

What You Need In Place Before Recipe Costing Works

Recipe costing delivers value only when the inputs are solid. The input burden is substantial, and without these foundations, live GP figures can mislead operators.

Clean, current supplier price files. Item master data hygiene requires one record per real product, with every supplier and pack size linked to that single record, and a current cost confirmed against a recent invoice. A unit-of-measure error at receiving, such as logging a case price as a single-unit price, can inflate a recipe cost line by a factor of twelve or more.
Accurate recipes with correct portion, yield, and wastage data. Ignoring yield and waste in recipe quantities is a common mistake that undermines recipe costing accuracy. Each recipe must be built with exact ingredient quantities per portion, and yield factors must reflect real prep loss rather than defaulting to 1.0.
Consistent unit and SKU data across suppliers. The same product named differently across locations and users fragments the catalogue and makes consolidated reporting inaccurate. Multi-site operators report that incomplete item master data blocks stock counts from completing and stops stock depletion from running correctly.
Admin resource to maintain recipes across sites. For most groups, manual recipe maintenance starts falling behind supplier price changes between three and five locations, which makes food cost reports unreliable. At that point the labour cost of manual maintenance exceeds the cost of software, but only if someone is actually doing the maintenance the software depends on.

Who Typically Uses Procure Wizard?

The typical Procure Wizard customer is a larger multi-site hospitality group, contract caterer, or estate with a central procurement or finance team. Testimonials on the Access Group’s own site come from Macdonald Hotels & Resorts, Dalata Hotel Group, Cairn Group, and RBH Hospitality. These organisations have the scale, dedicated admin teams, and IT infrastructure to extract full value from an enterprise-grade system.

Single-site or early multi-site restaurants, pubs, and boutique hotels often operate below that enterprise threshold. The governance structure, implementation scope, and ongoing maintenance commitment are designed for estates and can feel heavy for operators at the tipping point of their second or third site. Procure Wizard is a strong product for the right stage of growth; it is simply the wrong fit for operators below that threshold.

Allergen And Nutrition Integration

Recipe costing affects more than margin, because recipes also drive allergen and nutrition data and influence labelling compliance. Access Procure Wizard Evo automatically detects allergens for all major allergens whenever an ingredient is added or changed, and manages dietary tags such as vegetarian, vegan, allergen-free, and faith-based from a single recipe source. Allergen and nutrition data feed directly from recipes into menus, supporting compliance with UK food labelling rules.

This capability matters because the Food Standards Agency’s allergen guidance for food businesses applies to England, Northern Ireland, and Wales. Natasha’s Law, which requires full ingredient and allergen labelling on food prepacked for direct sale, places a legal obligation on operators to maintain accurate, up-to-date allergen records at the recipe level. A system that updates allergen data automatically when an ingredient changes reduces the risk of a labelling error caused by a missed manual update.

Procure Wizard Alternatives For Smaller Operators

Growing UK restaurants, pubs, and boutique hotels have a third path beyond Procure Wizard or a spreadsheet: recipe costing as a by-product of the invoices already being processed, rather than a separate data-entry project.

Jelly is built for this stage. It automatically scans every line item of every invoice, captured by photo or email, and uses that data to update ingredient costs in real time. Recipes are built by clicking on ingredients already populated from scanned invoices, so there is no separate catalogue to maintain. Dish GP margins update live as new invoices arrive. What used to take 28 minutes to cost a single menu item in a spreadsheet takes around three minutes in Jelly.

The commercial model is straightforward: a flat £129 per month per location, with no variable charge per user or feature. That simplicity extends to setup, and onboarding generates initial value in the first week. It also extends to integration: Jelly connects natively to POS systems including Square, EPOS Now, Lightspeed, and Toast, so real-time sales mix and GP margin data arrive the moment a transaction completes, without a separate implementation project.

The results operators report are material. Jelly users report three consistent results: food costs down 3% on average in the first three months, 10–20 hours of admin saved per month, and gross margins up 2 percentage points. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue. Populu lifted GP from 68% to 72% across 16 locations. Murat Kilic, Chef-Owner of Amber in East London, saves £3,000–£4,000 per month and says: “Jelly keeps my business alive.”

See how Jelly turns invoices into live GP without a separate data project.

Common Recipe Costing Challenges And Pitfalls

Recipe costing fails in predictable ways across platforms. Recognising these failure modes helps operators assess their own readiness honestly.

Inconsistent data capture. When invoices are entered manually or partially, ingredient costs drift from reality. GP figures become unreliable without anyone noticing until a month-end report surfaces the damage.
Delayed reporting. A mid-sized restaurant group can run at an inflated food cost for six full weeks before a spreadsheet-based reconciliation process catches it. That delay pushes corrective action back by more than a month of compounding loss.
Overreliance on spreadsheets. Spreadsheets do not cascade price changes. A supplier price movement requires manual updates across every recipe containing that ingredient, and this task falls behind almost immediately in a busy kitchen.
Poor adoption by kitchen teams. Systems that require significant manual input from chefs who are already at capacity during service will not be used consistently. Adoption collapses, and the data quality problem returns.
Fragmented systems. When procurement, recipe costing, POS, and accounting live in separate tools with no integration, the reconciliation burden falls on a person rather than a process.
Lack of accountability for recipe accuracy. Reviewing recipe costs only during menu changes is insufficient; operators should schedule regular cost reviews to catch price drift early. Without a named owner for recipe accuracy, the data degrades silently.

Best Practices For Reliable Recipe Costing

Each of those pitfalls has a mirror image. Effective modern recipe costing approaches share a set of characteristics that directly address the failure modes above.

Simplicity. The system must be usable by a busy head chef without dedicated training time. Complexity that requires an admin team to operate becomes a liability for a growing operator.
Timeliness. GP must be visible before month-end. The value of recipe costing sits in the speed of the signal rather than the sophistication of the report.
Visibility. Owners, operations managers, and chefs need to see the same numbers from the same source. A single source of truth reduces friction between kitchen and management.
Repeatability. The process must run without manual intervention. If accurate GP depends on someone remembering to update a spreadsheet, accuracy will erode quickly.
Ease of use for kitchen teams. The most effective systems reduce manual data entry to near zero and surface GP without requiring chefs to do office work during service.

Jelly embodies these characteristics for growing operators. Invoice scanning runs automatically, ingredient costs update with every new invoice, and GP margins stay live without waiting for a month-end report. Ruth Seggie, Owner of The Howard Arms, puts it directly: “Our accountant said we’d be lucky to hit 60% gross profit. After using Jelly, we reached 80%. Now I sleep better knowing my costs are under control and can react instantly, not weeks later.”

Make GP visible without adding admin burden.

Conclusion: Assessing Your Own Readiness

Recipe costing matters because margin erosion in a hospitality business stays silent until it becomes serious. Supplier prices move weekly, portion costs drift, and by the time a month-end report surfaces the problem, weeks of compounding loss have already occurred. The right system makes GP visible fast enough to act on it.

The evaluation lens for any operator considering Access Procure Wizard recipe costing should cover four questions. Is your supplier price file data clean and current? Do your recipes accurately reflect real portion, yield, and wastage? Do you have the admin resource to maintain administrative recipes across your sites? Does the commercial model, including enterprise pricing, implementation scope, and ongoing maintenance, fit your current stage and site count?

If the answer to any of those questions is uncertain, a lighter invoice-driven approach that produces live dish GP as a by-product of invoices you are already processing may be the more commercially sensible starting point. Jelly is built for that stage and serves growing restaurants, pubs, and boutique hotels that need operational control without an enterprise implementation project.

Assess your readiness and see Jelly in action.