Trading
Textile trader
From WhatsApp orders to GST invoicing and outstanding, in one flow.
The challenge.
The textile trader ran on WhatsApp messages and phone calls. A buyer would send a photo of the fabric or ask for a rate, someone would reply, and the order sat in that chat thread or on a paper pad by the phone. Orders came in through more than one person, at all hours. The godown, the billing desk, and the person who took the order each kept their own copy. Nothing tied the first enquiry to what got packed and sent.
The same order got written three times: once when the buyer asked, again when it went to the godown for packing, and again when the bill was cut. Each time it was copied, a length or a rate or a party name could change, and often did, so dispatches went out short or wrong and the buyer called back upset. Party credit was the hardest thing to keep track of. Nobody could say what a party owed until the books were tallied at month-end, so the owner kept selling on credit to parties who were already behind. Arguments over ’I already paid that’ came up because there was no live record either side could point to.
What we built.
- Orders captured once, from enquiry to dispatch
- GST invoicing straight from the order
- Outstanding by party, updated live
- No more writing the same order three times
The result.
Now an order is entered once, from the first WhatsApp message. The person taking it puts in the party, the fabric, the length, and the rate, and that same order carries straight through to the godown for dispatch and to billing. The GST invoice is made from the order itself, so what was ordered, what was packed, and what was billed all line up. Nobody rewrites the order to move it to the next step. The godown works from the same order the billing desk is looking at.
Outstanding by party is live. On any day the owner can open it and see what each party owes, updated as invoices go out and payments come in, instead of a guess that only settles at month-end. That changes how credit gets given: the owner can hold a dispatch for a party who is already stretched, or send freely to one who has paid up. The team stops copying the same details three times and stops chasing which version was right. Fewer wrong dispatches mean fewer angry calls, and the number the owner quotes a party is the same number the party sees.
- 10+ years
- building custom ERPs for businesses
- 50+ businesses
- run their operations on i1ERP
- 100% custom
- no two i1ERP systems are the same
When we changed how we bill, the change was done in days. With our old software it would have been a project.