An order in a cleaning shop is rarely “one item — one job”: three pairs, each with its own job, technician and deadline, half paid at drop-off. We go through how to manage such an order so that it doesn't get lost between the counter, the workshop and the client's phone — using how this is set up in CRM.Knopka on the SneakNFresh network.
why an order in a cleaning shop is harder than it looks
On paper it's simple: the client brought it in — the technician cleaned it — the client picked it up. At the counter it's different.
A client brings suede boots and sneakers. The boots need a full cleaning and a protective coating, the sneakers need cleaning and insole replacement. One technician does the coating, another the insoles. The sneakers will be ready in two days, the boots in four. The client pays half now and half at pickup.
If such an order is recorded as a single line, “2 pairs, 7,800 ₽”, questions follow that nobody can answer quickly:
- what part of the order is already ready?
- which technician worked on the boots, and how much should they be paid?
- how much has the client already paid and how much is left?
- the client is calling for the third time — what do we tell them?
The answer to all four is to manage the order by items: each pair and each job is a separate line with its own technician, price and status.
intake: the order is priced with the client present and item by item
Intake is the most important place. Anything not recorded here will have to be reconstructed from memory later.
In CRM.Knopka the front-desk administrator builds the order with the client present. The order card holds on one screen:
- items — what the item is and what job it needs;
- the performer for each item;
- the price of each item and the discount;
- the total, payment and balance due;
- the ready-by date — and how many days are left until it;
- a “before” photo.
An order for illustration (illustrative figures):
| item | technician | price |
|---|---|---|
| full cleaning · suede / nubuck · boots | Oleg | 3,800 ₽ |
| water-repellent coating · protection from water and road salt | Oleg | 1,800 ₽ |
| insole replacement · size 42 | Irina | 2,200 ₽ |
| total | 7,800 ₽ | |
| paid at intake | 3,900 ₽ | |
| balance | 3,900 ₽ |
Why so many details at the counter? Each line then works three times: the client sees the status from it, the cash register sees the balance, the ERP sees the technician's output.
receipt and document with a QR code
After intake the client receives a receipt: the service terms, the contents of the order and a QR code. The QR opens the order status — there is no need to call the location and give the number.
At pickup a document is issued — also with a QR code. The receipt and the document sit next to the order in the CRM; you don't have to look for them in a folder.
Why this matters for a network, and not just for one location: a receipt is a promise to the client. If the terms on receipts differ between locations, the conversation in a disputed situation will differ too. That is why it is better to have one receipt for the whole network — in the CRM it is generated by the system, not written out by hand by the administrator.
in progress: a status for each pair
As soon as the order is accepted, each item starts its own path. The sneaker cleaning is ready while the boot coating is still drying — the CRM shows it as it actually is: one item “ready”, another “in progress”.
What this gives:
- the front-desk administrator answers the client in seconds without going to the workshop;
- the technician sees their own items, not “order #1172 as a whole”;
- the location manager sees what is stuck from the status history: when an item was received, when it was started, when it was finished.
The ready-by date is in the card from the very start. If it is approaching and an item is still in progress, you can see it before the client comes and leaves empty-handed.
what the client sees
The most frequent call to a cleaning shop is “is it ready or not?”. It can almost be eliminated if the client sees the answer themselves.
In the client portal in CRM.Knopka — on the phone, no app needed — the client sees:
- the order status step by step: received, in progress, ready, picked up;
- each item separately — what is ready and what is not yet;
- the ready-by date;
- how much is paid and how much is left;
- “before / after” photos, once the technician has added them;
- points and level in the club, the club card, location promotions and delivery.
The “after” photo is a story of its own. For shoe cleaning it is the main argument: the client sees the result before coming in, and shows it to friends.
If the client does write — in Telegram, WhatsApp* or through the site — all messages arrive in the CRM's unified inbox, not on different phones. VK and Avito can be connected.
pickup
By pickup everything is already known: the items are ready, the balance is calculated. The front-desk administrator accepts payment of the balance and issues the document with a QR code, and the client is credited cashback in points under the club rules. The client starts the next visit already with points — that is the point of a club with levels and cashback: coming back pays off more than going to the place next door.
after pickup: cash and technician pay
The order is closed, but for the location owner it is only starting to work.
ERP.Knopka receives orders, payments, refunds and technician output from the CRM and calculates on its own:
- revenue and cash by day, location profit for the month;
- technician pay by each location's rates — Oleg has his own rate for cleaning, Irina has hers for repair;
- shift schedule and payouts;
- supplies inventory with minimum stock levels and push notifications;
- royalties by the location's terms.
This is exactly why the performer is recorded on every item already at intake. Without it, pay based on output would have to be assembled by hand from receipts. How this is calculated step by step — in the article how to calculate technician pay by location rates.
The ERP works at the first locations of the SneakNFresh network; the rest are being connected in waves.
when there are many locations
For one location, everything described is simply order. For a network it is a condition of survival: every new front-desk administrator at every new location must manage an order the same way as at the first one.
What is added in a network:
- analytics by location and by network — average receipt, how many clients came, how many orders were created and closed, how much money came in, with the change against the previous period;
- a shared directory of locations — each location has its own time zone and currency. The time zone determines which day an order belongs to: a location in Uzbekistan and a location in Moscow close the day at different times;
- roles by location — the front-desk administrator sees their location, the owner sees the whole network.
What this looks like in a large network: SneakNFresh has 70+ locations in 6 countries, 712,321 orders since 2021, 175,834 clients and 7,000+ orders a month (across the SneakNFresh network, including locations that keep records outside the CRM).
If you are moving from another program — read where errors hide in a migration: discounts, time zones and performers move not the way they seem to.
checklist: what to check in a CRM for a cleaning shop
Before choosing a program, check:
- can an order be broken down into items — each with a technician and a price?
- does the order show payment and balance, not just the total?
- is there a ready-by date, and can you see how much time is left until it?
- does each item have its own status — or one for the whole order?
- does the client receive a receipt with a QR code for the status?
- can the client see the status and photos on their phone without calling?
- do messages from all messengers arrive in one place?
- is technician pay calculated from the same orders — or does it have to be reconciled by hand?
- if there are several locations — is there analytics for each and for the network, and its own time zone for each location?
CRM.Knopka answers “yes” to all nine questions — verified on the SneakNFresh network. Pay and location profit are calculated by ERP.Knopka, which works together with the CRM.
frequently asked questions
do I need to split the order into items if the client brought one pair?
Yes, if there are several jobs on the pair: cleaning and repainting can be done by different technicians on different days. One item — one job.
does the client need to install an app to see the status?
No. The client portal opens on the phone, and the order status — via the QR code on the receipt.
what if the client pays in parts?
The order card shows the total, the payment and the balance. At pickup the front-desk administrator accepts the balance.
how is a technician's pay linked to the order?
The performer is recorded on each item. The ERP receives technician output from the CRM and calculates pay by the location's rates.
will this work for a clothes dry cleaner or a repair shop?
The scenario is the same: item → order items → technicians → status → pickup. Verified on the SneakNFresh network, which has both cleaning and shoe repair.
