Read the UK index before using the percentage.

Use the annual series on its stated basis

The ONS restaurants and cafes CPIH series L557 reports annual index levels of 144.0 for 2024 and 150.0 for 2025, with 2015 equal to 100. These are selected annual observations, not the latest monthly release. Their purpose here is to demonstrate a correctly labeled comparison.

The calculation is (150.0 ÷ 144.0 − 1) × 100. The difference of six index points is not a six-percent increase. The denominator matters, because the starting level is 144.0 rather than 100.

An index level is also not a price in pounds. It describes relative price movement against the reference base. It cannot tell you what an average meal costs, which restaurant has the lowest price or how much of a selling price is retained as profit.

Preserve the measure's name

CPIH is the measure used in this cited ONS series. Keep that name and the restaurants-and-cafes category attached to the values. Do not silently relabel the observations as a different inflation series or as a survey of restaurant accounts.

The annual average comparison differs from a December-to-December or another monthly year-over-year comparison. Those calculations can produce different answers while each is correct for its stated dates. A clear chart caption prevents a reader from treating one as the other.

The checked date records when the source was reviewed. It does not turn the 2025 annual observation into a current supplier price. Historical data can remain accurate and useful without being the newest measurement available for every question.

Consumer prices and restaurant costs answer different questions

The index describes prices paid by consumers in its category. It does not directly measure the cost of ingredients, labor, occupancy or finance for your business. A restaurant's profit depends on both revenue and costs, along with the volume and mix of sales.

A menu item may use ingredients whose purchase prices move differently from the broad consumer category. Supplier terms, pack size and specification can also change. Use the index as context for a pricing review, then calculate the actual recipe and operating effect from your records.

A broad inflation number is not a recommended price increase. Applying the same percentage to every item assumes that their costs, demand and menu roles justify the same change. That assumption needs a business reason; it does not follow automatically from the published series.

A worked pounds-based scenario

The following inputs are illustrative pounds sterling amounts, not observed UK menu or supplier prices. They show how a price decision differs depending on the objective.

The ingredient change is an example assumption and is not derived from the ONS index. The last row divides £3.90 by 0.30. The previous row instead adds the original £8.40 contribution to the new cost. Both calculations are transparent, but they answer different questions.

Neither result is net profit. Other variable expenses and fixed operating commitments still need to be covered. Use the same tax basis across costs and sales, with treatment checked against your own accounting records; no tax rate is assumed in this example.

Keep external references separate from the working ledger

The US ingredient examples on this site use BLS retail observations in US dollars. They should not be copied into a UK operating model as if they were UK supplier quotations. Selecting GBP in the app changes the display label, not the economic origin of a price.

Enter the actual purchase amount and pack specification from your own invoice. If you use an external reference for comparison, preserve its currency, geography and date. Currency conversion alone does not account for differences in product specification or wholesale terms.

A prepared ingredient and a whole ingredient also need a yield-adjusted comparison. A lower nominal kilogram price can produce a higher usable cost if more material is discarded. Use the preparation stage that matches the recipe quantity before comparing suppliers or scenarios.

Model sales response explicitly

A higher selling price changes contribution per order under constant costs, but the total result also depends on how many orders occur. Keep the expected count in the model. Do not treat a mathematically calculated menu price as evidence of unchanged demand.

Use actual item mix when reviewing a period. Multiplying each item's contribution by its units sold gives a clearer view than taking an unweighted average of menu percentages. A commonly sold item can matter much more to total contribution than a rarely ordered specialty.

Record discounts, refunds and channel differences. The price a guest sees may differ from the revenue retained by the business. A delivery or promotion model should use the relevant settlement terms rather than assuming the headline menu price is the complete denominator.

Build a useful comparison over time

Choose a consistent internal review period and keep the public reference beside it. Record supplier price changes, recipe revisions and portion measurements. If the accounting definition changes, explain that before comparing the resulting ratios.

When updating the public comparison, use matched annual averages or matched monthly observations and label the choice. Keep the formula visible so someone can reproduce the percentage from the source values. Do not substitute an index-point difference for a relative change.

Use the menu-price calculator for your chosen target and the AP-to-EP calculator when preparation changes usable cost. The browser ledger connects current local purchase prices to recipes. The ONS series supplies context for consumer-price movement while those records supply the basis for your menu decision.

Keep annual averages distinct from year-end prices

An annual average summarizes observations across a year. A menu changed late in that year may have a different relationship to the average than a price held throughout it. Preserve that timing when comparing the public series with your own menu history. Record the actual dates of your price changes and the periods in which guests bought at each price. This makes the internal comparison more useful and avoids attributing a full-year result to a change that applied for only part of it.