Scenario: The kiosk at reception displays outdated notices
In many companies, touch kiosks and printed displays are placed in break rooms, at factory entrances or at the office reception. They contain QR codes linking to shift schedules, absence reporting forms, onboarding guides or confirmations for safety trainings. But as soon as links change—because documentation was moved, a form updated, or an action is time‑limited—the codes on the physical media suddenly point to nowhere.
Why dynamic QR codes are the better solution
A dynamic QR code separates the printed code from the destination. The code on the kiosk remains unchanged while the stored destination URL can be adjusted centrally. For employees this means: always up‑to‑date content without reprinting. For IT and operators it means: centralized management, versioning and analytics of scans.
Advantages of a self‑hosted system for internal kiosks
- Data ownership: scan statistics, targets and media remain on your own infrastructure – no external SaaS providers.
- Access to internal resources: dynamic targets can point to intranet pages, internal forms or shared documents that are only reachable within the company network.
- Fallbacks & scheduling: if an employee scans outside the network, an explanatory fallback can be displayed or the redirect can be time‑controlled.
- Media & branding: centralized management of logos, landing content and export formats (PNG, SVG) for printing.
- Integration: API, webhooks and bulk import simplify connection to HR or shift‑planning systems and the creation of many codes.
Concrete use case: shift schedules at the factory gate
Problem: shift schedules change weekly. Printed notices are cumbersome to maintain, and external cloud links are not permitted for security reasons.
Solution with a self‑hosted system: a QR code is permanently installed at the factory gate. In the self‑hosted backend the destination is updated at the start of each week – the redirect shows the current shift list internally. Additionally, a fallback is configured to display contact information or an informational page for accesses outside the network. Everything stays within the company infrastructure, and HR manages the targets centrally.
Step‑by‑step: How to implement intranet QR codes for kiosks
- 1. Install self‑hosted: Deploy the solution on an internal VM or container, reachable only on the company network or via VPN for remote sites.
- 2. Create a target: In the admin area, create a dynamic link that points to the internal URL (e.g. http://intranet/shiftplans/woche42).
- 3. Define a fallback: Specify an alternative landing page to display when the internal page is not reachable (e.g. "Available only on the company network – contact the helpdesk").
- 4. Design and export: Adjust branding, generate the QR code, and export it as PNG or SVG for printing and mounting at the kiosk.
- 5. Test: Scan the code inside and outside the network, verify the redirect and the presentation of the fallback page.
- 6. Automation: Integrate the API or webhooks to update shift plan data automatically or to generate large numbers of codes via bulk import.
- 7. Monitoring: Use internal statistics to analyze scan times and usage intensity and to optimize locations.
Practical tips for operation at kiosks
- Placement: Mount QR codes at eye level and with good contrast. Use weather‑proof coating for outdoor sites.
- Scalability: Use bulk import for large sites with many devices or multiple language variants.
- Onboarding: Briefly instruct employees what to expect when scanning (e.g. "Scan here for shift schedule / Available only on the company network").
- Access checks: Regularly verify that internal targets are still reachable and that fallback pages are up to date.
- Data protection: Store only necessary scan metadata internally and define retention periods.
Short comparison: Static QR vs. Dynamic, self‑hosted solution
Static: The code points directly to a fixed URL. Advantage: Simple and works offline. Disadvantage: If the target changes, it must be reprinted.
Dynamic, cloud‑based: The target can be changed, setup is easy, but scan data is held by a third party.
Dynamic, self‑hosted: Combines flexibility with data sovereignty. Ideal for intranet resources because targets can point to internal pages and statistics remain internal.
Examples from practice — use ideas
- HR & Shift Planning: Weekly schedules, leave requests and short‑notice replacements accessible via QR directly in the break room.
- Safety Briefings: Current safety videos and checklists that need regular updating.
- Facility Management: Notice boards for cleaning schedules, order forms for consumables or fault reports.
- Onboarding Kiosk: Central contact point for new employees with an internal document pool.
Security and operational considerations
Host the system behind the firewall or on an internal VLAN. Ensure TLS/HTTPS for internal web access, role‑based admin rights for management, and regular backups. For sensitive content, additional authentication on the target side is recommended. Scan statistics should only be viewable by the responsible teams.
Conclusion — Why the effort pays off
For companies with internal resources, dynamic, self‑hosted QR codes provide clear efficiency and security improvements: lower printing costs, centralized control over destinations, and internal analytics without external data sharing. Employees benefit from always up‑to‑date content, and operators retain control over infrastructure and measurement data.
Linkentra self‑hosted enables exactly this operation: point dynamic targets to internal pages, centrally manage media and branding, analyze scans internally and update them automatically via API or webhooks if needed. Features like export formats (PNG, SVG), scheduling/fallback and bulk import simplify production and operation of kiosk QR codes.
Ready to make your employee kiosks secure and flexible? Discover Linkentra
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.