ContactBook a call

Industries/ Hospitality/ Ordering and loyalty apps

A branded ordering app that remembers your regulars

Your most frequent guests already know what they want. We give them a way to order it, collect points and book a table in a couple of taps, with every order landing on your own till and kitchen screen rather than a marketplace tablet.

A customer at a coffee counter collecting an order placed ahead on a phone, the barista handing over a cup.
Used by
Regular guests, shift managers, kitchen teams and marketing
Takes the place of
Paper stamp cards, marketplace tablets and re-keyed orders
Connects to
Your till, kitchen screens, card payments and reservations
Built with
Our customer apps service

Where it hurts today

A normal week, before it exists

Your best customers order through a delivery marketplace. The tablet on the counter chimes, someone reads the order aloud or keys it into the till, and the guest arrives as a first name and an initial. You cannot see that this person has ordered every Thursday for a year, you cannot thank them, and each of those Thursday orders pays the platform its commission before it pays you.

Loyalty is a paper stamp card, a rubber stamp behind the counter and a drawer of cards customers left behind. You have no idea who has lapsed, which regulars stopped coming after the menu changed or who only visits at weekends. A loyalty app you tried once did not talk to the till, so staff had to scan two things for every coffee, and before long they stopped.

Sold-out items are the other daily headache. The soup runs out at 1.30pm and is marked off on the till, but the website ordering page and two marketplaces keep selling it until someone remembers to switch it off in three places. The result is a refund, an apologetic phone call and a guest who orders from somewhere else next time.

What it does

Ordering and loyalty apps, feature by feature

What the app does for guests, and what it does for the team serving them.

  1. 01

    Reorder favourites in two taps

    Guests save favourites with their milk, extras and no onions, choose a collection time at their usual site and pay with a phone wallet or a saved card. Reorder puts last Tuesday's order back in the basket, ready to confirm on the walk in.

  2. 02

    Menu and sold-out items synced from your POS

    Dishes, prices, modifiers and sold-out items come from your till, so marking the soup off at 1.30pm takes it out of the app at the same moment. Photographs and longer descriptions are added in the app's own editor without changing anything on the till.

  3. 03

    Orders straight to the kitchen display

    Paid orders land on the till and the kitchen screen or printer with the collection time and the guest's name, so the team makes them in the normal flow of service. Nothing is read aloud from a tablet and nothing is keyed in twice.

  4. 04

    Collection slots the kitchen can keep

    Each site sets how many orders it can take in each quarter of an hour. When the 12.30pm slot fills, the app offers 12.45pm instead, so the lunch rush does not bury the kitchen in orders it cannot make by the time it promised.

  5. 05

    A loyalty app that works at the counter too

    Points or stamps live on the guest's account and build with each app order. Where your till allows it, guests also earn in person by showing a code at the counter, and their loyalty card can sit in Apple Wallet or Google Wallet.

  6. 06

    Table booking and order at table

    Guests book a table through your reservations system from inside the app. In the venue, they scan the code on the table to order and pay from their phone, and the table number travels with the order to the kitchen and the floor team.

A day with it

How the day runs instead

A weekday at a cafe group with three sites, once the app is running.

  1. 7.45am
    Regular on the way to work

    Taps the usual, a flat white with oat milk and a pastry, picks 8.05am at the Market Street site and pays with a glance at the phone. At the counter the order prints with the guest's name on it, and a stamp is added to their card.

  2. 11.55am
    Kitchen lead

    Lunch orders build. The 12.30pm slot reaches the limit the kitchen set, so the app starts offering 12.45pm. The kitchen screen shows app orders alongside counter orders, sorted by collection time.

  3. 1.30pm
    Shift manager

    The soup runs out. The manager marks it sold out on the till, and it disappears from the app at that site straight away. Two guests who had it in their basket are told before they pay, not after.

  4. Thursday
    Marketing lead

    Sends a notification about the new winter menu only to guests who switched on menu news, and only at the two sites where it launches. Guests who chose order updates only receive nothing at all.

  5. Monday
    Owner

    Looks at last week's orders by channel and site, and at the list of regulars who have not ordered for a month. Decides to send those guests a free pastry with their next coffee, and checks the week after how many came back.

What it connects to

Works with what you already run

The app is a new way in for guests. Behind it, the work runs through the systems your team already knows.

  • Point of sale

    Menu, prices, modifiers and sold-out items read from the till, and paid orders written back into it, for example Square, Lightspeed or Toast, where they offer an ordering API. We check this first, because everything else depends on it.

  • Kitchen display or printer

    Orders reach the kitchen screen or ticket printer through the till where possible, with collection time, table number and modifiers laid out the way your chefs already read them.

  • Card payments and phone wallets

    Payments, refunds and saved cards handled by an established payment provider, with Apple Pay and Google Pay, and app takings matched against the till at the end of each day.

  • Reservations and email marketing

    Table bookings pass to your reservations system, and guests who agreed to marketing pass to the email tool you already use, together with what they agreed to and when.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • Ordering for collection at each site, with favourites and one-tap reorder
  • Menu, prices and sold-out items taken live from your till
  • Collection slots with limits each kitchen sets for itself
  • A simple points or stamp scheme earned on app orders
  • Order notifications, with marketing switched off until the guest chooses it

