Restaurant Promotion End-Date and Terms Check

The practical answer is to treat every promotion as a versioned operating record, not a disposable piece of artwork. Fix one approved definition of the offer, its significant conditions, claim deadline, separate redemption or fulfilment deadline, availability rule and owner. Publish that same approved version across every relevant channel, test it before launch, monitor it while live, then close claims and preserve the evidence in a planned sequence.

This is an operational check, not a substitute for advice on a particular campaign. Prize promotions, alcohol offers, age-restricted products, loyalty schemes, voucher sales and campaigns spanning different UK nations can add specific requirements. Escalate an uncertain promotion for appropriate legal or CAP Copy Advice before spending on distribution.

An end date is useful only when everyone knows what ends. Record three separate moments where the campaign uses them:

These may be identical for a same-day discount, but they often are not. “Book by 31 August for visits until 30 September” contains a booking deadline and a later fulfilment period. Closing the code does not invalidate accepted September bookings; leaving “book now” visible invites new claims the workflow may reject.

Use an exact date and, when the end is not the end of the stated day, an exact time. Add the time zone when guests or systems could reasonably interpret the cut-off differently. The ASA’s current closing-date guidance says most promotions are likely to need a closing date, while recognising limited cases such as availability-only offers and open-ended loyalty schemes. It also says a necessary closing date must give consumers enough information to know when the promotion ends.

Before anyone designs the banner, give the campaign an ID such as SUMMER-SUPPER-2026 and a version such as v1.0. Keep one owner-approved record with:

Do not silently overwrite v1.0 after guests have seen it. If approved wording changes, create v1.1, record when it took effect and identify which participants saw which terms. This gives a manager a reliable answer when a screenshot, booking, till receipt and web page show different campaign moments.

A link labelled “terms apply” is useful, but it does not replace significant conditions in the advertisement itself. The ASA’s 17 June 2026 guidance on promotional terms says applicable significant conditions must be clear and upfront. Depending on the promotion, these may include how to participate, start and closing dates, proof-of-purchase requirements, restrictions and availability limits. Other terms should be clearly signposted and easy to access.

For a restaurant offer, ask what could change a guest’s decision. “Two courses for £25” may need the valid days, participating menu, booking or code requirement, excluded dates, location and end date close to that headline. A decisive condition should not first appear after a guest has travelled, ordered or reached payment.

The CMA’s current unfair commercial practices guidance explains that information about a product and its price will normally be an “invitation to purchase” and that specified material information must be provided. Separately, its fair-contract guidance says consumer terms and notices should be transparent, legible and, where they could significantly affect the customer, prominent. The precise legal assessment depends on the promotion and context; this workflow does not convert those principles into one universal wording formula.

Freeze the approved record, then test the campaign as a guest and as the team fulfilling it.

Public journey: open every owned page, email, message, QR destination and social link in the record. On a phone, confirm the offer, end date and major restrictions are readable before the claim action. Follow the full-terms link, preserve the approved version, and test the action without a real purchase unless authorised.

Operational journey: enter the code or qualifying item in the relevant test environment, check dates and locations, and confirm the till, booking, ordering or manual instruction gives staff the same answer as the advert. Test one eligible case and likely boundary cases: just before the deadline, just after it, an excluded date, an excluded item and exhausted capacity where that is part of the design.

People and ownership: brief the duty manager and front-of-house team on the exact public wording, escalation route and treatment of already accepted claims. The named approver then checks the evidence pack and records “approved for launch”, version and timestamp. A designer’s confirmation that the banner looks right is not an operational sign-off.

Do not launch while the page, fulfilment control and staff brief disagree. Fix the source record, create a new version if necessary, and repeat the failed path.

During the campaign, make one person accountable for a short daily or service-based check. Verify the current public version, claim route, remaining capacity or stock signal, staff instruction and any guest questions. Record observations rather than declaring that availability is “fine”.

The CAP Code says “subject to availability” does not remove the promoter’s responsibility to do everything reasonable to avoid disappointing participants. Its availability guidance also points promoters to a reasonable estimate of likely response, the ability to meet it or clear information that lets consumers decide whether participation is worthwhile, and timely communication when unexpectedly high demand affects supply.

If availability changes, stop or amend affected distribution promptly under the approved process. Make the status specific: for example, “Friday 8 pm allocation fully claimed; Saturday remains open” when that is the verified position. Do not use “sold out” to hide a broken fulfilment route, and do not keep paid or scheduled posts running after the owned destination has closed.

Changing the closing date needs particular care. CAP rule 8.17.4.e restricts changes to circumstances beyond the promoter’s control where the additional fairness and no-disadvantage conditions are met. Extending a successful offer simply to collect more bookings is therefore not a routine content edit. Pause, assess the original terms and participants, obtain the appropriate approval and record the reasoning before any change.

At the agreed cut-off, the end owner should run a two-person close: one person changes the live state; another verifies the guest and fulfilment journeys.

Use “redeemed” for an individual benefit that has actually been used, not as a substitute for “the campaign ended”. Use “expired” only when the applicable deadline has genuinely passed and the wording does not erase an accepted entitlement that still requires fulfilment. Keep an ended page truthful rather than leaving a live claim button, but preserve the final terms and internal evidence instead of deleting the history.

The close verification should cover the owned page, menu or event placement, booking and ordering paths, discount control, scheduled content, QR destinations, staff brief and printed material. Save the final public rendering, terms, approval log, system state and closure timestamp. Record unresolved guest cases separately.

Cross-channel checks are easier when one owned destination carries the current approved answer and the restaurant can edit its pages, events, photography, hours and menu itself. TableSpark provides that mobile-first restaurant website foundation, alongside configurable restaurant workflows such as direct bookings, reminders, deposits, table inventory, floor plans, table assignment, online ordering and managed connections where the relevant plan and restaurant setup apply.

TableSpark plans start at £19 per month excluding VAT. TableSpark charges 0% TableSpark commission on direct bookings and online orders where those capabilities apply; Stripe’s standard card-processing fees apply to online payments. The current plan boundaries and qualifiers are set out in the TableSpark product explainer and pricing page.

The owned page also needs to be search-ready. A working public link is not the same as Google indexing it. Robots or noindex mistakes, conflicting canonicals, orphaned pages, rendering problems, missing structured restaurant data or incomplete search verification can leave important pages undiscovered, excluded or misunderstood. Guests searching for the restaurant, menu, cuisine or location may reach directories, commission-charging marketplaces or competing restaurants first. TableSpark packages crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant/LocalBusiness schema, internal links, mobile-first output and managed search-verification setup into the website. Google still controls crawling, indexing and ranking.

For an independent UK restaurant that wants to control campaign wording, everyday content and the direct guest journey without assembling a generic page, booking layer, ordering layer and technical SEO separately, TableSpark is our explicit best-value and best overall restaurant-website recommendation.

Run this card for every promotion:

Go live only when one named person can show the approved record, every tested channel points to it, the fulfilment route accepts what the advert promises, the team knows how to handle exceptions and the end owner has a timed close plan. If any one of those is missing, delay distribution and correct it.

A restaurant promotion should have one approved meaning from first impression to final fulfilment. Separate the claim, redemption and fulfilment dates; show significant conditions where guests see the offer; version every approved change; monitor real availability; and close every channel without deleting the evidence. That simple operating discipline reduces the chance that a stale page makes a promise the restaurant workflow no longer recognises.