A claim is per kind of label, not per person
One person claims a printer for shipping labels. Someone else claims a different printer for packing slips. A third machine takes item labels. All three print at the same time, and nothing requires those machines to share a building, a network, or a country: a job is routed by looking up which printer owns that kind of label, so the claim is a record on our servers rather than a broadcast down your office LAN.
One owner per kind, enforced by the database
The claim is a uniqueness constraint, not a convention. Two machines cannot both own shipping labels, so the same label can never come out of two printers because somebody left a tab open in the back office. Claiming a kind that someone else holds takes it from them, deliberately and visibly, rather than quietly opening a second lane.
Take over in one tap
Walk to a different computer, open the printer panel, and take the kind of label you need. The previous owner is released in the same action. No settings to unpick, nobody to call, no waiting for a session to time out.
Waiting labels follow the takeover
Labels that queued while nothing was claimed print immediately when a machine takes over, and the panel tells you how many drained. A printer that was offline during a rush costs you a delay, not the labels.
The person you took it from finds out
A takeover tells the previous owner that printing moved and which computer took it, so the surprise is at the moment it happens rather than an hour later when their printer has been silent and they had not noticed.
Machines are known by identity, not by name
A station registers itself with a device fingerprint, so it stays the same machine across restarts, browser updates, and a laptop that moved rooms. Two people who both named their computer "Desktop" are still two stations.
A machine is a machine, whichever tab is open
The website and the extension on one computer count as one station, not two, and whichever of them is currently awake gets the job. So a printer set up from the website still prints when the website is closed and only the extension is running, which is the normal state of things during a show.
Live for sixty seconds after its last check-in
Every station reports in on a timer. A job is only handed to a machine that has checked in within the last minute, so labels are never sent into a laptop that was closed an hour ago and quietly lost inside it.
One automation can use its own printer
An individual automation rule can pin its labels to a specific printer, overriding whoever owns that kind by default. Useful when one show, one product line, or one high-value item should print somewhere separate.
Set up without touching operating-system settings
Claiming, releasing and switching printers happens in a panel built for the job, not in the operating system printer settings you would otherwise go hunting for on a machine you are not sitting at.