Can every tag in a batch carry a different URL?
Yes, and there are three routes. Write each tag individually, which is accurate and slow. Use a chip that mirrors its own identifier into the content, which lets identical writes produce unique results. Or accept a shared address and identify the tag some other way.
Three routes
| Route | Effort per tag | Main limitation |
|---|---|---|
| Individual writes | High, one operation each | Slow, and tracking becomes essential |
| Identifier mirroring | None, identical write | Requires a chip that supports it |
| Shared address | None | The tag itself is not distinguishable |
Mirroring, the one that scales
Some chips can inject their own factory identifier into the content as it is read. Configure the mirror once, write the same message to every tag, and each one delivers a different address because the chip appends what makes it unique.
The consequence is worth stating plainly: a thousand tags written identically in a repeat run still arrive at your server distinguishable from one another. The entire per tag encoding step disappears.
Two conditions apply. The chip must support the feature, which is a purchasing decision rather than something you can add later. And your server must handle an address with an appended identifier, which is trivial.
Writing individually
The route when mirroring is unavailable, and it is a different kind of job rather than a slower version of the same one.
Each tag needs its own content entered or supplied from a list, which is where a dedicated encoder earns its cost. Doing it by hand on a phone for more than a few dozen tags is where transcription errors appear.
It also makes a record mandatory. With identical tags a lost record is an inconvenience, and with unique tags it means you can change destinations and cannot tell which physical object you are changing.
Choosing between them
If the tags must be individually distinguishable and the quantity is more than a few dozen, buy chips with mirroring. It is the single decision that determines whether the run is an afternoon or a week.
If uniqueness is a nice to have rather than a requirement, use a shared address and let the landing page ask whatever it needs to know. Many deployments that specify unique tags never actually use the distinction.
And if the tags are already bought without mirroring and uniqueness is required, an encoder driven from a list is the honest answer rather than heroic effort with a phone.
Frequently asked questions
Does mirroring work on every phone?
The substitution happens inside the chip as the content is read, so no reader needs to support anything. Every phone sees the modified address without knowing anything special occurred.
Can I mirror a counter instead of the identifier?
Chips that offer mirroring often allow the read counter as well, which gives an address that changes on every tap. That is useful for detecting reuse and is a different purpose from identifying the tag.
Is the mirrored identifier unique?
It is the factory identifier, which is meant to be unique within a manufacturer's allocation. It is not a secret, since anyone can read it, so it identifies rather than authenticates.
What if my chips do not support mirroring?
Write individually with an encoder driven from a list, or reconsider whether per tag uniqueness is genuinely needed. Retrofitting the feature is not possible.