Restaurant gift card launch checklist: from first brief to first redemption

1. Start with the restaurant, the customer and one clear offer

Start with the question a purchaser wants answered: what will the recipient actually be able to enjoy? A gift card with a cash value, a tasting menu experience and a promotional voucher create different expectations. Choose the offer before choosing the artwork. Staff should be able to explain it in the same words as the website.

For a hypothetical Belfast neighbourhood restaurant, the first offer might be a digital gift card in three values, redeemable towards an ordinary dining bill. That is a planning example, not a client result. The example keeps the first launch manageable: one venue, one currency and a clear purchase journey that the team can rehearse.

Write the exclusions and awkward questions alongside the offer. Can the card cover drinks, takeaway orders or a private event? What happens if a menu price changes? If you cannot give a settled answer, keep that question open in the brief and resolve it before taking payment.

When you compare gift card systems for British restaurants, you will find plenty of feature lists. Use your brief to check whether those features suit your service, customers and working day.

Write down what the team must be able to do before launch. For this fictional venue, success might mean that a new server can redeem a card correctly using the handover, while the manager can trace the payment without asking the developer. You can check both tasks during the rehearsal. An ambition such as sell lots of gift cards is harder to use when deciding whether the service is ready.

Keep a decision log with four short fields: question, agreed answer, owner and date confirmed. Record whether an answer came from management or the supplier. This prevents a suggested feature from becoming a customer promise merely because it appeared in an early email. Review that log when signing off the public wording.

• Name the venue, offer, launch owner and intended launch date.
• List accepted uses and questions requiring a management decision.
• Record who approves the wording customers will see.

2. Decide whether you need digital, physical or both

Digital delivery can suit a purchaser arranging a gift at short notice. A physical card may suit someone buying at the restaurant or wanting something to put in an envelope. Neither format removes the need for a reliable balance record. Decide how each format connects to that record and how staff recognise the same card across formats.

Do not treat a printed card and a separate digital code as two unrelated promises. Ask the supplier to demonstrate whether both point to one balance, or whether you are proposing two different products. An attractive print design is not evidence that stock, activation or redemption will work together.

The existing Podium Cards service describes digital delivery by email, Apple Wallet and Google Wallet. Physical card printing is a separate requirement to discuss, rather than something to assume from the name. Likewise, scheduled delivery, recipient editing and customised messages should be confirmed in the proposed setup.

For an initial launch, fewer formats can make staff training easier. If physical cards are essential, include ordering time, secure storage, replacement procedures and responsibility for unsold stock in the schedule. Test the actual format you plan to give a customer.

3. Make the purchase page answer practical questions

A purchaser should understand the restaurant, the value and the delivery method before paying. Show the restaurant name consistently, use readable text and explain whether the buyer or recipient receives the card. Check the journey on a phone with a short message and an unusually long name, rather than reviewing only an empty desktop form.

Agree the card values using the way customers dine with you. A value may contribute towards a meal without covering every possible bill. Avoid promising a complete experience unless the offer actually includes it. If the card is money towards a visit, say so plainly and explain how a remaining bill is paid.

Put the important conditions where people can find them before checkout. Confirm the wording for validity, restrictions, cancellations and support with the person responsible for your business terms. There is no universal expiry or refund wording to copy safely from another restaurant.

Finally, check the confirmation. It should make the next step obvious: where the gift arrives, how the recipient presents it and how to ask for help. The customer should not have to infer those details from an attractive card image.

The Podium Cards demonstration lets you explore the purchase fields and recipient preview without a payment or an email being sent.

• Check every advertised value and the displayed currency.
• Read the purchase and recipient emails on a small screen.
• Check the support address and restaurant contact details.

4. Put business ownership and staff access in writing

The person who sets up a gift card account is not always the person who should control it long term. A manager, designer or temporary colleague may help launch it, but the restaurant needs a clear owner for access and recovery. Use contact details controlled by the business where the service allows them and record who can make changes.

Separate the job of accepting a card from changing business settings. Ask what permissions exist for checking balances, redeeming value, issuing refunds and downloading records. Where a system has fewer permission options than you want, agree the practical supervision needed rather than assuming a hidden setting will solve it.

For payment processing, confirm which business owns the connected payment account and who checks the bank details. Do not copy access details into a shared launch document. Keep the brief focused on responsible people, approved access methods and the process for a change of manager.

An export is worth testing before it becomes urgent. Ask which customer details, transaction references and outstanding balances you can retrieve, and whether another person could understand them without help from the colleague who set everything up.

Ask about a future handover while you still have time to choose. If the restaurant changes owner, loses access to its email address or moves to another supplier, what evidence would be needed to recover control? Ask which records remain available and what needs to be arranged in advance. Keep the answer with the business continuity information rather than relying on a colleague's memory.

Keep unanswered supplier questions in the brief. Ask: which actions have a staff activity record, which exports include balance changes, who can approve a correction, and what support is available during evening service? If a feature is essential, ask to see it demonstrated. Do not tick the box on the basis of a broad assurance that reporting is included.

5. Write the redemption instructions before training

Build the staff instructions around a real bill. The guest presents a card, the server checks its available balance, the agreed amount is redeemed, and any remainder is collected through the usual payment process. The exact screen sequence depends on the service, so ask for a demonstration using the restaurant device.

Podium Cards describes checking balances and taking partial or repeat redemptions from a private page on a phone, tablet or laptop. That does not establish an automatic connection to your till. Confirm how the gift card payment will be recorded in the till and who checks that the two records agree.

