How it works
How does an ePaper visitor badge work?
Reviewed by Daniel Cluderay, director of ONDRAFT LTD · Published 2026-09-06
Two machines exist. Lobby-state pushes a face over Bluetooth from a reception tablet. Ship-state compiles the 250×122 image in Cleckheaton before the box is taped. We run ship-state for hire. Owned badges update from your account during the window you paid for.
The compiler
The visual designer and the Dark Store label tools share a family of e-ink constraints: a fixed pixel grid, three inks, no anti-aliased grey from a full-colour logo. Upload a chapter mark as solid fills. Name hierarchy is encoded in the templates we start from — first-name giant, visitor bar, host, conference attendee.
QR destinations attach per person. Magic links let a visitor choose LinkedIn versus a booking URL before they arrive. The face updates while the kit is still here or during an active hire window. Paper tents cannot do that without a reprint.
When the hire window ends, face updates stop unless you bought the hardware. Return the kit in the same box with bezels protected. Missing units are a terms problem, not a shrug.
What happens between “submit dates” and a clip on a lapel
You pick quantity and dates on pricing or checkout. Kit sizes of one, ten, twenty-five, and fifty are shortcuts, not a ceiling. Checkout will quote up to five hundred. We confirm when the window is actually held. Programming does not start on a wishlist.
Names land in the designer by import, paste, or one-by-one. Role bars are template choices. QR magic links go out if you want guests to pick a destination. We render the three inks onto the film, charge the cells, label the bezels so a greeter can match hardware to a list without a scavenger hunt, and pack the prepaid return for hire.
Courier time from West Yorkshire is part of the product. A London morning still needs a working day of travel plus our compile queue. Scottish highlands need more. Do not treat us like a same-day print shop next to the venue. That shop still exists if you want it. It prints paper.
On the day, open the box the way we packed it. Faces should match the list. If they do not, photograph the mismatch and email before you invent a handwritten overlay. A hire-window update beats a marker. After the window, pack every unit. One badge in a jiffy bag is how the next customer waits on a cracked screen.
Owned fleet behaviour versus hire-window behaviour
Owned hardware stays in your cupboard. You still compile from the account. Weekly chapters like this because Tuesday’s visitor is Wednesday’s speaker without a return label. The thirty-pound platform fee after year one is the compiler staying switched on, not a workplace analytics suite.
Hire-window behaviour is stricter. Updates are for the dates you paid. When the window ends, we need the physical kit back so another face set can load. Late returns block someone else’s programming slot. Post within a day or two of the last date. Proof of posting until we scan at Cleckheaton.
Mixed models appear in the wild: ten owned for core members, fifteen hired for a visitor-heavy morning. That is allowed. Do not assume hired units silently become owned because they sat in a drawer. Custody follows the invoice.
We do not currently run a Bluetooth lobby assigner as the default path. If your reception already has a tablet-based badge radio from another vendor, that is a parallel system. Do not pair our MAC addresses into a portal we do not operate. You would be debugging two compilers.
Ship-state, in one sentence, then the long version
Ship-state means the image is already on the film when you open the box. Lobby-state means a tablet writes the image after the guest exists in the room. Joan’s public badge shop has described a Bluetooth lobby push in about ten seconds. That is lobby-state. We compile in Cleckheaton. That is ship-state.
Neither sentence is a moral. A weekday reception with unknown couriers wants lobby-state. A named visitor morning wants ship-state. Mixing the sentences is how a buyer pays for a subscription they will not use on Thursday and still stands at a printer.
During an active hire window we can often rewrite a face without a return post. That is still ship-state’s cousin: the compiler is ours, the radio is not a lobby kiosk you installed. Owned devices use the account the same way after year one, without the return clock.
Failure modes we own: misspelled names that left Yorkshire, cracked screens in a poorly packed crate, a date window that does not match the courier. Failure modes we do not own: your Wi-Fi, your tablet battery, a third-party BLE stack, a guest who refuses to wear anything on the chest. Write those on different lines of the incident log.
Charge, clip, return — the unglamorous loop
We charge before dispatch. You should still check a sample bezel when the box arrives, especially if the kit sat in a van over a weekend. USB-C is on the object. Do not invent a proprietary dock. If a unit is dead on arrival, photograph it and email hire@inkbadgehire.com before the morning starts.
Clips and lanyards: we focus the hire line on programmed bezels. If you need fifty identical cords in a brand colour, say so. Otherwise assume you have a way to hang a badge. A bezel in a pocket is not a visitor badge. Handshake distance requires chest height.
Return on hire uses the prepaid label in the box. Scan, pack foam, seal, post. Do not wait for a “we might buy these” conversation to finish while the next organiser’s compile slot is empty. Buy on checkout if you want custody. Hire if you want dates.
The programming calendar is a queue of windows, not an infinite SAM build. Late names after dispatch compete with the next crate. We will try. We will not promise a miracle because a slide said “real time.” There is no lobby radio in this loop unless you bought one from someone else.