InnerWeb
Skip to main content

QR label print order for the secretariat: a case from a production plant

A QR label print order sent before guests have registered ends in a blank page and a call to the host. At a corrugated packaging plant the problem was solved so that the system emails the secretariat only once the guests from the group invitation have their own accounts and badge IDs.

8 h
maximum wait for an order when registration is only partial
Source: internal card
5 min
how often the order queue is checked
Source: internal card
144
badge IDs in a single print
Source: internal card

Starting point: who invites and who prints

At a corrugated packaging plant (a Polish site with a German head office) guests are invited by employees from different departments: purchasing, quality, maintenance and logistics. The QR badge, however, is printed by a single unit, the secretariat, which runs the label printer and hands out badges at the entrance. Two roles, two workplaces and one bottleneck: the information about who is coming and when has to reach the person standing at the printer.

Before the rollout, it worked the way it does in many plants. The host sent a separate email to the secretariat or made a phone call, gave a list of names and waited for someone to retype the data. For a single visitor this worked. For an open day with a dozen or so customer representatives, mistakes followed: typos in names, missing people, and badges printed for guests who in the end did not come.

Problem: an order sent too early gives a blank page

After group invitations were launched, a new trap appeared. A group invitation does not create guest accounts in advance: the guest receives a message and registers on their own in the portal. The system therefore has no badge IDs to print at the moment the invitation is sent. If the print order had gone to the secretariat immediately, the secretary would click Print and see a page without a single label.

This is a classic error in the order of events, not the fault of one person. The result is costly, because guests wait at the entrance and the host has to step in. The plant needed a mechanism that knows the state of the registration and does not flood the secretariat with messages that cannot be answered with a printout yet.

Print order parameters in a group invitation

Print order parameters in a group invitationHorizontal bar chart: 8 hours of waiting, 5 minutes between queue checks, 13 days until the order expires.051015valueMax. wait (hours)Max. wait (hours): 8 value8Queue check (min)Queue check (min): 5 value5Expiry (days)Expiry (days): 13 value13
Source: Documentation of the QR label print order function

Solution: the order waits for guest registration

The invitation windows show a checkbox called Send QR label print order. It is visible only when the administrator has set the secretariat address in the system, so a plant without a label printer does not see an unnecessary option. The email to the secretariat contains the guest, the visit date, the host and a Print button that leads to the print page.

For a group invitation the system does not send the order straight away. It waits until the guests have registered. When only part of the group has registered, the order waits up to 8 hours, and the queue is checked every 5 minutes. If after 13 days nobody has registered, the system cancels the order instead of sending a message about something that will never happen.

Print page for security and the secretariat

The print page is available to security and secretariat roles only, not to every logged-in user. It accepts up to 144 badge IDs in a single print. For one label the operator chooses the size, and for many the system lays out a sheet. As a result, an open day with several dozen guests ends with one print job, not with several dozen clicks.

Hardware bought, software built in-house

InnerWeb is a software manufacturer. The label printer, computer and scanner are bought and integrated by the plant itself, while we deliver the order logic, the print page and the notification. This division matters to the purchasing department: there is no dependence on a dedicated device from a single manufacturer.

Effect: the secretariat gets an order only when there is something to print

After the change the secretariat stopped asking hosts for lists of names. The email arrives in the inbox only when the guests have accounts, and the Print button opens a ready set of labels. The host does not retype data, and the secretary does not have to check whether the registration has already taken place.

It is worth recording the numbers that decide how the mechanism behaves: an 8-hour waiting window, a check every 5 minutes, cancellation after 13 days and a limit of 144 badge IDs. These parameters were designed to cover the real rhythm of a plant: invitations sent several days ahead and guests who register at the last moment.

  • The order does not go out before the guests register, so no blank print page is created.
  • With partial registration the system waits up to 8 hours instead of sending several more emails.
  • An order that nobody responds to for 13 days expires on its own.
  • Access to the print page is limited to security and secretariat roles.

Conclusions for plants with a similar profile

The first conclusion concerns the order of events: a QR label is a product of registration, not of the invitation. Systems that treat the invitation and the printout as one event mislead the secretariat. The second conclusion is that a print order should have an owner, a lifetime and an expiry rule, just like any other task in the plant.

The third conclusion is operational. The email with the order contains the guest's host, so when a problem appears at the entrance, the secretariat knows whom to call. The fourth: the list of people to be printed is linked to the list of people on site, because recording a guest's entry writes a gate entry and adds the guest to the evacuation list. The label is therefore the first link in a chain that ends at the assembly point.

Plants planning a similar solution should start by agreeing the secretariat address, the roles allowed to print and the capacity of a single print queue. Only then is it worth choosing a printer, because the software does not dictate a device model.

Checklist

Video

Frequently asked questions

Will the secretariat get an email if the guest has not registered yet?

No. For a group invitation the order waits for the guests to register. When only part of the group has registered, the system waits up to 8 hours and checks the queue every 5 minutes.

What happens if the guests never register?

After 13 days the system cancels the order, so the secretariat does not receive a message about a visit that will not take place.

How many labels can be printed at once?

The print page accepts up to 144 badge IDs. For one label it offers a choice of size, and for many it lays out a sheet.

Does InnerWeb supply label printers?

No. InnerWeb is a software manufacturer. The plant buys the printers, scanners and kiosks, and we integrate them.

We will show the print order on your data

Book a talk about guest registration and badge printing. We will build a demonstration on the scenario of your secretariat.

Let's talk