Short answer: Define exactly which UHF tag memory must remain readable or writable before choosing passwords or lock settings. An Access password, a reversible lock, a permanent state and Kill have different effects. A password alone does not encrypt inventory data or prove that an identifier cannot be copied.
Name the memory and allowed operations
Record the tag chip and finished tag, memory bank and address range, inventory value, ordinary user permissions and maintenance permissions. Identify who holds credentials and how authorized tools obtain them. Keep passwords out of screenshots and ordinary logs.
The GS1 Gen2 standard distinguishes Access, Lock, permanent settings and Kill. Permanent states can preserve writability or prevent future writes; they are not all equivalent to read-only. Supported memory and commands depend on the actual tag and reader software.
Decide whether maintenance may rewrite the tag
For an illustrative asset PUMP-204, routine inventory must read its EPC while normal operators must not change it. Decide whether authorized maintenance may correct the same tag or must replace it. Keep asset ownership and service status in the application record.
If correction is permitted, test the required reversible restriction and authorized operation. If future changes must be prevented, independently read back the intended value before applying an irreversible setting on a designated sample. Document replacement when an encoded value is wrong.
Test the later behavior, not only the command response
Use sacrificial samples for a normal operator, authorized maintenance, a wrong credential and a previously locked tag. Record starting state, target memory, requested operation, reader and SDK versions, command result, subsequent read or write, and asset lookup.
A successful lock response alone does not establish the later permission rules. A rejected write may reflect credentials, addressing, unsupported operations or tag state. Preserve the error and identify the cause before repeating writes. Kill is destructive and is not an ordinary inventory-protection setting.
Keep replacement and inventory usable
After a permitted maintenance change, read the tag independently and verify its asset mapping. If the tag cannot be changed, preserve the relationship between the old identifier, replacement tag and existing asset history.
Send the memory policy, tag part, required ordinary reads, maintenance rights and tested software path to Integration & Support. A quotation should identify the specific supported commands rather than treating a general UHF inventory capability as evidence for every access-control operation.
Device options for this task
Compare AIDC GO RX-56 and AIDC GO SX-32 for a UHF RFID Sled Reader or handheld form factor. Request explicit documentation for the tag chip, memory operation and SDK command before including write or lock functions in a quotation.

