Written by: JJ Tan, Founder, Jelly

Key Takeaways

  • Restaurant365 recipe costing needs detailed manual setup across invoices, item mapping, recipes, yields, and POS links before plate costs are reliable.
  • Accurate costing depends on ongoing data hygiene, with every new item, pack size change, or substitution mapped correctly or costs drift.
  • The maintenance workload usually lands on already busy head chefs, adding admin pressure alongside running service.
  • UK operators must adapt Restaurant365’s US-focused documentation to UK realities such as VAT treatment and Xero-based workflows.
  • Jelly provides an invoice-driven alternative that scans supplier invoices and updates recipe costs in real time without manual mapping.

See Jelly In Action For Your Kitchen

Before You Begin With Restaurant365 Recipe Costing

Restaurant365 recipe costing needs careful setup before any plate cost is trustworthy. The following foundations must exist first:

  • Supplier invoices with line-item pricing entering the system correctly
  • A populated item list with purchased items mapped to the correct units of measure
  • Recipes and sub-recipes built in the system
  • Yield percentages and portion sizes entered for every recipe
  • POS menu items linked to the corresponding R365 recipes
  • The correct user permissions assigned across the team

Ownership of these tasks typically splits across roles, but the division is not always clear. The finance or operations lead usually owns item costing and purchasing data hygiene, while the head or executive chef owns recipe build, yield accuracy, and portion standards. The critical gap is the ongoing mapping of purchased items to recipes and POS menu items, and this is where most kitchens struggle. In practice, that job often falls to a busy head chef who did not sign up for office work.

UK operators also face a context gap. UK supplier invoices, VAT treatment, and accounting workflows such as Xero integrations shape how data must be entered and maintained. Restaurant365’s documentation is written primarily for a US operator context, so UK teams often have to adapt their processes.

Why Recipe Costing In Restaurant365 Matters

Accurate recipe costing produces trustworthy plate costs, visible gross profit margins, and faster reactions to supplier price changes before they erode margin. A one percentage point improvement in food cost percentage is worth £10,000 to the bottom line for a restaurant doing £1 million in annual food sales.

Without recipe costing, food cost is typically reviewed only at period end. The average gap between when a variance starts and when leadership finds out is three to five weeks. That window is long enough for a supplier price increase to compound across dozens of dishes before anyone acts. Recipe costing shortens that delay and gives operators the data to challenge suppliers, adjust menu pricing, and make faster decisions across sites.

For a broader view of how recipe costing connects to restaurant profit margins, see How Recipe Costing Improves Restaurant Profit Margins. Now that the importance is clear, the next step is understanding what Restaurant365 recipe costing involves in practice.

What Restaurant365 Recipe Costing Actually Does

Restaurant365 recipe costing links purchased items from supplier invoices to recipes and sub-recipes, then maps those recipes to POS menu items. The system uses quantity, unit of measure, yield, and portion size to calculate plate costs and food cost percentages, and it updates those figures as invoice prices change.

The data flow runs in one direction. Purchased items from invoices feed into recipes and sub-recipes, which then map to POS menu items. Recipe costs are tied to live purchasing data so vendor-price changes automatically update theoretical food cost. Operators can then compare actual versus theoretical food cost instead of waiting until period end.

Restaurant365 also provides a Recipe Cost Report, which presents plate costs and food cost percentages by menu item. Cost update options include nightly, on demand, and manual. That choice has real operational consequences for a UK kitchen reacting to mid-week supplier price changes.

How To Cost A Recipe In Restaurant365

Step 1: Set Up Item Costing

Every recipe is only as accurate as the purchased items feeding it. This means each ingredient must exist as a purchased item in Restaurant365, linked to the correct supplier, with the correct unit of measure and current price. When recipe management is not connected to purchasing data, operators continue using recipe costs that were accurate three months ago before a vendor price increase changed the margin on several dishes. A successful result at this step means every purchased item has a current, invoice-verified cost and a correctly defined unit of measure.

Step 2: Create A Recipe

Use the Recipes module and build the recipe by adding purchased items and any sub-recipes as ingredients. Build sub-recipes such as sauces or marinades first so they can be pulled into parent recipes. A successful result is a recipe where every ingredient line links to a live purchased item rather than a placeholder or archived record.

Step 3: Enter Quantity, Unit Of Measure, Yield, And Portion Size

