Baki becomes a problem when the history is unclear

Offering credit to trusted customers can be part of normal retail. The risk starts when the shop cannot answer four simple questions quickly: who owes money, how much, from which sale, and what has already been paid?

A paper ledger can work at low volume, but it becomes harder to reconcile when multiple staff members collect payments or when a customer pays part of the balance.

Use one customer record

Avoid creating a new note every time the customer buys on due. Keep the customer identity, sales history, due balance and payment history connected. That gives staff one place to check before accepting another due sale.

Record every payment, not only the new balance

If a customer owed ৳5,000 and pays ৳2,000, keeping only “new balance: ৳3,000” removes useful history. Record the payment event as well. When questions arise later, you can see what changed and when.

Make collection polite and factual

A good Baki workflow should reduce arguments, not create them. Use the system to confirm the amount and sale history before contacting the customer. Keep the conversation simple: outstanding balance, last payment and the relevant invoice or date.

Review overdue balances regularly

Do not wait until month-end to discover a large due balance. Add a short routine to your daily or weekly management review:

• customers with outstanding balances
• recent due sales
• payments received
• unusually old balances
• customers approaching an internal credit limit

What to check in a POS demo

Ask the vendor to show you a complete due workflow—not only a “Due” field on the sale screen. Create a due sale, make a partial payment, review the customer history and confirm the new balance.

DokanMate keeps customer records, dues, payment history and sales context connected so the owner or authorized staff can follow the history instead of relying on a separate notebook.