In this article
A laundry looks simple: garments come in, garments go out. What wears the owner down is not the washing, it is the remembering. How many pieces did that customer drop off on Thursday? Is his thobe at the press or in sorting? When the answers live in a counter notebook, an employee's memory and numbers scrawled on bags, the first lost garment costs you more than its price. It costs you a customer who leaves without telling you why.
The usual proposal is a point-of-sale terminal with screens and training. That fits large multi-branch operations. But in a shop with three staff, one location and a driver, the terminal stays closed most of the day, because the work happens standing up: at the counter, at the delivery car, at the pressing table. The one tool everybody holds is a phone, and the app open all day is WhatsApp. Instead of moving people to the system, move the system to where they are.
Where garments actually go missing
Most losses come from five recurring points:
- Intake without a recorded count: staff count in front of the customer but never write the breakdown down, so a later dispute is one word against another.
- Hand-written ticket numbers: two similar numbers on the same day are enough to swap two orders.
- Unknown status: the customer calls to ask and someone walks the racks instead of answering in a second.
- Handover without confirmation: nobody knows who received what and when, especially on delivery runs.
- Corporate accounts: monthly hotel or office contracts, reconstructed at month end from scraps of paper.
Six messages that cover a full laundry day
Every event in the shop maps to one line typed from a phone; each line updates the record and notifies the customer when it should:
| Message | Example | What it produces |
|---|---|---|
| Intake | intake 05xxxxxxx 8 pieces: 5 thobes, 3 trousers, standard | Ticket with a sequential number, plus a customer message with the number and pickup time |
| Rush | rush 1247 today 6pm | Updated due time and price on the express tariff |
| Ready | ready 1247 | Status update and a notice that the order is waiting |
| Delivery | deliver 1247 Al Narjis 5pm | A task assigned to the driver with address and ticket number |
| Handover | delivered 1247 cash 48 | Ticket closed and payment recorded |
| Corporate statement | statement Elite Co month 8 | All the company's tickets and their total, ready to invoice |
Why the ticket number is the backbone
Every message after intake starts with a number. It is generated once, automatically, so it never repeats, and it stays attached to the bag, the customer and the amount. When a customer calls with his ticket number, the answer arrives before anyone leaves their spot. At month end you can see how many tickets came in, how many closed, and how many have been open for more than two weeks — that last group is exactly what turns into a problem if you leave it alone.
Damaged and missing items
These are not solved after the fact. Record the condition at intake: an old stain, an open seam, a colour that may run. A line like "note 1247 stain on right sleeve before washing" takes a second to type and replaces a long argument two days later — and the customer should see it with the intake confirmation, not after collection.
Corporate accounts
Company contracts are the steady part of a laundry's income and the part that leaks most. The hotel sends laundry daily; month end arrives and the total is reconstructed from memory. The safer approach is an account per organisation, with the company name on each ticket at intake, so the statement is just a view of what was logged day by day. The difference is not tidiness, it is the amount you collect: you invoice earlier and take fewer deductions, because you can produce the detail that proves the count. To tie that to billing, see invoicing from WhatsApp.
Invoicing and compliance
A laundry, like any establishment in Saudi Arabia, falls under the e-invoicing requirements, whose phases and details are published by the Zakat, Tax and Customs Authority on zatca.gov.sa. Do not rely on WhatsApp groups or a vendor's interpretation; check the official source or your accountant for what applies to your business. Operationally, what matters is that each ticket is recorded the moment it happens, because a correct invoice starts from a correct record, not a later tidy-up.
Checklist before you start
- Write out your item list and tariff, with standard and express prices.
- Agree one fixed format for the intake message and hold everyone to it.
- Start with one branch and two weeks before expanding.
- Decide who may give a discount and who may close a ticket without collecting payment.
- Review every Thursday the tickets open for more than 14 days and contact those customers.
- Keep the paper notebook in parallel for one month, compare, then drop it.
A quick test: ask your employee how many tickets have been open for more than two weeks. If the answer takes more than a minute, the problem is not the employee.
In short: a laundry does not need a heavy system, it needs a record that does not forget. Six WhatsApp messages — intake, rush, ready, delivery, handover, corporate statement — cover a garment's cycle from the counter to collected payment, and turn a dispute into a ticket logged at the right time. That is what running operations from WhatsApp in Fahim is built on.
Run your business from WhatsApp
Fahim turns the messages your team already sends into stock, invoices and reports. Try it free for a month.
