Skip to content

Diese Seite gibt es auch auf Deutsch. Auf Deutsch ansehen

Esta página también está disponible en español. Ver en español

Deze pagina is er ook in het Nederlands. Bekijk in het Nederlands

Cette page existe aussi en français. Voir en français

Shown in the language you chose. Auf Deutsch ansehenVer en españolBekijk in het NederlandsVoir en français

tapja

For chains & franchises

One programme. Every branch. One overview.

One card for every branch, teams per location, numbers per branch and a price that drops with every additional location.

One card for every branch teams per location graduated pricing

One card works in every branch. You decide per programme where it can be redeemed.

In short

  1. One loyalty programme for every location, without building and maintaining an app of your own: the card lives in your guests’ Apple Wallet or Google Wallet.
  2. Your guests get one card that works in every branch. Collecting happens anywhere, and so does redeeming by default, though you can restrict a programme to specific locations.
  3. You assign staff and branch managers to one or more locations. A branch manager sees the numbers for their locations and their team; the view across all branches stays with you.
  4. You compare your locations side by side: new cards, stamps and redemptions per branch. Every action is logged with its person and its location.
  5. Every location has its own counter device and its own QR stand, as an A4 or A5 PDF, free of charge.
  6. Billing is per location, and the price per location falls as the count rises. Locations can be closed at the end of a period and reopened later.
  7. REST API and webhooks are included in the plan. You create API keys and webhooks yourself.

All branches side by side, or just one.

Switch between locations. With one selected, you see what the manager there sees.

This is your view as the owner: every branch side by side, for each programme.

This is what the Old Town manager sees: only their locations and their team.

This is what the Station manager sees: only their locations and their team.

This is what the Harbour manager sees: only their locations and their team.

New cardsStampsRedemptions
Old Town4831227
Station6340538
Harbour2918814
No location2113

Counted is whatever happens on a paired counter device. Bookings made in the dashboard appear as “no location”. Sample figures.

What a chain needs that a café does not.

Everything from the single-location plan stays, plus what only starts to matter with the second branch.

  • Every location in one account

    Every branch with its address and coordinates, which feed the lock-screen location notice. You add locations yourself, close them at the end of a period and reopen them later.

  • Redeeming across branches

    By default a guest collects and redeems anywhere, which is the point of a chain. If a programme should only be redeemable at certain locations, you restrict it to them.

  • Teams per location

    You assign staff and branch managers to one or more locations. So every action shows who did it and where.

  • Branch managers with their own view

    A branch manager sees the numbers for their locations and their team. The view across all branches and the security log stay with you as the owner.

  • Locations side by side

    New cards, stamps and redemptions per branch, next to each other, for every programme. What counts is what happens on a paired counter device.

  • One counter per branch

    Every location gets its own counter access: a tablet with the staff app or the till computer with the counter in the browser, paired with a code. Plus its own QR stand as a PDF.

  • Where your guests come from

    Per location you see how new cards came about: through your team, the QR stand, a referral or your short link in your Instagram bio and on WhatsApp. The short link counts as a channel of its own.

  • Campaigns per branch

    Break down every campaign you send by location, origin and channel. So you see in which branch guests came back after the message.

  • All your data for your own analysis

    The full dataset as Excel, CSV or JSON, filtered by location, card, origin and channel. Guests and staff appear only as numbers; names are added only if you, as the owner, explicitly tick the box. Owners and branch managers can export, a branch manager only for their own locations.

  • REST API and webhooks

    So your POS, shop or CRM can talk to tapja and knows when a card is issued, stamped or redeemed. You create API keys and webhooks yourself.

Start with one location for free. We’ll sort out the rest together.

The price

The more locations, the cheaper each one.

The first location costs the same as a single business, every further one less. Billing is graduated: each tier is charged at its own price, rather than the whole estate at the cheapest one. The current tiers are on the pricing page.

  • Locations come and go

    A branch can be closed at the end of the current period and reopened later. You do not pay for a site that is shut.

  • No self-service checkout

    Chains get an individual quote rather than a button. That is deliberate: with several locations it is worth settling once, together, which branches belong, who looks after which location and where rewards can be redeemed.

  • A named contact

    Instead of a ticket queue, one person who knows your setup.

Worth knowing

Honest about the limits.

Six points worth settling before a chain rollout.

  • No off-the-shelf POS integration

    There is no standard connector for a till system. One can be built on the interface included in the plan; that is development work on your side.

  • Assign branch managers first

    A branch manager without an assigned location sees the numbers for the whole business. So assign them to their locations before they get started.

  • Location notice on iPhone only, ten at most

    The lock-screen notice comes from the Apple pass; Google Wallet does not have it. And a card can carry at most ten locations; with more branches you pick the relevant ones.

  • Messages run through the card

    Even with twenty locations the channel stays the wallet card and its short note. There is no newsletter or SMS delivery to your guests.

  • Location only for stamps on site

    A branch gets whatever happens on a paired counter device: a tablet with the staff app or the counter in the browser. Bookings made in the dashboard show up in the comparison as “no location”.

  • Origin only since September 2026

    Where a card came from has been recorded since September 2026. Older cards appear in the report without an origin.

Not part of the standard yet

On request

  • Special structures

    Regions, franchise approvals or permissions beyond owner, branch manager and staff. What is possible, we work out together.

Read on: Pricing and tiers Developer docs Dashboard in the browser Automations Get in touch

Questions about multiple locations.

Question not listed?
Write to us, a person will answer.

Can my guests use their card in every branch?
Yes, that is the default. One card, every location: collecting works anywhere and so does redeeming. If a particular promotion should only apply at one location, it can be restricted to it.
Do I see my branches separately?
Yes. The location comparison shows new cards, stamps and redemptions per branch side by side, for every programme, plus where new guests came from. Everything that happens on a paired counter device is assigned; bookings from the dashboard appear as “no location”.
What does a branch manager see, and what not?
A branch manager sees the numbers for the locations assigned to them and the staff they are responsible for. The view across all branches and the security log stay with the owner role. Without an assigned location, though, a branch manager sees the whole business.
Does every branch need its own device?
One counter access per branch, yes. That can be a tablet with the staff app or the existing computer at the till running the counter in the browser. Either is paired once with a short code from the dashboard.
How does billing work?
Per location, graduated: the first location costs the most, every further one less, and each tier is charged at its own price. Chains get an individual quote rather than a self-service checkout.
Can we run this on our own domain?
No. The pages your guests see carry your logo and colours and run under our address.
Is there an interface to our own systems?
Yes, on the Favourite Chain plan. The POS finds the scanned card, adds stamps, redeems rewards and offers, and gets a sign-up link for new guests. The guest creates the card themselves, with their consent. Webhooks report events such as “Card issued”, “Stamp added”, “Reward ready” and “Guest deleted”. As the owner, you create API keys and webhooks yourself. There is no ready-made connector for a specific POS system; the interface is the way to build one. Go to the developer docs
Do we need our own app as a chain?
No. Your guests carry the card in Apple Wallet or Google Wallet, which is already on their phone. An app of your own would have to be built, published in two app stores and updated with every operating-system release, and every guest would have to download it first. With tapja you design the card once in the dashboard; it works in every branch and carries your logo and colours. Each branch stamps with the staff app or directly in the browser.
We already have our own app. Does this fit alongside it?
Often yes, as a complement: guests who will not install your app use the wallet card; your app users get the card on their lock screen as well. How closely the two run together depends on your system. We look at that case by case.

Tell us about your locations.

We will look at your locations, teams, redemption rules and price together. In the meantime you can start free with one location.