Aller au contenu principal
Tous les articles
OperationsJun 7, 2026

Customer segmentation for restaurants and hotels, with examples

Customer segmentation for restaurants and hotels means grouping guests who behave differently enough to deserve different treatment: a different email, a different offer or a note for the team on arrival. The most useful segments come from data you already hold, such as when a guest last visited, how often they come, what they spend, why they come and how far ahead they book.

A segment earns its place when it is big enough to matter, behaves differently from the rest of your guests and comes with a decision attached. If you cannot say what you will do differently for a group, leave it as a report.

How does RFM segmentation work for restaurants?

RFM scores each guest on three measures: recency (how long since their last visit), frequency (how many visits) and monetary value (how much they spend). IBM's SPSS documentation describes a common version: rank guests into five groups on each measure, with 5 for the most recent, most frequent or highest-spending, then combine the three digits into a code from 111 to 555. The same documentation names recency as the most important factor in identifying customers likely to respond to a new offer, followed by frequency and then spend.

You do not need all 125 combinations. A restaurant can work with a handful of groups:

SegmentRFM patternWhat to do
Best regularsR5, F4 to 5, M4 to 5Recognise them on arrival and invite them to previews and tastings
Lapsed regularsR1 to 2, F4 to 5A personal win-back message, ideally from the manager
New guestsR5, F1A reason to make a second visit within a few weeks
Occasional big spendersF1 to 2, M5Private dining, celebrations and set-menu events
Low-engagement guestsR1, F1, M1General news only, or leave them alone

When does a regular become a lapsed regular?

Lapsed depends on the guest. A weekly regular who has missed six weeks has changed their habits, while a guest who comes twice a year has not lapsed after six weeks. Define lapse relative to each guest's usual gap between visits, for example no visit in three times their average interval, or use a fixed window for each frequency band.

Say a guest has visited every three weeks for a year and has not booked in nine weeks. That guest belongs in a win-back segment. A guest whose only visit was nine weeks ago belongs with new guests who did not return, and needs a different message.

What are occasion-based segments?

Occasion segments group guests by why they come. Restaurants see business lunches, date nights, family meals and celebrations. Hotels see midweek corporate stays, leisure weekends and special-occasion breaks. The same guest can sit in more than one.

The data usually comes from the booking: an occasion field in the booking form, the day and time, the party size and whether a company card paid. A guest who books a table for two on a Saturday every few months and notes an anniversary is a better audience for a set-menu evening than for a weekday lunch offer.

Can you segment guests by dietary preferences?

Dietary preference segments are useful for menu launches, because guests who want to hear about a new vegan menu are an obvious audience. The safest way to build that segment is to ask: a preference choice on your signup form or profile lets guests pick the menu news they want.

Treat allergy information differently. A note that a guest has a nut allergy or coeliac disease says something about their physical health, and the ICO's guidance treats data concerning health as special category data under UK GDPR. Using it needs a lawful basis and one of the conditions in Article 9. Preferences such as halal or kosher can also reveal religious belief, another special category. Keep allergy records for service and food safety, and take advice before using any of this to target marketing.

How should hotels segment guests by booking lead time?

Lead time is the number of days between booking and arrival, and it tells you how a guest plans. Guests who book months ahead for summer respond to early offers and have time to add spa treatments or dinner before they arrive. Last-minute bookers respond to short-notice availability, and any pre-arrival messages for them need to fit into a day or two.

Useful bands for a hotel might be 0 to 7 days, 8 to 30 days and over 30 days. Compare average spend per stay across the bands before you build campaigns around them, because a band that books late but spends heavily on arrival needs a different message from one that books early and spends little.

How to build customer segments in Tiquo

Tiquo's segments are dynamic: they include every customer who matches the filters and update as customer data changes. Filters combine with AND and OR logic and cover age range, location, total spend, total orders, last visit date, customer status, membership plan, tags, service history, marketing consent and custom parameters. Last visit date, total orders and total spend give you the raw inputs for RFM-style groups, and the segment builder shows an estimated audience size before you send anything.

Custom parameters add typed fields to customer profiles, such as text, number, date, yes/no or dropdown values, and you can filter on them and build segments from them. A menu-interest or occasion field is one way to capture data your system does not hold by default.