Most operators introduce errors at this stage. Each ingredient line needs a quantity, a unit of measure that matches how the ingredient is used in the recipe, a yield percentage to account for trim and cooking loss, and a portion size. Missing or incorrect unit-of-measure conversions between how an ingredient is purchased and how it is used in a recipe can make invoice costs unusable or materially wrong. A successful result is a recipe where every ingredient line reflects actual kitchen usage rather than invoice pack sizes.

Step 4: Map Recipes To POS Menu Items

When new POS items are imported into Restaurant365, they appear unlinked by default and must be reviewed and mapped to corresponding R365 menu items. This mapping enables the system to use recipe and cost data for reporting and theoretical inventory usage. Multiple POS items can link to a single menu item, which helps when the same dish has different names across locations. A successful result is every selling item on the POS linked to the correct R365 recipe.

Step 5: Choose The Cost Update Frequency

Restaurant365 offers three cost update options: nightly, on demand, and manual. Nightly updates mean recipe costs reflect the previous day’s invoice data by the following morning. On demand allows a manual trigger at any point. Manual means costs only update when someone actively initiates the process. For a UK kitchen where a supplier raises prices mid-week, nightly updates are the minimum viable setting. Manual updates leave recipe costs stale until someone remembers to refresh them.

Step 6: Run The Recipe Cost Report

The Recipe Cost Report presents plate costs and food cost percentages by menu item, drawing on the recipe data, purchased item costs, and the cost update frequency selected. Best-in-class operators aim to keep the variance between actual and theoretical food cost below 1%. A gap of 2 to 3 percentage points can represent a material sum across a month or a multi-site group. Use the report to identify which dishes are drifting and trace the cause back to a specific ingredient or mapping error.

The Formula In Plain English

Recipe cost equals the sum of ingredient costs, each adjusted for yield and unit of measure. Food cost percentage equals recipe cost divided by selling price, multiplied by 100.

A worked example shows how this plays out for a dish with three ingredients.

  • Chicken breast: purchased at £8.00/kg, yield 75% after trim, portion 180g. Edible portion cost per kg = £8.00 ÷ 0.75 = £10.67/kg. Portion cost = £10.67 × 0.180 = £1.92.
  • Cream: purchased at £2.40/litre, no yield loss, portion 80ml. Portion cost = £2.40 × 0.080 = £0.19.
  • Shallots: purchased at £1.20/kg, yield 85% after peeling, portion 30g. Edible portion cost = £1.20 ÷ 0.85 = £1.41/kg. Portion cost = £1.41 × 0.030 = £0.04.

Total recipe cost = £1.92 + £0.19 + £0.04 = £2.15. Selling price = £14.00. Food cost percentage = £2.15 ÷ £14.00 × 100 = 15.4%.

Restaurant365 applies this logic automatically. Yield, unit of measure, and portion size are entered per ingredient line, and the system calculates the plate cost. Knowing the formula lets operators sanity-check the software’s output instead of trusting it blindly. If the system returns a plate cost that feels wrong, the first place to check is yield and unit of measure on the ingredient lines.

For a deeper guide to recipe costing calculators, see Recipe Costing Calculator Guide 2026: Boost UK Food Business.

Yield, Portion Size, And UOM Conversions Explained

Yield, portion size, and unit-of-measure conversions are the three inputs where Restaurant365 recipe costing most often goes wrong in a UK kitchen.

Yield is the usable proportion of a purchased ingredient after trimming, peeling, boning, or cooking. When yields are estimated rather than measured, the theoretical food cost understates the true edible-portion cost and actual-versus-theoretical variance becomes harder to interpret. A whole fish bought at £12.00/kg that yields 45% fillet has an effective fillet cost of £26.67/kg. Entering the invoice price without a yield adjustment understates the plate cost by more than half.

Portion size must reflect what the kitchen actually plates. A protein costed at six ounces but plated at seven ounces is a one-ounce over-portion worth $0.48 per plate at $7.70/lb, roughly $57.60 a night across 120 covers, or about $17,950 a year at six nights a week. In Restaurant365, portion size is entered per recipe line. If it drifts in the kitchen without being updated in the system, the theoretical food cost becomes unreliable.

Unit-of-measure conversions are required when the purchasing unit and the recipe unit differ. Buying in kilograms but costing in grams is standard in a UK kitchen. An invoice can contain the correct product and price but still generate an incorrect cost if Restaurant365 interprets a case as an individual unit or an individual unit as a case. Every conversion must be checked at setup and reviewed whenever a supplier changes pack size.

When any of these three inputs are wrong, plate costs drift and food cost percentages lose credibility. The corrective action is straightforward. Go back into the recipe, check yield, portion size, and unit of measure on every ingredient line, and update against measured kitchen reality rather than estimates.

