Supply chain operations

The orders that arrive as an email and a PDF.

EDI covers the partners who set it up. Everything else arrives as a PDF on an email, a changed date buried in a reply, or a short shipment someone notices at the dock. A person reads it and types it in. That reading is where we build.

All industries
01

Order intake

Highest volume

Purchase orders arrive in whatever format each customer happens to use. The agent reads them, checks them against your price lists and stock, and creates the sales order. Anything that doesn't match goes to a person with the reason.

  • PO lines read from a PDF, an email body or a spreadsheet, whatever the layout
  • Prices and part numbers checked against your master data before entry
  • Order created in the ERP, or held with the mismatch named
02

Supplier confirmations

Highest volume

You send a PO. The supplier confirms a different date, quantity or price, somewhere in an email thread. The agent reads the acknowledgement, compares it with what you ordered, and tells the planner what changed.

  • Acknowledgements reconciled line by line against the PO
  • Date, quantity and price changes flagged to the buyer who owns the order
  • Missing confirmations chased before they turn into late deliveries
03

Delay notices

Strong fit

A carrier delay or a supplier slip lands in a shared inbox. By the time someone reads it, the planner has lost a day. The agent reads it, works out which orders it touches, and tells the right person.

  • Delay notices matched to the open orders and customers they affect
  • Impact stated plainly: which order, how late, which customer
  • Expedite options prepared for a person to approve
04

Receiving discrepancies

Strong fit

Short shipments, damaged goods, wrong items. A claim needs the PO, the packing slip, the receipt and the photos, and they sit in four places. The agent puts them together.

  • Received quantities compared with the PO and the advance ship notice
  • Supplier claims drafted with every document attached
  • Credit notes tracked until they actually arrive
05

Master data upkeep

Approval only

Lead times, item attributes and supplier prices drift out of date. The agent finds the drift and proposes the change. A person approves anything that touches master data.

  • Quoted lead times compared with what suppliers actually delivered
  • Proposed updates queued for a person, with the evidence attached
01 How the agent works

Same pattern on every message. Read it, match it, act inside your rules, escalate the rest.

1 A message arrives

An order, a confirmation, a delay notice. By email, portal or scan, in whatever format the sender chose.

2 It reads and matches

The agent ties it to the open order, the item master and the customer, across every system it lives in.

3 It acts inside your rules

When everything matches your tolerances, it creates the order or updates the date. Nothing else.

4 Exceptions go to a person

What changed, what it affects, and a proposed next step. The planner decides.

02 What the research says

These are not our numbers. They are the published ones.

We have not published a client result yet. Until we do, here is what APQC's order management research says about the work we build on.

Perfect order performance complete, on time, undamaged, right paperwork
25TH PERCENTILE
80%
MEDIAN
84%
75TH PERCENTILE
85%
APQC, Measuring Order
Management Performance, 2026
Cost to process a purchase order range across organisations
LOW END
$14
HIGH END
$54+
APQC procurement
benchmarks, 2026
Customer order cycle time order received to delivered
MEDIAN
15 DAYS
APQC, Measuring Order
Management Performance, 2026

APQC's order data comes from 200 large North American companies with at least $100 million in revenue. Smaller operations usually look worse on cost per order. The perfect order figure is the one to hold onto. The gap between the 25th and 75th percentile is five points, and even the stronger performers lose roughly one order in seven somewhere between the PO and the delivery. Your own baseline tells you more than any median. We'd rather you measured it than took our word for it.

03 Process fit

Which part is worth building first.

Our assessment, not a measurement. The last column decides a lot here: the more a mistake costs, the more the agent prepares and the less it does on its own.

VOLUME &
REPETITION
RULES ALREADY
WRITTEN
SPREAD ACROSS
SYSTEMS
LOW COST OF
A MISTAKE
OUR READ
Supplier confirmations
START HERE
Order intake
START HERE
Receiving discrepancies
STRONG
Delay notices
STRONG
Master data upkeep
APPROVAL ONLY
STRONG CASE PARTIAL WEAK COUNTS AGAINST
Where we say no

The agent never changes master data, commits to a customer delivery date, or places a purchase order on its own. It prepares those with the evidence, and a person approves. If most of your volume already runs through EDI, an agent has little to add there, and we'll tell you so.

04 How we engage

Three steps. You can stop after the first one.

01 FREE
Discovery

We sit with whoever actually clears the exception queue and watch a normal week. Where one of our builds fits, we demo it on your own samples. Either way you get the Unwired Blueprint: one sheet with your process as it runs today, the process unwired, and the line your process owner signs. If the answer is not to build, the sheet says that too. If a scheduled job fixes it cheaper, we tell you that and we are done.

02 FIXED SCOPE
Build

One process, scoped and priced before we start. Built against your systems and your rules, not a demo environment. You see it running on your own data, not on ours.

03 YOU OWN IT
Handover

Code, documentation and runbook handed to your team. No licence, no lock-in, no retainer you have to keep paying to keep it working. Keep us on if you want more built.

Build pricing is set per engagement and quoted in writing before any work starts.

Which inbox is the bottleneck?

Tell us where orders or confirmations get retyped. We'll tell you honestly whether an agent is the right fix.