One problem — one printed QR, many branches
You printed restaurant table tents, flyers or product inserts with a single QR code. Scanners in branch A should open a WhatsApp conversation with branch A, scanners in branch B with branch B — without a new print run. How do you achieve this regional customer chat routing, retain central control and get meaningful usage data?
Why a dynamic QR is the best solution here
A dynamic QR code separates the physical print image from the target: the QR remains unchanged, the target can be changed at any time. With Linkentra you manage the code centrally, export high-quality PNG/SVG for printing, adjust branding and see how often and where it was scanned. Crucial for regional routing is that the shortlink does not rigidly point to a single WhatsApp URL, but is coupled to logic/redirects that select the appropriate WhatsApp destination based on the scan context.
Overview: Three practical ways to regional WhatsApp routing
- Server-side redirect (recommended): A dynamic link in Linkentra points to your own redirector (self-hosted or cloud). This determines the appropriate branch based on IP geolocation or similar signals and redirects to the corresponding WhatsApp URL.
- Location selection page: The link opens a slim landing page with branch selection (buttons to wa.me/…). Easy to implement, no geodata required, higher conversion because users have to click.
- Branch identifier as QR parameter: If you do want to print different QR variants per branch, a one-time print image per branch is enough. Advantage: simplest technique; disadvantage: no unified print file.
Practical setup with Linkentra — step by step (server-side redirect)
The following guide describes a robust solution: a Linkentra project, a dynamic shortlink and your own redirector that routes to WhatsApp numbers based on location.
1. Create a project and dynamic shortlink in Linkentra
- Create a new project in Linkentra for the campaign/branch group (central management of all associated shortlinks, media and analytics).
- Create a dynamic shortlink, e.g. /kontakt, and set the target to the URL of your redirector (self-hosted or cloud endpoint).
- Generate the QR code in Linkentra and export as PNG/SVG – this QR image remains identical for printing.
2. Implement the redirector
The redirector is a small web service that analyzes the incoming request and redirects with HTTP 302 to the appropriate WhatsApp URL.
- Logic: IP geolocation → industry selection → redirect to wa.me/?text=…
- Fallback: If IP geolocation fails or no suitable branch is found, redirect to a selection page or a central WhatsApp number.
- Integration: The redirector can use Linkentra APIs/webhooks to log scan metadata or update targets dynamically.
3. Configure fallbacks and scheduling in Linkentra
- Linkentra allows you to set a fallback target for the short link — e.g. a generic contact page or a central WhatsApp number. This keeps the user experience stable if your redirector fails.
- Use scheduling: For special actions (e.g. happy hour support) you can define time-based targets that switch automatically.
4. Tracking and analysis
Linkentra provides statistics about scans. Combined with server logs from your redirector you get:
- Number of scans per location (IP-based evaluation or selection data),
- Conversion: how many clicks led to WhatsApp opening,
- Temporal patterns: times of day with particularly high chat volume.
Concrete example: restaurant chain
Situation: A table tent with a uniform QR is used in 20 branches. Only one design is printed; nevertheless guests should chat directly with the local service WhatsApp.
Solution in brief:
- Create a Linkentra project and a dynamic short link /gastkontakt.
- Implement a redirector: IP geolocation maps visitors to branch numbers; in case of uncertainty a small selection page opens.
- Management: Phone numbers and texts are maintained centrally in the redirector or via the Linkentra API; changes without reprinting.
- Fallback: Outside the regions or in case of errors redirect to the central hotline.
Tips and practical notes
- Data protection: IP-based localization is only approximate and may be relevant under data protection law. Check local requirements and document data usage.
- Test fallbacks: Simulate redirector outages to ensure Linkentra fallbacks take effect.
- Branding: Export the QR as an SVG to integrate print data cleanly and adjust the appearance.
- Bulk import: For many branches import phone numbers via CSV/JSON and apply them automatically via the API.
- White-label and self-hosted: If you need full data sovereignty, self-host Linkentra or choose the white-label edition.
Checklist before rollout
- Created Linkentra project and generated a dynamic short link.
- Developed redirector and verified availability.
- Configured fallback URL in Linkentra.
- Set up branch mapping (IP ranges or lookup table).
- Exported QR in the correct format and conducted test prints.
- Clarified data protection and support processes (user notice, support hours).
When is the variant with a selection page useful?
If you don't want to use geolocation or if branch density is very high, a short selection page is practical: when the user opens the page, they can choose their branch via a button — direct redirection to WhatsApp. This is simple, transparent and minimizes data protection concerns.
Conclusion — Control, flexibility, measurability
With Linkentra you retain the best of both worlds: printed stability and digital flexibility. A single QR code remains unchanged in the printed design, destinations can be changed centrally at any time, fallbacks provide resilience, and the statistics deliver actionable insights for marketing and service. The self-hosted option is ideal for companies with their own infrastructure; agencies and marketing teams quickly benefit from the cloud option.
Ready to implement your WhatsApp routing without reprinting? Discover Linkentra: https://linkentra.de
Next step
Try Linkentra yourself
Dynamic QR codes with control over hosting and data: change content afterwards, adjust branding, manage media centrally and analyze scans — optionally on your own infrastructure (self-hosted) or immediately in the Linkentra Cloud. Edition-dependent features for teams, API and white-label.