Skip to content
← All articles

How Agencies Manage QR Codes for Many Clients

2026-11-12 · 6 min read agencies client reporting business plan tutorial

How Agencies Manage QR Codes for Many Clients

On this page
  1. Decide first: whose account holds the codes
  2. Organize codes per client
  3. Give each person only the access they need
  4. Report to clients without sharing a login
  5. White-label the parts the public sees
  6. When a contract ends
  7. Which plan you need
  8. FAQ
  9. Sources

An agency that prints QR codes for clients carries a long tail of responsibility: the codes outlive the campaign, the client changes their website, and a year later someone asks why the table cards stopped working. The setup decisions made on day one, whose account the codes live in and whose domain they use, decide how painful that is.

This guide covers the two account models that work in QR Maker AI, how to organize codes per client, how to give clients reports without sharing a login, and what to do when a contract ends. Most of it uses the Business plan, which includes team access, embeddable analytics, scan exports, the API and a custom short-link domain.

Facts checked on 22 October 2026.

Decide first: whose account holds the codes

Codes cannot be moved from one account to another, so pick the model before anything is printed.

Model A: one agency accountModel B: one Business account per client
Who paysThe agency, onceEach client
Short-link domainThe agency's own (one per account) or the shared qrmk.ccThe client's own subdomain, such as go.clientbrand.com
Who editsThe agency account ownerThe client's account owner
Agency staff accessOwner plus read-only team membersRead-only team member in each client account
When the contract endsCodes stay in the agency's accountNothing to hand over
Best forMany small clients, short campaignsClients with long-lived print (packaging, signage)

Two limits drive the choice. Each account can use one custom domain, so clients who want their own name on the short link need their own account. And team members are read-only, so in Model B the client's own account owner makes the edits, or the agency requests them.

There is a precedent for getting this wrong with domain names. ICANN warns domain owners that a developer they hired "may have registered the domain name using their own contact details", even when the client paid, and may then be listed as the official registrant (ICANN). The same thing happens with QR codes: if the codes sit in the agency's account, the client depends on the agency to keep them running. Say which model you use in the contract.

Organize codes per client

In Model A, every client shares one dashboard, so naming does the work:

Dashboard filtered to one client's folder, with codes named by client, campaign and placement

Screenshot from a demo account with sample data.

For a large rollout, the bulk CSV page creates one code per line, and the REST API can create them from your own systems with a client reference in external_id.

Give each person only the access they need

NIST defines least privilege as restricting access "to the minimum necessary to accomplish assigned tasks" (NIST CSRC). In practice:

The sharing analytics tutorial covers team invitations and tokens step by step.

Report to clients without sharing a login

Three ways to show a client their numbers without giving them access to the account:

  1. Embedded analytics. Create an embed key for a client's code and paste the snippet into the client's portal or intranet page. The key works only from the web addresses you list, shows scans, countries, devices and referrers, and never shows the destination or routing rules. An account can have up to 20 keys, one code each.
  2. A monthly export. On the Business plan, each code's analytics page has Export scans (CSV) with one row per scan; build the client's report in a spreadsheet (export guide).
  3. An automated report. The API's cross-code summary returns scans and unique visitors per code or per folder for a date range, which is enough to fill a client dashboard in your own reporting tool.

Embed key for one client code, limited to the client portal's address

White-label the parts the public sees

Clients' customers see two things: the short link and, if a code is switched off, an error page.

When a contract ends

Printed codes keep working after a contract ends, so plan the exit:

Which plan you need

What you wantFreeProBusiness
Unlimited dynamic codes, folders3 active codes, with foldersYesYes
Bulk creation, smart routing, password and expiryNoYesYes
Team members (read-only)NoNoUp to 10
Embedded analytics, scan CSV export, APINoNoYes
Custom short-link domain, white-label error pageNoNoYes, one per account
Price as of October 2026$0$3.99 a month or $34.99 a year$29 a month or $279 a year

The monthly Business plan starts with a 14-day free trial for new customers; a card is required. See the agencies page and the pricing page.

FAQ

Can I give a client access to only their own QR codes?

Not through the team feature, which shows the whole account. Use an embed key per code, a CSV export, or a separate Business account for that client.

Can I move a client's QR codes to their own account later?

No. Codes stay in the account that created them. If a client may want ownership later, create their codes in their own account from the start.

Can one account use a different custom domain for each client?

No. Each account can use one custom short-link domain at a time.

Do a client's codes stop working if our agency cancels Business?

No. Codes keep redirecting, including codes on your custom domain. Embedded analytics, the API and domain settings pause until the plan is renewed.

Sources

  1. ICANN — General Questions. Undated. Accessed 22 October 2026.
  2. Google — URL builders: Collect campaign data with custom URLs. Analytics Help, undated. Accessed 22 October 2026.
  3. NIST CSRC — least privilege (glossary). Undated. Accessed 22 October 2026.
  4. OWASP — Secrets Management Cheat Sheet. Undated. Accessed 22 October 2026.
  5. Microsoft — Prevent dangling DNS entries and avoid subdomain takeover. Updated 20 July 2026. Accessed 22 October 2026.

Create a free dynamic QR code — change the destination anytime and track every scan.

Start with this design →