Compatibility has several layers
A system can detect a tag without supporting its application. The radio layer establishes communication. The command layer defines available operations. The application layer determines how data, files and access permissions are organised. The host system then interprets the transaction. A purchasing decision should resolve each layer.
The phrase “MIFARE compatible” is insufficient for an order specification. Classic, Ultralight, DESFire and Plus are separate product families. The generation, memory variant, reader support and personalization requirements must also be recorded.
| Reference | Role in a specification |
|---|---|
| ISO/IEC 14443 | Proximity card interface family; identify applicable parts and Type A or B |
| ISO/IEC 15693 | Vicinity card interface family |
| NFC Forum tag type | NFC tag behavior and data organization for supported devices |
| GS1 EPC Gen2 | UHF reader and tag air interface |
| GS1 EPCIS | Business visibility event data and exchange; separate from the radio link |
Identifier reading is an incomplete test
A reader may return a UID even when its firmware cannot perform the protected application transaction. A DESFire deployment, for example, requires agreement on applications, files, access rights and authentication. Review the semiconductor specification and validate the personalized credential with the intended software. NXP: MIFARE DESFire EV3 product specification.
Replacement testing should include normal access, denied access, repeated use and any required write operation. If a system uses diversified keys or a particular file structure, specify that requirement explicitly. Do not use a generic chip family name as a substitute for an approved credential profile.
From radio observations to business events
A UHF identifier and an enterprise event are different data objects. EPCIS gives event data a structured context that includes the objects involved, time, location, business meaning and, where used, sensor information. The application must determine when a sequence of observations becomes a reportable event. GS1 EPCIS Standard, release 2.0, June 2022.
This distinction prevents a common integration error: treating every raw read as an independent inventory movement. Define event rules, duplicate handling and exception processing as part of the system design.
Maintain an approved compatibility record
Record the product model, IC part number, memory variant, reader model, firmware version and encoding profile. Retain a qualified sample and the acceptance results. Revalidate when a relevant element changes, including antenna construction or reader software. This record makes repeat procurement technically controlled.