How RFID Laundry Tracking Works, From Read Points to Wash-Cycle Counts
Jun 04, 2024
Leave a message
RFID laundry tracking works by reading a unique tag ID on each textile at fixed points in the laundry, then letting software turn those reads into location history, wash-cycle counts and sort decisions. The tag itself mostly carries an identifier. Whether the data is useful depends on where you read, which read counts as a wash, and what happens when an item is not seen.
This guide covers that operating layer for commercial laundries, hotel and hospital linen services, and the integrators who build their systems. For tag materials and purchasing, see the related guides at the end.
What the Tag Carries and What the Software Keeps
Laundry tags in the UHF band typically follow the EPC Gen2 protocol. GS1 explains the four memory banks on these tags: reserved memory for passwords, EPC memory for the item identifier, TID memory with chip and serial information, and optional user memory. Under Gen2v3, tags must support a serialised TID, but older tags may not, so check the chip before relying on TID as a second unique key.
In most laundry systems, the item record lives in the database and is keyed by the tag ID. This division of work keeps reads fast and keeps history intact if a tag has to be replaced.
| Data | Usual location | Why |
|---|---|---|
| Item identifier (EPC) | Tag | Read in bulk at every checkpoint |
| Chip serial (TID) | Tag | Helps detect duplicated or re-encoded EPCs, where the chip supports it |
| Item type, size, owner or customer | Database | Changes when linen is reassigned; no write to the tag needed |
| Wash-cycle count and scan history | Database | Writing to a tag during a bulk read adds time and a failure point; history can be moved to a replacement tag |
| Retire or repair status | Database | Drives sorting and reorder decisions |
Read Points: What Each Scan Proves
A read point should exist only if its scan proves something the business will act on. The checkpoints below are a common configuration; smaller operations often merge several of them.
| Read point | What the scan proves | Decision it supports | Common failure |
|---|---|---|---|
| Soiled pickup or customer return | The item left the customer site | Customer inventory and loss attribution | Items bundled tightly or wrapped in wet linen |
| Soil intake and sorting | The item entered the plant | Wash program assignment, customer separation | Heavily soiled or wet items blocking reads |
| After wash and drying, before finishing | The item completed a process cycle | Wash-cycle count, retire check | Counting the same batch twice |
| Clean pack-out | The item is in a specific delivery | Delivery note, shortage claims | Stray reads from nearby carts |
| Customer delivery | The item arrived | Proof of delivery, par levels | No reader at the site |
Wet and soiled linen deserves particular attention. RFID Journal reported in 2023 that tag placement and wet or soiled linen can block reads, and that a problem which looked like reader failure was traced to a misconfigured optical sensor. When a read point underperforms, check triggers, network and software before replacing tags or readers.
How Wash-Cycle Counting Should Work
Wash counts are the basis for predicting linen life and planning purchases, so small rule errors compound over hundreds of cycles. These rules keep counts consistent:
- Count at one checkpoint only. Pick a point that every washed item passes after the process, usually after drying. Reads at intake or pack-out update location, not the count.
- Deduplicate by batch or time window. An item read several times in one pass is one cycle. Set the window from your actual process time rather than a default.
- Decide how rewash is counted. A rewashed item has taken more wear, so many operators count it, but flag it separately so rewash rates stay visible.
- Compare counts with the rated life of both tag and textile. Tag ratings are conditional. A cloth RFID laundry tag specification, for example, states 200 wash cycles or 3 years from ship date alongside the wash, drying, ironing and sterilization conditions it applies to. Plan retirement around whichever limit your process reaches first.
Counts also matter commercially. TRSA has proposed standard RFID-tracked turns as a way to decide when a customer is responsible for damaged or lost items. If your contracts may use such a measure, the counting rule should be documented and applied the same way for every customer.
What RFID Sorting Can and Cannot Do
RFID tells the system what an item is and who it belongs to without opening bundles or reading labels by hand. It can direct items to the right wash program or customer lot and flag items due for retirement.
It does not physically separate linen. That still takes staff, sorting stations or conveyor equipment driven by the read data. Untagged items, failed tags and mixed customer bags need a manual path, and that path should record why the item was handled manually.
Missing Reads, Exceptions and Reconciliation
An item that was not read is not necessarily lost. Treat exceptions in stages:
- Single missed read: log it, but take no action if the item is seen at the next checkpoint.
- Repeated missed reads: after a number of consecutive checkpoints that you set for your cycle time, re-scan the likely location with a handheld reader.
- Suspected tag failure: if the item is found but does not read, retag it and transfer its history to the new ID.
- Unresolved: mark the item missing and attribute it to the last confirmed location, such as a customer delivery or an internal stage.
Reconcile at the level where money changes hands, normally per customer delivery and return cycle. Review read-rate trends per read point at the same time; a gradual drop at one point usually points to a hardware, placement or configuration issue rather than theft.
A Pilot Checklist Before Scaling
- Draw the plant flow and mark each proposed read point with the decision it supports.
- Tag a limited set of each textile type with the planned tag and attachment method.
- Run the items through your real wash, drying, ironing and sterilization programs, not just a lab cycle.
- Check read rates at every point, with dry and damp loads, and log misses.
- Confirm the counting and deduplication rules against a manual count of the same batches.
- Test the exception path: failed tag, untagged item, mixed customer bag.
- Request samples from our RFID laundry tag range that match the tested process conditions before bulk ordering.
Related Guides
- Textile, silicone and PPS laundry tags compared
- Procurement and selection guide for linen management
Send Inquiry