Factory encoded tags: when are they worth it?
Worth it above a few thousand tags, or when each tag must carry unique content matched to unique printing. Below that threshold a phone is cheaper, needs no lead time and leaves you able to change the content, which factory encoding takes away.
What it is
The supplier writes the content before shipping, usually as part of the same process that prints and converts the tags. You receive tags that are already programmed, and often already locked.
It is a service rather than a product feature, so it comes with a lead time, a minimum quantity and a specification you have to get right in advance.
When it is worth it
Quantity is the obvious trigger, and the threshold is higher than people expect. A phone handles a few hundred identical tags in an afternoon, so the labour saving only becomes decisive in the thousands.
Unique content matched to printing is the stronger trigger. If tag number four hundred and seventeen must carry an address that matches the number printed on its face, doing that by hand is error prone in a way that gets discovered by a customer.
And inaccessibility: tags laminated into cards or embedded in products cannot be written afterwards, so encoding has to happen where the assembly happens.
What it costs beyond the price
Lead time. Encoding is part of production, so a change to the content means a new production run rather than an afternoon with a phone.
Flexibility, permanently, if the tags arrive locked. Ask explicitly whether they will be, because a locked delivery with a mistake in it is a total loss.
And a dependency on the supplier's verification. You are trusting that they checked, so ask what their process is and what their rejection rate looks like. A supplier who cannot answer has not measured it.
Order a sample first, always
Have a small number encoded and shipped before committing to the full run. Verify them yourself, on both platforms, on the real surface. The cost of that step is trivial next to a locked delivery that does the wrong thing.
Specifying it properly
Give the exact record type, not a description of the outcome. Asking for a tag that opens a website leaves the supplier choosing between a URI record and a text record, and one of those does nothing.
Give the exact content, character for character, including the scheme.
State whether tags should be locked, and prefer not, unless the content is a redirect you control.
And specify the chip, since a substitution that fits their stock may not fit your content.
Frequently asked questions
What quantity justifies factory encoding?
Thousands rather than hundreds, for identical content. Unique content matched to printing justifies it much earlier, since hand encoding to a list is where mistakes appear.
Will factory encoded tags arrive locked?
Sometimes, and it varies by supplier and by what you asked for. Ask explicitly, because a locked delivery containing a mistake cannot be corrected.
Can I have tags encoded and printed to match?
That is one of the main reasons to use the service. Specify how the printed identifier relates to the encoded one, and verify the relationship on the sample.
Is factory encoding more reliable than doing it myself?
It should be, since it is automated and verified in line. It is also unverifiable by you until the delivery arrives, which is why a sample run matters.