The order is fine. The forty emails about it are not.

An order lives in a system that knows quantities and prices, and nowhere near the correspondence that decides whether it ships: the supplier confirming a date, the customer changing an address, the claim about the damaged pallet. OVIOO keeps that correspondence on the order, so the exception is as findable as the transaction.

OVIOO
Compose
#742615Halden & CoActive12 emails4 tasks6 documents
Emails
  • Adrián Soler09:41
    Delivery confirmation
  • Castellane SA08:52
    Proforma — Halden rollout
  • Ingrid HalvorsenYesterday
    Requirements — 2 changes
  • Castellane SAMon
    Delivery schedule received
Open thread →
Tasks
  • Confirm delivery windowDMToday
  • Resend requirements list to VantageDMToday
  • Signed contract from HaldenDMWaiting
  • Final payment reminderCOFri
Documents
Requirements_FINAL.xlsx
Sent to Vantage · 18 Aug 2026
Proforma_Castellane.pdf
Received 21 Aug 2026
Handover_742615.pdf
Created from template · 19 Aug 2026
Contacts
  • IHIngrid HalvorsenProject lead
  • ASAdrián SolerSupplier · delivery
  • CSCastellane SASubcontractor
Activity
Delivery schedule v3 sent · Mon 2 tasks added from Adrián’s email · 09:41

What a customer desk stops doing

Reading the thread before answering

Every message about an order — from the customer, the supplier, the carrier — is on the order, whichever mailbox it arrived in. “Where is my delivery?” is answered from one screen.

Losing the exception in a shared inbox

Short shipments, damages and claims become tasks on the order that caused them, with an owner and a date. Waiting on a supplier is a visible state rather than an unanswered email.

Arguing about the price that was quoted

Quotes, order confirmations and price lists are documents on the record, with the version each customer received and the date it went. Nobody has to work from memory.

Matching supplier invoices by hand

Invoices arriving as email are read into payables on the order, checked for duplicates and changed bank details, and routed for approval before anything is paid.

One order, from enquiry to settled

1
Enquiry arrives
in a shared mailbox, from a customer
2
Order opened
a reference, with its customer and supplier
3
Supplier confirms
dates and confirmations on the order
4
Exception handled
a claim becomes a task with an owner
5
Money closed
invoices approved, payments tracked to paid

Management reads the desk, not a status meeting

Which orders are stuck and on whom, how much is outstanding, where the workload sits — read from the orders themselves, with departments and permissions that match how the business is organised.

Your words, in the product
OrdersCustomersSuppliersShipmentsClaimsPrice listsCredit notesCarriers

Set once in the business profile. Every screen, button and dialog follows.

OVIOO
Compose
Payablesfrom email, linked to their reference
New payable
Pending 6Due soon 2Awaiting approval 1Processing 3Paid 41
Supplier · document
Reference
Due
Amount
Vantage SupplyProforma VC-2026-0418742615Halden & Co22 Aug€4,320.00CO
Castellane SAInvoice 2026/1187742615Halden & Co29 Aug€11,940.00DM
Museu PicassoProforma 5521742580Riverside2 Sep€780.00CO
Open payables
€17,040
3 documents · 2 references
Receivables due
€28,600
Halden · balance 14 Sep
Needs approval
Castellane SA · €11,940
Over Daniel’s limit · routed to Clara

What it replaces on a customer desk

Your order system stays. What changes is where the correspondence about an order lives.

The workaround today
In OVIOO
An order number and no way to see its emails
Every message about the order, on the order
“Where is my delivery?” answered by searching
One screen with the supplier’s last reply on it
A claim tracked in a note to self
A task with an owner and a date, on the order
Arguing about the price that was quoted
The quote sent, with its version and date
Matching supplier invoices by hand
Payables on the order, checked for duplicates as they arrive
A shared inbox two people both reply from
One thread, visible to both, with who answered

Fair questions

No. Stock, pricing, picking and the order transaction itself stay where they are. This holds the exception layer — the correspondence, confirmations, changes and claims that decide whether an order actually ships, and that currently live in a mailbox.

No stock levels, no warehouse locations, no replenishment. It is not a WMS and does not pretend to be one.

Yes — it takes your codes rather than issuing its own, and an order can carry yours, the customer’s PO and the supplier’s reference at the same time. A supplier who only quotes their own number still lands on the right order.

The volume is the reason for the three gates in front of the model: free filters first, cheap triage second, and a full read only for what carries work. Most of a busy mailbox is not work, and most of it never reaches the expensive step.

See it on your own work.

Connect one shared mailbox and watch a real week organise itself. Fourteen days, no card.