Loyalty, mobile ordering and a digital coffee card for your cafe

The stamp card gets forgotten in a wallet, a lost card has to be reprinted, and nobody knows who has had how many coffees. During the morning rush the barista is taking orders and stamping cards at the same time. A cafe app turns that cycle into a digital account tied to the receipt at the till, and lets you greet the customer by name.

How many separate apps does this need?

  • 01

    Customer app (iOS + Android)

    Digital stamp card, points balance, mobile ordering with pickup time selection, campaign notifications, and one-tap reordering of a favourite drink with its milk and syrup preferences.

  • 02

    Barista / till app (tablet)

    Queues incoming mobile orders, marks the preparing and ready steps, writes stamps and points by scanning a QR code, and lets staff temporarily pause mobile order intake when the shop is busy.

  • 03

    Admin panel (web)

    Branch and menu management, price updates and product disabling, campaign setup, loyalty rules, hourly sales reports, customer segments and targeted push notifications.

What the app includes

  • Saving milk, size and shot choice as a favourite drink
  • Different stamp values per product group in the loyalty rules
  • Barista-confirmed bonus points for bringing your own cup
  • Separate prep times and pickup slots per brew method
  • Opening a table tab via table QR for in-house service
  • Routing food to the kitchen and drinks to the bar separately
  • Time-window based automatic happy hour pricing
  • Prepaid coffee bundles drawn down cup by cup
  • Suspended coffee donations with counter and redemption log
  • Missing-points claim by receipt number, approved from the panel
  • Branch-specific menu, pricing and sold-out status
  • Single-use birthday and membership anniversary reward

State of the sector

Cafes no longer compete only with the shop on the next corner: they compete with the free-coffee reward in a chain's app, the convenience of ordering ahead and skipping the queue, and campaigns addressed to customers by name. While a chain customer orders from their phone and picks the coffee up ready, the independent cafe's customer is standing in the morning queue. A cafe without an app does not know who its customers are: it only sees the day's total takings, not visit frequency, not which regulars are drifting away, not where the basket could grow. What is lost is not a single sale but the direct channel to the customer who would have come back.

Metrics that matter here

  • Monthly visit frequency per active customer — The loyalty card and personalised reminder notifications are aimed at increasing how many times the same customer comes in within a month.
  • Reward redemption rate (earned vs. redeemed) — A reward that is earned but never redeemed has not brought the customer back; the stamp threshold and expiry window are tuned against this rate.
  • Average receipt value — The add-a-pastry suggestion and size upgrade offered at the moment of ordering in the app directly affect basket size.
  • Mobile orders as a share of total orders — It shows how much load has been taken off the till queue and how much extra demand the morning peak absorbs; preparation capacity is planned around it.

Common mistakes in this sector

  • Setting the reward threshold too high A buy-twenty-get-one-free scheme motivates nobody; customers see the card will never fill and give up. Starting with a reachable threshold and tuning it against the data keeps the app alive and keeps reward costs controllable.
  • Granting stamps without barista confirmation Stamp schemes based on location or a self-service button are abused within weeks; accounts appear that collect stamps without buying coffee. Stamps must always be tied to the receipt at the till, otherwise reward costs grow with no relationship to revenue.
  • Building the menu as a flat list with no variations If milk type, size and extra shot options are not built into the model from the start, every variation gets created as a separate product; the menu bloats, price updates become painful, and baristas make the wrong drink. Option groups must be designed from day one.
  • Sending the same mass notification to everyone A “good morning, coffee time” push sent to every user each morning gets muted fast, and often the app gets deleted. Notifications should be triggered by the individual's visit rhythm and order history, with a frequency cap defined in the system.

Regulation and compliance

