How an ERP helps a laundry business open more branches without chaos

A single counter runs on the owner's memory. The owner knows the regulars, remembers who paid and catches a wrong rate before the bill goes out. Add a second counter or a second shop and that memory no longer covers everything. The same problems show up almost every time:

• Numbering. Two slip books both start at 1. A customer arrives at one shop with a slip from the other, and nobody can find the order.
• Cash. Collections from two counters land in one drawer, or in two drawers nobody reconciles. A shortfall can't be traced to a shift or a person.
• Staff access. Everyone shares one login, so nobody can tell who gave a discount or cancelled an order, and every staff member can see every branch's takings.
• Prices and process drift. One branch charges ₹80 for a shirt and the other ₹90. One tags every garment, the other writes on the bag.
• Customers known at one shop only. A regular is treated as new at the other branch, and dues at one shop are invisible at the next.

None of these start as software problems. They are process problems that a second location exposes. Software helps by making the process visible and holding it in place once you have decided what it is.

Software copies whatever process you give it, good or bad. Before opening a new branch, write down how your best counter works and make it the standard:

• One rate card with normal and urgent rates, and one named person allowed to change it
• The intake steps: count pieces, check pockets, record condition, photograph expensive pieces, set the promised date
• A tag on every garment, not just the bag
• The hold reasons staff may use, and who calls the customer
• The handover rule: check the balance before the bag leaves the counter
• The discount rule: how much, and given by whom
• The closing routine: count the drawer against the day's collections

In KIWIKIT the rate card is set once for the business and every branch prices from it, so agreeing the rates is a one-time decision rather than a branch-by-branch argument.

The single biggest control in a multi-branch business is separate logins. When every action is tied to a person, mistakes can be traced and fixed instead of argued about.

KIWIKIT comes with Owner, Manager, Counter Staff, Cleaner/Presser and Accountant roles, and you can create your own. Each role has its own menus and permissions, and the workflow designer sets which actions it can take, which order stages it sees, whether it sees prices and how long it has to undo a mistake. Each user can also be limited to the branches they work in.

For example, a presser at the second branch might see only that branch's orders in cleaning, with prices hidden. The branch manager handles that branch's orders and payments. The owner sees every branch.

Plans include 4 users and 1 branch. Extra users cost ₹83 per user per month, and additional branches are quoted to fit your setup. Details are on the pricing page.

Each branch needs its own identity so customers and staff never confuse whose order is whose.

• Order numbers. Each branch numbers its orders separately within the financial year. An added branch carries its code in the number. For example, a branch with the code KTH issues numbers starting ORD-KTH, followed by the financial year and a running number, so a slip shows at a glance which branch took the order.
• Contact details. Each branch can have its own phone number and address, so a customer of the second shop isn't sent the first shop's address.
• WhatsApp sender. Each branch can connect its own WhatsApp number, so customers hear from the shop they visited and reply to the right counter.
• Orders and receipts stay with the branch that took them, which keeps each branch's work and cash apart.

Customers are shared across branches. A regular who usually visits one shop is found by mobile number at the other, with the same profile and credit terms, and is never added twice.

Shared customers need one rule about follow-up. Decide which branch chases a balance when a customer uses both shops, usually the branch that took the order, so the customer isn't reminded from two numbers about the same bill.

For the owner, the branch switcher means one login covers every branch. A practical habit is to switch into each branch at opening and closing and check its order list, overdue orders and receipts, exactly as you would at your own counter. The multi-branch software page shows how branches are set up.

• IP restriction per user, so a counter login works only from the shop's own internet connection. This works best when that connection has a fixed IP address.
• Active sessions with remote sign-out, for a lost phone or a staff member who has left.
• Login report with IP location, to see who signed in and from where.
• Audit trail, so cancellations and edits can be traced to a person.
• Emergency lock to shut staff out at once if something goes wrong.
• Sign in as another user to check exactly what a staff member can see.
• Daily encrypted backups at an hour you choose, stored in your own Google Drive or on the server.

These controls are described on the security features page.

1. Process written down and tested at the existing shop
2. Rate card reviewed, with one person responsible for changes
3. Branch created with its own code, phone number and address
4. WhatsApp sender connected for the branch and a test message sent
5. Staff users created, roles assigned and access limited to the new branch
6. IP restriction set for counter logins if the branch has a fixed internet address
7. Tag printer and receipt printer tested with a real tag and bill
8. Rack numbering planned so ready orders can be found quickly
9. Opening cash and closing routine agreed with the branch manager
10. Owner check-in times fixed for the first few weeks
11. User and branch count confirmed with us if you need more than 1 branch and 4 users

If you are planning one or more new branches, talk to us about a quote for your setup.