Segments can also be selected in Analytics to focus the charts on one group, so you can see how lapsed regulars or high spenders book and spend before you message them, and a customer's profile shows which segments they belong to.

A guest's place in a segment does not by itself make them eligible for a marketing message. When several lists or segments are selected for one send, Tiquo removes duplicates, and only customers who have opted in to marketing receive it. Our guide to customer lifetime value explains how to weigh segments by value, and the guide to choosing between a CRM and a customer data platform covers joining guest data from several systems first.

© 2026 Tiquo. « Tiquo » et le logo Tiquo sont des marques déposées de Tiquo Ltd.

GDPR · CCPA · PCI DSS · ICO · Cyber Essentials Certified · EU–US DPF · SOC 2 Type II (in progress) · ISO 27001 (in progress)

Security & Operational

  • 99.99% SLA Uptime
  • AES-256 encryption at rest
  • TLS 1.3 in transit
  • AES-256 / TLS 1.3
  • Perfect Forward Secrecy (PFS)
  • HTTP Strict Transport Security (HSTS)
  • 99.999999999% (11 nines) data durability
  • Automated backups
  • DDoS protection
  • Web Application Firewall (WAF)
  • Zero Trust posture
  • Role-Based Access Control (RBAC)
  • Principle of Least Privilege
  • Secret scanning in CI
  • SBOM generation
  • Dependency supply-chain controls
  • 24/7 infrastructure monitoring
  • GDPR Article 22 safeguards
  • Data Protection Impact Assessments (DPIAs)
  • Records of Processing Activities (ROPA)
  • SAML 2.0 SSO
  • EASIE SSO
  • OAuth 2.0 / OpenID Connect (OIDC)
  • SCIM 2.0 provisioning
  • MFA / 2FA enforcement
  • Responsible disclosure / bug bounty programme

Privacy, Data Protection & Statutory Obligations

  • ICO Registered
  • UK Modern Slavery Act 2015 compliant
  • UK Public Interest Disclosure Act 1998 compliant
  • EU Article 27 Representative appointed (Paris, France)
  • Swiss FADP Article 14 Representative appointed
  • UK GDPR compliant
  • EU GDPR/DSGVO compliant
  • UK Data Protection Act 2018 compliant
  • Swiss revFADP compliant
  • CCPA / CPRA compliant (California)
  • VCDPA compliant (Virginia)
  • CPA compliant (Colorado)
  • CTDPA compliant (Connecticut)
  • TDPSA compliant (Texas)
  • OCPA compliant (Oregon)
  • MCDPA compliant (Montana)
  • FDBR compliant (Florida)
  • ICDPA compliant (Iowa)
  • ICDPA compliant (Indiana)
  • TIPA compliant (Tennessee)
  • DPDPA compliant (Delaware)
  • NJDPA compliant (New Jersey)
  • NHDPA compliant (New Hampshire)
  • NDPA compliant (Nebraska)
  • MCDPA compliant (Minnesota)
  • MODPA compliant (Maryland)
  • KCDPA compliant (Kentucky)
  • RIDTPPA compliant (Rhode Island)
  • Canada PIPEDA compliant
  • Quebec Law 25 compliant
  • Alberta PIPA compliant
  • British Columbia PIPA compliant
  • Singapore PDPA compliant
  • Hong Kong PDPO compliant
  • Brazil LGPD compliant
  • Japan APPI compliant
  • Australia Privacy Act / APPs compliant
  • India DPDPA 2023 compliant
  • Thailand PDPA compliant
  • Malaysia PDPA 2010 (as amended 2024) compliant
  • New Zealand Privacy Act 2020 compliant
  • South Africa POPIA compliant
  • UAE PDPL compliant
  • Mexico LFPDPPP compliant
  • Kenya Data Protection Act 2019 compliant
  • Ghana Data Protection Act 2012 compliant
  • Nigeria NDPA 2023 compliant
  • Indonesia PDP Law 2022 compliant
  • Philippines Data Privacy Act 2012 compliant