What Restaurant365 Recipe Costing Leaves Out

Restaurant365 recipe costing works, but the real-world demands often exceed what the vendor documentation describes. The following points reflect how the system behaves in active UK kitchens.

The setup burden is manual and ongoing. Results depend on disciplined setup of items, recipes, and mapping to purchases. Every new supplier item, pack size change, or product substitution must be mapped correctly or the recipe cost is wrong. In one documented multi-brand R365 environment, more than 4,000 obsolete or duplicate recipes had accumulated before remediation, which came directly from mapping discipline slipping over time.

The system is only as good as the invoices feeding it. Inventory counts that are infrequent or inaccurate, and recipe costs that do not reflect current ingredient pricing, produce a percentage that cannot be trusted. If purchasing data is incomplete, late, or inconsistently entered, the recipe costs and food cost percentages are unreliable regardless of how well the recipes are built.

Someone has to own recipe maintenance. Restaurant365’s automatic recipe cost refresh still depends on invoice and purchasing data entering the system correctly, and on recipes, purchase records, and their relationships being maintained. In most UK kitchens, that job falls to a head chef who is already running a service.

The UK context is secondary. VAT treatment, UK supplier invoice formats, and Xero-based accounting workflows are not the context Restaurant365’s documentation is written for. UK operators frequently have to adapt their processes to fit a system built around US accounting conventions.

Cost-update lag affects decisions. If cost updates are set to nightly or manual and a supplier raises prices on a Tuesday, the recipe cost does not update until Wednesday morning at the earliest or until someone manually triggers a refresh. For a kitchen that needs to react before the next service, that lag matters.

Restaurant365 Recipe Costing Vs Spreadsheet Costing

Most growing UK kitchens start with spreadsheets because they are free, flexible, and require no implementation. The trade-off is maintenance. Every ingredient price change requires a manual update across every recipe using that ingredient, sub-recipes feeding multiple dishes become error-prone, and there are no automatic alerts when a dish crosses a food cost percentage threshold.

Restaurant365 centralises costing and updates it from invoices, which is a structural improvement over spreadsheets. Spreadsheet-based inventory combined with separate accounting software has no invoice variance tracking, no real-time food cost visibility, and no automatic COGS calculation, and breaks down entirely as location count grows.

The practical comparison is straightforward. Spreadsheets are cheap in licence cost but expensive in time and error exposure. Restaurant365 reduces manual maintenance once set up correctly, but demands a significant upfront investment in data hygiene, item mapping, and recipe build, plus ongoing discipline to keep it accurate. Total cost of ownership includes internal labour, key-person dependency, and error exposure for spreadsheets, and subscription, setup, training, data-cleaning, and support costs for integrated software.

For a structured comparison of recipe costing software options, see Recipe Costing Software Pros And Cons: A UK Operator’s Guide.

Restaurant365 Recipe Costing Vs Jelly: A Simpler Invoice-Driven Approach

Having compared Restaurant365 to spreadsheets, it is worth considering a third option built around invoices rather than manual mapping. For growing UK restaurants, pubs, and boutique hotels that want accurate recipe costing without the mapping burden, Jelly focuses on exactly that job.

Restaurant365 requires purchased items to be manually mapped before recipe costs are accurate. Jelly takes a different approach. It captures invoices by photo or email and automatically scans every line item such as quantity, SKU, price, and tax so ingredient costs populate without manual data entry. Chefs build dishes in the Cookbook by clicking on ingredients already populated from scanned invoices, and Jelly handles unit conversions and the maths instantly. What used to take 28 minutes to cost a single menu item in a spreadsheet takes around 3 minutes in Jelly.

Dish costs and gross profit margins update in real time as new invoices arrive. A red or green percentage flags margin movement the moment a new invoice posts, with no nightly update cycle or manual refresh. The Price Alert feature flags every supplier price increase or decrease, giving chefs the hard data to negotiate or claim credit notes. Stuart Noble, Head Chef at Cairn Lodge Hotel, reduced food costs by 5% in a month after switching: “Price hikes were crushing our margins, I felt helpless. With Jelly, every dish cost is up-to-date at my fingertips.”

POS integrations with Square, Lightspeed, EPOS Now, and Toast deliver item-level sales data so margins and sales mix stay live. Connecting any supported POS takes approximately five minutes, and Jelly is listed on the Lightspeed marketplace. Invoices push into Xero automatically, with Sage integration coming soon.

