Owners can see all locations, compare activity, open location detail pages, and review business-wide Dashboard and ROI views.
Multi-location
One loyalty program,
the right access for every team.
Webbership is built for businesses that grow beyond one counter. Each location can have its own QR code, each card use keeps its location, and managers or staff work only with the shops they are responsible for.
Structure 1+ locations
Location enrollment, location activity, scoped team access.
Why it matters
A six-location café should not be managed like one counter.
Once a business has multiple shops, loyalty becomes a question of origin, activity, and access. You want to know where a customer joined, where they actually come back, and which team is allowed to work with that data.
- Separate QR code per location, so enrollment keeps its starting point
- Each stamp and reward can be tied to the location where the card was used
- Admins and staff can be limited to one or more assigned locations
Concrete example
Sunbeam has six cafés. Each team sees its part.
The owner sees all six locations. The north manager sees Unirii and Pipera. The west manager sees their three locations. Staff can work across one or more shops depending on shift. A customer can join at Unirii, use the card at Floreasca, and still be tracked correctly in both places.
Enrollment Unirii QR Customer enters the program through the location code.
Usage Floreasca The stamp is recorded where the card is used.
Access Area manager Sees assigned locations, not the whole chain.
Access model
Location scope is applied where work happens.
Multi-location loyalty is not just a dropdown on a report. Access rules need to affect the counter, member records, corrections, and the numbers owners trust.
Non-owner admins work inside their assigned location set. Member lists, history, staff views, and stamp corrections respect that boundary.
Staff access is tied to the selected location. The app re-checks that the location is still active before allowing the counter flow.
Stamps and redeemed rewards carry the location where they happened, so reporting can separate where customers joined from where they returned.
Structure
How access splits in practice.
Location QR
A customer who joins at Unirii, Floreasca, or Pipera keeps that enrollment location in their history.
Real activity
See where a customer uses the card, not only where they first entered the program.
Scoped teams
Admins and staff can work across one or more locations depending on shifts and responsibility.
Filtered data
Members, history, stamp actions, and location details respect the access boundary.
What this means for you
Location loyalty should be clear for people, not just reports.
This is the difference between a digital stamp card and a loyalty operating system: each team sees what it needs to run, while you see the whole business.