Multi-location redemption is now available on VoucherGrid Professional.
A voucher issued at your Paddington salon can be redeemed at your Newtown salon. Your reports still split redemptions by site. Your accountant can still see which location supplied the service. Your liability ledger still reconciles cleanly.
Nothing breaks.
Here's what changed, how it works, and why we built it this way.
What's live today
Every Professional tenant can run a single voucher pool across all active locations.
The voucher belongs to the business. The redemption record carries the location where the voucher was redeemed. Every report you already use - redemptions CSV, redemption ledger, redemption velocity, GST dashboard, BAS summary - can now be filtered by location.
At a glance
Tier: Professional.
Single-site businesses: nothing changes. The redemption screen still defaults to your one location.
Multi-site businesses: a location picker appears on the redemption screen. Reports gain a location filter and an "issued at" column.
The problem
Multi-site businesses - salon groups, clinic groups, hospitality groups, small venue networks - run into a voucher problem that single-site businesses rarely face.
The customer does not know which site issued the voucher. They usually do not care. They just want to use it.
Before this release, the cleanest model was location-specific: a voucher issued at Paddington was redeemed at Paddington. That works until the customer turns up at Newtown with a perfectly valid voucher from the same business.
At that point, the business has three bad choices. The staff member refuses the voucher, which feels absurd to the customer. The staff member accepts it manually, creating a reconciliation problem later. Or the manager has to override the process while the customer waits.
That is fine for a single-site café. It is not good enough for a business with multiple locations under one brand.
The routing model we chose
There were two possible models.
Option one - voucher-level location binding. The voucher belongs to the site that issued it. If another site redeems it, the system creates a transfer journal or settlement event between locations. Simple in theory, but it turns every cross-location redemption into an accounting event.
Option two - tenant-level voucher pool. The voucher belongs to the business. The redeeming location is recorded on the redemption event, not locked to the voucher itself. Cross-location redemption is treated as normal redemption, with reporting split by where the sale happened and where the redemption happened.
We chose option two.
The customer sees one brand. The voucher belongs to that brand. The system records the location details underneath, so the customer experience stays simple and the reporting stays usable.
The voucher belongs to the business the customer thinks they bought from - not necessarily the till, room, or front desk where it was first issued.
That model matches the customer's mental model first, then gives the business the reporting detail it needs behind the scenes.
What the staff member sees
On the redemption screen, the location picker has two modes.
Single-location businesses see no picker. Redemption defaults to their one location, the same as before.
Multi-location businesses see a picker at the top of the redemption screen. It defaults to the logged-in staff member's home location and can be changed before the redemption is confirmed.
So if a staff member at Newtown redeems a Paddington-issued voucher, Newtown is pre-selected. If they are covering a shift at another site, they can change it before confirming the redemption.
The location flows through to the confirmation state, customer receipt, redemption ledger, and GST reporting.
If Newtown redeems a Paddington-issued voucher, the redemption report says Newtown. The voucher history still shows where the voucher was originally issued. The business can see both sides without making the customer care about either.
Per-site reconciliation, unchanged
The reports you already rely on still work.
Run the Newtown report and you see what was redeemed at Newtown, regardless of where the voucher was issued. Run the all-locations report and you see the full voucher pool.
The ledger now carries both "issued at" and "redeemed at" location data. That gives owners and managers a cleaner view of which sites are generating voucher sales and which sites are supplying the services.
That matters because cross-location redemption is not automatically a problem. Often, it is a signal. A site that sells a lot of vouchers in December and another site that redeems most of them in January may be showing you something useful: where your buyers are, where your recipients are, and how demand moves across your network.
The franchise-style edge case
Independent multi-site businesses are straightforward: one tenant, multiple locations, one reporting layer at the top.
The harder version is franchise-style operation, where locations may have separate books, separate owners, separate managers, or separate internal expectations about who "owns" voucher revenue.
We have not designed the feature around a fictional case study. We designed it around the accounting shape of the problem.
If Site A sells the voucher and Site B redeems it, there are two different questions:
- Customer question: "Can I use this voucher here?"
- Business question: "Which site should see the sale, the redemption, and the service cost?"
The customer answer should be simple: yes, if the business allows cross-location redemption.
The business answer needs reporting, not friction at the front desk.
Settlement support
For operators who need it, VoucherGrid can show issued-versus-redeemed activity by location. That gives multi-site groups the data they need to make internal settlement decisions.
Independent operators may never need to think about settlement. Franchise-style or separately managed groups might. The same feature supports both without making the redemption flow harder for staff.
How to turn it on
If you are on Professional, multi-location redemption is available as part of the multi-location setup.
If you are a single-site business, nothing changes.
If you add a second location, VoucherGrid can move your voucher pool to the tenant-level model so existing vouchers remain valid. From the customer's perspective, nothing changes: same code, same balance, same expiry. The only difference is that the voucher can now be redeemed at any active location you allow.
If you are on Premium and operate multiple sites, this is one of the practical reasons to upgrade. Once you have more than one front desk, one voucher pool with location-aware reporting is much cleaner than reconciling vouchers by hand across separate spreadsheets or accounting files.
What's next
Location-specific voucher products are the logical next layer.
In most cases, a voucher should be redeemable anywhere under the same business. But there are exceptions: a spa voucher inside a broader hospitality group, a service only offered at one clinic, or a premium experience available at selected locations.
That is where location-restricted products make sense: vouchers that are explicitly limited to a subset of locations at sale time.
That feature is planned for a later release. For now, the main multi-location problem is solved: one voucher pool, location-aware redemption, clean reporting, and no awkward moment at the front desk.