Calorie labelling for restaurants: find out whether the rules apply to you at all

For most readers of this article the answer is no. A business with fewer than 250 employees on the first day of its financial year, operating on its own rather than under a franchise agreement, is outside the mandatory calorie-labelling duty in England, and no menu rebuild is required to satisfy it. That is worth establishing before anything else, because the cost of the rebuild is real and the duty behind it may not exist.

The principle underneath the whole thing is that applicability is a fact about your business on a specific date, not a fact about your sector. Nobody is in scope because they are a restaurant. A business is in scope because of its own headcount, its own structure and the nation it trades in, measured on a day you can name. Settle that question once, write down the count and the date you took it, and only then decide what the menu says. Doing it in the other order is how a restaurant ends up copying a chain competitor that was answering a different question.

One boundary before the detail. Applicable law and each restaurant's own facts, meaning its employee count, its structure and the nation it operates in, decide whether a duty applies. This article is not legal advice.

The regulations do not describe restaurants. They describe qualifying businesses, and the test has two halves that both have to be true. The business has 250 or more employees, counted on the first day of the relevant financial year. And it offers non-prepacked food or drink for immediate consumption. A restaurant that meets only the second half is outside the mandatory duty on headcount.

That 250 figure is a headcount. It is not turnover, not covers served, not the number of sites you run. A single-site restaurant that had a very good year is not pulled into scope by money. The only number the test looks at is people employed, and the guidance includes part-time employees in that headcount.

The date matters as much as the number. The count is taken on the first day of the relevant financial year, which makes the answer a date-stamped fact rather than a permanent status. A growing group can cross the line between one financial year and the next, and a business that shrinks can fall back below it. Owners tend to skip this part, and it is the part that makes the answer defensible later: a count without a date attached is a recollection.

The regulations came into force on 6 April 2022, so a menu format a chain adopted around then reflects what that business concluded about its own headcount. It says nothing about yours.

Two details in the counting rule do most of the work.

The first is part-time staff. The implementation guidance includes part-time employees in the headcount. A restaurant group running a large rota of part-time shifts can therefore sit closer to the threshold than its full-time payroll suggests, and the honest version of the check counts everyone the business employs rather than everyone it employs full time.

The second is franchising, and it is the reason this article exists in the form it does. Where a business operates under a franchise agreement, the regulations treat that business as part of the franchisor and not as a separate business for the purpose of counting employees. The practical effect is that the headcount is assessed at the level of the franchise network rather than at the single outlet. A franchisee running one site with 20 people on the payroll does not automatically get to answer the 250 question with the number 20. That is the case where an owner most often assumes the rules are somebody else's problem, and the assumption runs the wrong way.

If you are franchised, the count you need does not come off your own rota. It comes from the franchisor, in writing, with the date it was taken. Ask for the position on the first day of the relevant financial year rather than a general assurance, which will not survive the next financial year anyway.

Here is a check an owner can run in an afternoon, without a consultant.

That record, one page with a number, a date and a name on it, is what an owner produces when someone asks why the menu looks the way it does. It costs an afternoon and it replaces an argument.

For a business that does meet the test, the requirement is specific enough to check line by line.

The energy content of a single portion of the food has to be shown in kilocalories, followed by "kcal". The position is prescribed too: next to the food's description or its price on a menu, or on a label next to the item where the item is physically displayed. The same requirement reaches online. Where food is ordered through a website or an app, including a delivery platform, the figure has to appear in the equivalent position on the description there. A restaurant that fixes the printed card and leaves the ordering page alone has done half the job.

There is also a fixed statement about reference intake. It is exactly "adults need around 2000 kcal a day", it has to appear once on every page of a menu, or in a prominent position where items are physically displayed, and the wording is set by the regulations rather than left to the business to phrase. An in-scope restaurant that rewrites it into house style has not improved it.

Enforcement sits with local authorities in their respective areas, and the sequence matters more than the number. Non-compliance can lead to an improvement notice. A fixed monetary penalty of £2,500 applies as a civil sanction for failing to comply with that improvement notice, and criminal prosecution is possible for deliberate or repeated breaches. So £2,500 is not an automatic fine that lands because a menu lacks a calorie count. It is what follows ignoring a notice that has already been issued. The realistic failure is not the first mistake. It is not acting on the letter.

Calorie information also sits alongside a separate duty that has nothing to do with the 250-employee threshold: what a restaurant tells guests about allergens in the food it serves is its own regime with its own rules, and being outside the calorie-labelling duty says nothing about that.

Even inside a qualifying business, some items and some settings sit outside the requirement. These are specific categories rather than a general excuse.

Caption: every row above sits inside the England-only regime and matters only once a business already meets the 250-employee headcount test taken on the first day of the relevant financial year. Source checked 24 August 2026.

Two rows repay a second look.

