What this site is for

Hotels rarely need another RFID catalogue. They need an answer to a narrower question: which physical credential fits this installed system, this guest journey, this wear environment and this issuing workflow — and which ones will fail, before anybody orders 2,000 of them.

So the work here is specification rather than selling. The catalogue exists, and most of what we publish is about how to choose within it, including the cases where the honest answer is that a construction a property likes is wrong for their property.

A realistic family of silicone, woven, paper and wood RFID wristband constructions
MATERIAL + USE / REAL CONSTRUCTION

Why there are no customer names on this site

Publishing a hotel name as proof requires permission most suppliers do not actually hold, and it tells a reader almost nothing about whether a product suits them. A named property implies a relationship and an endorsement; it does not describe a specification.

Where an example genuinely helps, we write it as a worked scenario and say plainly that it is one. The reasoning is the part that transfers to your property; somebody else’s logo is not.

What that means in practice:

  • No named customer portfolios and no hotel names used as proof
  • No competitor names used as marketing keywords
  • No claim of universal lock-system compatibility
  • Original generic artwork in every public visual — no property identity or crest

How compatibility is treated

It is possible to write a sentence implying any credential works with any lock. It is not possible to make it true: installations differ by site, by configuration and by age, and a credential that works at one property with the same lock brand can fail at another.

Compatibility is therefore confirmed against the actual installation before production, and every product page says so. That is slower to read than a promise and much faster than discovering the problem after a run is made.

The statement we hold to

Compatibility is confirmed against the property’s lock system, credential technology and encoding requirements before production. We do not claim universal compatibility.

A guest presenting a natural-material RFID wristband to a resort reader
PRODUCTION + CONTROL / REAL PROCESS

How material claims are handled

Every credential here contains a sealed electronic module, so no wristband is compostable, recyclable or sustainable as a whole product, whatever the strap is made of. Statements describe the component and are evidenced by a material declaration issued against the production run rather than the product line.

Where certified material options are used, the approved sentence is used exactly as written and is not expanded, quantified or extended to other materials on the same page.

Where our scope ends

We specify and supply the physical credential against a confirmed environment. Lock hardware, access-control software, property management systems and payment integration are separate unless a written scope says otherwise.

That boundary is deliberate. A supplier who claims the whole system gets blamed for the parts they do not control, and a property is better served by one who is precise about where their responsibility begins and ends.