Discounts, coupons and loyalty

This page is for restaurant owners and marketing teams who want to drive traffic, lift average check, and reward returning guests. Everything here runs from the Fooodo admin and shows up in the same guest checkout — no separate growth tool to wire up.

Time-window discounts

The simplest promotion type, and the one most chains start with: a discount that's only live during a specific window. A 20% lunch special, Tuesday-night pizza deal, or weekend brunch upcharge.

Configurable in the admin per discount:

• Day-of-week and hour window — e.g. Mon–Fri, 11:00–14:00.
• Eligible categories — apply only to "Lunch", or "Pizza", or anything else.
• Minimum spend — gate the discount above a threshold so it lifts ticket size rather than just shaving margin off small orders.
• Stackable or exclusive — choose whether time-window discounts can combine with coupon codes.

Discounts are applied automatically during the eligible window — guests don't need to enter a code, and you don't need to push staff to remember the rules.

Coupon codes

For email campaigns, social posts, partnership giveaways, or staff-give-this-to-a-disappointed-guest moments. Two shapes are live:

• Single-use codes — each code is consumed by one order. Generated in batches and tied to a campaign so you can track which channel converted.
• Multi-use codes — one code, many orders. Typical for "WELCOME10" style campaigns.

Discount mechanics are flexible:

• Percentage off (e.g. 15%) or fixed amount (e.g. €5).
• Per-product whitelist — discount only applies to specific items.
• Minimum spend to redeem.
• Per-user dedupe so a single guest can't drain a campaign.
• Expiry date — codes age out automatically.

Bulk generation for email campaigns — generating hundreds of unique single-use codes for a CRM blast — is in active development. Today, multi-use coupons cover most needs; bulk single-use is the gap we're closing next.

Loyalty cards (R-Keeper-driven)

If your R-Keeper installation already runs a personal-card programme — Vilniaus Šeima for Čili Pizza is the reference — Fooodo binds to it directly:

• A guest who has linked a loyalty card sees the loyalty pricing in the menu, not the rack rate.
• Card binding happens once, in the guest's profile, and persists across visits.
• Pricing comes from R-Keeper. Fooodo doesn't override; it surfaces what your card programme already says.

There's no second loyalty engine inside Fooodo. There are no in-app points, no parallel tier system, no "earn 1 point per €" mechanic. The card programme you already run is the loyalty programme — Fooodo plugs into it.

Cross-sell — "people also added"

A targeted prompt at the right moment in the order flow: "Going for the pizza? Most guests add a soft drink." You configure which products trigger which suggestions; the guest sees a soft prompt rather than a popup ad.

This module is in late development — UI polish stage, close to production. The mechanics are operator-controlled (no opaque AI choosing what to push); rules look like "when a Margherita lands in the cart, suggest a Coke or Sparkling Water at €X."

The point of the feature isn't AI — it's giving the operator the same upsell prompt a good waiter would deliver, but consistently, at every table, without coaching staff.

Donations

A guest-facing checkout option that routes a donation to a partner organisation — Red Cross is the live reference example. Configurable at the company level:

• Preset amounts (€1, €2, €5) plus a custom amount field.
• Cause description — short copy explaining what the partner does.
• Optional default — opt-in (off until selected) or opt-out (on by default, guest can clear it).

Donations are charged through the same Mollie transaction the guest is already paying for, but the donation portion is routed to the partner organisation's Mollie account. From the guest's perspective: one charge. From the operator's perspective: the donation does not appear in restaurant revenue or in R-Keeper sales reports — it lands cleanly in the partner organisation's books, with the right tax treatment.

It's a guest-trust move with no margin impact on the restaurant.

Tips

Tipping isn't a promotion mechanic per se, but it's adjacent — and it's usually where chains see the fastest revenue lift after rolling out Fooodo. The tipping flow:

• Fixed-percentage presets (10%, 15%, 20%) plus a custom amount.
• Per-table on/off — keep tipping disabled at the takeaway counter, on at dine-in tables.
• Default percentage configurable at the restaurant level.

Tips bundle into the same Mollie charge as the order, then settle in R-Keeper as a tip line — so existing tip-out workflows don't change. The R-Keeper code that represents tip revenue is set per-restaurant.

Reviews

A post-payment rating prompt captures guest sentiment for operator review. Ratings are not displayed publicly — they exist for you, not for other guests. The flow:

1. Guest pays.
2. Optional 1-5 rating prompt with a free-text comment field.
3. Captured against the order, the table, and the staff/shift in scope.

This gives chain managers a per-shift, per-location quality signal that lines up with the actual transaction — useful for surfacing "Tuesday-night service at Akropolis is consistently underperforming" before it shows up in repeat-visit numbers.

What's intentionally not in the system

• No public reviews. Guest ratings are operator-visible, not surfaced to other guests. If you want public reviews, that's Google, TripAdvisor, or Wolt — Fooodo doesn't compete with them.
• No referral rewards. No "give your friend €5, get €5" mechanic today.
• No tier-based loyalty. R-Keeper's card programme is the only loyalty surface; no parallel Bronze/Silver/Gold inside Fooodo.
• No automated email blasts from Fooodo. Coupon code generation lives here; the actual send happens in your CRM.

Where to go next

• Day-to-day operations: Getting started for onboarding and the dry run.
• The order side: Order flows for how Pay-First and Pay-Later interact with promotions (e.g. coupon codes can apply on either flow).
• The money side: Payments for tipping, donations, and refund mechanics in detail.