What to ask an order automation vendor
Every vendor in this category demos well on a clean PDF. Here are the questions that separate them — including the ones we would rather you didn't ask us.
Order automation demos are easy to make impressive. Take a tidy purchase order, drop it in, watch structured data appear. Every product in this category clears that bar, which makes it a useless bar.
Ask what happens when extraction is wrong
Not whether it is ever wrong — it is. Ask what the system does about it. Is there a confidence score? Does a low-confidence order route to a human automatically, or does it write to the ERP and hope? Can you see, after the fact, which orders the AI was unsure about?
A system that is confidently wrong is worse than manual entry, because nobody is checking.
Ask to see a failure
Ask the vendor to show you an order the ERP rejected. You want to see the actual error, attached to the actual order, with a way to fix and retry. If failures are only visible in a log somewhere, your team will find out from the customer.
Ask about the messy channels specifically
- A photo of a handwritten list sent over WhatsApp
- A voice note from a chef listing eleven items
- A spreadsheet using the customer's product codes, not yours
- An email that changes an order sent an hour earlier
These are not edge cases in food distribution. They are Tuesday. If the demo only covers clean PDFs, you are being shown the easy half.
Ask where your business rules live
Minimums, cutoffs, delivery charges, entity and warehouse routing. Ask whether these are configurable by you, or whether each change is a support ticket. Rules you cannot change yourself will drift out of date.
Ask what happens to the original
When a customer disputes an order, you want the original message — the email, the photo, the recording — attached to the order, permanently. Any system that discards the source is asking you to win arguments from memory.
And ask us the awkward one
ManualOut is early. We do not have a decade of reference customers to point at, and we would rather say so than construct a logo wall. What we do have is a working product and the willingness to show you the failure states in a live demo, not just the happy path.
If a vendor will not show you what breaks, you have learned something.
Order automation demos are easy to make impressive. Take a tidy purchase order, drop it in, watch structured data appear. Every product in this category clears that bar, which makes it a useless bar.
Ask what happens when extraction is wrong
Not whether it is ever wrong — it is. Ask what the system does about it. Is there a confidence score? Does a low-confidence order route to a human automatically, or does it write to the ERP and hope? Can you see, after the fact, which orders the AI was unsure about?
A system that is confidently wrong is worse than manual entry, because nobody is checking.
Ask to see a failure
Ask the vendor to show you an order the ERP rejected. You want to see the actual error, attached to the actual order, with a way to fix and retry. If failures are only visible in a log somewhere, your team will find out from the customer.
Ask about the messy channels specifically
- A photo of a handwritten list sent over WhatsApp
- A voice note from a chef listing eleven items
- A spreadsheet using the customer's product codes, not yours
- An email that changes an order sent an hour earlier
These are not edge cases in food distribution. They are Tuesday. If the demo only covers clean PDFs, you are being shown the easy half.
Ask where your business rules live
Minimums, cutoffs, delivery charges, entity and warehouse routing. Ask whether these are configurable by you, or whether each change is a support ticket. Rules you cannot change yourself will drift out of date.
Ask what happens to the original
When a customer disputes an order, you want the original message — the email, the photo, the recording — attached to the order, permanently. Any system that discards the source is asking you to win arguments from memory.
And ask us the awkward one
ManualOut is early. We do not have a decade of reference customers to point at, and we would rather say so than construct a logo wall. What we do have is a working product and the willingness to show you the failure states in a live demo, not just the happy path.
If a vendor will not show you what breaks, you have learned something.