Global Fiscal & E-Invoicing

  • EN 16931 - EU e-invoicing core standard
  • UBL 2.1 - Universal Business Language
  • Austria - RKSV
  • Belgium - Peppol BIS 3.0 (B2B)
  • Czechia - fiscalization
  • Croatia - Fiscalization 2.0
  • Denmark - Peppol BIS 3.0 (B2B)
  • France - NF525 / LNE / Infocert, Factur-X / PDP, E-Reporting
  • Germany - KassenSichV / TSE, DSFinV-K, GoBD, E-Rechnung B2B (XRechnung / ZUGFeRD)
  • Hungary - Online Szamla
  • Italy - Scontrino, FatturaPA (via SDI)
  • Lithuania - i.SAF / i.MAS
  • Norway - Peppol BIS 3.0 (B2B), SAF-T
  • Poland - KSeF
  • Portugal - ATCUD/QR, SAF-T PT
  • Slovakia - eKasa
  • Slovenia - fiscalization (davcno potrjevanje)
  • Spain - FacturaE, SII, VeriFactu, TicketBAI
  • Sweden - SKVFS (certified cash registers)
  • Argentina - ARCA (Q4 2026)
  • Australia - Peppol PINT A-NZ (Q4 2026)
  • Brazil - NFe, NFCe, NFSe (Q4 2026)
  • Chile - SII Chile (Q4 2026)
  • Colombia - DIAN (Q4 2026)
  • Finland - Finvoice, TEAPPSXML (Q4 2026)
  • Japan - JP PINT (Peppol) (Q3 2026)
  • Malaysia - Peppol Malaysia (Q4 2026)
  • Mexico - CFDI (Q4 2026)
  • New Zealand - Peppol PINT A-NZ (Q4 2026)
  • Peru - SUNAT (Q4 2026)
  • Romania - Peppol (RO e-invoice) (Q4 2026)
  • Saudi Arabia - ZATCA (Q4 2026)
  • Singapore - Peppol BIS 3.0 (Q4 2026)
  • United Arab Emirates - Peppol (5C) (Q4 2026)

Standards & Frameworks

  • Cyber Essentials Certified
  • SOC 2 Type II - audit in progress
  • ISO/IEC 27001 - audit in progress
  • NIST Cybersecurity Framework - aligned
  • NIST Privacy Framework - aligned
  • NIST SP 800-53 / 800-63 / 800-63B - aligned
  • NIST AI Risk Management Framework - aligned
  • CIS Critical Security Controls / CIS Benchmarks - aligned
  • OWASP ASVS & OWASP Top Ten - aligned
  • ISO 25010 (quality) - aligned
  • ISO 31000 (risk) - aligned
  • ITIL - aligned
  • W3C Web Standards - aligned
  • OpenAPI Standard - aligned
  • DevSecOps practices - aligned
  • ePrivacy Directive - aligned
  • EU Whistleblowing Directive (2019/1937) - aligned

Payments Compliance

  • PCI DSS Level 1
  • PSD2 / Strong Customer Authentication
  • 3D Secure (3DS)
  • EMVCo Level 1 & 2
  • AML / KYC controls
  • Sanctions screening (OFAC, UN, EU, HMT)

International Data Transfer Mechanisms

  • EU-US Data Privacy Framework
  • EU Standard Contractual Clauses (Decision 2021/914) - Modules 2 & 3
  • UK International Data Transfer Agreement (IDTA) + ICO Addendum
  • Swiss FDPIC-recognised transfer mechanisms
  • APEC Cross-Border Privacy Rules (CBPR)

Accessibility Compliance

  • ADA (Americans with Disabilities Act) - aligned
  • European Accessibility Act (EAA) 2025 - aligned
  • WCAG 2.2 - aligned
  • EN 301 549 - aligned
  • WAI-ARIA - aligned

Une plateforme unique pour hôtels, spas, cours, événements, restaurants et plus encore.

Tiquo Ltd
Londres, Royaume-Uni

LinkedInTop Performer Spring

Nous utilisons des cookies

Choisissez si vous autorisez les cookies d’analyse et de publicité. Vous pouvez les accepter ou les refuser. Fermer cet avis revient à les refuser.

En savoir plus