Everything it does

Grouped by where in the shop it happens. Nothing here is bought separately.

At the counter

The Windows application the cashier uses all day.

One order, several garments: A kameez, a shalwar and a waistcoat on one ticket, each with its own status, karigar and shelf.
Measurement profiles: Save an order as a profile — measurements and style choices together. Pick it next time and the order fills itself in. On menswear the profile picker can open on its own, set per brand or per branch.
Re-measurement history: A new measurement is appended, never written over the old one. A wrong entry is voided and stays visible as a void.
Rush pricing and hand-work: Normal or rush price on each garment. Special hand-work is agreed and priced at the counter.
Park an order: Put a half-finished order aside when the queue builds, and pick it up again without retyping it.

Who has the work, and what it is worth to them.

Give work out by name: Each garment goes to a karigar by name. The counter can take it back or hand it to somebody else.
A printed ticket per garment: Laser sheet and a label. On menswear the measurements print large enough to work from.
Numbered shelves: Finished work goes to a shelf addressed by position, so the counter can find it without walking the workshop.
Order tracking for your customers: The QR on every receipt opens the customer’s order on their phone, with no app and no sign-in, so they can see where it is without calling the shop.
The karigar’s own app: A browser app where each karigar sees their own work, their history and their earnings. Shown as “Designers” in the applications.
Commission or salary: Chosen per person when the account is made. Unpaid earnings are earned minus paid out, calculated rather than entered.

What came in, what is still to pay, and a day that reconciles.

Part payments and instalments: All of it, some of it now, or a few payments over time. Cash, card or bank transfer on each.
Refunds are recorded: A refund is entered as a refund against the original. Nothing is edited away, so the history still explains itself.
One day-closing per branch: Counted by method, once a day, per branch — not per shift.
Karigar payouts: Paid from the counter, and deliberately kept out of the day’s cash count so the reconciliation still works.
The order number as a barcode: Printed on the receipt so the counter can pull an order up quickly.

The browser dashboard, for you and your managers.

Collections by period: Total taken this period against the period before, branch by branch.
Day-closings, reviewed centrally: Every branch’s close, in one place, without ringing anybody.
Prices per branch: A branch can price its own work, and you decide which of them may.
Roles and permissions: Adjustable to how your shop runs — a branch manager is not a cashier, and neither is head office.
Staff and counters: Add people, give each their own sign-in, and pair a counter to a branch.

Worth knowing before you ask, rather than after. None of these is planned for Pakistan today.

No stock or inventory. It sells work and cloth from the counter; it does not tell you what is left in the store room.
No tax filing and no FBR integration. These are workshop job tickets, not fiscal invoices.
No online payment collection — no JazzCash, no EasyPaisa, no card gateway. Money is recorded at the counter, not processed.
No barcode scanning. The order number prints as a barcode; nothing in the system reads one.
No thermal or roll printers. Laser sheet plus a label printer, on ordinary Windows drivers.
No phone app for the shop. The counter is a Windows application; the dashboard and the karigar app run in a browser.