Zorvia Weaves
The full piece-level operating system for a Banarasi textile workshop — from a bolt cut into pieces, through every vendor stage, to a finished tagged product and sale.
Live — in daily use at a Banarasi textile workshop01 — The Problem
A bolt of fabric is cut into pieces of variable length. Finished products like suits, sharara, and gharara are made of 2–3 separate pieces that are dyed, polished, and finished independently before being reunited into one final product. Historically this was tracked by memory and paper — pieces left too long at a vendor, weaver dues kept in a notebook, sales totals reconstructed after the fact.
- Where is this piece right now?
- How long has it been there?
- If a final product is missing a piece, which piece, and where was it last seen?
- What do I owe each weaver?
- What's actually selling?
02 — The System
Physical Tracking
- Taffeta QR tags survive dye/polish/chemical processes
- Every piece scanned at every stage
- Auto-minted dispatch/receiving challans
- Set-completeness check catches missing pieces before combination
Weaver & Vendor Accounting
- Weaver raw-material intake and invoices
- FIFO-allocated payment ledger
- Vendor rate cards and bills rolled up from scan-generated challans
Finished Goods & Sales
- Binding a product QR to a completed set
- Sale recording by channel — retail, wholesale, online
- Returns, dead-stock detection, and revenue reporting
03 — Who Uses It
Scanner
Runs the physical scan loop only — receive, dispatch, and set-completeness checks at each vendor stage.
Tracker
Reads everything the system holds — records intake and sales, resolves piece and set questions.
Admin
Everything the Tracker can do, plus money — ledgers, vendor bills, and system configuration.
“Built first for a Banarasi textile workshop, to solve a problem paper and memory never could.”
Have a similar problem?
Start with a Coordination Audit