Total memory and usable capacity
Memory figures need a defined scope. An IC can contain manufacturer data, configuration bytes, access control fields and application storage. Total physical memory is not necessarily the space available to a user message. Eight bits equal one byte; a quotation should identify both the unit and the memory region.
NTAG213, NTAG215 and NTAG216 provide 144, 504 and 888 bytes of user memory respectively. Their total memory figures are larger. NDEF structures consume some of the available data area, so user memory must not be presented as a universal maximum text or URL length. NXP: NTAG213, NTAG215 and NTAG216 data sheet.
Identifiers serve different purposes
A factory UID identifies the IC within its defined scheme. A printed serial number supports visible handling and reconciliation. An application identifier links the credential to a record in the host system. These values may be related by a production rule, but they are not automatically identical.
Specify byte order, hexadecimal or decimal representation, leading zeros and the correspondence between printed and encoded data. Two software tools may display the same underlying bytes differently. Approve example records before authorising production encoding.
NDEF and NFC content
An NDEF message contains records with a defined structure. For a web interaction, use the appropriate URI record and calculate the encoded message size. A stable address controlled by the deploying organization allows the linked service to change without replacing the physical tag. NFC Forum: NFC Technology, technical overview.
Treat ownership of the destination, service availability and redirection policy as operational requirements. A correctly encoded tag cannot compensate for an unavailable website. Test the complete interaction on representative devices rather than validating the memory contents alone.
Encoding as a controlled production process
Define the input dataset, uniqueness rules, initial memory state and required output report. Verify each programmed identifier against the intended record. Establish how duplicate identifiers, rejected units and replacement units are reconciled. For protected credentials, define the provisioning process separately from ordinary quotation correspondence.
Write protection and permanent locking require an explicit production sequence: encode, read back, compare and then apply the approved protection. Preserve a qualified sample of the final state. A successful write before locking does not prove the final credential remains usable by its intended application.