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.

ModelFitsCost
One SSID and one password everywhereUnder three to five stores; mostly regulars and staffOne leak breaks every branch; a rotation replaces every card
A guest network per branch (SSID suffixed with store code)Many stores; most traffic from strangersOne card per branch; changes and restocking need an owner
Mixed: shared staff SSID, per-branch guest SSIDWhat most chains end up doingTwo 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

  1. 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.
  2. Name the exported files the same way. SH01-guest-v1.png, never "final2" or "new new". Six months later nobody can tell them apart.
  3. 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.

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.

  1. Print the new cards and ship them before the new password goes live.
  2. Place the new code beside the old one in the same position, keep both for three days to a week.
  3. At the end of the overlap, remove and collect the old stickers and bump the revision in the register.
  4. 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

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 studio

Related reading

Frequently asked questions

Can every branch share one SSID and one password?
Technically yes, and one card design covers all of them, which saves dozens of print runs. The cost is that a single leak invalidates every branch and a password change means replacing every card. Past three to five stores, or where most traffic is strangers, separate guest networks per branch are safer.
How do you produce dozens of branch-specific codes efficiently?
Keep one template and vary three fields: store name, SSID suffix and password. Export per branch and name files by store code and purpose. Doing it through the studio beats scripting, because the template guarantees identical quiet zone, contrast and size on every card.
A branch rotates its password. What about the old stickers?
New first, old later: put the new code beside the old one in the same spot, leave both for three days to a week, then remove and collect the old stickers so nobody scans a dead code.
How do you stop store managers from changing the guest password?
Keep guest-network admin rights at head office and give managers view-only access. Log every change with store, date and operator, and spot-check 10% of branches by actually scanning during quarterly audits.

Templates that fit this setup

Three layouts picked for this scenario — swap the venue name and password, then export.