QR codes on your clients' domains: a workflow for agencies

You print menus, posters or stands with a QR code for a client. If the link runs on your agency's domain or the service's domain, the print depends on that address. If it runs on qr.yourcompany.com, the client's own subdomain, the code stays theirs no matter who looks after it later.

What the Agentur plan offers

With the Agentur plan you can connect up to 50 custom domains, usually one subdomain per client. Only a subdomain can be connected, never the main domain, so your client's website is not touched. For comparison: Gastro Pro and Marketing Starter allow one domain, Marketing Pro three, Gastro Expert five and Marketing Expert ten.

Who sets the DNS record

The records have to be created where the domain is managed. That is almost always the client, their host or their IT, not you. You enter the subdomain in the dashboard (the “Custom domain” window) and get two records to pass on to the client:

• A TXT record named _sameqr.qr.yourcompany.com with the value sameqr-nachweis=… (the proof of ownership shown in the dashboard).
• A CNAME record: qr.yourcompany.com points to kunden.sameqr.com.
• If the client uses Cloudflare for DNS, set the CNAME to “DNS only” (grey cloud).

Once both records are in place, the service issues the HTTPS certificate automatically and the status changes to “Active”. If it takes longer than expected, the article on troubleshooting custom domains helps.

Getting sign-off from the client

A DNS record is a change to the client's infrastructure. Get their approval in writing, an email is enough. It helps if the message covers these points:

• Exactly which subdomain will be created, for example qr.yourcompany.com.
• That only this subdomain is affected, not the website and not email.
• Who creates the records, the client or their provider.
• That the domain belongs to the client and they can repoint it at any time.

Handover checklist

• The client's approval is on file.
• TXT and CNAME are set and the dashboard status reads “Active”.
• When creating the code, the client's domain is selected as the address and the path is readable, such as qr.yourcompany.com/menu.
• Test scan with an iPhone and an Android phone, with no certificate warning.
• The client knows the CNAME must stay in place as long as the codes are in circulation.
• The client has access to their DNS provider login, even if you do not create the records yourself.

Each path exists only once per domain and stays reserved even after the code is deleted, so plan your paths before printing. Scans are counted as usual and time rules work the same way.

What happens when a client leaves

The domain always belongs to the client. If they part ways with you or with Same-QR, they point the CNAME at the new provider. The printed codes keep working as long as the new provider can serve the same paths on that domain. Hand over a list of all paths and their targets.

If you delete codes, the printed copies stop working, so do not remove anything before the client has switched. A domain can only be removed once no codes remain on it. If you move to a smaller plan yourself, codes on domains that are already connected keep running. New codes are then possible only on as many domains as the new plan allows.

Frequently asked questions