Jelly charges a flat £129 per month per location with no variable charge per user or feature. Onboarding generates initial value in the first week, because price alerts and spending insights go live as soon as suppliers send invoices to a dedicated email address or within 24 hours of the kitchen photographing invoices into the app.

Restaurant365 suits larger operators with dedicated office teams and the resource to maintain clean purchasing data at scale. Jelly suits growing kitchens from single-site to small groups that want accurate, invoice-driven recipe costing with far less setup and maintenance overhead.

For a broader look at how Jelly compares to other options, see Best Recipe Costing Software For Restaurants: 2026 UK Guide and Easy Recipe Costing Software: A Guide For UK Operators.

See How Jelly Automates Recipe Costing

Common Mistakes And Troubleshooting

The same issues appear repeatedly in Restaurant365 recipe costing setups that have drifted from accuracy.

  • Unmapped or incorrectly mapped purchased items. Cause: a new supplier item or pack size change was not mapped on arrival. Corrective action: audit the item list against recent invoices and remap any unlinked or mislinked items before running the Recipe Cost Report.
  • Wrong unit-of-measure conversions. Cause: purchasing unit and recipe unit were assumed to match without a conversion factor being entered. Corrective action: check every ingredient line where the purchase unit and recipe unit differ, and enter the correct conversion factor.
  • Missing or stale yield percentages. Cause: yield was left at 100% or was entered as an estimate at setup and never measured. Corrective action: measure actual trim and cooking loss in the kitchen and update yield percentages against real data.
  • Portion sizes that do not match what the kitchen plates. Cause: the recipe was costed at spec but portion drift has occurred in service. Corrective action: re-weigh portions during a service and update the recipe card to reflect actual plating.
  • Recipes never updated after a supplier change. Cause: no ownership assigned for recipe maintenance. Corrective action: assign a named owner for recipe updates and build a review trigger into the supplier onboarding process.
  • Cost update frequency set to manual. Cause: the default was left unchanged at setup. Corrective action: switch to nightly updates as a minimum, and use on-demand updates when a supplier price change is confirmed mid-week.

How To Measure Success With Restaurant365

Restaurant365 recipe costing works correctly when every purchased item is mapped, every recipe has accurate yield and portion data, plate costs reconcile against invoices, and food cost percentages are trusted enough to support pricing decisions.

Measurable indicators that the setup is functioning include:

  • Reduced time spent manually checking invoice prices against recipe costs
  • Fewer invoice discrepancies reaching the P&L undetected
  • Faster reaction to supplier price changes, measured in days rather than weeks
  • Clearer margin tracking by dish and by site
  • Menu pricing decisions made on current data rather than estimates

Food cost percentage should be tracked at minimum weekly, with daily tracking of actual-versus-theoretical variance and high-volatility ingredient usage giving the earliest signal of problems.

Advanced Tips And Next Steps For Multi-Site Operators

Operators running Restaurant365 across multiple sites can improve consistency and reduce maintenance overhead with a few structured practices.

  • Build sub-recipes for every shared component such as stocks, sauces, and dressings so a cost change in one ingredient updates every dish using that component automatically.
  • Establish a single item naming convention across all locations and enforce it at the point of supplier onboarding.
  • Assign one named owner for item mapping across the group, because distributed ownership produces inconsistent mapping and makes variance signals harder to attribute.
  • Run a menu engineering review quarterly, using the Recipe Cost Report alongside POS sales mix data to identify which dishes are high-margin and high-volume, and which are neither.

Adjacent tasks worth tackling once recipe costing is stable include connecting purchasing data to stock control, building a supplier price benchmarking process, and linking recipe costs to delivery menu pricing where commission overheads change the margin calculation.

Operators who find the maintenance burden too heavy often look at invoice-driven alternatives like Jelly, which automates the data entry that Restaurant365 recipe costing depends on. For more on what to look for in a recipe costing tool, see Best Recipe Costing Software: A UK Operator’s Guide For 2026 and Real-Time Recipe Costing Software For UK Restaurants.

Talk To Jelly About Reducing Recipe Admin

FAQ

How Often Does Restaurant365 Update Recipe Costs?

Restaurant365 offers three cost update options: nightly, on demand, and manual. Nightly updates apply the previous day’s invoice pricing to all recipes by the following morning. On demand allows a manual trigger at any point during the day. Manual means costs only update when someone actively initiates the process. For most UK kitchens, nightly is the minimum practical setting. If a supplier raises prices mid-week and the kitchen needs to react before the next service, on-demand updates are the appropriate choice. Manual updates are only suitable when purchasing data is very stable and recipe costs are reviewed infrequently.

