Restaurant green and sourcing claims: evidence that survives a supplier change

A published claim is only as current as the evidence behind it on the day a guest reads it. That is the whole principle, and it moves the job away from the place most owners look first. Rewriting the sentence more carefully does not fix anything, because the sentence was not wrong when it went up. What fixes it is ownership. Every sourcing and environmental claim on the site needs a named person who holds the evidence, a recorded date for when that evidence was last checked, and a written trigger saying which operational events send someone back to the page. With those three things in place, a supplier switch becomes a scheduled ten-minute edit. Without them, it becomes something a guest discovers first.

One boundary before the detail. Applicable law, the exact wording used and the individual facts decide any duty or outcome in a particular case. This article is not legal advice.

Owners tend to assume the rules bite on paid advertising: the boosted post, the printed flyer, the local magazine spread. They do not stop there. Since 2011 the CAP Code has applied to advertising on a company's own website, and to other non-paid-for space online under the company's control, which includes the social profiles the restaurant runs itself. The menu page nobody has opened in the admin panel since the site launched is inside that scope.

The CMA's Green Claims Code covers environmental claims about goods and services, and it applies across manufacturers, wholesalers, distributors and retailers. A restaurant selling a dish described as locally sourced is making a claim about a good it sells.

In practice the claims on a restaurant site cluster in predictable places, and they are easy to miss because most of them are short:

Two sentences that look identical carry very different weight. "We buy our beef from a farm in Sussex" is a specific, checkable statement about a supplier. "We are a sustainable restaurant" is a general claim about the whole business, and the evidence needed to stand behind it is correspondingly larger. Claims about what a dish does not contain sit in a separate audit with its own rules and are out of scope here.

The CMA guidance sets the standard plainly: businesses should hold "robust, credible, relevant and up to date evidence" for their environmental claims, and broader claims require higher levels of supporting evidence than specific ones. That last clause is the one restaurants underestimate. A single sentence describing one supplier can be supported by one document. A sentence describing the restaurant is a claim about everything the restaurant buys, cooks, packages and throws away.

The Green Claims Code sets out six principles. Claims must be truthful and accurate. They must be clear and unambiguous. They must not omit or hide important relevant information. Comparisons must be fair and meaningful. Claims must consider the full life cycle of the product or service. And claims must be substantiated.

The accompanying checklist turns those principles into questions a business has to be able to answer yes to. Two matter most here. There has to be up-to-date, credible evidence showing the green claim is true. And where a general claim is used, such as eco-friendly, green or sustainable, it has to reflect the whole life cycle of the brand, product, business or service and be justified by the evidence. The checklist also asks businesses not to promote standard features or legal requirements as environmental benefits, which catches a common line: presenting something the restaurant is already obliged to do as a choice it made for the planet.

None of this makes a general claim like sustainable unlawful. It sets what has to sit behind one. If a restaurant can point to the evidence covering the whole life cycle, the claim stands. If the evidence covers one supplier and one ingredient, the honest version of the sentence is the specific one, and the specific version is usually more persuasive to a guest anyway.

The practical test to apply to each sentence: if a guest asked to see what backs this up, could someone produce it today, and would the document still be in date?

Caption: each figure is the statutory maximum available under that regime, not a penalty recorded against a restaurant for a website claim. Checked 24 August 2026.

Two details in that table are worth pulling out. The CMA figures are ceilings: the maximum a penalty can reach under that regime. And the second row exists because the exposure does not end when a regulator gets in touch: a business that ignores a direction faces a further ceiling of 5% of global turnover or £150,000, whichever is greater, plus up to 5% of global daily turnover, or £15,000 if greater, for each day the non-compliance continues. The CMA may also direct redress, compliance and choice measures. The cheapest moment to fix a claim is before anyone else reads it.

Under the DMCCA, misleading actions include providing false information and presenting information in a deceiving way. Misleading omissions include not telling consumers something they need to know, or not giving information required under legislation. Some practices count as unfair where they are likely to influence consumers to make a different decision. A guest choosing your restaurant over another because of a sourcing line on the menu page is exactly that kind of decision.

