Guest rooms
Key cards specified for the existing lock and encoder workflow.
Use case / Hotels
A familiar arrival, backed by a precise credential brief.
Hotels need access products that hand over in seconds at check-in and stay exact behind the front desk. We begin with the installed system, then define material, artwork, encoding and replenishment requirements.
01
Fast, familiar front-desk issue
02
Room and staff credential separation
03
Artwork and numbering control
Operational fit
Design around how the guest actually moves.
Product, credential and delivery decisions follow the use case—not the other way around.
Staff areas
Clearly differentiated credentials with controlled numbering where required.
Reorders
Recorded material, artwork and encoding details for a cleaner repeat brief.
Manufacturer detail
What hotels change about the manufactured product.
These are production controls, not assumed functions of a property's access system.
Card body and finish follow handling volume
A room card is handled more often than almost any other object a property issues. It is pushed into a wallet, dropped on a wet counter, carried to a pool and returned through a desk drawer. That handling pattern, not the visual reference, sets the body thickness, the laminate and whether the surface should be matte, gloss or tactile. A high-turnover property with short average stays puts a different mechanical load on the card than a low-density property whose guests hold one credential for ten nights.
We record the intended finish against a production-representative sample rather than a screen proof. Surface friction affects how the card feeds through a desk encoder; edge finish affects how it looks after a hundred issues. Where a property wants a natural or textured face, the approval sample also records which side carries any writable or variable area, because those surfaces do not accept print and wear in the same way as a standard laminated body.
Guest and staff populations are manufactured as controlled variants
Most hotels need at least two credential populations: rooms issued to guests, and cards used behind the desk or in service areas. The separation is an operating requirement first and a production instruction second. The property defines which areas need visually distinct credentials, whether staff cards carry a controlled number, and whether any variant must be identifiable without a reader. We reproduce that instruction and report what was actually produced in each range.
The manufacturing consequence is that every visually distinct variant is a separate production item with its own minimum. Three colours of staff card is three items, not one order with three shades. Properties frequently reduce this by keeping one stable body design and letting printed or encoded variable data carry the separation, which holds the artwork count down while still giving the desk something it can read at a glance.
Numbering is a stock-control instrument, not decoration
Sequential numbering, barcodes and printed identifiers earn their place when the property needs to reconcile stock. If a desk can tie a physical card to a range, a missing block is visible before it becomes an access question. The property sets the range, the start value and whether the identifier is printed, encoded or both; we keep those fields clear of the read area and any artwork region flagged during approval, and we report the finished range in the release record.
Numbering also changes what a reorder can be. A run released with a recorded range can be continued rather than restarted, so the second order does not duplicate identifiers already in circulation. Without that record, a property either restarts from one and accepts duplicates, or spends desk time working out where the previous run ended.
The reorder is priced by the record, not the memory
Hotel credential demand is repetitive and mostly predictable: a baseline consumption rate plus loss, plus whatever a refurbishment adds. The order that repeats cleanly is the one whose artwork revision, body construction, finish, credential type, numbering range, packing order and carton labelling were written down at release. Where that record exists, a repeat run is a confirmation rather than a fresh specification exercise.
Where it does not, the property is describing a card from a photograph and a memory of what the last supplier produced, and the risk of a near-miss reprint moves onto the property. We keep the release record so the next brief starts from an approved object. It does not fix price or production timing in advance; it removes the part of the delay that comes from re-deciding settled questions.
Build the brief
Start with the installed system.
Share the property, destination, product direction and any system information already available. The secure form sends the brief directly to our manufacturing team, with the product, quantity and system notes kept together for review.
Plan the order ↗