Skip to content
CAPPATERY
Sign up
Counter Ops / Loyalty & regulars

Being recognised is the reason people walk past two other cafés to reach yours.

Every café has them. Twenty or thirty people whose order has not changed in a year, who account for a share of the month that would surprise you if you added it up. The relationship is real, and it is usually held entirely in the head of whichever member of staff has been there longest.

That is a fragile place to keep something valuable. When they are on leave, a customer on their sixtieth visit gets asked what they would like, as though it were their first.

Match point
At the till
Basis
Repeat order pattern
Confirmation
Always by staff
Across outlets
One identity
How recognition works

Four steps, and a human confirms the last one.

This is deliberately not a system that charges people for what it assumes they want. It shortens the conversation; it does not remove it.

01

Customer identified

Through the loyalty identifier they already use at your counter, or by staff selecting them from recent visitors.

02

Pattern read

Their order history is checked for a stable pattern rather than just the last thing they bought.

03

Usual staged

The established order appears on the till pre-filled, with the modifiers they always take.

04

Staff confirm

One tap accepts it, or it is adjusted like any other order. Nothing is charged from a prediction.

What staff see

Priya M.visit 41

Usual: oat flat white, no sugar

Weekday mornings, 8:10 to 8:25. Adds a croissant on Fridays.

Staged at the till, awaiting confirmation

The Friday croissant line matters more than the drink. It is the kind of detail a long-serving barista knows and a new starter has no way to. Surfacing it turns an upsell into a courtesy.

Note what is not on this card: no scoring, no segment label, no lifetime value figure. A person at a counter needs the order and one useful thing about it. Everything else is noise at the moment of service.

Rewards

Loyalty that runs on what people actually did.

Punch cards fail because stamping them is an extra job during the exact minute nobody has one. Accrual here is a by-product of the sale.

  • Accrual happens at the till, automatically

    Nothing to stamp, scan or remember. The visit counts because the order was rung up.

  • Rewards you define, in café units

    Every tenth coffee, a pastry after a run of visits, a birthday item. Set in terms of drinks and bakes rather than abstract points.

  • Redemption is one tap at the counter

    Available rewards show alongside the recognised customer, so staff are not hunting through a menu during a rush.

  • Visit rhythm, not just visit count

    Whether someone comes four weekday mornings or every Saturday is more useful than a running total, and it is what makes a lapse visible.

  • Lapsed regulars surfaced

    When a four-mornings-a-week customer has not been in for two weeks, that is worth knowing while it is still recoverable.

  • One identity across a group

    For chains, a regular recognised at the station branch is recognised at the high street branch, with the same usual and the same reward balance.

Where we stop

Recognition is a courtesy. It stops being one quickly.

There is a version of this feature that gets unpleasant. Tracking people who never asked to be tracked, building profiles that outlive the relationship, pushing offers at somebody because a model decided they were price-sensitive this week. We are not building that, and it is worth being specific about the limits.

A customer is only recognised if they are using your loyalty identifier or have been added by staff. Recognition is visible to them the moment it happens, because a person says their name and their order out loud. A regular can ask to be removed and the profile goes, including the order history behind it.

We do not sell, share or pool customer data between cafés. Your regulars are yours. What runs on the CAPPATERY side is the matching and the accrual, on your data, for your counter.

The test we hold this to: would a regular be pleased or unsettled to learn exactly what the system knows? If the answer is unsettled, it does not ship.

Questions

Recognition, in practice.

How many visits before someone has a usual?
It needs a stable pattern rather than a fixed number, so a customer who orders the same drink five times running is recognised sooner than one whose orders vary. Where the pattern is weak, no usual is staged - an unreliable suggestion is worse than none at a busy counter.
What if a regular changes their order?
The pattern follows them. A run of new orders replaces the old usual, and staff overriding a staged order feeds back into that. It corrects itself within a few visits.
Do customers need an app?
No. Recognition works from whatever identifier they already give at your counter, or from staff selecting them. We are not asking your regulars to install something to be greeted properly.
Can a customer be removed entirely?
Yes, on request, including their order history. The visit is still counted in your aggregate sales, but the profile and the pattern behind it are deleted.
Does this work if two people share one loyalty identifier?
Shared use tends to produce a weak pattern, in which case no usual is staged and the counter behaves normally. It fails quietly rather than confidently suggesting the wrong drink.

Loyalty & regulars

Stop keeping your most valuable relationships in one person's memory.

Recognition that survives a shift change, a new starter and a leave day is worth more than a loyalty scheme nobody has time to stamp.

Sign upTalk to us
  • Usual orders staged at the till for confirmation, never charged blind
  • Rewards accrued from the sale itself, with nothing to remember
  • Regulars removable on request, history included