Once it is in use

  • Earning loyalty at the counter by showing a code at the till
  • Order and pay at the table from a code on each table
  • Table booking inside the app through your reservations system
  • Delivery by your own drivers or through a delivery partner

Buyer's guide

Before you commission one

Four things worth deciding before you commission an ordering app.

  1. 01

    A white-label platform or your own app

    For a single cafe or takeaway, a white-label ordering platform, which gives you an app and an ordering page under your brand on shared software, will probably serve you better than an app of your own. Some reservations and till providers offer one. A custom app earns its place with several sites, a loyalty scheme that drives the business, or a menu and kitchen setup the platforms cannot handle.

  2. 02

    Check the till, then write the loyalty rules

    Everything depends on whether your till can share its menu, mark items sold out and accept orders from outside, so ask your provider for its ordering API documentation and any partner fees first. Then decide on paper what earns points, what a reward is, whether points expire and whether they work across sites. It is far easier to add benefits later than to take them away.

  3. 03

    Decide who runs it day to day

    An app needs owners after launch. Usually the marketing lead owns messages, offers and the loyalty scheme, the operations lead owns the menu, prices and collection slots, and each site manager owns sold-out items and the prompts on the counter. Agree who answers guests' app questions too, because a regular with a missing stamp will ask the person behind the till.

  4. 04

    Watch repeat orders, not downloads

    Downloads are easy to count and say little. Watch how many app customers order again within a month, the split between your own channel and the marketplaces by site, notification opt-outs, refunds for sold-out items, and which counter cards or receipts led to installs. Record the marketplace split before launch, so the comparison afterwards is fair.

Terms worth knowing

The words you will meet

Order injection
Sending orders from the app straight into your till and kitchen system, so they appear alongside counter orders without anyone keying them in. Ask any provider whether your till supports it, because it decides most of what an ordering app can do for your team.
White-label ordering app
An ordering app and web page built on a provider's shared software but carrying your name, logo and menu. It is quicker and cheaper to start with, but you rent rather than own it, so check who holds the customer data and what happens to your regulars if you leave.
Wallet pass
A loyalty card, voucher or ticket that lives in Apple Wallet or Google Wallet on the guest's phone, so they can show it at the counter without opening the app. It matters because plenty of regulars will not open an app just to collect a stamp.

Handled with care

The details that matter here

An ordering app handles food allergies, payments and personal data for people who visit often. These are the details we take most care over.

  • Allergens before and after the order

    Allergens show on every dish from the same record the menu and till use. In the UK, food sold online needs allergen information both before purchase and when it is handed over, so we design for both, such as a note on the collection label. Choosing no sesame seeds never quietly changes the allergen statement.

  • Refunds and the end of the day

    We agree with you what happens when an item sells out after payment, when a guest never collects and when an order is partly wrong. Refunds go back through the payment provider, and we design the end-of-day check so app takings and the till agree before anyone cashes up.

  • Guest accounts, deletion and consent

    Order updates and marketing are separate choices, both changeable in the app. Apple expects apps with accounts to let people start deleting them inside the app, and Google Play expects an in-app route and a web link, so we build both. We agree how long order history is kept under UK GDPR, EU GDPR or your local rules.

  • Large text, screen readers and one hand

    Guests order on the move, sometimes with a pram or a dog lead in the other hand. We size buttons for a thumb, label every control for screen readers, respect larger text settings and design to WCAG 2.2 level AA. Where you sell to guests in the EU, we check with your adviser how the European Accessibility Act applies.

Guides

Worth reading first

Questions

What buyers ask first

Will our own ordering app replace the delivery marketplaces?

Probably not, and we would not advise trying. Marketplaces bring you guests who have never heard of you, which your own app cannot do. What the app does is give the regulars who already like you a better way to order directly. Most operators keep both and steer repeat guests towards their own channel, and we set up the reporting so you can see the split by site.

Do restaurants need an app, or is online ordering enough?

If most of your guests order a few times a year, ordering on your website is enough, and we will say so. An app pays its way when the same people order every week, when a loyalty scheme gives them a reason to keep it, and when a message such as your order is ready is genuinely useful. Web ordering can come first, sharing the same menu and till connection.

Who owns the customer data from a restaurant app?

With an app we build, you do. The developer accounts are opened in your business's name with us added as members, the code sits in a repository you own, and guest accounts and order history live in systems under your control. That is the point of your own channel: the relationship and the data stay with you, and our access can be removed without anything breaking.

How do restaurants get customers to download their app?

From the guests they already serve. A listing in an app store brings very few people on its own. Downloads come from table cards, receipts, a prompt on your website, a word from the team at the till and a reason to install on the first day, such as a free coffee. We count each of those routes, so you know early which ones are working.

Can a restaurant loyalty app work with our POS?

Usually, but it depends on your till. Where the till lets us look up a guest and add or redeem points at the counter, the guest shows a code from the app or their phone wallet and the team scans it as part of the normal sale. Where the till cannot do that, we will tell you before you design the scheme around it.

Tell us how your regulars order today

Tell us which till you use and where your orders come from now. We will reply within 48 hours with whether an app makes sense for you, or whether web ordering would serve you better.