Consider a hypothetical £50 card used towards a £68 bill. The team needs to record £50 against the card and collect the remaining £18, following the restaurant's agreed treatment of any other bill items. If the bill is only £32, staff need to leave the correct £18 balance and explain it to the guest.

Write the order of actions clearly. A vague instruction to take the voucher can leave one colleague reducing a balance while another records the same payment a second time.

• Confirm the bill and the amount the guest wants to use.
• Check the live balance through the approved staff route.
• Record the redemption once, then record the remaining payment.
• Confirm the result and explain any balance left to the guest.

6. Test the process with a second colleague

A successful purchase is only the start of testing. Have one colleague act as purchaser, another as recipient and a third follow the staff instructions if possible. The colleague redeeming the card should not need a running commentary from the person who configured it. That is a useful test of the handover.

Use a test method approved by the provider, or agree a small real transaction and its reversal before starting. Do not invent a refund route after money has moved. Keep a record of the expected result, actual result, tester and any unresolved issue. A screenshot can help explain a problem, but do not circulate a spendable code.

Test on the restaurant's connection at the places where the device will be used. A good connection at the office desk does not prove the staff page is usable beside the till. Include a quiet rehearsal of a failed connection and agree when staff should contact a manager.

Delay the launch if a balance test fails, delivery goes missing or a payment record is unclear. Fix it and repeat the affected journey. Cosmetic changes can be scheduled separately if the essential customer information remains clear.

Use a test sheet with a separate row for each action. For a £40 example card, write down the starting balance, a £12 test redemption and the expected £28 remainder before touching the screen. After the action, compare the actual record with that expected result. Then give the card to a different tester for a second use, checking that they begin with £28 rather than the original value.

Add an email delivery scenario in which the purchaser initially cannot find the message. Establish how staff verify the order and whether the approved support process can resend it. Also test a purchaser and recipient with different email addresses if that arrangement is supported. The team should know which address receives which message, rather than exposing someone else's details while trying to help.

7. Give the team a short handover guide

Training works better when the shift team can find the answer during service. Keep a short handover beside the normal payment instructions, in an approved location. Include the staff page route, the steps for checking and redeeming, the person handling problems and the wording for explaining a remaining balance.

Avoid putting full customer card codes or administrator passwords in that handover. It should help staff perform their job without becoming a loose collection of access details. Show a clearly labelled training example and remove temporary test information once the exercise is complete.

Let a new colleague explain the process back to you. Ask what they would do if a guest only has an email screenshot, the balance is smaller than expected or the screen stops responding after confirmation. Their questions often reveal missing instructions more effectively than a manager reading the guide aloud.

Assign cover as well as a primary owner. If all customer queries go to one person who is away for the weekend, the launch still has a gap. Name a deputy who can investigate without improvising a refund or promising a replacement.

If you already have a business website, explore how gift cards can be added to WordPress and WooCommerce and include the website owner in the launch handover.

8. Launch quietly, then review the first week

Start by checking the final purchase link from your website and the places you plan to share it. A correct link in a project document does not help if the public button opens an old page. Check the text around it too, especially any delivery promises or references to physical cards.

A small initial launch gives the team an opportunity to review real questions before a busier promotion. Agree who checks incoming queries, delivery problems and the day's outstanding balances. The aim is a routine that can be maintained during service, rather than a spreadsheet that only makes sense to its creator.

Keep the first review practical. Were any emails difficult to find? Did guests understand partial use? Did staff record gift card payments consistently? Record what happened, the change agreed and who owns it. Do not turn one successful test into a claim about future sales or customer behaviour.

If you plan a seasonal campaign, leave time for another rehearsal after changes to offers, staff or devices. A system that worked at launch can still need a refreshed handover when the restaurant's working arrangements change.

A review sheet for the first week can be very small: date, issue type, bill or order reference, owner, action and status. Keep the entries factual. For example, a fictional entry could say recipient could not locate email, order verified, approved resend completed. Do not store full card codes or copy an entire customer message when a short operational note is sufficient.

Decide what would pause further promotion. Repeated failed delivery, unexplained balance changes or an unavailable redemption route warrant investigation before a larger announcement. A confusing question about the offer may instead need clearer wording and another staff reminder. Naming these responses in advance helps the launch owner act consistently without treating every issue as either trivial or disastrous.

9. Decide whether you are ready to launch

Before promoting the card widely, bring the brief, test results and staff handover together. A manager should be able to say what is being sold, how it is delivered, who can redeem it and how a problem reaches someone who can act. Record the decision and any remaining tasks that can wait until after launch.

Use a simple readiness check: customer wording approved, accounts owned by the business, live journey tested, partial redemption checked, records export reviewed and shift cover named. If an item remains unclear, give it an owner and resolve it before adding more promotion. A launch date is useful only if the restaurant can support the promise.

Keep the final launch pack somewhere the manager and deputy can both find it. Include the approved offer, customer wording, purchase link, completed test sheet, staff handover and list of unresolved supplier questions. Give the pack a review date. When a value, restriction or working step changes, update the public wording and the staff instructions together. Customers and staff should be working from the same information, including during a busy service.

To discuss the digital approach described here, review the Podium Cards service. Bring your completed brief to the conversation so the discussion can confirm current features, pricing and fit. Ask separately about physical cards, till connections or any unusual redemption requirements.

For the daily routine after launch, use the companion guide to gift card redemption and reconciliation. It focuses on transaction records, corrections, reporting and handover once cards are already in use.