Define the identifiers
Distinguish the factory UID, application identifier, printed serial number and any backend record. Explain which values must match. A printed number is not automatically the same as the chip UID.
Choose the data format
For NFC, provide the final NDEF content or generation rule. For UHF, specify EPC encoding and any additional memory use. For smart credentials, provide the required memory or application layout. Include byte order and numbering conventions where relevant.
Prepare controlled input data
Agree the file structure, character encoding and unique record rules. Use sample data first. Identify who checks duplicate records, missing values and the relationship between printed and encoded information.
Specify the verification step
Define how the encoded product will be read back and checked against the source data. Agree how rejects and replacements are handled, and what result file or serialization record you require.
Approve locking separately
Permanent memory locks and security personalization may be irreversible. Approve an encoded sample and the locking procedure before a production run. Keep production credentials out of routine email exchanges.
Specification requirements
Include your reader, chip preference and application conditions in the quotation brief. Roxtron can review the requested product configuration with you.
Prepare a quotation