QR codes for agencies, organized around the client work you actually deliver

Use folders to separate client campaigns inside one shared QRLynx workspace, assign team roles, create batches, report scan activity, and add a custom redirect domain on Enterprise.

What QRLynx gives an agency

QRLynx gives an agency one shared QR workspace with client folders, role-based team access, dynamic destination editing, plan-scoped analytics, CSV export, bulk creation, API access, and an eligible custom redirect domain.

The boundary matters: a folder organizes a client's QR codes, but it is not a separate client workspace, billing account, or permission boundary. Team roles apply to the active workspace. Keep client-facing delivery in your own reporting process unless you intentionally invite someone into that shared workspace.

Agency capability and boundary

Use the table to decide what QRLynx manages directly and what stays in your agency process.

Agency capability and boundary. Use the table to decide what QRLynx manages directly and what stays in your agency process.
Need	QRLynx support	Important boundary
Client organization	Folders and searchable saved QR projects	Folders do not create separate client tenants or folder-level permissions
Team access	Business supports up to 10 members; Enterprise supports up to 100	Viewer, editor, admin, and owner roles apply to the shared workspace
Bulk creation	Pro: 100 per batch, Business: 250, Enterprise: 1,000	Every dynamic batch also counts against active dynamic QR capacity
Reporting	Plan-scoped dashboard analytics and Business or Enterprise CSV export	QRLynx does not generate a white-labeled client PDF report
API	Business and Enterprise API keys with read and write scopes	Keys act on the owning workspace, so scope and storage need agency controls
Custom redirect domain	Enterprise can connect an eligible active domain for dynamic short links	This changes the redirect hostname, not the QRLynx dashboard or hosted pages

How to organize an agency workflow in QRLynx

A repeatable setup for one shared workspace.

Choose the workspace owner

Use the agency account that should own billing, QR records, API keys, and the active custom domain.

Create one folder per client or account

Name folders consistently, then keep each client's saved QR projects and campaign naming inside its folder.

Invite the internal delivery team

Assign viewer, editor, admin, or owner roles according to what each teammate must do in the shared workspace.

Create and test the campaign

Use individual creation, Pro or higher dynamic bulk creation, or the Business or Enterprise API. Test the exported QR on the final material.

Report from a defined campaign range

Filter the analytics view, export eligible CSV data, and turn those records into the client report your agency delivers.

Use a custom domain for the scan link, not as a portal promise

Enterprise can connect an eligible custom hostname for dynamic QR redirects, such as qr.agency.com. Add the domain in Custom Domains, point its CNAME to the QRLynx target, wait for activation, then select the active host when saving the dynamic QR.

The printed hostname cannot be changed without creating and printing a new QR pattern. Connect and test the domain before a large print run. The custom host does not rebrand the QRLynx account dashboard, login, hosted profile pages, or analytics interface. The white-label QR page documents the exact scope.

Choose Business or Enterprise by operating model

Business fits an agency that needs a shared team, CSV exports, API access, lead capture, and 250-code dynamic batches. Enterprise fits larger active-code capacity, 100 team members, 1,000-code batches, eligible custom domains, retargeting, and the broadest analytics history.

Pro can create dynamic batches of up to 100, but it does not include team management, CSV analytics export, or API access. Review the live pricing table for current prices and complete allowances.

Set up the agency workspace before the next client rollout

Start with one client folder and one tested campaign. Move to team, API, bulk, or custom-domain controls when the delivery model requires them.

Open QRLynx Business is the shared-team entry point. Enterprise adds the custom redirect domain.

Compare plans

QRLynx agency questions

Does QRLynx create a separate workspace for every agency client?

No. QRLynx resolves one active workspace owner at a time. Use folders to organize client QR projects inside that workspace. Folders are organizational, not separate tenants or permission boundaries.

Can clients log in to see only their own folder?

QRLynx team roles apply to the shared workspace and do not provide folder-level client isolation. Invite people only when shared workspace access fits your operating model, or deliver client reports outside the dashboard.

What does white-label mean in QRLynx?

On Enterprise, an eligible dynamic QR can use an active custom redirect hostname. It does not rebrand the QRLynx dashboard, login, hosted pages, or reports. See the white-label scope.

Which QRLynx plan supports agency team members?

Business supports up to 10 team members and Enterprise supports up to 100. Pro supports dynamic bulk creation but not team management.

Can an agency create QR codes through an API?

Yes. Business and Enterprise include scoped API keys for programmatic dynamic QR creation and management. Keys act on the owning workspace and should be stored like production credentials.

Can QRLynx export analytics for client reporting?

Business and Enterprise can export eligible analytics as CSV. The export is data for the agency's reporting workflow, not a branded client PDF report.