This is an illustrative example, not a customer story. The business below is invented to show how the workflow could run on Woxox. It does not describe a real company, and it contains no real results.
The illustrative business
Picture a regional distributor of electrical fittings in South India: a sales team of six, an accounts team of two, a warehouse, and around a few hundred trade customers (contractors, retailers and electricians' firms). Orders come by phone, WhatsApp, email and walk-ins. Most customers buy on credit.
Today the business runs on three things: a spreadsheet of price lists, an accounting package for invoices, and the sales team's phones.
Where it hurts (typical problems, not measured results)
- Quotes from memory. Salespeople quote from an old price list or from what they remember the customer paid last time.
- Customer details in two places. Sales has the customer's new GSTIN and site address in a chat; accounts still has the old ledger.
- Delivered quantity ≠ quoted quantity. Part deliveries are common, and the invoice sometimes follows the quote rather than the delivery.
- Collections by guesswork. Nobody on the sales team can see which invoices are overdue before calling a customer for the next order.
How the same week could run on Woxox
1. Enquiry. A contractor messages for 40 items for a new site. The salesperson opens the customer in Woxox CRM (or creates a lead) and logs the enquiry as a deal. The business's own rule: legal name, GSTIN, billing address and the site's delivery address are filled in on the record before a quote goes out.
2. Quote. The salesperson prepares the quote from the current price list, with the HSN code and GST rate on every line and the agreed discount written into the quote itself, not left in a chat message.
3. Acceptance. The customer confirms, and the accepted quote is saved against the deal. If the customer later changes the scope, a new version is saved, not a chat message.
4. GST invoice. The warehouse dispatches 32 of the 40 lines. Accounts raises the GST invoice in Woxox Finance for the 32 delivered lines, working from the accepted quote on the deal. Because sales and accounts share one database, the customer's name, GSTIN and addresses are not re-typed into a second ledger.
5. Collections. The invoice, its due date and any payment received sit on the same customer record. When the salesperson calls about the next order, they can see that the last invoice is overdue and raise it politely in the same call. Accounts reconciles the bank receipt against the invoice in Finance.
6. Review. At month end, the owner reviews deals in CRM and receivables in Finance. Both come from the same database, so the two sets of numbers describe the same customers.
What would change (in workflow terms)
| Before | After (illustrative) |
|---|---|
| Customer exists in a chat, a spreadsheet and a ledger | One customer record used by sales and accounts |
| Quote lines typed free-hand | Quote lines from the current price list with HSN and GST rate |
| Invoice re-typed from the quote | Invoice raised from the accepted quote on the deal, for the delivered quantity |
| Sales calls customers without seeing dues | Sales sees open invoices before the call |
| Month-end numbers compiled from three places | Deals and receivables from one database |
We are not claiming any time saved or revenue gained: those depend on each business and have to be measured on a real deployment.
Questions a real distributor should ask before switching
- Which system is the master for the customer's GSTIN and addresses today?
- How many price lists are in use, and who can change them?
- How are part deliveries invoiced now?
- Who chases overdue invoices, and what do they look at before calling?
- What would need to be migrated (customers, items, opening balances), and who would own the migration?
Implementation, migration and training are scoped per customer.
See it on your own workflows: book a Woxox demo and bring one recent quote and its invoice.
By WOXOX Editorial Team