Dry-cleaner and laundry software: intake, status, pickup, delivery
The customer asks if the suit is ready. Staff hunt a bag by a paper number. Laundry software: intake with a photo, SMS status, pay on collection or online, a B2B pickup route — instead of a notebook and three calls a day from the same hotel.
A cleaner sells batch turn and trust. A 2,000 PLN suit cannot vanish in Thursday’s pile. Customers want a number and a status — like a parcel. Hotels, restaurants and clinics want a standing pickup 3× a week, a piece protocol and an invoice, not “are you coming today”. Ready tools are thinner than restaurant POS: eOrderFlow (dry and wet, SMS, labels, cloud), Pralnia77 and RFID laundry, SOVRANA / Battista UNI in industry, Kotrak in commercial plants. Many shops still sit on a till and a book. Search volume is smaller than restaurant POS; a lost garment or a hotel without a route is expensive.
The counter must finish in 20 seconds. Staff will not fill 12 fields in a queue. Scan, piece count, stain yes/no, due date, print a tag / QR staple. The rest (hotel contract prices, shortcuts “shirt / suit / down”) lives on the account or the service, not in the cashier’s head. The same discipline as a workshop intake — only the carrier is a bag, not a boiler job.
The flow the system must close
- Intake: customer / site, piece list, defects (stain photo, missing button), due date, price list (dry / wet / carpet / leather).
- An ID (barcode / QR on a staple, RFID at higher volume) scanned at every stage: sort, wash, press, out.
- Statuses: in, in process, stain treatment, ready, out, claim. A “ready” SMS + a status link with no account.
- Pay at the counter, up front, or on invoice for a site. Do not mix a retail receipt with the hotel loop.
- B2B: standing days, a driver route, a piece protocol at the hotel (how many out, how many back) — Android like field service.
- Several sites: in at A, out at B, a batch transfer, SMS “collect on Puławska”.
Street counter vs hotel on a route
Two products. Retail: Mr Kowalski’s suit, parcel-like status, SMS, 48 h collect, a claim with the intake photo. B2B: linen, cloths, workwear, RFID in industry, a fixed Tue/Thu/Sat route, a discrepancy protocol (“40 cloths out, 38 back”). eOrderFlow and Pralnia77 aim at the first world plus light B2B. Battista / RFID — the second, when you count pieces at a gate. Custom when you run both and the counter cannot look like hotel ERP, while the driver cannot carry a notebook.
Damage claims: the intake photo is your defence. Claim status and a decision (re-do, discount, refuse) in the panel, not in email. GDPR: customer data and a photo of their garment. EU server, stain-photo retention. We do not post the suit on Instagram “because it pressed well” without consent.
RFID, a staple, 20 seconds — not everything on day one
RFID on workwear and hotel linen makes sense at hundreds of pieces and losses. On a street counter a coded staple and a stain photo beat a 2 PLN tag on every shirt. We do not sell RFID gates because they are “modern”. We add a scan when volume and vanishing tablecloths justify it. Chemistry and bag stock — phase two, a cousin of a simple shop, not a reason to delay the ready SMS.
Why the niche is worth it and when to go custom
Polish “laundry ERP” is thin; many shops sit on a till. A good candidate for a small own SaaS or a panel for a 2–5 site chain under your brand. Stay on eOrderFlow / Pralnia77 when one counter, a simple price list and SMS are enough. Custom when: a chain, a hotel route, RFID, “book a home pickup” like a local delivery shop, a white-label site portal (the hotel logs in and sees its batches), or you want off someone else’s cloud when you sell the firm.
- MVP: intake (fast counter) + tag + status + ready SMS.
- A defect photo at intake. Payment and B2B invoices.
- Several sites, batch transfer.
- A driver route and hotel protocol — when the site calls more than retail.
- Home pickup for retail, RFID, chemistry stock — after numbers, not on a slide.
Describe street counter vs chain vs hotel B2B, daily piece count and whether status, losses or the route hurt. MVP: intake + status + SMS. A driver route when hotels call more than retail.
Tag, sort, stain, press — a scan in every room
A coded staple at intake is nothing if nobody scans at sort and at issue. Then you hunt the bag again. A tablet / scanner in sort, at the machine, at the press, on the counter. Status moves itself. Seasonal staff learn three buttons, not ERP. A “lost the waistcoat” claim has a trail: taken in, scan 11:02 in sort, no scan at press — you know where to look. RFID on hotel garments does this without a staple, but a tag on Mr Kowalski’s suit is overkill. A mix: staple for retail, RFID for cloths — two IDs in one status engine, not two programmes.
Counter price list: shirt, suit, down, leather, carpet, curtain, express. Shortcuts on screen, not 12 fields. Hotel price list: a contract, per kg or per piece, a route flat fee. The retail cashier does not need the hotel rate. The driver does not need the street-suit price. Roles. A bulk invoice for the site, a receipt for retail, KSeF when the hotel is invoiced from the panel.
A 3× weekly route and home pickup
Hotel, restaurant, spa, clinic: standing days, a window, a quantity protocol, a tablet signature, a discrepancy. Android like field service. Home pickup for retail: a courier-like slot, a bag, online pay, parcel-like status — a cousin of a local shop. Do not mix a hotel route (weight, standing pins) with a one-off wedding-dress pickup. Two job types, one map.
A 2–5 site chain under a brand: a shared regulars file, collect at another shop, bag transfers. A good candidate for a small own SaaS. One counter: eOrderFlow / Pralnia77. Pieces a day, hotels, sites.
Down-jacket season, weddings, hotels in August — peaks a notebook loses
Autumn and winter: down, coats, a queue at the counter. June: dresses, wedding linen, hotels at peak. A 20-second counter and a due-date tag are the shield. Express (24 h) is a separate service with another queue in sort, not “a note on a slip”. Without status the customer calls three times and staff hunt the pile. A “ready” SMS kills those calls; a status link kills the rest. A down “it went fluffy” claim without an intake photo is indefensible — the photo is cheaper than a suit.
Workwear with RFID: a gate on issue, wear, losses, a closed wash loop with a hotel or a plant. Another product than a street suit, but the same status engine. Pralnia77 and RFID vendors sell gates — buy them when you count hundreds of pieces. On 40 shirts a day, a staple. Chemistry, film, hanger stock: a minimum alert when you start counting laundry “food cost”, not on opening day. Season peak, hotels, RFID or staple.
A chain of shops and a small laundry SaaS
Two–five sites under one brand, a regular with a card, collect at another shop, an evening courier around estates: a classic candidate for your own panel, because packages are often single-site or industrial. White-label for a hotel (login, batches, protocol) sells a B2B contract better than a PDF in email. We do not build SOVRANA on the first street counter. We build intake, status and SMS, then a route, then a chain.
A hotel protocol and a counter loss — two courts, one code
The hotel signs on a tablet: 40 cloths out, 38 back. The discrepancy is a record, not a call. Retail: a lost waistcoat has a scan trail. Both worlds use the same ID and status, other roles and price lists. The driver does not price a street suit; the cashier does not see kg of linen. That is not “one SAP window”. Two screens on one API. eOrderFlow can be fine on the counter. RFID gates — when cloths vanish in the hundreds. Home pickup of a dress: a courier slot, not squeezed into the Tuesday hotel route.
A retail regular with an account: piece history, invoices, “always dry clean, never steam”. A hotel with a login: batches, protocols, invoices. A chain: the same card, another collect shop. That is SaaS worth writing when you have 2+ shops or 5+ B2B sites. One counter with a book: first a tag and SMS, not RFID. A claim without an intake photo is lost before the suit comes back.
A two-thousand-zloty suit and an eight-zloty tablecloth
The same status engine handles a piece whose loss ends in a one-star review, and a piece whose loss ends as a line on a hotel protocol. That is why an ID and an intake photo are mandatory in retail, and why hotels care about quantity and RFID. The counter list has shortcuts; the hotel list — kg and piece. Cashier and driver do not see each other’s rates. An SMS to Mr Kowalski does not go to hotel reception. Obvious on paper and the first thing that breaks in a “universal ERP”.
Counter hours, express cutoff, a Tue/Thu route: three clocks. Software with one “due tomorrow” lies to the hotel and to retail at once. MVP: counter + tag + SMS. Then the route. Then a chain and a hotel login. Not an RFID gate on a street-shop opening. Suits vs hotels, piece count, how many “is it ready” calls.
A counter MVP: scan, tag, ready SMS
Intake in 20 seconds, a stain photo, a code on a staple, status, a “ready” SMS. That closes the call and a lost suit. A hotel route, RFID, a chain, home pickup — after a month where the counter really scans. We leave eOrderFlow on one shop. Custom when the hotel calls more than retail and wants a protocol on the driver’s tablet. We do not mount RFID gates on 30 shirts. We do not fake a fiscal till. Pieces a day, hotels, how many times a day they ask about the suit.
Seasonal counter staff learn three buttons: intake, stain yes/no, print. If the screen needs ERP training, they return to the book in the first rain. “Ready” SMS goes out on its own. The hotel driver has a separate route screen. Two interfaces, one API — the same pattern as field service and towing, only the carrier is a bag.
Express cutoff at 12:00, standard 48 h, carpet 7 days: three dues on the tag, not in the cashier’s head. The customer sees the date in SMS and in the link. The hotel sees the route window, not the street-suit date. Mixing those clocks is the notebook’s most common error and the reason to have statuses at all.
eOrderFlow, Pralnia77, RFID — counter vs hotel
eOrderFlow aims at dry and wet: labels, SMS, cloud. Pralnia77 and RFID gates — workwear and hotels when you count hundreds of pieces. SOVRANA / Battista UNI is industry. Kotrak — commercial plants. On a street counter a QR staple and a stain photo beat a 2 PLN tag on Mr Kowalski’s shirt. Intake must finish in 20 seconds: scan, pieces, stain yes/no, print. Twelve ERP fields return to the notebook on the first wet Friday.
- Statuses: in, wash, stain, ready, out, claim — SMS with a link and no account.
- Retail: a suit like a parcel. B2B: standing days, a quantity protocol, a signature on the driver’s tablet.
- Several shops: in at A, out at B, a batch transfer, SMS where to go.
- A claim without an intake photo is word against word.
A 3× weekly route and a dress pickup at home
Hotel, restaurant, spa: Tue/Thu/Sat, a window, a discrepancy “40 cloths vs 38”. Android like field service. Home pickup is another job type — a courier slot, a cousin of a local shop, not squeezed into the morning hotel route. The cashier does not see the per-kg linen rate; the driver does not price a street suit. Two screens, one API. KSeF when the hotel is invoiced from the panel. We do not fake a fiscal till.
Down-jacket peak, weddings and three clocks on the tag
Autumn: down and coats. June: dresses and wedding linen, hotels at peak. Express by 12:00, standard 48 h, carpet 7 days — three dues on the staple, not in the cashier’s head. The hotel sees the route window, not the street-suit date. Mixing clocks is the notebook’s most common error. A regular with an account: “always dry clean, never steam”. A hotel with a login: batches and protocols. A 2–5 site chain is a candidate for a small own SaaS; one counter — eOrderFlow / Pralnia77.
Frequently asked questions
- Can the customer track like a parcel?
- Yes — a link with a number, no account if you want. An account helps regulars and invoices. A “ready” SMS kills “is the suit done”.
- Damage claims?
- The intake photo is your defence. A claim status and decision in the panel, not in email. Without a photo it is word against word.
- Several drop-off points?
- In at A, out at B, a batch transfer. SMS says where to go. Batch stock per site, not one notebook on a bus.
- A customer app?
- A status page first. An app when you have a chain and want “book a home pickup”. The driver and counter app matters more.
- eOrderFlow / Pralnia77 / RFID instead of custom?
- One counter and SMS — often a package. RFID on hotel garments and losses. Custom for a chain, a B2B route, home pickup and a hotel portal. We do not mount RFID gates on 30 shirts a day.
- Does this replace the fiscal till?
- No. Status and intake in the system; the receipt on the till you have. B2B invoices from the panel, with KSeF if that is your source. We do not fake a printer.
- Does a hotel want a discrepancy protocol?
- Yes — how many pieces out, how many back, who signed on the driver’s tablet. That is the heart of B2B. Without a protocol you get a call and a tablecloth complaint.
- How long is an MVP?
- Intake + tag + status + SMS: weeks if the service list is short. A hotel route and a second site — after the first month where the counter really scans and does not duplicate the book.
Describe your project