What it can see, and what it can't
Connecting anything to your ERP is a fair thing to be careful about — it is where your customers, pricing and stock live. So it is worth being precise: ManualOut reads only the data it matches against, writes sales orders, and touches nothing else.
Data and security for AI order automation
Precise about the footprint, not vague about it
The honest way to talk about security is to say exactly what the software needs and stop there. ManualOut needs to read the data it matches an order against — products, price lists, customers — and to create sales orders. That is close to the whole footprint. It does not need your ledger, your costs or your people data, so it does not have them. Being specific about that is worth more than a page of assurances.
In front of the ERP, never in place of it
A distributor does not need another system to become the master record for customers, products and orders — the ERP already is. So the layer sits in front: it reads from your master data to understand an order, and writes the finished sales order back through the ERP's own interface. Your systems remain the source of truth, and ManualOut is the thing that gets a clean order into them.
Control that stays with you
Access runs on credentials your team creates and can revoke, scoped to what the product uses. There is no standing super-user, no undocumented integration, and no need to open your network wide. If you ever want it gone, you turn off the credentials — the same way you granted them. Security you can end unilaterally is the only kind worth trusting.
Every order leaves evidence
The original message stays attached to the order it became, and every write to the ERP is timestamped with the reference that came back. That is not only for audits: it is what lets the desk see why a line was flagged, lets customer service settle a “we ordered six” dispute in seconds, and gives IT the trail when a mapping needs checking. A sales order without its source loses context; here, the context never leaves.
In the product
Everything listed here exists today.
Credentials you control
ManualOut connects with credentials you provision and can revoke, scoped to what it needs — not a standing key to everything.
Reads only what it matches
It reads your products, price lists and customers, and writes sales orders. It does not touch your ledger, margins or payroll.
Encrypted, and logged
Data moves over encrypted connections, and every order written to the ERP leaves a timestamped record you can reconcile against.
The original as evidence
Every order keeps the source message attached, so there is always an auditable trail back to what the customer actually sent.
In context
Every write to the ERP, timestamped and reconcilable
The order that reached the ERP, when it landed, and the reference that came back — a record you can reconcile against, and a trail back to the exact message the customer sent.
- ERP order no.
- SO-4471203
- Synced by
- Automatic
- Synced at
- 14 May 2026, 10:17 PM
- Confidence
- 94%
- Order received
- AI parsing completed
- Validation completed
- Inventory checked
- Synced to ERP
- Order confirmed
For IT
Access that is scoped, revocable and logged
What your IT team needs to sign off is not a compliance slogan — it is a clear answer to what the system can reach, how, and what it leaves behind. Here is the footprint, honestly.
Least-privilege by design
ManualOut connects through your ERP's own interface with credentials you create and can revoke, scoped to reading master data and creating sales orders. There is no standing administrative key and no access to parts of the ERP that have nothing to do with an order.
Your systems stay the source of truth
The layer sits in front of the ERP, not in place of it. Customers, products, prices and orders still live in your ERP; ManualOut reads what it needs to match an order and writes the result back. It does not become a second, competing record of your business.
An audit trail on both ends
Every order carries its original message, and every write to the ERP is timestamped with the reference that came back. If a line is ever questioned, you can trace it from the sales order all the way back to what the customer actually sent.
Questions
Data & security, answered
What data does ManualOut actually access?
Only what it needs to turn a message into a sales order: it reads your product list, price lists and customer records to match each line, and it creates sales orders. It does not need or touch your general ledger, your margins, your payroll or anything in the ERP unrelated to order entry.
How does it connect to our ERP — and can we revoke it?
Through your ERP's own API or a supported import, using credentials you provision and can revoke at any time. Access is scoped to what it uses, so switching it off is entirely in your control — there is no separate back door to close.
Is the connection encrypted?
Yes. Data moves over encrypted connections, and for an on-premise ERP behind a firewall the link is made through a secure connection or a small agent rather than by opening your network to the internet.
Where is the original order kept, and why?
Every processed order keeps its source — the email, PDF, spreadsheet, WhatsApp thread, image or voice recording. It is both the audit trail and the way a dispute is settled: whether the customer asked for six cartons or sixteen is answered by looking at what they sent, not by memory.
Do you make security or compliance claims you can't back?
No — and you should be wary of anyone who does. This page describes how the integration actually works and what it can reach, not a badge. The fair test is to put the plain questions to any vendor, us included: what do you store, who can see it, and can we switch it off.
What happens to an order the ERP rejects?
You see the rejection and the reason, and the order waits for a person rather than vanishing. Nothing is written half-way and nothing fails silently — a rejected order is visible work, with its original message attached, not a gap you discover later.
The rest of the product
Order capture
Take the order however it arrives
AI extraction
Read the order, match it to your products
Rules & validation
Your rules, checked on every single order
ERP sync
It only counts once it is in your ERP
Customer management
Set each account up once, then let the good ones run
Analytics
See what you are selling, and how well the AI is doing
Review & exceptions
Uncertain orders reach a person, not the warehouse
See it run on one of your own orders
Send us a real order — the messiest one you can find. We will run it live and show you what happens when it works, and when it does not.