One customer promise needs an operating agreement
Quick answer
A loyalty program for multiple locations should feel simple to the customer even when the business structure is complex. A customer may expect to earn at one branch and redeem at another. Headquarters, however, must decide who funds that reward, who can change the rules, and how branches reconcile transactions.
Business owners publicly ask whether they can run separate programs for different locations in a Square Community thread. That question exposes the first decision: are you offering one shared promise, separate local offers, or a shared core with approved variations? Choose before creating card templates.
Define shared and local rules explicitly
Write a short program specification covering eligible purchases, thresholds, available rewards, expiry, refunds, and cross-branch redemption. Then mark which terms a branch may vary. Local prices and stock can differ, but a customer should not discover at redemption that their earned benefit means something entirely different elsewhere.
Boomerangme's franchise and multi-location page describes a unified loyalty program, cross-location earning and redemption, and headquarters versus local views. Those are relevant capabilities to evaluate. Confirm that your intended account structure, card type, and commercial plan support the exact shared workflow you need.
If locations are independently owned, customer data access and program liability need an agreed commercial framework. A shared brand does not automatically mean every franchisee should see every customer or absorb every reward. Put the operating rules in writing before enrollment creates obligations.
Cost cross-location redemption
Here is a hypothetical two-branch example. Branch A records ten eligible purchases that earn one reward. The customer redeems it at Branch B, which incurs $6 of variable fulfillment cost. If no settlement exists, A receives the earning sales while B bears the cost. Repeated across many customers, that can create disagreement even when the customer experience looks seamless.
Possible policies include a centrally funded pool, a fixed reimbursement per eligible redemption, or an allocation based on qualifying earning activity. These are design options, not assumptions about Boomerangme's accounting functions. Choose one with your finance team and maintain a reconciliation record.
Track the branch where earning occurs, the branch where redemption occurs, reversals, and the amount eligible for settlement. Reconcile on a regular timetable. A loyalty report may support the process, but it should not silently become the authoritative franchise accounting ledger.
Test permissions rather than trusting a role name
Boomerangme's franchise-account documentation states an important limit: the main franchise account owner has access to all branches, while franchise-level managers do not gain branch access merely by receiving all available permissions. That matters when designing a headquarters operations team.
Do not promise every central employee a complete branch dashboard. Map actual people to actual permitted actions and test those accounts. If the documented permission structure does not match your operating model, discuss the requirement with the provider before rolling the program out.
A branch employee may need to record earning and redemption without changing templates or viewing unrelated customer records. Boomerangme's manager-profile documentation lists configurable permissions. Use the least access required for the job and verify both what a user can do and what they cannot do.
A two-location pilot checklist
- Write the shared customer promise and any approved local variations.
- Confirm the actual account structure and plan with the provider.
- Assign responsibility for reward funding, reversals, disputes, and reporting.
- Test earning at A and redemption at B, including an unavailable reward.
- Test owner, headquarters manager, branch manager, and counter-staff access separately.
- Check refund behavior and avoid restoring value twice across systems.
- Reconcile a sample week of transactions before adding more branches.
The official franchise page also describes location-level statistics. Use them to compare execution: invitation rates, eligible transactions recorded, and successful redemptions. Avoid comparing raw branch revenue without adjusting for traffic, pricing, opening hours, and product mix. A strong branch may reflect a better trading location rather than better loyalty management.
Questions multi-location owners ask
Can customers use one card at every branch?
That is a documented Boomerangme franchise use case, but verify your specific configuration. Decide eligible locations and make the customer-facing terms match the tested workflow.
Can all headquarters managers access every branch?
Do not assume so. Current franchise documentation reserves full branch access to the main account owner; manager access has limitations that should be tested before launch.
Who should pay when another branch redeems a reward?
The business needs an explicit settlement policy. Software capability alone does not resolve the commercial agreement between independently operated locations.
A successful chain program combines a clear customer benefit with clear internal responsibility. Explore Boomerangme using your proposed account map, cross-branch test cases, and reward-funding rules.
Sources & further reading
- Boomerangme franchise and multi-location storesVerified cross-location program and location-level reporting use cases; commercial configuration must be checked.
- Boomerangme franchise account documentationVerified main-owner branch access and franchise-level manager limitations.
- Boomerangme manager profile permissionsObserved permission controls; article recommends testing actual roles rather than claiming universal access.
Sources reviewed October 5, 2026. Numerical examples are illustrative unless a cited source states otherwise.
