One card, one balance, branches as labels
A branch in Waya is a label on activity, not a second loyalty card. You build one card, and every location uses it. A customer who enrolls at your Olaya store and gets stamped in Tahlia the following week sees a single balance on one wallet pass, not two half-full cards.
All the branch does is tag rows in your data. Waya records which branch a customer joined at, and which branch each stamp or redemption happened at. Nothing about the pass itself changes between locations: same design, same reward, same QR lookup for your cashier.
There is no POS integration and no hardware to install, so every branch works identically. Staff add stamps by scanning the customer's card on an ordinary phone, either in the web dashboard or the Waya merchant iOS app. Waya sits beside whatever till each location already has, and no SMS is involved anywhere in the flow.
One thing to know before you plan the rollout: the free plan allows 1 branch. Multi-branch starts on Growth at 85 SAR a month (867 SAR a year), which covers up to 3 branches and 5 staff accounts. Premium at 149 SAR a month removes the branch, staff, and message limits.
Adding a branch takes about two minutes
Branches live in Settings, under the Branches section. Each row takes a name, an address, a phone number, and a map pin. You can capture the pin from the device's own location while standing in the shop, or open the map picker, search for the address, and drop it manually. Merchants who don't want to share live location should use the picker.
Name each branch the way your staff says it out loud: "Olaya", "Tahlia", "Granada Mall". That name is what shows in your reports and on the branch QR code card, so a vague name like "Branch 2" costs you clarity later.
The first active branch you create is automatically the primary one. Primary matters in exactly one place: wallet passes accept a maximum of 10 locations, so if you ever pin more than 10 branches, the primary goes in first and the rest follow in the order they were created.
Removing a branch archives it rather than deleting it. Past sign-ups and scans keep their branch name in reports, and the archived branch stops counting against your plan's branch limit, so closing one location and opening another doesn't require an upgrade.
Give each branch its own QR code
Once a shop has two or more active branches, the card's QR screen shows a separate QR per branch alongside the plain shop-wide link. Each branch QR carries that branch's id in the enrollment URL, so a sign-up scanned from the table tent in Tahlia is attributed to Tahlia automatically. Print the right one at the right counter and attribution takes care of itself.
The shop-wide link keeps working. Anyone enrolling through it, from your Instagram bio or a shared poster, lands in an "Unassigned" bucket in the branch report. That's fine for online channels, and it's the main reason a branch comparison sometimes has a large unattributed slice.
Staff accounts can be assigned to a branch when you create them. An assigned cashier's scans are always tagged to that branch, whatever is selected on screen, which stops mis-tagging without asking anyone to remember a step. Unassigned staff and owners pick the branch on the scan screen, and that device remembers the last choice.
Which reports split by branch, and which don't
A "By branch" panel appears in your Insights once you have more than one branch with activity in the selected date range. It shows two things: a donut of who came from which branch, and a table with Sign-ups, Visits, and Redeemed for each branch, plus an Unassigned row when untagged activity exists.
The definitions are worth memorizing before you draw conclusions. Sign-ups counts passes created in the range, attributed to the branch a customer joined at, not where they later spend. Visits counts stamp and point additions. Redeemed counts rewards actually claimed. So a branch with high sign-ups and low visits is enrolling people who never come back to that counter.
Plenty of the dashboard stays deliberately shop-wide: total customer count, new versus returning, and the list of regulars who have gone quiet. Your monthly wallet message allowance is pooled too, not divided per branch, which means 100 messages a month on Free and 5,000 on Growth cover all locations together. Excel and CSV customer import, available on paid plans, is also shop-level.
A worked example with three branches
Assume three branches in Riyadh, each serving roughly 200 customers a month, and a shop-wide enrollment rate of about 20%. That would be around 40 sign-ups per branch, or 120 for the month. These are assumptions for the arithmetic, not measured Waya averages.
Now suppose the report comes back at 51 for Olaya, 44 for Tahlia, and 9 for Granada Mall. The interesting question isn't customer quality, it's whether the Granada QR is actually visible at the register or sitting in a drawer. Branch reporting is most useful as a check on staff habits and poster placement, which is something you can fix the same day.
Be careful with the comparisons you make. A mall kiosk and a neighborhood cafe do not have comparable footfall, so visits per sign-up tells you more than raw totals. And a branch that opened three weeks ago will always look weak against one that has been collecting customers for a year.
Branch pins drive proximity reminders. The card's address fields don't.
This is the part that catches most multi-location merchants. The card designer has its own Address field and a Google Maps link field. Those two print on the back of the wallet pass so a customer can tap through for directions. They are static text. They never create a geofence, and filling them in does nothing for reminders.
Proximity reminders come from branch coordinates only. Every time you save the Branches screen, Waya rebuilds the location list attached to your card from active branches that have a pin, primary first, capped at 10. Apple Wallet receives those as the pass's own locations with a maximum distance; Google Wallet receives them on the loyalty class. That's why a branch you typed an address for but never pinned contributes nothing.
Two switches both have to be on. The location reminder toggle in the Notifications screen must be enabled, and at least one branch must have coordinates. The radius is a slider from 50 to 500 meters, in 50-meter steps, and it defaults to 150 meters. Tight radii suit a standalone shop; a mall unit usually needs more.
Set expectations honestly with your team. This is passive relevance, not a push you schedule: Apple and Google decide whether to surface the card on the lock screen when the phone is near a pin, and the customer's own settings affect that. On the plus side, it isn't a wallet message, so it doesn't draw down your monthly message allowance. Treat it as a free nudge, not a campaign.
Frequently asked questions
Does each branch need its own loyalty card?
No. One card covers every branch, and the customer keeps a single wallet pass with one balance. The branch is recorded as a tag on each sign-up and each scan, which is what feeds the by-branch report. Building a separate card per location just splits your data and wastes card slots.
Can a customer collect stamps at one branch and redeem at another?
Yes. The balance belongs to the customer's pass, not to a branch, so stamps collected in one location are redeemable in any other. The redemption is still recorded against the branch where it happened, so your report shows which counter is giving away the rewards.
How many branches can I have on the free plan?
One. The free plan allows 1 branch, 1 stamp card, up to 100 customers, and 100 wallet messages a month, at 0 SAR with no credit card. Growth at 85 SAR a month raises that to 3 branches and 5 staff accounts, and Premium at 149 SAR a month is unlimited on branches, staff, and messages.
Why aren't my customers getting branch reminders?
Almost always one of three things: the location toggle in the Notifications screen is off, the branch has an address typed in but no map pin, or the radius is set too tight for the building. Remember that the Address and Google Maps fields on the card itself are only for directions on the back of the pass and never create a geofence. Even with everything configured, Apple and Google decide when to surface the pass, so it is a nudge rather than a guaranteed delivery.
What happens to my reports if I close a branch?
Removing a branch archives it instead of deleting it, so its past sign-ups, visits, and redemptions stay visible in historical reports under the same name. The archived branch stops counting toward your plan's branch limit, which frees the slot for a new location on the same plan.