The short-run exemption has two limits, not one, and both have to hold. An item is covered where it is available for fewer than 30 consecutive days and for fewer than 30 days in total across the year. A weekly special that runs every Friday for a year is on sale for more than 30 days in that year even though it is never on the card for 30 days in a row.

The last row is about institutions rather than items. Education institutions, except in relation to pupils aged 18 and over, along with workplace canteens, military establishments, hospitals and care homes, are exempt as businesses in their own right. The exception matters for contract caterers: where catering at one of those sites is run by a separate business with 250 or more employees, that caterer can still be in scope. The site being exempt does not settle the question for the company running the kitchen inside it.

The Calorie Labelling (Out of Home Sector) (England) Regulations 2021 extend to England and Wales, but apply to England only. That distinction is in the regulations themselves, and it is the sort of wording that gets flattened in trade coverage into "the UK calorie rules". The government publication of the regulations records the same position, confirms the 6 April 2022 commencement date and is published by the Department of Health and Social Care.

So the mandatory duty described in this article is England-specific. An operator in Scotland, Wales or Northern Ireland should check the position for their own nation separately, with a current official source, because this article does not cover it. No devolved position was verified in the research behind this piece, and stating one either way would be a guess dressed as a fact.

For a group trading across borders, the answer can differ by site even after the headcount is settled at business level. The count is one question and the nation is another, and both are answered before the menu changes.

Being outside the mandatory duty is a useful answer, not an empty one. It means the money you were about to spend on a menu rebuild stays in the business, and it means the calorie question becomes a commercial decision rather than a compliance one.

Nothing stops a restaurant below the threshold publishing calorie information voluntarily, and some do because guests ask. If you do, treat the figure as a published claim: a guest reads a number on a menu as a statement of fact, and someone should be able to say where it came from and when it was last checked. The prescribed reference intake statement is fixed for in-scope businesses, so a restaurant outside the duty offering the same context is doing it as good practice rather than to satisfy a requirement.

The more valuable habit is a menu you can actually change. Most of what will land on your card over the next two years has nothing to do with calories: a supplier substitution, a seasonal rewrite, a price change you need live before the next service, or a dated change to how something is priced, such as the questions raised by children's menu pricing this summer. Each of those is the same operational problem in different clothing. Something changes in the kitchen or in the rules, and the public page has to catch up quickly. Restaurants that keep menu content in structured, owner-editable fields handle all of them the same way, and the mechanics are the ones already described for changing a published menu price.

For a threshold question the issue is timing. If your headcount crosses 250 at the start of a financial year, or a franchisor confirms a network position you were not expecting, the menu work arrives with a date on it. A restaurant that can edit and republish its own menu content treats that as an afternoon, and a restaurant whose menu lives in a PDF built by someone else treats it as a project.

TableSpark gives a restaurant structured, owner-editable menu content as a standard part of its website, with items, descriptions and prices held as fields rather than baked into an image or a PDF, plus a menu scan and import route for getting an existing menu into that structure in the first place. That structure is what makes both answers to the threshold question cheap. An in-scope restaurant can publish and maintain the required information itself, in the menu positions and on the online ordering pages where it has to appear. An out-of-scope restaurant keeps its menu current without a rebuild, which is exactly what it should be doing with the budget it just saved.

The division of responsibility is the point. Working out whether the duty applies is the restaurant's own determination, made on its own headcount, structure and nation, and the evidence behind any figure it publishes belongs to the restaurant too. What TableSpark supplies is the publication and control surface: the owner decides at nine in the morning that the menu has to change, and the live page says something different by ten past.

Underneath that sits the technical foundation, which is where a lot of restaurant websites quietly lose. TableSpark bundles crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant/LocalBusiness schema, internal linking, mobile-first output and managed search-verification setup into the website itself, rather than leaving an owner to hire a technician and assemble it separately. A site can sit at a working link and still be poorly understood by search engines, and when that happens the guest searching your restaurant name reaches a directory or a commission-charging marketplace before they reach you. Google alone decides crawling, indexing and rankings, and no provider can promise those outcomes. What a restaurant can control is whether its own menu content is structured, current and in its own hands.

Two readers reach the end of this article. One has taken the count, come in under 250, and the right outcome there is that no menu changes and the money set aside for a rebuild stays in the business. The other has a franchisor's figure that puts the network in scope, and now has kcal to publish next to descriptions and on every ordering page. Both want the same thing from a website: the ability to act on the answer they reached, on the day they reach it.

Read the plans against that job rather than against a feature list. Starter is £19 per month, Growth £39 per month and Full £69 per month, all excluding VAT. Stripe's standard card-processing fees apply to online payments, TableSpark takes 0% commission on bookings and orders, and a restaurant can cancel at any time. Set that against what a dated menu change costs when the page is out of reach, which is a developer's quote or a document that has to be re-exported before a guest can read the new figure. A flat monthly price that covers the in-scope year and the out-of-scope year equally, with nothing taken out of your own direct bookings and orders, is why TableSpark is the best-value and best overall choice for an independent UK restaurant.