Technology Guide

Hotel Key Card Encoding Explained

What encoding actually is, what happens at the front desk at check-in, and the four details a card supplier needs from your property before production starts.

Front-Desk WorkflowChip Families ComparedSupplier Checklist

The Short Answer

How does hotel key card encoding work?

In two stages. At production, the card gets its permanent identity: a chip from the family your lock platform reads, with its factory serial number, laminated inside the printed card body. On property, your front-desk encoder writes the changeable data - room, dates, access permissions - at every check-in, driven by the lock-management software and PMS. The supplier's job is stage one; your lock system owns stage two. Orders go wrong when stage one ships the wrong chip.

This page covers the encoding workflow and what it means for ordering cards. For per-card pricing, see the key card cost guide; for the underlying radio technology, the NFC vs RFID explainer.

Chip Families

What the encoder is actually writing to

Hotel cards operate at 13.56 MHz under the ISO/IEC 14443 standard, but the chip families inside differ in how they store and protect data - and your lock platform dictates which family your property uses.

Chip Family	Security	Memory	Typical Hotel Use
MIFARE Classic 1K / 4K	Crypto1	1K / 4K	The installed base - standard guest room access on legacy lock systems
MIFARE Plus	Crypto1 / AES-128	2-8K	Migration path - Classic compatibility with upgraded security
MIFARE DESFire EV2 / EV3	AES-128	2-8K	Current-generation properties; required where cards also carry payments or multiple applications

The operational difference: Classic-era systems write room data into the chip's fixed memory sectors, while DESFire structures data as separate applications - which is how one DESFire card can hold room access, cashless payment, and loyalty data without the systems touching each other. Both are re-encoded at the same front desk in the same way; the difference is what the property can safely build on top.

The Check-In Second

What happens when reception makes your key?

The receptionist selects the room and stay dates, and the encoder writes them to the card under the property's own security keys - the write itself takes about a second. Nothing about you persists from the previous guest: each encoding overwrites the last. When a card is lost, the next card encoded for that room supersedes it and the locks stop honoring the old one, which is why a lost card is an inconvenience rather than a security incident.

The same mechanism is why guests cannot be locked out by a phone "demagnetizing" the card: RFID chips hold data in solid-state memory and have no magnetic stripe to corrupt. When an RFID card stops working, the realistic causes are physical - a cracked card body or damaged internal antenna - or an expired encoding, both fixed in seconds at the desk.

Ordering It Right

What does a supplier need to know before production?

Four details, settled in writing before anything prints: the lock platform (ASSA ABLOY VingCard, Dormakaba, SALTO, Onity, and Miwa are the major systems our cards are made compatible with), the exact chip family your encoders write, the artwork, and the quantity against published MOQs - 1,000 units for PVC and BioBoard cards, 500 for bamboo. The chip line is the one that cannot be fixed after delivery: artwork can be reprinted, but a pallet of cards with the wrong chip family is a pallet of coasters.

Before a full production run, validate a small sample on your own encoders and locks - a standard step we plan into project schedules, and cheap insurance against the one failure mode that matters. Our quotes confirm the chip specification in writing for exactly this reason; the supplier comparison guide explains why we treat that as a non-negotiable ordering practice for any vendor, not just us.

Beyond Guest Rooms

When does pre-encoding at production make sense?

When the data is static. Hotel stay cards are always encoded on-property because rooms and dates change per guest - but event credentials, staff cards with fixed roles, and amenity passes tied to a season can carry data written at production, with sequential numbering linking each card to your system. The dividing line is simple: dynamic data means property-encoded, fixed data can be pre-encoded.

Wristband programs at resorts sit on the same logic and the same chip families - a property that understands card encoding already understands band encoding. The resort access solutions page covers running cards and bands on one system.

Chip specifications referenced on this page - ISO/IEC 14443 operation at 13.56 MHz and DESFire AES-128 security among them - are published in NXP's MIFARE datasheets, for example the MIFARE DESFire EV3 data sheet. Card materials, chip options, and MOQs are from our hotel key card product page; lock-platform compatibility detail lives in the VingCard, Dormakaba & SALTO compatibility guide.

FAQ

Frequently Asked Questions

What does encoding a hotel key card mean?

Encoding is writing data to the RFID chip inside the card - which room it opens, for which dates, under which security keys. It is separate from printing: the artwork is fixed at production, while the chip is written and rewritten electronically. In hotels, encoding happens at the front desk at every check-in, using an encoder connected to the property's lock-management software.

Do RFID key cards arrive pre-programmed from the supplier?

Hotel stay cards do not - they cannot, because room assignments and dates only exist at check-in. Cards ship with the correct chip family for your lock platform and are encoded on-property by your own system. What a supplier must get right is the chip: a card with the wrong chip family will never encode on your encoders, no matter what the artwork looks like.

What is a hotel key card encoder?

The desktop device at the front desk that writes the chip - typically sitting beside the check-in terminal, connected to the lock-management software and, through it, to the PMS. When reception makes a key, the encoder writes the room, dates, and access permissions to the card in about a second. Encoders are supplied by the lock-system vendor; the cards are the consumable that must match them.

Which details does a card supplier need before production?

Four things: your lock platform (ASSA ABLOY VingCard, Dormakaba, SALTO, Onity, and Miwa are the major systems), the chip family your system reads (MIFARE Classic 1K versus DESFire EV2/EV3 is the decision that matters), your artwork, and your order quantity against the published MOQ. With those four settled, compatibility issues at delivery are essentially eliminated.

Can hotel key cards be re-encoded and reused?

Yes - re-encoding is the normal duty cycle, not an exception. Every check-in overwrites the previous guest's data, and the chip families in our catalog carry 10+ year published data retention with write endurance engineered for exactly this daily rewriting. Cards leave service because of physical wear - cracked bodies, damaged antennas - not because the chip runs out of rewrites.

Does switching PMS or lock software mean replacing all key cards?

Not necessarily. If the new software runs on the same lock platform and reads the same chip family, existing card stock usually carries over - the encoding changes, the cards do not. A lock-platform change is different: if the new platform reads a different chip family, the card stock must follow it. Confirm the chip question with both vendors before either migration.

Keep Reading

Order Cards That Encode First Time

Tell us your lock platform and chip family - we confirm the specification in writing and quote your exact configuration.

Request Quote