Agency qr code client work, one owner
SmartQRCode editorial · Updated October 2026
Agency qr code client work is hosted codes you create for someone else's shoppers. Give each client their own owner namespace. Do not share a scan host. Write who keeps destination control after the retainer ends. Canva remains the honest one-off when the client will never edit or count.
How agency qr code client work should be namespaced
Isolation is one owner account per client. The rule is do not share a scan host. Write the handover of destination control in the SOW. Keep a short code to sku sheet with the files.
one owner account per client is the isolation unit. Seats on that owner see every code in the namespace. An admin who works both Brand A and Brand B on one login will see both lists. That is convenient and wrong. Two owners is the split. Your people hold member or admin seats on each.
do not share a scan host. The certificate in the padlock is the hostname. Mixing tenants is how a shopper sees the wrong company. The print-facing version of that rule is agency QR white label host. Scanner chrome is white label qr codes. Seats are QR codes for teams.
Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. Deliver custom landing pages when the brief is a page you author, the website URL generator when it is a link, and tracked QR codes when finance wants a series. Product launch placements are the usual retainer shape.
Hosted objects last as long as the provider resolves them. If the client needs a code that survives with no resolver, it has to be static. This product's static type is Wi-Fi, which is not editable and not trackable. For a marketing URL, static means a Canva file, and a later URL change is a reprint.
How to keep client A off client B's host
Create codes against the host that will appear in the modules. Proof the padlock on a phone. A staging scan through another client's hostname should 404. If it 302s, stop the press.
- Open a distinct owner for the client, or use their existing owner and take a seat.
- Attach their hostname only after it is active, then create. Do not encode your agency subdomain on their cartons unless the SOW says the padlock is yours.
- Map short code to SKU on a sheet the client can read without you.
- Export SVG or 300 dpi PNG or PDF. Ban screenshots of /qr-preview in the traffic folder.
- Size at least 2 cm at 30 cm with a four-module quiet zone. Larger for trade-stand distance.
- Proof on the formed pack, rather than the flat proof alone, when the job is packaging.
- Pause-test the status page on their host so a failure does not show a trial button if the brief forbade it.
- At handover, transfer owner or document that the agency remains owner. Do not leave this verbal.
handover of destination control is the clause that prevents a 3am call when the client fires you and the cartons still 302 through your account.
Who owns the destination after you leave
If the agency is owner, pause, destination edits, and billing sit with you. That can be the product you sell. It is also a lock-in you must state. If the client is owner, your designers are seats. They can be removed. The ink keeps working on the client's resolver.
Print does not care about the SOW. Modules encode a URL. Whoever controls that hosted row controls the shopper. Write the named owner in the SOW before the first plate.
A provider outage on that owner stops the field. F91 is part of the handover conversation, not a footnote.
What to print on a retainer pack
A short code to sku sheet, the vector or high-resolution rasters, and a note of the encoded host. That pack is what a plant needs. A Figma frame with a screenshot is not.
Agree pause versus archive. Archive keeps scanning. Night operators who "archive" a live SKU will not understand the ticket.
Do not put Wi-Fi on the same spec as tracked URLs without labelling which one is silent.
Agency failures that reprint the wrong brand
Encoding the agency host because DNS on the client host was "almost ready." The cartons show you. Reprint is the only fix.
Reusing one short code across two clients to "save a row." Analytics and destinations then mix. Isolation is not a colour.
Leaving /qr-preview in the approved art. Every guest opens a preview payload.
Assuming white label rebrands your invoices. It does not. Scanners are the audience.
How to price the lock-in you are actually selling
If the agency remains owner, say that destination control is a retained service, with an off-boarding that reprints or transfers the owner account. If you stay silent, the client will assume they can log in on Friday after they fire you on Thursday. They cannot, if you hold the namespace.
If the client is owner, your hours are labour on their object. Your designers can be removed. Keep local copies of the approved SVGs anyway. Plants call the last person who had the file, which may be you, after the seat is gone.
Do not put two clients in one Stripe customer because it is easier for your bookkeeper. Isolation is one owner account per client. Bookkeeping can join later. Shoppers cannot unsee a mixed padlock.
White-label scanning will not rebrand your invoices. Tell the finance contact that before they promise "it will look like our software" to their board. Scanner chrome and operator chrome are different products.
A Canva one-off the client exports themselves should be in the SOW as out of scope, so you are not paged when their bake-sale poster fails on uncoated stock.
Put a kill switch in the SOW: who may pause, in what window, and how the client is told. A merchandiser at the client who is a member can pause without you. That can be the product. It can also be a surprise if the SOW implied only the agency may touch destinations.
Do not use the client's production host as a staging sandbox. Create staging codes on the platform host or a staging hostname, and never mix those short codes into the plant ZIP. Agency qr code client work goes wrong most often as a ZIP that contains last week's experiments.
When the client asks for a weekly PDF of scans, agree whether they get hops or a unique approximation, and paste the privacy sentence: no scanner name or email. Over-promising identity is how legal reviews stall a launch you already plated.
Archive the SOW, the SKU map, and the encoded URL screenshot in one folder named after the client legal entity, not after the job nickname. Nicknames collide. Legal entities do not. When a holding company asks for all QR assets, you need that folder, not a Slack search.
When the client should generate in Canva
One frozen URL, no count, no later edit: they should use Canva or another free static generator. Charging a retainer to host that poster is the wrong product.
Many SKUs, later URLs, padlock on their name: agency qr code client work. Keep namespaces, hosts, and the SOW in the same folder as the print files.
Questions this raises
The owner account that holds the codes. If that owner is the agency, the client cannot retarget without you. If that owner is the client, your access is a seat. Write it in the SOW before the first plate.
Hosted types with a mapped short code, SVG or 300 dpi files, and a proof scan on the real stock. Do not ship /qr-preview screenshots. Do not share a scan host across brands.
When they have one frozen URL and will not count scans. Agency qr code client work is overhead on a bake-sale poster.
Not on one owner namespace. Seats see that namespace. Isolation is a second owner, not a costume role.
No. White-label scanning is scanner-facing. Your invoices still look like the product. See white label qr codes.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.