Linen tracking with UHF RFID

The problem

A linen operation needs to know which pieces arrived, which returned to usable stock and which left for the next customer. Those are separate events. An identification tag supplies an item identity; the receiving and dispatch process must decide what each read means. Start by drawing the route of a sheet, towel or tablecloth through your operation. Mark where a count changes ownership, creates a customer charge or triggers a search. Choose a pilot read point that answers one of those questions rather than trying to record every movement at once.

Keep a written expected list for the pilot. A reader log alone cannot reveal an item that never appeared in the log. Register the test pieces before the first load and link each tag identity to a linen record with a visible reference. Record the attachment location and keep a photograph or sketch in the pilot file. If the identity is later reassigned, retire the old association explicitly. Otherwise a repaired or replaced tag can appear to represent two different pieces in the stock system.

Receiving and dispatch deserve different acceptance checks. At receiving, a mixed bag may need to be reconciled with a customer's manifest. At dispatch, an item read beside the intended load must not silently enter that customer's shipment. Include an adjacent trolley in the trial and mark its contents as outside the expected set. Count missed expected pieces, unexpected identities and repeated observations separately. Repeated reads of one identity are observations of the same item, not additional linen. Let the software and operator workflow resolve the event before posting the count.

Attachment is part of the linen design. A seam position that is convenient for sewing may be awkward in a finishing machine or noticeable to the user. Compare candidate positions on the actual linen, using the actual seam, patch or heat-seal process proposed for deployment. The textile family includes models with different attachment options; an option listed on one model should not be assumed for another. Inspect for folding, loose stitching and local fabric wear after the pieces complete the intended route. Ask the laundry team to review the placement before increasing the trial size.

A wash-cycle figure in a catalogue is a supplier-stated specification, not the outcome of your linen pilot. Define what a cycle contains at your site: washing, extraction, drying, finishing and any rewash. Keep the process recipe with the log, including chemistry and time at each heat stage. Where conditions fall outside the model's stated limits, change the candidate or obtain additional evidence before proceeding. A tag that still responds after processing can nevertheless have an attachment problem. Inspect the linen and the identification function as separate acceptance items.

Finish the pilot with an exception procedure that an operator can use on a busy shift. Decide who handles an unread piece, how to confirm its visible identity and how to prevent a manual correction from creating a duplicate event. Keep quarantined and retired pieces separate from usable stock. Compare the trial records with the expected list before changing the inventory ledger. Proceed to another read point only after the first one has a documented decision, a workable correction path and an accountable owner for the data. This page is a deployment plan; it does not claim a measured recovery rate or a finished laundry software system.

Deployment checklist