Uloborus runs buying, making and dispatch on one set of records

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.

1. BuyIndent to purchase order

   An indent becomes a quotation, then a purchase order, then the supplier bill that has to match it.

2. ReceiveGate entry to goods receipt

   What arrived short or damaged is recorded at the gate, not reconstructed at month end.

3. DecideInspection and hold

   Released, rejected, or used on concession. Held stock stays held until somebody decides.

4. StoreBin-level ledger

   Every movement has a document behind it, so the count and the paperwork cannot drift apart.

5. MakeWork order against a formula

   The bill of material, what was actually consumed, and what actually came back out.

6. ShipChallan, 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.

Nothing on the right is retyped into a separate accounts package.

Not eight products that sync overnight, but one record set seen from eight desks.

1. 01Buying

   Indents, quotations, purchase orders and the supplier bills against them.

2. 02Receiving

   Gate entry to goods receipt, with short and damaged recorded as it happened.

3. 03Quality

   Inspection plans, held stock, and a decision on every batch.

4. 04Stock

   A bin-level ledger where every movement has a document behind it.

5. 05Making

   Bills of material, work orders, what went in and what came back out.

6. 06Selling

   Customer orders, pricing, and the tax working out before anyone commits.

7. 07Dispatch

   Delivery challans and e-way bills, with the vehicle and the driver on them.

8. 08Invoicing

   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.

1. 01The 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.

2. 02Every 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.

3. 03It 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.

None of these is a module you buy separately or a setting somebody has to remember to switch on. They are how the tables are built.

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.

It runs in both directions, in seconds. That is what a certificate of analysis is written from.

A read-only Flutter companion where each screen answers one question somebody asks away from a desk.

1. ScreenToday

   What is waiting on somebody, and what the plant is worth.

2. ScreenAlerts

   What is about to stop the plant: out, low, and running out of time.

3. ScreenStock

   How much of this have we got, and where.

4. ScreenOrders

   What we owe customers, and what suppliers owe us.

5. ScreenMoney

   What they owe us and what we owe, by how late.

6. ScreenParties

   Who to ring, with a number that dials.

7. Kept offEvery 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.

8. Kept offSetup, 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.

9. Runs onAndroid today

   Android is built and verified. iOS is configured but not yet compiled, and we are not going to pretend otherwise.

This is where a manufacturing product page usually starts lying, so here is what is in the product and what is not.

1. ShippedEvery 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.

2. ShippedOne 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.

3. Roadmap, not shippedAnomaly 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.

4. DirectionThe 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.

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.

• Compliance paperwork should fall out of the transaction, not be typed againThe invoice, the e-way bill and the goods that actually left the gate are one event recorded three times. That arithmetic is what month end is really paying for.
• A recall is a query, and you find out in an hour whether you can run itA complaint arrives with a batch code printed on it. Whether you can trace that code in an hour was settled years earlier, by how you record consumption.
• The shop floor will not fill in a form it gets nothing back fromCapture at the machine fails for physical and social reasons long before technical ones. The designs that survive ask for less and give the operator something back.