Use cases · 06 Taking over order confirmations
The confirmation is in the ERP before anyone opens it.
Suppliers confirm your purchase orders by email, PDF or scan, each in their own format. The AI reads the date, quantity and price; fixed rules compare them with your order. What matches is in the ERP. Anything that deviates or is uncertain goes to your purchasing team.
Today
Your purchasing team types in confirmations when there is time. Until then, the ERP plans with the requested date.
Afterwards
Confirmed dates are in the ERP. Purchasing only gets what deviates or is uncertain.
First run alongside, then switch over.
Eight confirmations from one morning in your purchasing department, in three states: as today, in shadow mode and switched on.
Example with fictitious data
Purchasing inboxConfirmations by email, PDF, scan
- Supplier APDFsame result
- Supplier BPDFsame result
- Supplier CEmailsame result
- Supplier DPDF, bilingualsame result
- Supplier BPDFsame result
- Supplier EScansolution asks for clarification
- Supplier FEmail with PDFsame result
- Supplier DPDFsame result
Exceptions · Purchasing
BE-24117 · Supplier A · DiscrepancyPrice confirmed at €4.50 per unit, ordered at €4.20.
From the confirmation
Seal kit DS-12500 units€4.50 / unit
Your order
Seal kit DS-12500 units€4.20 / unit
Nothing entered. Your decision. The order in the ERP stays unchanged until your purchasing team decides.
BE-24119 · Supplier C · DiscrepancyDate confirmed for Wk 50, ordered for Wk 48.
From the confirmation
Geared motor GM-4012 unitsDelivery Wk 50
Your order
Geared motor GM-4012 unitsDelivery Wk 48
Nothing entered. Your decision. The order in the ERP stays unchanged until your purchasing team decides.
BE-24122 · Supplier E · uncertainScan hard to read: quantity not read with certainty.
From the confirmation
Sheet metal 2 mm, folded8? unitsWk 48
Your order
Sheet metal 2 mm, folded80 unitsWk 48
Nothing entered. Please take a look. The order in the ERP stays unchanged until your purchasing team decides.
ERP · Purchase ordersYour ERP remains the system of record.
| from your order | from the confirmation | ||||
|---|---|---|---|---|---|
| Order | Item | Date | Date | Number | Status |
| BE-24117Supplier A | Seal kit DS‑12 | Wk 47 | –– | –– | opento purchasing, not entered, sent to purchasing |
| BE-24118Supplier B | Ball bearing 6205 | Wk 47 | Wk 47 (by hand)Wk 47 | AB-31206AB-31206 | confirmedconfirmed |
| BE-24119Supplier C | Geared motor GM‑40 | Wk 48 | –– | –– | opento purchasing, not entered, sent to purchasing |
| BE-24120Supplier D | Hex bolt M10 | Wk 47 | Wk 46 (by hand)Wk 46 | OC 88412OC 88412 | confirmedconfirmed |
| BE-24121Supplier B | Coupling K‑25 | Wk 49 | –Wk 49 | –AB-31219 | openconfirmed |
| BE-24122Supplier E | Sheet metal 2 mm, folded | Wk 48 | –– | –– | opento purchasing, not entered, sent to purchasing |
| BE-24123Supplier F | Hydraulic hose HS‑08 | Wk 48 | –Wk 48 | –2611-047 | openconfirmed |
| BE-24124Supplier D | Flange gasket FD‑50 | Wk 49 | –Wk 49 | –OC 88430 | openconfirmed |
Only these three fields are written. Quantity and price are compared, never written.
Today
Two systems that don’t talk to each other. In between, your purchasing team types things in.
Two of eight purchase orders have a confirmed date, entered by hand. For the other six, the ERP plans with the ordered date.
Shadow mode
The AI reads the same confirmations as your purchasing team. Its result is compared, not used.
The AI has read seven confirmations the same way as your purchasing team; for one poorly legible scan, it asks for clarification. Nothing changes in the ERP.
Switched on
Only once the comparison is convincing does it take over work.What matches is in the ERP. What deviates or is uncertain lands with purchasing.
Five confirmations were entered. Three went to purchasing: two discrepancies in price and date, one quantity read with uncertainty.
Why nobody needs to step in here.
AI alone, only where we have measured the accuracy and a mistake is easy to fix. Uncertain cases go to a person.
- Measured beforehand.Before anything is switched on, the AI reads along with your real confirmations. We compare every field with what your purchasing team entered. It is only switched on once the comparison is convincing and you agree.
- Only three fields.The connection writes the confirmed date, the confirmation number and the status. It only compares quantity and price. Nothing in a confirmation triggers an action or retrieves other data.
- Uncertain cases go to a person.If a field has not been read with certainty, the order is missing or something deviates, the connection enters nothing. Exceptions always go to a person.
- Checked continuously.Every entry refers to the confirmation it came from and can be reversed. Corrections by your purchasing team feed back in. A new version only replaces the current one if it performs better on a fixed test set and a person agrees.
Counter-exampleWe don’t switch over like this for supplier invoices: money is at stake there, and a mistake is not easy to undo.
What changes and what it takes.
- For your teamPurchasing no longer types in confirmations. It resolves discrepancies while there is still time to do so.
- PrerequisitesPurchase orders in the ERP that your suppliers refer to by order number. A mailbox where the confirmations arrive. A way to write three fields to the ERP.
- Measuring successShare of purchase orders with a confirmed date in the ERP, time until a discrepancy reaches purchasing, corrections to entered values, each before and after.
- Area
- Connecting systems
- Capabilities
- Extracting
- Fixed connection
- Approval mode
- AI alone
Which task takes up most of your team’s time?
Bring a specific task or an initial idea. You do not need a finished project brief.
Your first conversation is directly with one of the founders: Julius, Luis, Max or Quentin.
Prefer to write directly? kontakt@omnerio.com Two or three sentences about your task are enough.




