Uloborus runs buying, making and dispatch on one set of records
Woodfrog's manufacturing system for Indian process plants. Buying, receiving, quality, stock, making, selling, dispatch and invoicing sit on one thread, with the GST paperwork that travels with it. Built with a working factory rather than for a demo, alongside Rajaram Consumer Care in Sangli.
The shape of the product in four numbers
What Uloborus covers, what it puts on a phone, who it is built for, and how long it takes to start.
From the indent to the invoice, one thread
Every step writes to the same records, so the next step already knows what happened.
- Buy
Indent to purchase order
An indent becomes a quotation, then a purchase order, then the supplier bill that has to match it.
- Receive
Gate entry to goods receipt
What arrived short or damaged is recorded at the gate, not reconstructed at month end.
- Decide
Inspection and hold
Released, rejected, or used on concession. Held stock stays held until somebody decides.
- Store
Bin-level ledger
Every movement has a document behind it, so the count and the paperwork cannot drift apart.
- Make
Work order against a formula
The bill of material, what was actually consumed, and what actually came back out.
- Ship
Challan, e-way bill, invoice
The vehicle and the driver on the document, and an invoice that reconciles against its challan.
The paperwork comes out of the step that produced it
Each document that leaves the factory is written from the same records the plant runs on.
- ReceivingGoods receipt against the purchase order
- QualityCertificate of analysis
- DispatchDelivery challan and e-way bill
- InvoicingGST invoice and credit note
Eight modules, one set of records
Not eight products that sync overnight, but one record set seen from eight desks.
Buying
Indents, quotations, purchase orders and the supplier bills against them.
Receiving
Gate entry to goods receipt, with short and damaged recorded as it happened.
Quality
Inspection plans, held stock, and a decision on every batch.
Stock
A bin-level ledger where every movement has a document behind it.
Making
Bills of material, work orders, what went in and what came back out.
Selling
Customer orders, pricing, and the tax working out before anyone commits.
Dispatch
Delivery challans and e-way bills, with the vehicle and the driver on them.
Invoicing
GST invoices that reconcile, credit notes that reference the original, payments matched against them.
What makes it hold together
Three properties that are structural rather than optional.
The paperwork is the product
Delivery challans, e-way bills, GST invoices and certificates of analysis come out of the same records the plant runs on, rather than being retyped into a separate accounts package.
Every row says who and when
An author and a timestamp on every record, because the table cannot be written without them. Every document that changes state keeps the before and the after.
It refuses the impossible
You cannot dispatch against an unconfirmed order, consume a batch quality is holding, or invoice a challan twice. The rules sit in the database, not in a training session.
Where Uloborus is the wrong answer
It suits batch plants of roughly twenty to three hundred people in cosmeceuticals, food, speciality chemicals, pharma ancillaries and their contract manufacturers, so here is where it does not belong.
Discrete assembly
Deep multi-level bills of material with routings are not what this is. Batches and formulas run all the way into the data model, and configuration cannot talk you out of that.
A plant with no quality step
Half the value is holding material until somebody decides and signs their name to it. If nothing is ever held, inspected or released, most of it is not there for you.
Anyone who needs full financial accounting
Payroll, fixed assets and full books are not in it. It produces GST invoices, it is not your books, and it sits alongside whatever your accountant already uses.
If you are not sure which side you are on
Talk to us before you spend a month on the software. Week one is a fixed-fee audit, and we would rather talk you out of it there.
The mobile app, and what was kept off it
A read-only Flutter companion where each screen answers one question somebody asks away from a desk.
Today
What is waiting on somebody, and what the plant is worth.
Alerts
What is about to stop the plant: out, low, and running out of time.
Stock
How much of this have we got, and where.
Orders
What we owe customers, and what suppliers owe us.
Money
What they owe us and what we owe, by how late.
Parties
Who to ring, with a number that dials.
Every write
The app cannot change anything. Read-only is enforced in code: the API client hard-codes GET and a test asserts it stays that way.
Setup, bins, tax rates, people
Master data, bin management, tax rates and people administration are absent by choice. Nobody sets a plant up on a four-inch screen.
Android today
Android is built and verified. iOS is configured but not yet compiled, and we are not going to pretend otherwise.
Built for the AI era, and what that does and does not mean
This is where a manufacturing product page usually starts lying, so here is what is in the product and what is not.
- Shipped
Every list view is analytical
The shared table carries a stats strip, boolean search and a breakdown panel, so counts, totals and breakdowns sit on every list. Real analytics on real records, not a separate module.
- Shipped
One clean governed dataset
One set of operational records, an author and a timestamp on every row, a before and after on every state change. That is the precondition for anything agentic later.
- Roadmap, not shipped
Anomaly and margin-leak detection
Which products, customers or lines quietly cost more than quoted. This is on the roadmap and is not in the product. Nothing in Uloborus forecasts, flags or explains anything on its own today.
- Direction
The dataset agents get built on
There is no assistant, copilot or agent in Uloborus. Agentic work comes through Antvia and through Woodfrog's AI practice, on a dataset that is clean because of how Uloborus records it.
Trace a finished batch back to the order that started it
Each record points at the one behind it, so the chain is a link you follow rather than a report you run.
- Finished batchWork order that made it
- Work orderMaterial it consumed
- Material issuedReceipt that brought it in
- Goods receiptPurchase order behind it
Questions people ask before they start
Is this an ERP?
It covers buying, receiving, quality, stock, making, selling, dispatch and invoicing as one record set, and produces the GST paperwork that leaves the factory. It does not do payroll, fixed assets or full books. If ERP means your books, the answer is no.
Does it ship an AI assistant or copilot?
No. Every list view carries a stats strip, boolean search and a breakdown panel, which is real analytics on real records. Anomaly and margin-leak detection is on the roadmap. There is no agent, assistant or forecast in it today.
Who built it, and against what?
Woodfrog built it with Rajaram Consumer Care, a contract manufacturer of cosmeceutical topicals in Islampur MIDC, Sangli. Every module was built against how they actually work, then argued about, then changed. Its own site calls it the intelligent web of manufacturing.
Can I run the plant from my phone?
You can read it from your phone. The Android app is built and verified, iOS is configured but not yet compiled, and the app cannot write anything at all. Approvals, documents and setup stay on a real screen.
How do we start, and what does it cost?
A workspace on uloborus.com takes about a minute and no card, so you can put a real purchase order through it first. If Woodfrog runs the move, week one is a fixed-fee audit with two calls and a one-pager you keep either way. Pricing is not published here.
If you are a batch plant that has outgrown the spreadsheet
Uloborus is at uloborus.com and you can start a workspace without talking to us. If you would rather plan the move than improvise it, book a call and we will tell you honestly whether it fits. If it does not, we will say so, the same way we said so halfway up this page.