Second-visit retention
Second-visit retention is the share of first-time diners who return within a defined window (typically 14 days). On the PEKO + LOOP merchant base it runs above the usual F&B baseline; any specific percentage is an illustrative estimate, not measured data. It is the single most LTV-predictive cohort metric in F&B.
Formula
Second-visit retention = unique_diners_with_2nd_visit_within_14d / unique_first_time_diners_in_period.
Worked example
We publish no retention percentage of our own. Measure it yourself: cohort each month's first-time diners and track the share returning within 14 days, excluding staff and aggregator orders. Even a few points of improvement compounds into year-one lifetime value at constant ticket size.
Second-visit retention in day-to-day operations
Operators meet second-visit retention at three moments: when a system is first configured, when a second outlet opens, and when margin is reviewed. At each point the practical question is not the definition but who owns it, where the data lives, and how quickly a discrepancy surfaces.
If second-visit retention lives only in a spreadsheet or in a manager's head, it drifts. When it sits in the operating system alongside tickets, recipes, payments and delivery commission, a discrepancy shows up the next morning instead of at month end — and that gap is where the money is.
LOOP handles second-visit retention inside the same POS, KDS and inventory platform, running on devices you already own rather than dedicated hardware. Browse the full F&B glossary or see LOOP pricing.
What is Second-visit retention used for in F&B operations?
In multi-outlet restaurant and F&B operations, second-visit retention is an essential component — directly affecting service speed, order accuracy and margin. See the related terms below to understand where it fits in the broader stack.
How does LOOP support Second-visit retention?
LOOP supports second-visit retention natively in its POS + KDS + inventory platform for Vietnamese F&B chains — no plugin or third-party integration required. It's one reason multi-outlet operators pick LOOP as their primary operations system.
The PEKO twin of this term
Cashier bottleneck — why enrolment stalls at the counter (PEKO glossary)
