Clothing store POS software in Nepal that shows which sizes sell

A customer brings a kurta to the counter in a size the rail was nearly out of. It scans, because the tag was printed in the shop: Code 128 labels come out of the app and off an ordinary printer, so stock that arrived unlabelled still scans. The line on the bill is the variant, that size in that colour, with its own price. The bill carries your PAN and 13% VAT on the taxable lines, and stock for that exact variant drops when the invoice is approved.

A second customer wants the same piece in a larger size. One look at the product shows whether it exists and where. If it is at the other outlet, a request moves it, the dispatch names the lot, and it shows as in transit until the receiving outlet confirms it.

Mid-morning the online orders are worked through. The connected store reads the same catalogue as the counter: the product page shows what is left in each size, and an order placed there arrives in Kuver Books to approve, not as an email to type in again. Nothing is sold twice, because stock only moves once, on approval.

In the afternoon the new season’s delivery is received against its purchase order, and the range is imported rather than typed. Then somebody pulls the two reports that decide the end-of-season sale. The ageing report and its chart show what has been sitting longest, and product profitability shows cost, sales, gross profit and margin per item. The markdown is set from those numbers, as a line or bill discount, and only by staff allowed to discount at all.

The day closes on the cash-flow ledger with collections recorded by method, since you can record payments across 10 Nepali methods: cash, Khalti, eSewa, bank transfer, ConnectIPS, Fonepay, IME Pay, PrabhuPay, card and mobile banking, and the lock goes on.