WeaveDesk
Custom textile and fabric trading software
Greige to dispatch, with job work and broker accounts in order.
For traders, processors and wholesalers dealing in grey and finished fabric, where stock is counted in thaans and metres at the same time, goods sit with a processor for weeks, and much of the business runs through brokers on commission. Built around the trade's own units and terms rather than a generic inventory model.
Screens
What it looks like
4 screens from the working demo — the same data you will see if you open it.
The problem
Why this gets built
Fabric leaves for dyeing, comes back short, goes out for printing, and somewhere in there a broker commission and a party outstanding are agreed verbally. The register catches up weeks later, by which point nobody agrees on the numbers.
Who it is for
Fit
Fabric traders, processors and wholesalers in Surat and other textile markets.
Capabilities
What the system does.
Greige & finished stock
Quality and design-wise stock in metres and thaan, with what is in-house versus out on job work always separated.
Job-work challans
Issue and receipt against dyeing, printing and embroidery units, with shortage recorded at receipt.
Sales orders
Party orders against quality and design with rate, delivery and pending quantity visible.
Brokers & commission
Commission percentages applied per deal and accrued per broker, not reconstructed later.
Party ledger & ageing
Outstanding by party with ageing buckets, so follow-up is prioritised by exposure.
Dispatch
Lorry receipt details against dispatch, closing the loop between stock leaving and the invoice raised.
See it running
WeaveDesk is a clickable demo — open the modules, browse the tables, see how the screens fit together.
Buying decision
Why off-the-shelf falls short here.
Standard inventory software assumes an item has one unit of measure and one location. Fabric has neither. A lot is bought in metres, stored as numbered thaans of unequal length, sent out for processing where it loses and gains weight, and sold in cut pieces. Forcing that into a single-unit stock record means the quantity on screen is never the quantity in the godown.
The second mismatch is ownership. Goods at a processor are still yours but are not in your godown; goods sold through a broker are gone but the commission is not yet settled; goods on approval may come back. A system with one stock figure and one ledger cannot represent any of that, so traders keep the real position in a separate book - which is the position that actually gets used.
A custom build models the trade as it is: dual units carried together, lot and thaan identity preserved end to end, processing treated as a location rather than a sale, and broker commission accrued against the deal that earned it.
Comparison
Packaged product vs a custom build.
The differences that decide it, for this sector specifically.
| Aspect | Packaged product | Custom build |
|---|---|---|
| Units | One unit per item | Metres and thaans carried together, with per-thaan lengths, so both figures stay true |
| Lot identity | Lost at the first transaction | Lot and thaan number preserved from purchase through processing to the cut piece sold |
| Processing | Modelled as a sale and a repurchase | A stock location - goods stay yours, with shrinkage and process loss recorded against the lot |
| Brokers | Not modelled; handled outside the system | Commission accrued per deal, per broker, with a settlement ledger of its own |
| Quality | A single grade field | Grade, shade and lot matching, so a buyer asking for the same shade can be answered |
| Party ledger | Standard receivable ageing | Ageing alongside bill discounting, part payments and the goods still lying with that party |
Integrations
What it connects to.
A system that cannot reach the tools already in use becomes another island. These are the connections this sector normally needs.
Accounting
Sales, purchase and commission entries into Tally or Zoho Books, with GST already apportioned at line level.
E-invoice and e-way bill
IRN generation and e-way bills raised from the invoice rather than re-keyed into a portal.
Lot scanning
Barcode or QR on the thaan so godown movement is scanned, not written.
Processors
A limited external view so the processing house can update status without access to your ledgers.
Messaging
Rate lists and stock availability pushed to the buyer groups on WhatsApp.
How it runs
From first conversation to cutover.
Indicative for a build of this shape. The parallel run is not optional — nothing is retired until the numbers agree.
- 1-2 weeks
Discovery
We take your actual item master, a month of real purchase and sale bills, and the broker terms you work on.
- 4-7 weeks
Core build
Dual-unit stock, lot tracking and party ledgers first - the parts everything else depends on.
- 2-4 weeks
Parallel run
You run it beside the existing books for a full cycle, including one processing round trip, until the closing stock matches.
- 1-2 weeks
Cutover
Opening balances locked, brokers and processors given their views, old books retired.
After rollout
What changes day to day.
- The stock figure on screen is the stock in the godown, because metres and thaans are reconciled rather than converted.
- Goods lying at a processor stop disappearing from the position - they are visible as yours, at a known location, with an expected return.
- Broker commission is settled from the deals that earned it instead of a running verbal total.
- Shade and lot matching becomes a query rather than a walk through the godown.
Described qualitatively on purpose. We do not publish percentage improvements we cannot attribute to a named client with their agreement.
Questions
Common questions.
Does it track stock sent for dyeing or printing?
Yes. Job-work challans record what left, what came back and any shortage at receipt, with in-house and out-on-job-work stock kept separate.
Can it calculate broker commission?
Yes. Commission percentages are applied per deal and accrued per broker, rather than reconstructed from memory later.
How is party outstanding tracked?
Outstanding is maintained per party with ageing buckets, so follow-up can be prioritised by exposure rather than by whoever called last.