Operations · Run module
Purchase orders arrive by email and get retyped
Customer POs come in as PDFs and emails, and inside sales keys them in by hand. What is built today to cut the retyping, and what is not built yet.
Starts on One module · Run · $350 a month
In your words
Our customers send purchase orders every way you can imagine: a PDF from their ERP, a spreadsheet, a photo of a form, three lines in the body of an email. Two people in inside sales spend most of their morning reading them and keying them into our system.
The mistakes are small and expensive: their part number instead of ours, last year’s price, a quantity in cases instead of units. We find out when the wrong pallet arrives at their dock.
Why it happens
Every customer’s purchase order looks different, uses its own part numbers and sometimes its own units. Matching each line to your catalogue and to that customer’s contract price is judgment work, so it stays manual.
The order also arrives in a shared mailbox among everything else: questions, complaints, invoices. Nothing tells the team that this message is an order and should be handled before the newsletter replies.
What it costs
Order entry by hand is slow at the worst time, when a customer has already decided to buy. Each hour an order waits pushes back its ship date.
Keying errors cost twice: once in freight and restocking to fix the wrong shipment, and once in the customer’s confidence that the next order will be right.
How Humonix fixes it
01Agent
Orders rise to the top of the Inbox
An email that says order, purchase order, PO or bon de commande is read as an order and scores higher in the Inbox, with the word that decided it shown, so it is handled before routine mail.
02Agent
Priced from your book, for that customer
Hue can turn what the customer asked for into a formal quote, priced at that customer’s tier or contract price, with their PO number on it, stock per warehouse and a promised ship date.
03Agent
A person confirms, once
The quote waits for a person, who checks it against the customer’s PO and approves it. The approved quote has its number and a printable page, and can be signed online.
04Agent
A place customers can send orders
Customers you invite to your customer portal can send requests there, signed in with an email code, and see their quotes, jobs and invoices.
01Agent
The department
This is part of the Run module, in early access and run with Head of Digital. Reading a PDF or spreadsheet purchase order line by line, matching their part numbers to yours and entering it in your ERP is not built yet; today a person reads the PO and confirms the priced quote.
02Hue
Hue’s part
Hue answers the questions that come with an order, such as stock, lead time or a contract price, from your own records, and says so when it does not know.
03You
Your yes
Nothing reaches the customer before a person approves the quote. An automatic approval rule exists for simple cases and is off unless you turn it on.
What you see
Inbox: an incoming order ranked high, with the word that marked it as an order and the customer’s tier.
Where to start
One module · Run
One of twelve modules, run end to end by agents; you approve what goes out. No person included. Month to month.
Questions
Can it read the PDF attached to the email?
Not yet. Reading a purchase order file line by line is not built; this page says so on purpose. Today the order is ranked, priced and confirmed, not read from the file.
Can it enter orders in our ERP?
No. Your price book comes in from an ERP export, and quotes are made in the client app. Writing orders back to an ERP is not built.
Will it use the customer’s contract prices?
Yes. Contract prices and tiers in your price book are applied per customer, and each line names the rule that set its price.
Can customers order without emailing?
Customers you invite to your portal can send requests there; each request is routed to your team like any other inquiry.