Answers / Loyalty programs

    What is the optimal win-back voucher amount for an F&B venue?

    Written by PEKO Team.Last updated: 07/30/2026.

    Updated July 2026 Ten to fifteen percent off, or a free item worth roughly one-third of an average ticket, with a 14-day expiry. Below 10% nothing happens; above 20% you train customers to wait for offers. 10–15% off is the working band. Under 10% reads as noise; over 20% erodes margin and teaches discount-waiting.

    The TL;DR
    • 10–15% off is the working band. Under 10% reads as noise; over 20% erodes margin and teaches discount-waiting.
    • A named free item converts 1.3–1.6× better than the same value expressed as a percentage.
    • Fourteen days is the right expiry: long enough to fit a normal visit cycle, short enough to create urgency.
    • Scale the offer to the customer's value, not uniformly. High-CLV lapsers justify a larger gesture; one-visit customers rarely do.
    • Do not send win-back to everyone who is quiet. Send it to people whose gap exceeds their own established cadence.

    Published: 07/30/2026

    Quick facts

    Answer
    Ten to fifteen percent off, or a free item worth roughly one-third of an average ticket, with a 14-day expiry. Below 10% nothing happens; above 20% you train customers to wait for offers.
    Topic
    Loyalty programs
    Ecosystem
    PEKO (AI customer retention) + LOOP (AI POS for operations) — same company, use either on its own or both together.
    Updated
    07/30/2026

    There is a narrow band where win-back offers work. Below roughly 10% of ticket value, the offer does not clear the mental threshold that makes someone change their afternoon plans. Above roughly 20%, two bad things happen at once: the margin on the recovered visit disappears, and — more damaging — the customer learns that going quiet produces a discount. That is a habit you pay for repeatedly.

    Percentages versus items. At identical cost, a named free item consistently outperforms a percentage discount by around 1.3–1.6× in conversion. The reason is that customers value the item at menu price and the discount at cash saved, and menu price is always the bigger number in their head. 'A free pastry with your next coffee' and '15% off your next order' can cost the venue the same $1.20; only one of them sounds like a gift.

    Expiry. Fourteen days is the default that survives testing. Seven days is too tight for anyone whose normal cycle is fortnightly — you burn the offer on people who were going to come back anyway and miss the ones who needed the nudge. Thirty days removes urgency entirely; redemption clusters in the last 48 hours regardless of window length, so a longer window mostly just delays the outcome.

    Uniform offers waste money. A customer who visited eleven times and then went quiet is worth a meaningfully larger gesture than someone who came once. The practical rule: tier the offer into three bands — a small item for one-or-two-visit lapsers, the standard 10–15% or free item for established regulars, and a personal, non-discount gesture (a reserved table, an off-menu item, a note from the owner) for the top decile, where a discount actually cheapens the relationship.

    Targeting matters more than the amount. The most common mistake is blasting the offer to everyone who has not visited in 30 days. Thirty days means nothing without context: for a daily commuter it is a crisis, for a weekend brunch customer it is a normal gap. Trigger on deviation from each customer's own cadence, and the same voucher will convert two to three times better because it lands on people who genuinely drifted rather than people who were on schedule.

    Measure recovered value, not redemption rate. A 25% offer will always redeem better than a 12% offer — that is not the question. The question is contribution margin from recovered customers over the following 90 days, minus the cost of every voucher issued, including the ones redeemed by customers who would have returned anyway. Run a holdout of 10% of the eligible list and the honest number appears within a quarter.

    1. Anchor at 10–15% or one-third of a ticket

    Express it as a specific item wherever the menu allows. Reserve deeper offers for a second attempt, not the first send.

    2. Use a 14-day window

    Then send one reminder at day 11. The reminder typically recovers a third of the eventual redemptions on its own.

    3. Tier by customer value

    Three bands — light, standard, and a non-discount gesture for the top decile. Discounting your best customers is the most expensive way to say thank you.

    4. Trigger on personal cadence, not a fixed day count

    Deviation from each customer's own visit rhythm beats a global 30-day rule by 2–3× on conversion.

    5. Hold out 10% and measure margin

    Without a holdout you cannot separate recovered customers from customers who were coming back anyway.

    FAQ

    What percentage is optimal?

    10–15% of ticket value, or a named item of roughly equivalent cost. Treat 20% as the ceiling for a first attempt.

    Percentage off or a free item?

    Free item, when the menu allows it. Same cost to you, 1.3–1.6× the conversion, and it does not train customers to expect discounts.

    How long should the voucher last?

    Fourteen days, with a reminder at day 11. Redemption clusters at the deadline regardless of how long you make the window.

    Should I personalise the amount per customer?

    Yes — three tiers by prior value is enough. Uniform offers overpay for low-value lapsers and undervalue your best customers.

    Should everyone who goes quiet get a voucher?

    No. Trigger on deviation from each person's own cadence. Sending to every 30-day-quiet customer wastes budget on people who were never at risk.

    Calculate your PEKO ROI

    The PEKO ecosystem

    PEKO and LOOP are two products from the same company. PEKO is the AI retention layer and runs alongside the POS you already use. LOOP is the AI-native POS that covers operations: recipe-level inventory, staff shifts, table plans and the kitchen display. Each works on its own, and run together they share one dataset, so nothing has to be entered twice. See PEKO + LOOP in one ecosystem

    Related

    People also read