B2B Laundry Billing for Hotels & Hostels — A Step-by-Step Setup

A single 80-room hotel can do 600–1,200 laundry pieces a week. Land one, run it well, and you've doubled your shop's throughput without a single new walk-in customer. Land one and run it badly — late invoices, lost tickets, no GSTIN on file — and you'll be replaced by the next laundry on the manager's spreadsheet within two months. This piece walks through the practical setup that turns a hotel from a fragile account into a recurring revenue engine.

Step 1 — Agree pricing on a per-kg + escalation basis

Hotels rarely buy laundry per-piece. They buy in bulk by weight because their inventory turns predictable: each room produces roughly 1.2 kg of laundry per night across linens + towels, and a banquet event adds another 4–6 kg per cover. Quote per-kg with two sub-rates: a base rate for standard linens and a premium rate for delicate or branded items.

Two clauses worth writing into the agreement:

• Volume escalator— a 2–3% rate reduction at a defined monthly threshold (e.g. 800 kg/month). Hotels love this; you've already amortised your fixed costs past that mark, so the discount costs you almost nothing.
• Quarterly review on diesel + chemical pass-through — a clause that lets you raise the rate by the verifiable input-cost increase. Without it, a 12% chemical price hike eats a year of margin.

Step 2 — Capture the GSTIN and billing entity properly

On the very first order. The hotel's registered name, GSTIN, billing address, and PAN go into the client record before any pickup. If you skip this, the hotel can't claim ITC on the 18% GST you charge — which means they're paying 18% out of pocket, and they'll figure that out the moment their CA runs the next month's reconciliation.

Tip: many hotels operate as a partnership or LLP whose registered name differs from the brand name on the door ("Marriott Suites Kochi" might bill as "Lakeside Hospitality LLP"). Get the registered name right at the contract stage; mistakes here mean reissuing invoices later, which delays payments by 4–6 weeks.

Step 3 — Tag every order to the client at creation

The hardest mistake to undo is a missed tag. Once a pickup runs as a normal walk-in instead of a tagged hotel order, you have to manually back-track at month-end — reading dispatch logs, matching driver routes, calling the hotel housekeeper to confirm. Nothing reconciles cleanly.

A modern shop console fixes this with a one-tap Bill to → Marriott Suites dropdown on the new-order screen. Every order tied to that client through the month aggregates automatically into the statement. See the Deelo Shops Bill-to flow →

Step 4 — Issue the consolidated statement on day 1

The 1st of the month. Not the 5th, not the 7th. Hotels pay on a 30-day cycle from invoice date — every day you delay is a day you don't get paid for, but the hotel has already consumed the service. A statement out on the 1st with Net-30 terms means money on the 31st, not the 27th of the following month.

The consolidated statement should carry:

• A statement number formatted SMT-YYYYMM-NNNNso the hotel's accounts team can reference it cleanly in audits.
• One row per order: order date, booking ID, item count, kg weight, taxable value, CGST + SGST, total.
• A summary block: subtotal, total GST, grand total, due date, payment instructions (NEFT / cheque / UPI).
• Your GSTIN andthe hotel's GSTIN, both prominent at the top.

Send the PDF by email and by WhatsApp. The accountant prefers email (audit trail), the housekeeping manager prefers WhatsApp (acts on it faster).

Step 5 — Track payments + chase systematically

The polite chasing schedule that doesn't damage the relationship:

• Day 0: Send the statement.
• Day 25:Friendly WhatsApp reminder — "your May statement is due on the 31st, would you like the UTR'd when you pay?"
• Day 31: If unpaid, polite email. Attach the statement again, list the bank account details. No mention of late fees yet.
• Day 38:Phone call to the accountant. Don't escalate to the GM — that burns the relationship if it's a genuine paperwork delay.
• Day 45:If still unpaid and no clear commitment, pause new pickups (politely framed as a "pending settlement" pause) and now escalate.

Your console should mark every statement's status as you go — ISSUED → PARTIALLY_PAID → PAID or OVERDUE— so the dashboard tells you who's slipping without you having to remember.

Common mistakes to avoid

• Free pickup for "just one month". Once you do it, it becomes the norm. Charge a delivery fee on every cycle from day 1, even if it's ₹500/month — you can renegotiate down later, but you can't add it on later without friction.
• Bundling damages into the next month's statement. Damages need a separate, clearly-marked credit note within the same billing cycle. Mixing them in the next month's statement looks like you're hiding adjustments.
• Letting the laundry runner be the contact point. Runners change. Have a single account-management contact (you or your manager) named on the contract; the hotel should never have to call the driver to chase a missing ticket.
• Quoting per-piece while billing per-kg. Pick one for the entire account and stick with it. The two-mode mismatch is where 80% of hotel disputes start.

The credit-risk rule

Three-star and four-star hotels in Kerala pay reliably on Net-30 once the relationship is established. Five-star branded hotels often run Net-45 or Net-60 because of their internal accounts-payable cycle — agree to it consciously, but factor the cost of working capital into your rate. Set an internal credit ceiling (60–90 days of expected billing) per client and pause new pickups if outstanding crosses it. The Deelo Shops client profile carries this credit limit field and surfaces a warning when an account approaches it.

The whole loop in one sentence

Capture the GSTIN, tag every order, issue on the 1st, chase politely from day 25, pause from day 45, never bundle damages — and the hotel becomes the cleanest revenue line on your P&L.