What a laundry business can automate — and what it shouldn't

Most counter work in a laundry falls into two kinds. Some tasks follow a fixed rule and happen dozens of times a day: find the rate for a shirt with dry clean, add up the bill, tell the customer the order is ready. Others need someone to look, listen or decide: is this stain old or new, is the customer right, should this regular get ₹50 off. The first kind is where software saves time and prevents mistakes. The second kind is where taking the person out usually makes things worse.

Before automating any task, ask four questions:

• Is the rule the same every time? A rate card is. A discount for an unhappy customer is not.
• Does it happen often? Something done forty times a day is worth automating. Something done twice a month usually isn't.
• Is a mistake easy to make and costly when made? Wrong totals, forgotten messages and skipped backups are typical examples.
• Does the customer lose anything if software does it? If the answer is a personal touch or a judgement call, keep a person on it.

Each of these is something staff already do by hand, usually with a calculator, a slip book or their own phone.

Rate lookup at the counter

When staff remember prices, they remember them differently. A rate card in the system removes the guesswork. In KIWIKIT, tapping a garment and a service fills the rate from your rate card, with a separate urgent rate for rush work and a choice of pieces or kilograms on each line. Prices are changed in one place and every change is logged, so nobody quotes last year's rate.

Bill generation when the work is finished

Adding up a bill at handover, while the customer waits, is where errors creep in. If each garment is marked done as it is finished, the bill can be built from the order itself. KIWIKIT generates the bill automatically when the last garment in an order is marked done and moves the order to Ready for Pickup. Shops that want to check every bill first can switch to manual billing.

Status messages to customers

Most 'is my order ready?' calls can be avoided. Once the shop's WhatsApp sender is connected, KIWIKIT can message the customer when an order is received (with a PDF receipt), when cleaning starts, if it goes on hold, when it is ready, when it is handed over or cancelled, and when a payment or refund is recorded. Order messages carry a private tracking link that shows status and balance.

Receipts

Every advance and payment should produce a receipt without anyone writing one. Recording an advance at intake creates a receipt, and each later payment is recorded against the order with its mode (cash, UPI, card, bank transfer, cheque or other), so the customer's balance is always current.

Reminders for dues, partly

The amount and the wording can be automated. The decision to send should not. In KIWIKIT the receivables list shows who owes what, and one tap sends a WhatsApp payment reminder listing the customer's unpaid orders and total balance. Reminders are not sent on a timer: someone at the shop chooses who to remind and when.

Daily backups

A backup that depends on someone remembering is not a backup. KIWIKIT takes an automatic daily backup at the hour you choose, encrypts it, stores it in your own Google Drive or on the server and keeps it for 7 days by default.

Reports

End-of-day totals should never be added up by hand. The counter dashboard shows today's orders and collections against yesterday, orders by stage and what is overdue, and the daily receipt summary splits collections by payment mode. Which numbers to read, and when, is covered in the reports guide.

Software can record a decision. It should not make the ones that need eyes, hands or a conversation.

• Inspection at intake. Someone has to turn out pockets and look for stains, loose buttons, worn collars, missing beads on a lehenga and colours that might bleed. The system should make it quick to record what they find (KIWIKIT has inspection tags, a condition note per garment and up to 4 photos per order), but it cannot do the looking.
• Quality check before handover. Scanning a tag tells you a garment is finished, not that it is finished well. A quick look at pressing, stain removal and folding before the order goes on the rack prevents a complaint later.
• Complaints. An unhappy customer wants to be heard by a person. Use the intake record to settle the facts, but have the conversation yourself.
• Discounts and write-offs. Who may give a discount, and how much, is a business decision. Write the rule down and let the system record what was given.
• Chasing dues from regulars. A WhatsApp reminder suits most balances. A long-standing customer with a large balance usually deserves a phone call.

Switching everything on in one day is the most common mistake. Staff stop trusting the system the first time it sends a message they didn't expect, and customers get four updates about one shirt. Roll it out in stages:

1. Clean up the rate card first. Everything downstream depends on correct rates. Check your most common garments and services, normal and urgent, before anything else.
2. Start with intake and billing. For the first week, let staff take orders, tag garments and let bills build themselves. Keep WhatsApp messages manual.
3. Switch on one message at a time. Begin with the receipt at intake and the ready-for-pickup message. Add others only if customers find them useful.
4. Give each person only the screens they need. A presser who sees only their work queue makes fewer mistakes than one who sees everything. Roles and permissions are explained under staff, roles and branches.
5. Tell customers at the counter. One sentence is enough: you will get a WhatsApp message with your receipt now and another when the order is ready.
6. Review after two weeks. Ask staff what feels slower than before, and fix the setting rather than blaming the person.

Customers gave you their number to hear about their clothes. Treat that as a limited permission. A few rules keep your messages welcome:

• Timing. Automatic messages go out when the step happens. If garments are scanned as done at 11 at night, the ready message goes at 11 at night. Finish scanning during shop hours, or keep that message manual.
• Frequency. Most customers want two or three messages per order: received, ready and paid. In KIWIKIT each message template can be set to send automatically or only when staff press send, so the rest can be kept for when they matter.
• Language. Write templates in the language your customers read. Templates are editable text, so a shop in Pune might write them in Marathi, while a shop in a mixed area might use two short lines of Hindi and English.
• Content. Shop name, order number, what happened and what the customer should do next. Leave out long greetings, capital letters and offers.
• Dues. One polite reminder, then a call. Repeated reminders to a regular customer cost more goodwill than most balances are worth.

WhatsApp messages need the shop's WhatsApp sender connected. Without it, the rest of the automation (rates, billing, receipts, printing, reports and backups) still works.

• Rate card checked, including urgent rates and per-KG items
• Automatic or manual billing chosen, and staff know which
• Inspection and photo habit at intake agreed with counter staff
• Two or three WhatsApp messages set to automatic, the others manual
• Templates rewritten in your customers' language
• Daily backup hour set and the first backup checked
• One named person responsible for the quality check before handover
• A written rule for discounts and who may give them

If you would like to see these settings on a working shop before deciding, you can book a demo.