Managing WiFi QR codes across many stores
Three branches and memory works fine. At a dozen, the same three failures show up: someone scans the code from another branch, a sticker gets removed and nobody replaces it, a password changed but the card on the wall did not. Multi-site really needs three conventions — network model fixed first, one numbering scheme, and every change going through a process.
1. Decide the network model before designing anything
None of the three models is inherently better; it depends on store count, who your guests are, and whether staff roam between sites.
| Model | Fits | Cost |
|---|---|---|
| One SSID and one password everywhere | Under three to five stores; mostly regulars and staff | One leak breaks every branch; a rotation replaces every card |
| A guest network per branch (SSID suffixed with store code) | Many stores; most traffic from strangers | One card per branch; changes and restocking need an owner |
| Mixed: shared staff SSID, per-branch guest SSID | What most chains end up doing | Two policies to document and maintain |
A workable SSID convention is brand plus store code plus purpose, for example 365Lab-SH01-Guest. Store codes of two to four letters and digits do not give away an address, and the suffix separates staff from guests. This sharply reduces wrong-branch scans and makes device lists filterable. See SSID naming rules for the details.
2. Numbering: give every card an identity
- Print an ID on the card. A small line at the bottom such as
SH01-G-01— store code, purpose, revision. Guests ignore it; restocking does not. - Name the exported files the same way.
SH01-guest-v1.png, never "final2" or "new new". Six months later nobody can tell them apart. - Fix the placement in the standard. Three fixed positions per store, such as counter stand, table corner, next to the till. A fixed position is what makes an inspection meaningful.
Five columns the register needs
- Store code and store name
- SSID and the actual password (in an internal document, not on a store PC desktop)
- Card revision and sticker date
- Owner — who reprints, who holds admin rights
- Result of the last scan spot-check
With all five filled, staff turnover, password rotation and missing stickers are all self-documenting.
3. The least painful way to produce them in bulk
One template, three variables (store name, SSID suffix, password), export per branch. The reason this beats scripting: the template guarantees identical quiet zone, contrast, margins and size on every card, while a script will quietly shrink the code for the branch whose name is two characters longer.
- Pick one layout from the template library and lock the font sizes and margins.
- If a store name runs over about eight characters, shorten the name rather than shrinking the code.
- After exporting each branch, run the payload through the validator once — especially where the name contains non-Latin characters, a hyphen or an ampersand.
- Derive sizes from viewing distance with the size calculator so every branch gets the same number, not each manager's own guess.
4. Rotating a password without a gap
The risk is not the rotation itself but doing it unevenly: half the branches pulled the old code and half never got the new one.
- Print the new cards and ship them before the new password goes live.
- Place the new code beside the old one in the same position, keep both for three days to a week.
- At the end of the overlap, remove and collect the old stickers and bump the revision in the register.
- Delete old export files from store computers so nobody reprints from a stale file.
On the single-password model there is no phased overlap at all — you must replace everything in one closing window. That is the hidden cost of that model. For a single store, see what to do with old codes after a password change.
5. Quarterly audit checklist
- Scan at 10% of branches in person and confirm both connection and actual internet access — connected is not the same as online, see connected but no internet.
- Check for stickers covered, torn, warped by drinks, or hidden behind a new poster.
- Reconcile the register against the live SSID, especially branches that got a new router.
- Confirm no branch changed the guest password privately or added a second router.
- Write the result back into the register so revision history stays traceable.
Start from one standard template
Lock the layout and the size in the studio, then export branch by branch with only the variables changed.
Open the WiFi QR code studioRelated reading
Frequently asked questions
Can every branch share one SSID and one password?
How do you produce dozens of branch-specific codes efficiently?
A branch rotates its password. What about the old stickers?
How do you stop store managers from changing the guest password?
Templates that fit this setup
Three layouts picked for this scenario — swap the venue name and password, then export.