·
Digital Engineering
Manufacturing, Indian process plantsProduct story, no client result yetOne set of records, from indent to invoice.
In Uloborus you cannot invoice a challan twice, consume a batch that quality is holding, or dispatch against an unconfirmed order. The rules sit in the database, not in a training session.
EightModules on one set of records
SixPhone screens, read only
20 to 300People in the plants it suits (roughly)
About a minuteTo a workspace, no card
Whowoodfrog's own product, Uloborus, built with design partner Rajaram Consumer Care, a contract manufacturer in Islampur MIDC, Sangli. No result is claimed for Rajaram.
Read this asA product story and a playbook for a plant like yours. It is not a client result.
BuiltEight modules on one set of records, with the GST paperwork
Before and after
Eight desks, one record.
Before
- Each desk keeps its own copy, synced overnight
- Short and damaged receipts rebuilt at month end
- Challan, e-way bill and GST invoice retyped into a separate accounts package
- Rules live in memory, so a held batch can still be used
After
- One record set seen from eight desks
- Short and damaged goods recorded at the gate
- The paperwork is written from the step that produced it
- Rules sit in the database and refuse the impossible
The problem
When every desk keeps its own records, the paperwork gets retyped.
Picture a batch plant that has outgrown the spreadsheet. What arrived short or damaged is rebuilt at month end instead of recorded at the gate. The challan, the e-way bill and the GST invoice are typed again into a separate accounts package. And getting from a finished batch back to the purchase order behind it means someone runs a report.
What was broken
- Eight products that sync overnight, so the next step does not know what just happened.
- Month-end reconstruction of short and damaged receipts.
- Documents typed again into a separate accounts package.
- Rules held by memory, so nothing stops a held batch being used or a challan being invoiced twice.
- A trace from batch to order that needs a report.
You might be here if
- Your challans, e-way bills and GST invoices are retyped.
- What arrives short or damaged is rebuilt at month end.
- Nothing stops a held batch being used.
- Tracing a batch to its purchase order means running a report.
The approach
The paperwork is the product.
We stopped treating paperwork as something typed up after the work. The goods receipt, certificate of analysis, challan, e-way bill and GST invoice are written from the same records the plant runs on, by the step that produced them. Three rules are built into the tables themselves: you cannot invoice a challan twice, consume a batch that quality is holding, or dispatch against an unconfirmed order.
The plant's steps
Buy and receiveGoods receipt against the order
Check and storeQuality and stock
Make, sell, dispatchWork orders, sales, challans
Uloborus, built by woodfrog
One record setEight modules on it
Three refusalsHeld in the database
Trace in both directionsBatch to order, in seconds
Paperwork written for you
Goods receipt
Certificate of analysis
Challan and e-way bill
GST invoice
Nothing retyped
Deliberately not builtFull books, payroll, any AI agent or forecast, or any write from the phone
The solution
Eight modules, six phone screens, rules in the database.
What was built
- Eight modules on one record set: buying, receiving, quality, stock, making, selling, dispatch and invoicing.
- GST paperwork from the step that produced it, with invoices reconciled against their challan.
- An author and a timestamp on every row, and a before and after on every change.
- A trace you follow: finished batch, to work order, to material used, to the receipt, to the purchase order.
- Analytics on every list: a stats strip, search and a breakdown panel.
- A read-only phone app with six screens: Today, Alerts, Stock, Orders, Money and Parties. It can only read, never write.
Where it is the wrong answer: assembly plants with deep bills of material and routings, plants with no quality step, and anyone who needs full financial accounting. “Week one is a fixed-fee audit, and we would rather talk you out of it there.”
The impact
What we would measure for a plant like yours.
Where the plant's records livePlaces buying, making and dispatch were kept, before and after
Before
3 places
After
1 record set
0123
Eight steps on one line, one set of recordsEach document is written by the step that produced it. Nothing is retyped.
Schematic- 1Buy
- 2ReceiveGoods receipt
- 3QualityCertificate of analysis
- 4Stock
- 5Make
- 6Sell
- 7DispatchChallan and e-way bill
- 8InvoiceGST invoice
1Buy
2ReceiveGoods receipt
3QualityCertificate of analysis
4Stock
5Make
6Sell
7DispatchChallan and e-way bill
8InvoiceGST invoice
← TraceFinished batch → work order → material used → receipt → purchase order. In seconds, both directions.
Three things the system refuses
Invoice a challan twice
Use a batch quality is holding
Dispatch an unconfirmed order
What we would measure at the Week 1 auditNo client values yet
Documents retyped each monthTarget: none
Time to trace a batch to its orderTarget: seconds
Short and damaged receiptsCaught at the gate, not at month end
Bin count against paperworkCannot drift apart
Invoices against their challanAlways agree
See if it fits your plant.A short call, or record a message. A person replies within one business day.
