Partner track
One brand, separately owned locations
Franchisees run their own sites, often as separate legal entities, and a network still has to look like one brand to the customer standing in front of it. White Label gives every location the same domain and the same system emails.
Underneath that, each location keeps its own administration, and the network reads analytics that roll up across all of them.
At a glance
- What the customer sees
- The network's brand, on the network's domain
- What the franchisee runs
- Their own locations and Staff Logins
- What the network reads
- Ratings by Staff Login, rolled up
- Billing today
- Through the partner's access codes
Updated
What a network actually needs
Franchising breaks most tools at the point where ownership and brand stop matching each other.
The brand does not fragment
Every code, page and email carries the network's domain, whoever owns the location it is printed in.
Comparable numbers
One rating scale across the network means a site in one city can be compared with a site in another without a caveat.
The complaint reaches the right owner
Every counter rating carries its Staff Login, and the review is emailed to the business that collected it, so it reaches the people who can act on it.
A franchisee can be a partner
A large franchisee can sit on either side of the arrangement — end customer, or partner reselling into their own region.
Said plainly
What we can and cannot promise about franchisee billing
Today, locations in a managed network are paid for through the partner's access codes. That is the released mechanism and the one to plan around.
A partner's own billing — invoicing each franchisee directly through your system — is an early invitation for selected partners, without dates and without guarantees. On the standalone 7Feedback side, billing is still being defined rather than inherited.
The honest formulation for a franchisor is this: today it runs through partner codes, and direct franchisee billing is an early-access conversation, not a shipping feature.
Network questions
Do we need to integrate with our POS?
No. The terminal application installs next to your other Android apps and does not touch the payment flow, so it needs no payment-side certification. A printed QR needs no integration at all. Your own POS can ask through the Integration API if you want the question on its screen.
Can we run it under our own brand and domain?
Yes. With White Label the feedback page and the system emails come from your domain in every channel — the printed QR, the follow-up pages and the chat-bot's web page alike. For a terminal fleet sold under an acquirer's brand this is a condition of the deal rather than an option.
Is card-linked recognition actually live?
It is built and running with a payment partner, on stacks that expose PAR or a stable token at the moment of the transaction. It is not a claim that it works on every stack: without access to PAR the fallback is a token stable within one acquirer. The card number is never used and never hashed.
How many applications go onto the terminal fleet?
One. Feedback collection is a mode inside the existing 7Stamp Scanner APK, so an acquirer certifies, versions and supports a single application across the fleet. A second application is not published and is not offered.
Next step
Tell us how the network is owned
How many locations, how many legal entities, and who you want to hold the invoice. The answer follows from that.