A khata app for udhar that spikes at weddings and festivals
Cloth and garment credit is seasonal — quiet for weeks, then a wedding order or a festival rush puts a dozen large entries on the book at once.
A garment shop's credit does not arrive evenly through the year. It clusters around weddings, Diwali and back-to-school season, when customers buy more than they can pay for immediately and settle over the following weeks. The khata needs to handle that burst without becoming unreadable.
Wedding and festival orders as one clear entry
A single wedding order can span blouses, sarees and accessories across several family members. Record it as one credit entry with the full amount and a note describing the order, so the family's balance is one clear figure rather than a scattered set of small purchases.
Part payments as the order gets settled
Customers rarely clear a large festival order in one payment. Record each part payment as it arrives — after the function, after a salary — and the remaining balance stays accurate without you tracking it by memory.
Notes for measurements and order details
Use the notes field to keep a measurement, a fabric choice or an alteration date alongside the entry, so the ledger doubles as an order record for the busiest weeks of the year.
See who is still outstanding after the season ends
Once a festival rush settles down, the due-date and overdue view shows exactly who has not cleared their balance, instead of you trying to remember who bought what in a week of constant sales.
Common questions
Can I record a big wedding order as one entry?
Yes, record the full order value as a single credit entry and use the notes field for the order details.
Can customers pay in parts over several weeks?
Yes, each part payment is its own entry with its own date, and the balance updates automatically after every one.
Does the khata reset each festival season?
No, balances carry forward continuously. You see exactly who is still outstanding from a previous season alongside anything new.