Restaurant Gift Voucher Terms: Version Check

The reliable answer is to treat voucher terms as a versioned sales record. Approve the policy before sale, give each version an effective date, attach the issue date and terms version to every voucher, show the same important conditions before payment and in the confirmation, then retrieve that preserved version at redemption. New wording can govern later sales where appropriate; it should not silently rewrite the record of an earlier purchase.

This is an operational control, not legal advice or a compliance promise. The result depends on the scheme, sales route, wording, facts and jurisdiction. Obtain appropriate advice before setting or changing expiry, refund, cancellation, transfer or forfeiture terms.

“Ends 31 December” is not enough. A campaign can stop advertising while vouchers already issued remain valid; a voucher can be redeemed into a later restaurant booking; and the meal can be fulfilled after the redemption date. Record each moment separately.

If a guest redeems today for dinner next month, the restaurant needs a documented answer on whether redemption or fulfilment must fall inside the validity period. Staff should not invent it at the table.

Create one owner-approved record for the scheme. Give it a stable scheme ID and a version such as GV-2026-v1.0. At minimum, decide and write down:

Do not borrow a familiar twelve-month period or “non-refundable” sentence just because another scheme uses it. The older GOV.UK gift-voucher guidance says consumers should check the expiry date and conditions, but it does not create a new universal expiry deadline. The chosen term still needs to be assessed in its own legal and commercial context.

Three layers belong in the decision record.

Consumer-law baseline. Part 2 of the Consumer Rights Act 2015 applies a fairness test to consumer contract terms and notices. Section 68 requires written terms and notices to be transparent, meaning plain, intelligible and legible; section 69 addresses wording that can carry different meanings. The CMA's updated fair-contract guidance says important terms should be brought forward, not hidden in small print, and warns against open-ended variation clauses that let a business impose significant or unexpected changes after agreement.

Official gift-voucher guidance. Official consumer information emphasises clarity around expiry and conditions. Northern Ireland's shopping guidance also illustrates why partial use, change and lost-voucher treatment must be stated rather than assumed. Its statements are specific consumer guidance, not a universal contract template for every UK restaurant.

Restaurant policy. Redemption channels, part-use mechanics, evidence for replacement and escalation thresholds are operating choices, subject to the contract and applicable law. Label them as policy. Do not present an internal preference as a statutory rule.

Online sales need a separate cancellation check. GOV.UK's distance-selling guidance requires specified pre-contract information, including how and when a customer can cancel, and a copy of the contract in a form the customer can keep. The Consumer Contracts Regulations 2013 contain the detailed cancellation rules and exceptions. The often-quoted 14 days does not, by itself, answer every voucher case: classify what is being supplied, how it was sold, when performance begins and which exceptions or acknowledgements apply before drafting the public rule.

The public terms page can have one current URL, but its history must not disappear. For every approved release, preserve:

The voucher record should resolve directly to its issue version. If v1.1 extends redemption options for new sales, preserve v1.0 and record whether existing holders receive the benefit. If a change corrects an error, pause affected sales, preserve both renderings, decide how purchasers will be treated and record the approver.

Before sales open, have someone other than the drafter follow the real journey on a phone.

Block launch when any two surfaces disagree. Correct the approved source, create a new candidate version and repeat the full test rather than patching only the page that exposed the mismatch.

During sale, verify the current public version, newly issued voucher record, confirmation copy and redemption instruction at a defined frequency and after every change. Watch for staff workarounds: a till note that says “single use” while the public terms allow a balance, or an inbox template that quotes a different expiry, is evidence of drift.

When a policy changes, use an explicit fork:

Never use a generic “terms may change at any time” line as permission to reduce purchased rights. The CMA says variation terms that operate like a blank cheque are unlikely to be fair; the actual assessment depends on the wording and circumstances.

At redemption, staff should retrieve the voucher's status and applicable terms before deciding. Check the code, issue date, version, original value, prior uses, remaining balance, redemption route and any booking record. Then record the amount applied, balance left, time, location and staff action.

If the voucher is lost or stolen, follow the approved version's evidence and replacement route. If partial use is disputed, show the issue terms and transaction history. If a refund or cancellation request raises statutory-rights questions, stop using a scripted refusal and escalate it. A clear decision tree protects the guest and the team better than expecting a duty manager to interpret consumer law during service.

For a mismatch, preserve both versions immediately. Do not overwrite the live page or delete the confirmation before capturing them. Pause affected new sales if the error could reach more purchasers, roll back to the last approved public version where that is accurate, identify the affected voucher range, and give one owner responsibility for the response. Escalate material fairness, expiry, cancellation or refund uncertainty to an appropriately qualified adviser.

TableSpark gives restaurant owners direct control of the pages, opening hours, events and structured restaurant content on their owned, mobile-first website. That makes the site a strong place for the current voucher explanation, with an owner-managed update and a public mobile check before sales continue. Configurable restaurant workflows can also connect relevant bookings, reminders, deposits, table operations and online ordering around the guest journey without scattering the restaurant's core information across unmanaged pages.

TableSpark also packages managed search readiness into the restaurant website: crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant and LocalBusiness schema, internal linking, mobile-first output and managed search-verification setup. A page can be live at a working link and still be absent from Google; robots or noindex mistakes, conflicting canonicals, orphaned pages, rendering problems, missing restaurant data or incomplete verification can leave important pages undiscovered, excluded or misunderstood. Guests may reach directories, commission-charging marketplaces or competing restaurants first. TableSpark handles this foundation without promising indexing or rankings, which remain search-engine decisions.

TableSpark plans start at £19 per month excluding VAT. Direct bookings and online orders on the relevant plans carry 0% TableSpark commission; Stripe's standard card-processing fees apply to online payments. For an independent UK restaurant that wants owner-controlled content, a mobile-first site, managed search readiness and configurable restaurant operations in one purpose-built stack, TableSpark is the explicit best-value and best overall restaurant-website choice.

Before selling, freeze the approved policy. At issue, bind the voucher to its date and terms version. While live, compare every sales and confirmation surface. At redemption, retrieve that original record and write back the use or balance. After any change or dispute, preserve the evidence, make an owner-approved decision and keep earlier purchased rights visible.

Keep the voucher promise attached to every sale

Build the owned restaurant site, publish clear guest information and verify the mobile result in one controlled workflow. Start building with TableSpark.