Somebody else's socks in the bag
A customer drops off a bag of washing on Monday morning. The attendant writes their name on a piece of tape, weighs the bag, notes the weight on a pad and puts it in the queue. By lunchtime there are fifteen bags. Some loads are split across two machines, some share a dryer because they are small.
On Wednesday the customer finds a child's t-shirt in their folded laundry and is missing a work shirt. Another customer rings about a missing towel. The attendant who folded both loads was covering for someone else and cannot say which pile was which.
Separately, the weight on the pad says 6kg but the customer is sure it was less. There is no record of who weighed it or what the scale said.
Students at the start of term, holiday lets on changeover day and busy families all drop off at once. The busier the morning, the more loads share machines, and the more likely a small item ends up in the wrong bag.
The load loses its label as soon as it leaves the bag
The tape on the bag identifies the bag, not the clothes. Once the load is in the machine, the only link is the attendant's memory of which machine had whose washing.
- Loads are split or combined to fill machines without recording it.
- Folding happens in batches, sometimes by a different attendant.
- Weights are written on a pad that is not linked to the customer or payment.
- Special instructions (no fabric softener, hang dry the jumpers) are spoken, not recorded.
- The customer is not told when it is ready, so collections drift.
Refunds, lost regulars and arguments about weight
Mixed-up washing is personal. People do not like strangers' clothes in their bag, and a missing favourite item feels bigger than its value. Regulars stop using the service. Weight disputes chip away at the price you are owed, and without records, the attendant cannot defend the figure.
How we build service wash tracking
- At drop-off, the customer is found or created by mobile number. The load gets a numbered tag or a mesh bag with a code, used from start to finish.
- The weight is read from the scale, or typed in by the attendant, and saved to the order with a timestamp. The customer receives a text receipt showing the weight.
- Instructions are picked from a short list (no softener, low heat, hang dry) and printed on the tag.
- When a load goes into a machine, the attendant taps the machine number against the tag. If a load is split, both machines are recorded.
- At folding, the folded clothes go straight into a bag with the same code. The system flags if a code is used twice.
- Tagging the finished bag sends the customer a ready message.
| Step | Recorded against the load |
|---|---|
| Drop-off | Customer, weight, instructions |
| Wash and dry | Machine numbers used |
| Fold | Same code on the finished bag |
| Ready | Text to the customer |
| Collection | Who collected and when |
If you use a laundry system like CleanCloud for service washes already, we build on its customer and order records rather than starting again.
A shop floor where every load has a name
Attendants can see at a glance which loads are in which machines and what is waiting to be folded. Weight queries are answered with the receipt the customer already has. Instructions are on the tag, not in someone's memory, so the jumpers that should be hung are hung.
When a customer says an item is missing, the record shows which machines their load went through, which narrows down where to look.
Is this your laundrette?
- Service wash bags are identified with tape and a pen.
- Customers have found other people's items in their laundry.
- Weights are written on a pad, not linked to the order.
- Instructions are given verbally.
- Customers do not know when their service wash is ready.