LINEN WASH LIFE
How many washes does hotel linen last?
Industry reporting puts towel life at roughly 100 to 200 washes (rmthospitality.com), but an average is no use for planning a specific stock holding. IntelTagRFID is a UHF-RFID textile tracking and laundry reconciliation platform that accumulates a lifetime wash count on each individual tag, so replacement is driven by what that item has actually been through rather than by an assumed average or the date it was bought.
Per-item wash counts, not batch averages
Each tag accumulates its own lifetime wash count across its whole life. Two towels bought on the same day and put into the same store will diverge, because one spends its life in a high-turnover area and the other does not. A per-item count captures that; a purchase date and a rule of thumb cannot.
The thresholds, and what they are for
Rated wash life is configured per deployment — a default of 100 cycles, with towels set to 150 in one build — because fabric, wash chemistry and process vary and no single figure is right everywhere. Items are flagged for inspection from 75 washes, and a condemn threshold at 80 washes marks stock for withdrawal. A separate tag auto-retire limit of 200 washes, with a near-limit flag at 90% of it, governs the tag rather than the textile. Every one of these is a configured setting, not a measured outcome or a guarantee.
Condemnation recorded as condemnation, not loss
An item formally removed at end of life is recorded with a reason, which separates disposal from disappearance. Without that distinction, every withdrawn item inflates the loss figure and the real loss rate becomes unknowable. Condemnation reporting shows monthly trends split by reason — over-washing against damage or loss — and a watchlist flags stock approaching end of life for physical inspection before it fails in service.
Forecasting the replacement order
An end-of-life forecast projects from recent wash rates when each item type will reach its threshold and how many units to reorder. Items with no recent activity are flagged as stalled rather than counted as consumed, because an item sitting in off-cycle storage is not ageing. The output is a procurement recommendation with a quantity against a date, which is a different document from a stock count.
Common questions
Industry reporting puts towels at roughly 100 to 200 washes (rmthospitality.com). For a specific operation the useful figure is the per-item wash count against a rated life configured for that deployment, because fabric, chemistry and process vary.
100 cycles by default, with towels configured at 150 in one build. It is a configured setting per deployment, not a product guarantee.
The condemn threshold is a configured setting, 80 washes by default, with an inspection watchlist from 75 washes so stock is physically checked before it fails in service.
Condemnation is recorded with a reason, so a withdrawn item is reported as disposal rather than disappearance. Trends are split by reason — over-washing against damage or loss.
Yes. An end-of-life forecast projects from recent wash rates when each item type reaches threshold and how many to reorder, and flags items with no recent activity as stalled rather than consumed.
They are tracked separately. A tag auto-retire limit, 200 washes by default with a near-limit flag at 90%, governs the tag. The textile has its own rated life and condemn threshold.
Talk to Us
Tell us about your operation and we will come back with a practical assessment.