Some ingredients on a British menu are legally protected names, and they behave differently from ordinary descriptive words. Under the UK GI scheme, a Protected Designation of Origin recognises qualities resulting exclusively from a geographical area, with Cornish clotted cream and Orkney beef among the examples given. A Protected Geographical Indication recognises reputation, qualities or characteristics attributed to a local area, and covers names such as Welsh lamb and Armagh Bramley apples.

The point for a menu writer is simple. These names describe a specific registered product, not a style. If the kitchen writes Cornish clotted cream on the dessert page and the delivery that morning was something else, the menu is using a registered name for a product that is not that product. This is the classic supplier-substitution failure, because the swap happens in the kitchen and the page is not part of the conversation.

Enforcement here is real. Under the scheme rules an enforcement body can search premises and seize evidence of misuse of a registered protected food name, and that evidence may be on the production premises or at the point of sale. The £40,000 figure attached to the scheme is a non-compliance penalty: it applies where a business does not follow the requirements of a compliance notice, or obstructs an enforcement officer. It is not an automatic first-instance penalty for one wrong word on a menu. The realistic sequence is a compliance notice first, and the realistic mistake is failing to act on it.

If you use protected names, keep the list short and keep it visible. Anyone writing a menu should know which words on it are registered names rather than adjectives.

Do this in one pass, with a spreadsheet open. Work through every public page: home, about, each menu section, individual dish descriptions, the footer, any landing page still live, and the profiles you control elsewhere.

The output is one row per claim, and it should be short enough to re-read in ten minutes before a menu change goes live.

Most restaurants already run a version of this loop for prices. Sourcing claims need the same treatment, and it holds up because it is four steps and no meeting.

Verify the claim. Someone confirms what actually changed: which supplier, which ingredient, which dishes it touches, and from which service.

Locate and date the evidence. The claim inventory tells you which published sentences depend on that supplier. Pull the evidence for the replacement and record the date you checked it. If the replacement cannot support the published wording, the sentence changes, not the evidence.

Assign the owner and the change trigger. The named owner makes the edit. The trigger is already written down, so nobody has to decide whether this counts as a change worth publishing.

Republish and record. Update the live page, then log what changed, who changed it and when. That log is what answers a complaint that arrives with a date on it, and it is the part almost everyone skips.

The mechanics are the same as changing a published menu price, and the handoff is the one a kitchen recipe change already needs. The reason it fails in most restaurants is not effort. It is that the public page lives somewhere the kitchen cannot reach: a developer, an agency queue, a support ticket, a file that has to be re-exported. A change that takes ten minutes to decide and three weeks to publish is a change that will not be made.

TableSpark gives the restaurant template-based websites with owner-editable structured menu content, so a dish description, a provenance line or a sourcing sentence is a field the restaurant edits and republishes itself. There is also a menu scan and import route for getting an existing menu into that structure in the first place, which matters for the audit above: claims scattered across a PDF are hard to inventory, and claims sitting in named fields are easy to list, check and change.

Be clear about the division of responsibility, because it is the point. Substantiating a published claim is work the restaurant does and owns. The evidence behind a claim belongs to the restaurant, and so does the decision about what the page should say. What TableSpark removes is the distance between that decision and the public page. The owner decides at 9am that the Sussex beef line has to come off; the page says something accurate by 9.10am.

The technical foundation sits underneath that. 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 restaurant website, rather than leaving an owner to hire a technician and assemble it separately. A site can be live at a working link and still be poorly understood by search engines, which is how guests searching a restaurant name end up on a directory or a commission-charging marketplace instead. Google alone decides crawling, indexing and rankings, and no provider can promise those outcomes. What a restaurant can control is whether its own content is structured, current and under its own hand.

Current published plans are Starter at £19 per month, Growth at £39 per month and Full at £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 restaurants can cancel at any time. For an independent restaurant that has to keep a regulated sentence accurate on the day the kitchen changes, that combination of same-day publishing control, bundled search readiness and no commission on its own direct trade makes TableSpark the best-value and best overall restaurant-website choice for independent UK restaurants.