Choose supplier-prepared tags when the EPC is allocated and written before delivery and the supplier can provide the exact encoded values and exception evidence the buyer needs. Choose on-site print-and-encode when the value or visible label content must be written at the site. A pre-encoded tag can be bound to an asset or business record later, at the work position, without re-encoding it. Either route still needs independent readback, duplicate control and installed-read verification. The decision is who owns numbering, writing, binding, equipment and exceptions, not whether a tag can be read at all.
This guide compares two procurement workflows. It does not assert that AIDC GO sells pre-encoded tags, RFID printer-encoders or a particular tag-writing configuration. Ask each proposed supplier to confirm its exact scope.
Fix the identity contract before asking for media prices
Specify whether the business identity is a GS1 EPC or another approved enterprise identifier, who allocates it, and how the application prevents duplicate assignment. Treat allocation of a unique number, writing it to a physical tag, and binding the observed tag to an asset or transaction as three distinct events. They can occur at different places and times. State which visible barcode or text, if any, must correspond to the encoded value. The GS1 EPC Tag Data Standard defines EPC encoding and data carried on EPC-encoded RAIN RFID tags; it does not automatically allocate IDs for a buyer. GS1's serialization guidance also shows why a proposed binary scheme and tag memory capacity must be checked against the actual serial-number format, including leading-zero requirements. Do not quote a tag solely by a nominal bit count.
Distinguish a tag chip's factory-programmed value from the buyer's approved EPC. A factory default, pre-serialized chip value or unique TID is not automatically the business identifier expected by the WMS or asset system. The buyer must define the translation and record ownership if those values are used. The existing UHF memory-bank guide explains why EPC, TID and User Memory should not be interchanged.
Decide where the value becomes final
Supplier-prepared labels fit a controlled, forecastable serial allocation and a supply chain that can return a verified data file keyed to physical rolls, cartons or batches. They can still be bound to individual assets only after arrival, if the site scans the EPC and commits the asset mapping then; that later binding does not itself require another write. Ask whether the supplier is printing only, encoding the approved EPC, testing readback, applying a lock, or merely supplying inlays with manufacturer values. “Pre-encoded” must name the actual field and the evidence delivered. Define how a void, missing label, duplicate value or damaged shipment is reconciled without reusing an identifier silently.
On-site print-and-encode moves serial allocation, label printing, programming and failure handling into the buyer's operation. It can avoid shipping a pre-numbered batch that becomes obsolete when a job changes, but it adds a printer/encoder, supported RFID media, software integration, calibration, consumables and operator controls. A plain barcode label printer should not be assumed to encode RFID. Zebra's ZT411/ZT421 RFID menu documentation is a model-specific third-party example: its tag calibration determines programming position, antenna and read/write power for the loaded RFID media. Those controls do not prove another printer or media combination works.
| Decision factor | Supplier-prepared tags | On-site print-and-encode |
|---|---|---|
| When the final identity is known | Supplier-prepared: confirm the supplier receives an approved, unique allocation before production. | On-site: confirm the application allocates and reserves each value at issue time. |
| Evidence handed to the application | Supplier-prepared: require a batch/roll manifest, encoded value, visible value and rejects/voids. | On-site: require a transaction record joining print job, tag readback, asset/order and rejects. |
| Exceptions | Supplier-prepared: define short shipment, damaged roll, duplicate ID and replacement rules. | On-site: define failed encode, void label, reprint and interrupted-job rules. |
| Equipment and change control | Supplier-prepared: qualify supplier process, media and incoming inspection. | On-site: qualify exact printer, RFID media, label format, firmware and application versions. |
Each column is a responsibility model, not a guaranteed cost or quality ranking. The buyer may also use a mixed model: pre-encoded stock for stable high-volume items and controlled on-site issue for exceptions. If so, establish unified numbering governance and duplicate prevention. A central allocation service is one option; controlled, non-overlapping number ranges with reconciliation are another. Neither architecture is required by this guide, but two parties must not silently issue the same business identity.
Price the exceptions, not only the good label
Request a sample batch and an explicit acceptance data file for the supplier-prepared option. Read a selected sample independently, compare the EPC and printed human-readable or barcode value with the manifest, and test whether the receiving app rejects a duplicate. For on-site encoding, run the exact media and label design through the quoted printer and software. Zebra's ZT411/ZT421 troubleshooting guide documents model-specific causes of void labels and low yield, including incompatible tag type, calibration, programming position and power settings. The point for procurement is to budget a tested exception route, not to assume that every failed label can be salvaged or that the named Zebra behavior applies to all equipment.
Ask each bidder to show what happens when an encode fails after a serial was reserved, when a label is reprinted, when the visible print and EPC disagree, and when a previously issued EPC appears twice. Keep invalid physical labels out of use and preserve an audit trail for values that were consumed, voided or reissued. The tag-commissioning guide covers the subsequent controlled write/readback/asset-binding transaction in depth; it does not make either procurement workflow automatically safe.
Accept the installed result separately
A correct encoding file is not a proof that the mounted tag reads on metal, in a carton, or at the intended station. After a controlled sample is issued, mount it in the real assembly and verify the reader returns the approved business identity to the right record. The metal-asset attachment guide and read-range guide cover those distinct physical checks.
For a quote, provide the identifier scheme, sample serials, label dimensions and materials, installation surface, expected batch pattern, regional deployment, application interface and exception ownership. Ask for separate line items for prepared labels versus printer/encoder, software integration, media, training and rework. Request evidence for the actual configuration; no manufacturer demonstration transfers automatically to AIDC GO inventory.
Discuss the field reading and integration side through AIDC GO's RFID solutions and integration support. Use the contact page to confirm which tags, encoding services, readers or printers—if any—can be quoted for the specific project. Do not infer supply or write capability from this general guide.