Understands
Built to read what happens in your systems and connected channels, and to show where each data set came from and when it was read.
Product
A business operating system,
from the inside.
How Wosool turns scattered work into operations that move forward: from the first event, to the card you sign, to the record that stays.
What Wosool does
Wosool turns scattered work into operations that move forward.
It captures what happens, gathers the context, opens the right operation, asks for your decision when one is needed, executes what's allowed, then keeps a record of everything that happened.
Runs
Opens the operation and moves it from the event to the next step, so the next step doesn't live in someone's head.
Governs
Knows what's allowed, on which data, and who owns the decision. When a piece of information, an identity, or a permission is missing, it declines the step.
Remembers
Every signed decision and its execution stay with the operation, with their owner, time and status, so you don't start from scratch tomorrow.
A real purchase
One real purchase, step by step.
What we proved, and what is built.
The steps of a purchase in Wosool, in order. The first six ran in production. The rest are built, and we say so plainly.
Steps 1 to 6Proven in production, 8 to 10 September 2026
- YouOpen a purchase request: the items, the quantities, and the suppliers to ask. Wosool opens the operation.
- YouRead the price request card, then sign it or decline it.
- WosoolEmails the request to each supplier in your company's name, with a private link.
- The supplierOpens the link and enters a price.
- WosoolGathers the prices and names the cheapest offer.
- WosoolStops if the chosen supplier isn't in your main system, and tells you what to add.
Steps 7 to 21Built, not yet proven in production
- WosoolOpens a purchase on its own when stock drops below its reorder point.
- YouSign the card that links an item to a supplier, one card for each.
- WosoolReuses a price that is still valid, instead of asking again.
- YouChoose between equal offers.
- WosoolCloses the request if 14 days pass with no price, and says so.
- YouGroup several requests under one, then release them together, one order for each supplier.
- The approverSigns the purchase order card.
- WosoolIssues the order in the system that owns your orders, and sends it to the supplier.
- The supplierConfirms the order.
- YouConfirm the payment, on a signed card with its document.
- Your teamMarks the goods as in transit.
- The warehouseReceives the goods, in full or in parts, on a signed card.
- FinanceMarks the order as paid in full.
- WosoolCloses the order, then the operation.
- WosoolReminds the person responsible when a step waits more than 30 days.
Six steps proven in production. Wherever a step needs a decision, the decision stays yours.
Watch it work
One purchase, from the first request to the final record.
The steps above, as one example purchase, hour by hour. Purchasing is our first proven operation, not the only thing Wosool does. Example: numbers are illustrative, and nothing leaves this page
Wosool In purchasing
I know. Your buyer asked for 48 cartons of engine oil 5L, from two suppliers. Wosool opened a purchase.
Request opened by the buyer, 09:40
Wosool
Gathered what the purchase needs, in one place.
The two suppliers you named48 cartons, the quantity you asked for46 in stock, read from your main systemWosool I need your decision.
Request for quoteEngine oil 5L, 48 cartonsIn purchasing- What will happen
- Two emails will go out in your company's name to the two suppliers you named
- On what
- 48 cartons, as the request asked
- Can it be undone?
- No. An email can't be recalled once it's sent
Signed by: youA third supplier quoted lower, and someone asked for a purchase order to them.
I can't.This supplier isn't in your main system. Add them there first, then try again.Declined. Nothing changed.Your main system
46cartons in stockRead from your main system at 14:05
Wosool never makes up a number. You decide which system owns each kind of data: your own system, or Wosool.
The manager Built, not yet proven in production
Approved the purchase order for 48 cartons from the second supplier. The approval carries their name and the time.
The purchase stays open until the need is met
- Payment confirmationBuilt, not yet proven in production
- In transitBuilt, not yet proven in production
- ReceivedBuilt, not yet proven in production
- CompleteBuilt, not yet proven in production
These steps are built. We haven't proven them in production yet.
How it works
From the event to done.
In Wosool, an operation doesn't start from a blank page and a search for data. It starts from something that actually happened in your business, and ends with a clear result and a record that stays.
- 1
Event
A purchase request from your team
- 2
Context
Suppliers, quantity, stock
- 3
Operation
With a status, and an owner for the decision
- 4
Decision
A card a person reads and signs
- 5
Execution
In the system that owns the change
- 6
Effect
What went out, what changed, and when
- 7
Memory
Stays with the operation for tomorrow
PeopleAgentsSystemsWork together inside the operation, not around it.
The card
Know what will happen before it happens.
When an operation is ready to act, the effect isn't buried in a vague message. It shows up on a card: what will happen, on what, who signs, and whether it can be undone.
- 1What will happenThe action itself, in your business's words.
- 2On whatThe numbers, and which system they were read from.
- 3Effect, and whether it can be undoneWhat goes out, and whether it can be pulled back.
- 4Who signsOne decision, in its owner's name and time.
Purchase order, example48 cartons from the second supplier
Built, not yet proven in production- What will happen
- A purchase order is issued in the system that owns your orders, and sent to the supplier
- On what
- Engine oil 5L, 410 per carton, offer valid for 30 days
- Effect
- A purchase order in your system, in the name of whoever approved it
- Can it be undone?
- A draft order can be withdrawn before it is sent
Approver: the manager
Business memory
Tomorrow, you don't start from scratch.
An operation doesn't disappear once it's done. You know what happened, why, who decided, what changed, and what is still open, without digging through email or calling whoever knew the story. What happened is added to it, never edited or deleted. This memory is built, and not yet proven in production.
The item
- Inventory movement
- What was bought and when
- Who supplies it
- Previous operations and their decisions
The supplier
- Prices it offered
- Purchase orders
- Its confirmations and delays
- What was said to it, and when
The operation
- What triggered it
- Its context
- What was proposed, and what was approved
- What was executed, and what resulted
Your systems
Keep your systems. Change how your business runs.
Your accounting, inventory and sales systems stay where they are. Wosool runs each operation on top of them, and sets where it reads data, where the decision is made, and where the change lands.
OdooDaftraAccountingInventoryEmailWhatsAppFiles
Wosool: the operating system
The operation: from event to effect
Built to run on top of Odoo and Daftra. We set up the connection with you before we start. Any other system, we check with you before we promise it.
Operations
One system. Many operations.
Purchasing is the first operation we proved on a real company, in production between 8 and 10 September 2026. Everything else is listed as it stands today. None of it is a promise.
Purchasing
From need to price received: the request, the price request, and the prices.
Inventory
From signal to restocking: an item dropping below its reorder point opens a purchase on its own.
Sales
From order to fulfillment.
Collections
From due date to collection.
Shipping
From shipment to arrival.
Supplier relations
From one-off orders to a supplier history you can use.