Because a cafe app processes names, phone numbers, order history and often location, the privacy notice, explicit consent flow and privacy policy required under KVKK (Turkey's data protection law, aligned with GDPR) must be present inside the app; marketing notification consent must be collected separately, and users must be able to delete their account and their data. Sending commercial electronic messages requires İYS registration (Turkey's commercial message consent registry) and consent management. Whether registration in the data controllers' registry is mandatory is assessed against the business's own thresholds. A sales document must be issued for payments taken through the app; if the business is registered for e-Fatura/e-Arşiv (Turkey's mandatory e-invoicing system), the flow must be set up to issue GİB-compliant (Turkish Revenue Administration) e-Arşiv invoices.

The real challenges in this sector

  • Tying every stamp to a real sale

    If customers can stamp their own on-screen card, the loyalty programme collapses. A stamp must be tied to a receipt generated at the till: the barista tablet displays a QR code that refreshes every second, the customer scans it, and the server matches it to the receipt total and line items before writing the stamp. Screenshots, re-scanning the same code and a second stamp from the same receipt are all rejected server-side.

  • The morning peak preparation queue

    Between 08:00 and 10:00, the customer in line and the mobile order are waiting on the same machine. The app has to allocate pickup times against real capacity: you define how many drinks can be prepared per minute, and once slots fill up the next available time is offered. The barista can pause mobile order intake with one tap on the tablet, and the queue updates on screen in real time.

  • Pricing milk, syrup and shot variations

    A latte is not a single product: the oat milk surcharge, an extra shot, sugar-free syrup, hot or iced, and size combinations all change both price and preparation. The menu model must support required and optional choice groups, limits on how many options can be selected, and a price difference per option; the variation must be printed clearly on the barista ticket so the wrong drink is not made.

  • Taking a sold-out item down instantly

    If the cheesecake runs out but the app keeps selling it, the customer arrives, the item is gone, and you are left with a refund and an argument. The barista should be able to mark an item sold out for today with one tap on the tablet, the change should reach every open app within seconds, and the item should reopen automatically the next morning.

  • Winning back customers whose visit rhythm has broken

    The real loss in a cafe is the customer who came three times a week and has not been in for three weeks. The system should calculate each customer's own visit rhythm and fire a notification when that rhythm breaks. Instead of one mass notification sent to everyone at the same time, it should generate a personal, time-limited, single-use coupon, and coupon redemption should again be verified against the receipt.

Required integrations

  • Till/POS and order-management software integration (so receipt lines flow into the app)
  • In-app card payments and one-tap payment with a saved card via iyzico or PayTR (Turkish payment providers)
  • Bank virtual POS infrastructure, plus a pay-at-the-till option flagged on the order
  • A GİB-compliant (Turkish Revenue Administration) e-invoicing integrator or bookkeeping system for issuing e-Arşiv invoices
  • Multinet, Sodexo, Setcard and Ticket meal-card providers reflected on the order using their setup at the till
  • Kitchen/bar printer or kitchen display system (KDS), plus push notification infrastructure

Who this page is for

  • A single-branch neighbourhood cafe

    The priority is not mobile ordering but knowing who the regulars are: a digital stamp card, receipt-bound QR confirmation on the barista tablet and a simple menu panel are enough on their own; the ordering flow can wait for a later phase.

  • A local cafe chain opening new branches

    The scope centres on branch-level menu, price and sold-out management with per-branch reporting; stamps and rewards valid across branches, and a POS integration that behaves identically in every location, are designed in from the start.

  • A specialty cafe roasting its own beans

    Loyalty needs a retail side: origin and roast-date fields, grind preference, shipped bag sales, a recurring bean subscription and prep times split by brew method all belong in the scope.

A phased plan that splits the budget

  1. 1

    Phase 1 — Loyalty core running in a single branch 5-7 hafta

    The iOS and Android customer app, digital stamp card, barista tablet screen, receipt-bound QR validation and basic menu management in the web panel. This ships as a complete product on its own: the customer list and visit history start accumulating from day one, and the cafe keeps working without any ordering flow.

  2. 2

    Phase 2 — Mobile ordering, payment and prep queue 4-6 hafta

    A menu model with milk, size and shot option groups, pickup time slots, the barista queue, in-app card payment and a pay-at-the-counter option. Ordering comes second on purpose: without real visit and product data, the option model and the per-minute capacity settings would be pure guesswork.

  3. 3

    Phase 3 — Segments, campaigns and multi-branch 4-6 hafta

    Notifications triggered by each customer's own visit rhythm, personal time-limited coupons, happy hour rules, prepaid coffee bundles and branch-level menu, pricing and reporting. It comes last because segmentation only becomes meaningful once several months of visit history exist.

Typical scope and timeline

Typical scope: iOS and Android customer app, barista tablet screen, web admin panel, loyalty engine with till/POS or manual receipt verification, payment provider integration, campaign and segment-based notification infrastructure, menu management with milk/size/shot variations, UI/UX design, store assets, QA and the App Store and Google Play release process.

Estimated timeline: 10-16 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Connecting to the POS and tab software Off-the-shelf loyalty apps ship ready-made connectors for popular POS brands; if yours is on the list, setup really is fast. If your POS is not on that list or is a local tab program, the connection is built as part of the project; where no API exists, a barista-confirmed receipt entry path is set up instead.
Flexibility of the loyalty rule Packaged tools usually offer one template: one stamp per purchase, a reward at X stamps. For a simple scheme that is entirely enough. Rules can be set per product and per hour: no stamp on the breakfast plate, half a stamp on filter coffee, double stamps on weekday afternoons.
Monthly subscription or one-off investment A monthly subscription lowers the barrier to entry: you can try it, cancel it, and no large budget is committed up front. Custom development is a one-off investment; cost does not grow with users or branches, but maintenance and app store releases have to be planned separately.
Ownership of the customer data Hosted platforms keep the data in their own system; most allow an export and take backup and security work off your hands. With a custom build the customer list, visit history and notification channel sit in your own database, and consent flows for KVKK (Turkey's data protection law) and IYS (Turkey's commercial message consent registry) are designed to your setup.

Sector glossary

Adisyon (open table tab)
The running tab opened for a table and closed when the guest leaves. In the app it is opened by table QR, every later item lands on the same tab, and payment plus stamps attach to the single closing receipt.
Option group (modifier)
The set of choices that changes a drink's price and preparation: milk type, size, extra shot, syrup. Groups can be required or optional, limited in how many may be picked, and each choice can print as its own line on the barista ticket.
Askıda kahve (suspended coffee)
A coffee paid for in advance and left for someone else. The app keeps a donation counter, the remaining number and a redemption log; each cup handed out is deducted with barista confirmation so the donation stays traceable.
Fire (waste and shrinkage)
Product thrown away unsold: end-of-day pastries, spilled milk, drinks made wrong and returned. If it is not logged separately in the panel, the gap between sales and stock cannot be explained and cancelled mobile orders get mixed into it.
Third wave (specialty coffee)
A cafe approach that foregrounds bean origin, roast date and brew method. In the app this shows up as origin and roast details on the product card, a brew method choice such as V60, and selling retail bags of beans.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →