In a lot of shops, half the relationships run on trust. A customer takes goods now and pays later, or pays part now and the rest on Friday. QuickPOS treats that as a first-class flow, not an afterthought — with a ledger that survives being offline.
A customer created offline gets a stable local identity so it never duplicates when it finally syncs — and any credit sale tied to that customer is automatically remapped to the server record once it exists. This is one of the quiet pieces of engineering that keeps the books straight when the network is unreliable.
See who owes you across 7, 14, 30, 60 and 90-day buckets so nothing slips.
Every payment against a balance is recorded and visible on the customer.
Sell on credit or take part-payment directly from the sell screen.
Purchase history per customer is the base for loyalty and targeting.
Yes. At the till you can complete a sale as credit or take a partial payment; the remaining balance is tracked against the customer for later repayment.
They queue like any sale. Offline-created customers keep a stable identity and their credit sales remap to the server customer record on sync, so balances stay correct.
Yes. The debtor aging report buckets outstanding balances by age (7/14/30/60/90 days) so you can chase the oldest debts first.