How-to
RFID Laundry Tag Encoding: EPC and TID
Short answer
Specify laundry tag encoding by the identifier your application accepts, who allocates unique values and how each tag maps to a textile asset. Agree the delivery file and read-back checks before ordering. EPC, TID and the asset record have different roles; readable tags alone do not establish correct item identities or an accepted batch.
Define the laundry tag encoding brief
Describe the identifier, reader and batch-file requirements alongside the tag model. Confirm the availability and scope of any requested encoding work in writing before ordering.
- Identifier and ownership
- Specify the accepted identifier format, who allocates unique values and how each value maps to a linen or garment record. Include a representative data example approved by the integrator.
- Model and reader
- Name the finished tag, chip revision, memory requirement, reading country and actual reader software. State whether tags arrive encoded or are commissioned after delivery.
- Delivery and checks
- Request agreed batch-file fields, read-back results and a procedure for duplicate, missing or rejected records. Give sample and order quantities; confirm which activities are included in the written offer.
Begin with the asset identity
A towel keeps its asset history when it is washed, reassigned or retagged. Decide which record represents that towel before choosing the value written to a tag. Keep changing customer, wearer and location assignments in the application unless the system explicitly requires another design. A physical tag and a business asset need not have the same replacement lifecycle.
GS1 explains EPC as a way to encode GS1 identifiers on RAIN RFID tags and connect them with barcode-based identification. That establishes a representation, not your laundry's enrollment policy. GS1 is not a requirement imposed by this guide on every system. Ask the integrator and any exchanging partners which identifier scheme they actually accept.
Separate EPC, TID and application data
EPC is interpreted according to the agreed scheme. The GS1 Tag Data Standard defines EPC and Gen 2 tag-memory contents. A decimal asset number, a reader's hexadecimal output and an application identifier are not automatically interchangeable strings. Document the expected representation at each interface and preserve its formatting.
TID concerns the tag chip rather than the complete textile record. GS1's tag-memory explanation distinguishes chip identification from serialized tag identification. Confirm the exact chip's structure, serialization and reader support before using a TID as a unique reference. Do not assume that every existing generation has identical contents or that a partial TID read uniquely identifies a tag.
Specify additional on-tag data separately. Ask which memory is available in the delivered configuration and which reader operations are supported. The chip comparison addresses published memory differences; this guide concentrates on the data the buyer expects to receive and accept.
Write a numbering and encoding brief
Give the supplier and integrator the same approved specification. Assign one owner for numbering so two suppliers, a reorder and a replacement operation cannot unknowingly allocate overlapping values.
| Brief item | Buyer decision | Written confirmation to request |
|---|---|---|
| Asset identity | Stable linen or garment record and visible reference | How the tag value resolves to that record |
| Identifier scheme | GS1 scheme or another documented application format | Accepted representation, length and sample data |
| Number allocation | Responsible party and permitted number range | Uniqueness checks across current stock and repeat orders |
| Delivered configuration | Exact model, chip and required memory | Configuration matching the approved encoding |
| Commissioning stage | Before shipment or after receipt | Which party writes, enrolls and verifies tags |
| Locks and access | Operations required by the application | Separately agreed behavior and credential handling |
For example, LTX-70x17-S provides a concrete model reference for a request. Have the integrator check its published configuration against the intended EPC memory use. An installation method or catalogue photograph does not confirm encoding-service availability.
Define any locking separately from writing. First verify the identifier and required updates, then apply only the approved locking procedure. Avoid placing operational passwords in a routine delivery spreadsheet. Confirm credential handover with the parties responsible for access. This is a requirement checklist, not a command sequence for every chip.
Agree a batch file that receiving can use
Request the delivery file before accepting the first sample. Its purpose is to reconcile expected tags, observed values and asset records. Agree the delimiter, field meanings, value representation and version with the receiving software. Preserve identifiers as text where the chosen format requires it; spreadsheet conversions should not silently change the accepted value.
| Delivery field | What it records | Receiving check |
|---|---|---|
| Batch and specification revision | Shipment identity and approved configuration | Match the written order |
| Visible item or sample reference | The physical reference available during enrollment | Associate the correct textile |
| Expected identifier | Agreed value and representation | Check uniqueness and format |
| Read-back value | Value obtained after the specified writing operation | Compare with the expected value |
| TID, if required | The documented chip reference and read scope | Check the agreed tag association |
| Acceptance status | Accepted, rejected or unresolved, with a reason | Keep exceptions out of automatic release |
If tags arrive before attachment, the file may describe tag references awaiting enrollment. If the buyer attaches them later, that buyer completes the asset association. State this handoff explicitly. A shipment file should not imply that loose tags have already been matched to specific towels.
Perform buyer acceptance in stages
- Review the representative data and approved configuration with the integrator. Confirm that the intended software interprets the identifier as the expected asset.
- Read back the agreed sample values and compare them with the delivery file using the declared representation. Record mismatches and failed operations.
- Check the file and existing inventory for duplicate allocations, missing expected records and unexpected identifiers. Resolve exceptions before enrollment or release.
- Associate accepted tags with visible textile references, then verify the intended business event at the actual station. Preserve the accepted file, setup and decision.
Agree the inspection scope rather than inventing a universal sample size or assuming every shipped tag was individually checked. Ask the offer to state which verification the supplier performs and which remains with the buyer. An accepted encoding sample does not establish production variation, attachment durability or station capture performance.
Two towels are different from repeated observations
Consider two towels enrolled as Towel-A and Towel-B. These names illustrate business records, not valid EPC encodings. The reader may observe Towel-A, Towel-A, Towel-B and Towel-A during one receiving event. With verified associations, those four observations concern two distinct expected towels. The application must define how observations become that event's accepted item list.
If only Towel-A appears twice, Towel-B remains unresolved; two observations do not establish two received towels. If both physical towels were incorrectly assigned the same identifier, the identifier log alone cannot separate them. Investigate the allocation file and physical associations. The laundry workflow comparison explains expected lists and exception handling without promising a capture rate.
Preserve identity across reorders and replacement
For a repeat order, reserve the next approved number range and check it against previous allocations. Retain the model, encoding and file revisions. Request review when the chip, memory configuration or representation changes. A compatible-looking tag is not a reason to skip a representative data check.
For replacement, preserve the towel or garment record, retire the old tag association and authorize the new one. Decide whether the old tag remains readable and how it leaves service. Reusing an EPC is a controlled system decision: two active tags with that value could otherwise represent one asset. Changing a chip also changes any chip reference used by the application.
Send an encoding requirement with the RFQ
Compare these textile laundry models with hard buttons by their published records, then request samples with your data specification. Any desired pre-encoding, file preparation or verification service must be confirmed per request. Include that scope in the quotation request; this page promises no default service, compatibility guarantee or finished laundry software system.
From the catalogue
Put the guide into a sample trial
Compare the documented formats, open the model specifications and ask for samples before choosing for your application.
Frequently asked questions
Are laundry tags supplied pre-encoded by default?
This guide establishes no default encoding service. State the required format, numbering responsibility, tag model, batch-file fields and acceptance checks in the request. Availability, included work and terms must be confirmed in the written offer.
Can I use TID as the permanent identity of a towel?
TID describes the tag chip and has a different role from the towel's business identity. Confirm the exact chip's structure, serialization and reader support before using it as a unique tag reference. A replacement chip needs a new association with the existing towel record; do not assume every TID value or tag generation is globally unique.
Must every laundry application use a GS1 EPC scheme?
This guide does not make GS1 mandatory for every application. Use the scheme required by the system owner and trading partners. For a GS1-based deployment, agree the applicable identifier and TDS representation; for another system, document its format and verify that the reader and application interpret it correctly.
Do four reader observations mean four towels were counted?
Not necessarily. Repeated observations can refer to the same towel, while a missing towel may produce no observation. Compare accepted item identities with the expected list for the defined event, resolve duplicates and check unwanted nearby items. The example here demonstrates bookkeeping, not a measured capture rate.
Sources
Test it on your own items
Samples are handled per request. The team confirms availability and terms by email.