What Is The Restaurant365 Recipe Cost Report?

The Recipe Cost Report is a reporting output within Restaurant365 that presents plate costs and food cost percentages by menu item. It calculates from the recipe data, purchased item costs, yield percentages, portion sizes, and unit-of-measure conversions entered in the system. It is the primary tool for reviewing whether dish costs are within target and for identifying which items drive food cost variance. The report’s accuracy depends entirely on the quality of the data behind it, because unmapped items, stale yields, or incorrect unit-of-measure conversions produce misleading outputs.

How Does Restaurant365 Handle Yield And Unit-Of-Measure Conversions?

Yield and unit-of-measure conversions are entered at the ingredient line level within each recipe. Yield is expressed as a percentage of the purchased weight that is usable after trim, peeling, boning, or cooking. The unit-of-measure conversion bridges the gap between how an ingredient is purchased, for example by the kilogram, and how it is used in a recipe, for example in grams or millilitres. Restaurant365 applies both inputs to calculate the true edible-portion cost per recipe unit. If either is wrong, the plate cost is wrong. Common failure points include leaving yield at the default 100%, entering estimated rather than measured yields, and failing to update conversions when a supplier changes pack size.

Who Should Own Recipe Costing In A UK Kitchen?

Recipe costing in Restaurant365 spans at least two roles. The finance or operations lead should own purchasing data hygiene, ensuring invoices enter the system correctly, purchased items are mapped accurately, and item costs are current. The head or executive chef should own recipe build, yield accuracy, and portion standards. A third owner, ideally a dedicated operations or systems role, should own the ongoing mapping of purchased items to recipes and POS menu items. In smaller UK kitchens, this third function often defaults to the head chef, which creates a maintenance burden that competes directly with running a service. Assigning clear ownership before go-live is the most effective way to prevent recipe cost drift.

What Happens When A Supplier Changes Pack Sizes?

A pack size change from a supplier is one of the most common causes of silent recipe cost errors in Restaurant365. If a supplier moves from a 5kg case to a 4kg case at the same case price, the per-kilogram cost increases. If the item mapping and unit-of-measure conversion in Restaurant365 are not updated to reflect the new pack size, the system continues calculating costs against the old pack size. The result is a plate cost that appears unchanged while the actual ingredient cost has risen. The corrective action is to update the purchased item record in Restaurant365 as soon as a pack size change is confirmed and to re-check every recipe using that ingredient for unit-of-measure accuracy. Building a supplier change notification process so pack size changes trigger a recipe review is the most reliable way to catch these before they affect margin reporting.

Can Restaurant365 Recipe Costing Work Across Multiple Sites?

Restaurant365 can support multi-site recipe costing, but it requires additional governance. The same dish can carry different costs at different sites due to local supplier contracts, different pack sizes, or location-specific purchasing. Consistent item naming conventions, a centralised item mapping owner, and a recipe approval and versioning process are all necessary to prevent variance signals from becoming unattributable. Without these controls, a food cost variance flagged at one location may reflect a mapping inconsistency rather than an operational problem, which makes it harder to act on the data with confidence.

Is There A Simpler Alternative For UK Restaurants, Pubs, And Boutique Hotels?

Jelly is built specifically for growing UK kitchens that want accurate, invoice-driven recipe costing without the manual mapping workload that Restaurant365 demands. As mentioned earlier, Jelly captures invoices by photo or email and updates costs in real time, with a flat £129 monthly fee per location and no per-user charges. For operators who find the maintenance overhead of Restaurant365 too high for their team size, Jelly is a practical alternative.

Conclusion

Restaurant365 recipe costing delivers strong results when purchased items are correctly mapped, recipes are built with accurate yields and portion sizes, and invoices enter the system cleanly. Under those conditions, the platform provides trustworthy plate costs and live food cost percentages. The mechanics are documented, while the ongoing maintenance burden often receives less attention.

UK operators with a dedicated office team and the resource to maintain clean purchasing data at scale can gain real value from Restaurant365. Growing restaurants, pubs, and boutique hotels that want accurate, invoice-driven recipe costing with less setup and mapping overhead often find Jelly a better fit. The outcome is the same, but the day-to-day friction is lower from the first week of onboarding.

For more on how UK operators are approaching recipe costing in 2026, see Best Recipe Costing Software For UK Restaurant Chefs and Best Restaurant Management Software With Recipe Costing UK.

Get A Jelly Walkthrough For Your Team