RFID Laundry Exceptions: Missing, Duplicate and Unreadable Items
A practical worksheet for operations, stores and project teams.
By addanode · Published 5 November 2026
An RFID laundry exception workflow should distinguish an item that was expected but not observed, a repeated event and an identity that could not be resolved. These conditions need different checks. Preserve the reader evidence, manifest and handling context so reconciliation improves the item record without turning a missed read into an unsupported loss claim. RFID laundry exception handling needs a clear route from an unresolved observation to a documented operational finding.
Use the working record
Download the editable worksheet. Record the actual evidence and responsible reviewer against each relevant row. The empty results are inputs for your project, not completed tests. Add the equipment identity, operating period and reference method before assigning an outcome. Retain unsuccessful checks and the evidence from any repeat after correction.
Define what was expected at the handover
Identify the shipment, trolley, bag or other handling unit and the manifest used for comparison. Record who created the expected item list and when it became effective. A missing-item exception has meaning only against a defined expected population at a particular event.
Keep changes to the manifest visible. Items added after dispatch or removed for rewash should have their own authorised events. Editing the expected list until it matches the received count can hide a process problem and erase the evidence needed to resolve a dispute.
Preserve the actual read observations
Retain tag identity, reader or zone, acquisition time and the event grouping used by the system. A reader may observe the same tag repeatedly during one passage. Those observations can support confidence in an event without representing additional physical items.
Record the accepted rule that turns raw observations into a business event. Include the relevant read window and movement evidence. A tag seen in an adjacent trolley should not automatically join the current shipment solely because it appeared during the same broad time interval.
Treat an expected but unseen item as unresolved
When a manifest item is absent from the accepted read event, create an exception linked to that handover. Possible explanations include an actual shortage, unreadable tag, wrong manifest or an item outside the validated reading arrangement. The first status should reflect the unresolved evidence.
Use the agreed recount or search procedure. Record the physical finding, any manual identity check and the person who resolved it. Only apply a loss or shortage conclusion when the available evidence and responsible operational process support that outcome.
Distinguish duplicate observations from duplicate identity
Repeated reads of one tag during one passage are usually an event-processing issue. Two physical items associated with the same identifier are an identity-control issue. Keep separate exception categories because deduplicating the first does not solve the second.
For an identity conflict, inspect the physical items and the association history. Preserve the incorrect relationship and its correction with effective dates. A replacement tag should close the earlier tag association without deleting the item's previous wash and movement history.
| Exception | First question | Evidence needed for closure |
|---|---|---|
| Expected item unseen | Was it physically present? | Recount or authorised search finding |
| Unexpected item seen | Does it belong to this shipment? | Manifest and custody review |
| Repeated observation | Is it the same passage event? | Reader timing and grouping rule |
| Duplicate identity | Are two items using one identity? | Physical association check |
| Unreadable item | Can its identity be established another way? | Manual identification and tag inspection |
| Event arriving late | When did the movement actually occur? | Acquisition and arrival timestamps |
Investigate unreadable items systematically
Record the item type, tag position, condition and handling arrangement. Compare with the representative reading conditions accepted during commissioning. Wetness, dense loading, orientation and surrounding material may affect a particular installation and should be assessed with actual evidence.
A controlled reread can help distinguish a damaged tag from a difficult reading arrangement. Retain the first failure and later result. If a tag is replaced, preserve the item's identity and maintenance history, and verify the new association before returning it to the normal workflow.
Keep the exception separate from custody liability
The event record should identify the parties and physical handover being reviewed. Commercial responsibility for a shortage follows the actual agreement and verified evidence. A reader exception alone should not automatically create a charge or assign blame to a driver, hotel or laundry operator.
Provide a review route for disputed findings. Keep the original event, supporting observations and authorised resolution together. Where a financial adjustment is made in another system, link its reference without presenting the RFID observation as the entire basis for that decision.
Test recovery and reprocessing behaviour
Communication recovery can deliver earlier events after a receiving count has already been reviewed. Preserve acquisition time and stable event identity so a retry does not create another issue or receipt. Define how a late event reopens or amends a provisional reconciliation.
Record the processing rule version used for each result. If the event-grouping method changes, evaluate its effect before recalculating historical reports. Preserve the previous outcome and the reason for any authorised revision so operational teams can explain changed totals.
Use exception patterns to improve the workflow
Review exception frequency alongside the number and type of handled items, the reading arrangement and the closure findings. A high unresolved count can reflect poor manifest discipline as well as reading conditions. Inspect underlying records before choosing a hardware or process change.
Handover should demonstrate one example of each relevant exception through to closure. Include the manual route, identity repair, late-event handling and export. The resulting process should let an authorised reviewer understand what was expected, what was observed and what evidence justified the final item status.
Connect the decision to the project
Use Hotel linen, Rfid laundry linen tracking to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.
Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.
Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.
Sources and method
GS1 EPCIS 2.0.1 provides event-data and correction modelling background. Read performance and exception closure require evidence from the actual laundry handling and selected tag installation.
Frequently asked questions
Does a missed read mean an item was lost?
Treat it as unresolved until the manifest, physical check and reading evidence support a conclusion.
Are repeated reads the same as duplicate tags?
Repeated observations can refer to one item in one event. Duplicate identity means separate physical items share an identifier and needs an association review.
How should late records affect a closed count?
Use a controlled amendment with original acquisition time, stable event identity and preserved previous results.
Define a first stage your team can verify.
Tell us the site, equipment, existing records and the decision you need to improve. We will use those inputs to discuss the scope and acceptance evidence.