InnerWeb
Skip to main content

Guest QR labels ordered by the host in advance

At a packaging plant a guest is often invited by phone or email, and the secretariat only learns about them when they stand at the desk. A QR label print order moves that knowledge earlier: the host ticks one box, and the badge is ready before the guest reaches reception.

8 hours
after this many hours an email goes out with part of the group
13 days
after this time the batch stops waiting

Problem: the badge is printed only at the desk

A guest arrives at the plant without an account, without a badge and without induction training. Reception turns the guest's name into an external account with a registration number and a printed QR badge in one step. This works well, but a queue forms at the desk when several guests arrive at once, for example for a supplier training session.

An additional difficulty concerns guests invited by phone or email. The secretariat also prints labels for them even though they are not standing at the desk, so it needs to know who is coming, when, and who invited them. Without this information, every badge has to be prepared on site.

Solution: the print order from the host

The person inviting a guest can tick the box "Send QR label print order" in the invitation. The secretariat receives an email with information about who was invited, when, and by whom, together with a Print button that prints one or several labels on a DYMO printer.

The secretariat address for print orders is a system setting, empty by default. Until the administrator fills it in, the print order field is not visible in invitations. As a result, a plant that does not want this path sees no extra fields, and a plant that enables it does so with one setting.

The "For QR code printing" list

Alongside the email, a "For QR code printing" list works for the secretariat. It shows people who have created an account and are in training, and who have never had a printed label, so the badge is ready before the guest reaches reception. A person leaves the list after printing, which protects against printing the same label twice.

Time limits of the print order for a group

Time limits of the print order for a groupBar chart: the email with part of the group goes out after 8 hours, and the batch stops waiting after 312 hours, that is 13 days.0100200300400hoursEmail with part of the group: 8 hours8 hoursEmail with part of the groupEnd of batch waiting (13 days): 312 hours312 hoursEnd of batch waiting (13 days)
Source: 13 days converted to 312 hours

Inviting many guests at once

When a group is invited, the secretariat does not want a separate email for each person. The email goes out immediately once all invited people have registered, and after 8 hours from the order if only some have registered. Later registrations receive a separate email, and after 13 days the batch stops waiting.

For the secretariat this means one batch of labels per group if the guests registered together, or two messages if some joined later. The host does not need to remember a manual reminder, and the secretariat does not spend time checking who is still missing.

  • All invited people registered: email to the secretariat straight away.
  • Part of the group registered after 8 hours from the order: email with the people already registered.
  • Remaining people: a separate email after their registration.
  • After 13 days the batch stops waiting for the missing people.

Printing and access: what the secretariat needs to know

The label printing page sits under the security panel path, so the secretariat must log in. The page itself issues a badge to people who do not have one and prints each label on a DYMO. The window.print() function is a fallback when the printer is not available in the browser.

The login requirement has a reason: a QR label is an access document, so it should not be available to anyone who knows the address. The plant should assign the secretariat an account with the security role and check it before the function is launched.

Conclusions for a packaging plant

First conclusion: the print order shortens the time at the desk, because the secretariat's work moves ahead of the guest's arrival. Second: the secretariat address is the only setting that has to be filled in, so the launch is quick. Third: the print list is a safety net when the host forgets to tick the box.

The guest invitation is the first step of their path, and the next steps are the health statement and the training. It is worth planning them together rather than separately.

Checklist

Video

Frequently asked questions

Why don't I see the print order field in the invitation?

The secretariat address for print orders is empty by default. Until the administrator fills it in, the field is not visible.

Can the secretariat print a label for a guest without a badge?

Yes. The print page issues a badge to people who do not have one and prints the label on a DYMO.

Does the secretariat have to log in?

Yes. The print page sits under the security panel path, so it requires login.

Let's talk about guest registration

We will show the QR label print order from the host to the secretariat. Book a conversation with the InnerWeb team.

Let's talk