Occuris Command
Six agents watching your supply chain so you don’t have to.
Procurement, inventory, supplier risk, compliance, forecasting and reporting, reasoning across your data in real time, and flagging risk before it becomes a delay.
- Flags the late shipment before the line stops.
- Finds two alternate suppliers when a price jumps.
- Raises the reorder before the shelf is empty.
Where the news starts
- What
- Dispatch, drivers, port agents and suppliers post updates in groups, in Roman Urdu and English.
- When
- All day, the moment something happens.
- How
- Occuralog reads the group export as it is. Nobody changes how they type.
- Why
- It is where the first sign of a delay shows up, hours before anyone else knows.
What the office believes
Spreadsheets
- What
- Stock sheets, price lists and order trackers kept by hand.
- When
- Whenever someone remembers to update them.
- How
- Read next to the messages, so a number that has gone stale gets caught.
- Why
- The sheet says 230 cartons. The store says 30.
Where commitments hide
- What
- Supplier threads: revised lead times, confirmations, price changes.
- When
- In long threads nobody re-reads.
- How
- Connected for each client, on your own servers.
- Why
- The new lead time is in reply number four of a thread called Re: Re: Re:.
The system of record
ERP
- What
- Orders, stock and bills of materials in SAP, Tally or your own system.
- When
- On its own schedule, often a day behind.
- How
- Read-only exports, connected for each client. Nothing is written back without a person.
- Why
- It is the truth on paper. The messages say what is true today.
What needs you now
Alerts
- What
- A customs hold, a stock-out coming, a price that jumped.
- When
- As soon as an agent sees it.
- How
- Each alert carries the message that caused it, so you can check it in a second.
- Why
- You act days early instead of after the line stops.
Your yes, then it happens
Approvals
- What
- Reorders, supplier replies and changes drafted and waiting for a person.
- When
- Whenever a decision needs someone in charge.
- How
- Nothing is sent without your approval, by tap or by voice.
- Why
- You stay in charge of every action Occuris takes.
The day, written down
Reports
- What
- The day’s records and decisions in one place.
- When
- Every evening, or whenever you ask.
- How
- Built from the log, with every line pointing back to its message.
- Why
- An audit trail nobody had to write.
The core, on your servers
Your data
- What
- One clean record of everything your WhatsApp groups, sheets, email and ERP say.
- When
- Updated the moment Occuralog turns a message, sheet or email into a record.
- How
- Kept on your own servers, each record linked back to the message it came from.
- Why
- All six agents reason from the same facts, and none of it leaves your building.
Agent: buying
Procurement
- What
- Watches prices, lead times and every open purchase order.
- When
- Whenever a quote, a price list or a PO changes.
- How
- Compares the new number with your history and your other suppliers, then drafts the approval.
- Why
- A price jump or a slipped lead time is caught while you can still switch.
Agent: stock
Inventory
- What
- Keeps one true stock count across warehouses and sheets.
- When
- Whenever stock moves, a sheet is edited or a delivery is logged.
- How
- Reconciles the numbers, trusts the newest source, and works out when each item runs out.
- Why
- The reorder goes out before the shelf is empty, not after.
Agent: suppliers
Supplier risk
- What
- Scores every supplier on price, delays and how often they deliver on time.
- When
- All the time, and the moment a supplier misses a date or raises a price.
- How
- Keeps each supplier’s record and finds alternates within your price range.
- Why
- A second supplier is lined up before the first one fails you.
Agent: paperwork
Compliance
- What
- Keeps claims, certificates and customs papers in order.
- When
- When goods arrive damaged, sit at customs, or a document falls due.
- How
- Logs the evidence, starts the claim and counts down the deadline.
- Why
- Claim windows and filing dates stop slipping past.
Agent: demand
Forecasting
- What
- Predicts demand and stock levels weeks ahead.
- When
- Every night, and again when orders spike.
- How
- Learns from your past orders, seasons and supplier lead times.
- Why
- You buy for the month ahead, not for last month.
Agent: the daily report
Reporting
- What
- Writes the report of what happened today and what was decided.
- When
- At the end of each day, or whenever you ask.
- How
- Pulls every record and decision from the log onto one page.
- Why
- Everyone reads the same numbers, and every decision has a trail.
- Supplier risk: copper wire price up 12% at Lahore supplier. 2 alternates found within 8%.
- Inventory: generator spare arrives in 10 days. Current unit end-of-life in 14. Margin: 4 days.
- Compliance: 2 damaged pallets logged with photos. Claim window closes in 48 hours.
What it does
-
Six agents on your data
Procurement, inventory, supplier risk, compliance, forecasting and reporting, each watching its part of the chain.
-
Tied to your bill of materials
Stock, lead times and end-of-life parts are checked against your BOM, so a risk is tied to what it would stop.
-
Answers you can check
Ask in plain language. Every answer names the model that produced it, and a fallback answer says so.
-
Your model, your servers
A local model by default, or Claude when you choose. Nothing has to leave the building.
How it works
- 01 Connect: ERP exports, spreadsheets and Occuralog records
- 02 Watch: checks for lifecycle, risk and scenarios
- 03 Decide: alerts, approvals and reports, with the source behind each
Where it stands
Runs today
- The Command Deck and its backend, running locally
- Multi-agent chat over a local model, Claude or Groq
- BOM storage and an evaluation harness
Next
- Live news, weather and supplier feeds
- Storage moves to Postgres
- Alerts streamed to each company separately
Piloted for six months with NKE Technica, an electronics import and export business.
Try it on your own data
Engagements start with a two-week scoped pilot, on your servers, with you owning the code.