Rice arrives as a sack and leaves by the kilo.

Who this is for

You run a grocery, a kirana, or a provision shop. Prices change often, some goods are loose, and the closing balance of a regular customer still lives in a notebook.

A mart with several cashiers is a different page. This one is the grocery counter: units, weight, perishables, and a fast sale.

What I build

• A purchase unit and a sale unit on the same product, with the conversion
• A price per kilo and a weight on the line, typed or read from a scale barcode we have tested
• Packed bags with their own barcode and price, separate from the loose price
• Expiry or a received date, a near-expiry list, and a write-off that is not pretending to be a sale
• A customer balance: the goods leave now, the payment reduces the balance later
• Search, scan, and a held basket so the queue keeps moving

I test a weighing scale with your counter before relying on it. An untested scale means the cashier types the weight. Card numbers stay on your payment device.

What you keep

• Your prices, your suppliers, and your customer balances
• Receipts that still show the weight and the rate
• The code

How an engagement starts

1. You pick three products: one loose, one packed, one that expires.
2. I trace how each is bought, sold, and written off.
3. We continue at $35 an hour, or I send a fixed quote once those paths are specific.
4. The counter sells on it. Old receipts keep the price from the day they were made.

I will not claim a scale, scanner, or printer works until it has been tried on your counter.

Read these before the call

• Weight, packs, and food that expires
• What a shop POS has to do
• If the shop is a mart with several cashiers
• Pricing — $35 an hour, or a custom quote

Questions