Email can support useful, lower-pressure communication with repeat customers, but it needs a lawful list, clear purpose, operationally accurate content and disciplined measurement.
Give email a defined role
Email works well for menu updates, planned seasonal communication, loyalty explanations and thoughtful re-engagement. It is less suitable for urgent order-status messages or an offer that expires before many recipients will read it.
Build the list correctly
- Collect details directly through owned channels.
- Separate order receipt from marketing choice.
- Record consent or every requirement of a valid soft opt-in.
- Do not import marketplace contact details into the restaurant’s own list without a valid basis.
- Explain the business identity, content and frequency customers should expect.
- Apply opt-outs and suppression before every send.
Use a campaign architecture
| Campaign | Purpose | Operational prerequisite |
|---|---|---|
| Welcome | Explain direct channel and preferences | First order completed and list entry valid |
| Menu update | Show genuinely available items | Menu, prices and allergens reviewed |
| Regular digest | Provide useful choice without constant discounting | Frequency and segment approved |
| Win-back | Test a reason to return | Lapse definition and stop rule |
| Seasonal | Plan around a real event | Capacity, stock and terms confirmed |
| Loyalty | Explain earned value | Balance and redemption are accurate |
Protect deliverability and trust
Use a domain the business controls, authenticate sending, remove invalid addresses and monitor complaints. Avoid purchased lists and misleading subject lines. Deliverability is not a reason to hide the sender or make unsubscribe difficult.
Measure business outcomes
Track delivered messages, clicks, successful orders, contribution, opt-outs, complaints and later repeat behaviour. Opens can be incomplete or privacy-affected and should not be the sole performance measure.
Govern suppliers and data
Document who acts as controller and processor, where data is stored, which subprocessors are used, how suppression is exported and what happens on termination. Test deletion, correction and access workflows rather than accepting a feature-list answer.
Practical next step
Audit the current list by source and permission. Quarantine records whose origin, wording or opt-out history cannot be demonstrated before planning another campaign.
Use pre-send quality control
Test sender identity, subject, preview, personalisation, mobile rendering, price, conditions, links, location and unsubscribe. Send to internal addresses across common providers. Confirm the landing page and ordering system show the same offer.
Plan for mistakes
Define who can pause a campaign, correct a broken link and respond to customers. If the wrong audience or offer is sent, preserve evidence, stop further automation and decide whether a correction is genuinely useful rather than sending another promotional message.
Coordinate with the order operation
Campaign planning should use live opening times, menu availability, collection capacity and delivery coverage. If conditions change after scheduling, pause or update the send. Marketing approval should include an operations owner who can confirm that the promised customer journey still exists.
Review the programme as a portfolio
Quarterly, list every automation and recurring send with owner, purpose, audience and result. Remove duplicate journeys and campaigns that survive only because they are scheduled. This reduces fatigue and makes capacity planning more predictable.
Related guides
- Restaurant Marketing and Customer Retention — the main guide for the wider topic.
- Building an Email List from Orders — a detailed next step for putting this guidance into practice.
- Email Campaign Types for Restaurants — a detailed next step for putting this guidance into practice.
- Customer Data and Database Management — a closely related operational control to review alongside this page.
- Loyalty and Retention Strategy — a closely related operational control to review alongside this page.
Sources and date checked
Guidance checked: 24 July 2026. Recheck current ICO, supplier and advertising guidance before acting.
