Order Inbox Drafter
Reads orders arriving by email, PDF, voicemail, and text, extracts the line items, matches each to your SKU master, and produces a structured draft sales order — flagging anything ambiguous for a person to approve, never posting an order on its own.
The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.
Reads each inbound order — email, PDF, voicemail or text — matches every line to your SKU master and the customer's pricing, and surfaces a draft sales order with every uncertain line flagged for an order processor to approve before anything reaches the ERP.
It does the overnight re-keying every morning, in full, and shows where each line came from.
- Done by hand a non-EDI order runs roughly 15–30 minutes each, and transcription slips — a misheard quantity, the wrong pack size — surface as wrong-goods deliveries and credit notes days later.
- Best for a fresh-food wholesaler or distributor whose order desk faces a daily morning crush of varied, free-text orders from hospitality and retail accounts that order outside EDI.
- At dozens of orders a morning, the recaptured hours go back into the calls that need judgement — a substitution, an unusual quantity, a credit query — not into typing.
It is confidently wrong when the description is ambiguous or the SKU master is stale — and a clean draft hides it.
- Weak where a description maps to several SKUs, where the same customer says "the usual" with no list, or where a new product isn't in their order history yet. It should flag for a person, not guess.
- Allergen-bearing substitutions (a gluten-free flour swapped for plain, a different nut paste) are a judgement and a labelling risk under the Food Standards Code, not a match — it flags, it does not substitute.
- If most of your volume already arrives as clean EDI or a structured order portal, there is little loose text to interpret and the build isn't worth it.
If your own order processor couldn't fill the order confidently from the message alone — without ringing the customer back — neither can this, and a stale SKU master just makes the wrong line faster, not safer.
It drafts the order. An order processor approves. That boundary is deliberate.
A wrong line on a food order is not just a credit note — a substituted ingredient can carry an undeclared allergen, and Plain English Allergen Labelling under the Food Standards Code makes that a safety matter, not a clerical one. Get the customer, the SKU and the quantity wrong and the consequence lands on the supplier. The accountable person stays on the decision because the consequence lands on them — not the tool.
A current SKU master, per-account pricing and order history, and live stock the draft can lean on.
The SKU master and per-account pricing are usually the weak point — full of duplicate or retired codes, with contract prices held in a spreadsheet someone maintains by hand. Getting product, price and customer data into a clean, current state the matcher can trust is usually the real first job — larger and more valuable than the extraction layer on top. Once the master data is right, every order after that drafts faster and right by default.
The worried-buyer questions, answered straight
Fixed scope, fixed price, fixed dates.
Considering this for your order desk?
The honest place to start is a bite-sized first piece — one customer segment, one inbox, low risk. Tell us where it hurts; we'll play it back, scope it, and show you what's possible.