Orders arrive by email. And then someone retypes them.
At a wholesaler, nobody retypes over 3,300 of 5,017 order emails anymore. A model reads the email and stages a draft order in the ERP or TMS. The team approves every order and checks the exceptions, and customers keep emailing as they do now.
- 2 out of 3Order emails at a wholesaler nobody retypes anymore
- 5,017Order emails measured, September 2026
- 70-80%Straight through at the start
- 2-4 wksTo go live
Talk to the solution architect.
No sales team. In 30 minutes we map your document streams and I'll tell you honestly whether automation pays off for your volumes. If it doesn't, you'll hear exactly that.


Sound familiar?
On busy days the pile of order emails grows
More orders means more retyping, or one more person. Customers email the way they always did, and that does not have to change.
The admin who did this is leaving, and there is no replacement
Administrative staff is among the hardest roles to fill in logistics. Every departure makes the retyping pile more fragile.
One typo on a CMR and the insurer rejects the claim
A wrongly copied seal number or licence plate can void a claim. Automated extraction validates against your master data.
How it works, without risk on your side
- 01
A 30-minute call, with the builder
You talk to the person who builds the model. We map your document streams and tell you honestly whether automation pays off. If it doesn't, you'll hear that too.
- 02
Free feasibility study on your real documents
We test the AI on a sample of your actual orders and CMRs and report the achievable automation rate and the hours saved. Before you invest anything.
- 03
Built in 2-4 weeks, fixed price, straight into your TMS/ERP
Model, review screen and the TMS/ERP integration, at an agreed fixed price. Your team only checks the exceptions.
Why not a standard tool or EDI?
| Standard tool | EDI | Stratalytic | |
|---|---|---|---|
| Works with deviating formats | Fails outside the template | Only for connected partners | Reads the content |
| Project needed per customer | Template per sender | EDI project per partner | None, reads email/PDF as-is |
| For your customers | Nothing, as long as the template fits | They have to connect to EDI | Nothing, they keep emailing |
| Cost model | Subscription per document | Costs per connection | Fixed build price upfront |
Before the call
What does it cost?
The exact price follows from the free feasibility study and depends on your document types and the TMS/ERP integration. A price-per-document model is also possible, so you only pay for what the system actually processes. A proposal only comes when the saving in hours and errors clearly outweighs the price. If that does not work out, there is no proposal.
How much of our time does this take?
The call takes 30 minutes. For the feasibility study we ask for a share of the orders as they arrive now, for example two years of order emails; we handle the rest. Customers do not have to change anything.
What if the AI makes a mistake?
The system shows how sure it is for every field. Doubtful cases go to a review screen where the company's own team approves or corrects them in seconds, and the team approves every order before it lands in the ERP. It starts at 70-80% straight-through processing and grows towards 90%+, with fewer errors than manual retyping.
Do we need to replace our TMS or ERP?
No. The AI layer sits next to the existing systems and delivers data through the interfaces the TMS or ERP already has. Nothing to migrate.
Our orders all look different. Does this still work?
That is exactly the point. Software that lifts text from a scan (OCR) needs a template per customer. Here the system reads the content regardless of format. The free feasibility study tests this on a share of the real documents, so the answer is on paper before anything is spent.
Who maintains this later?
Your own team, or us if that is easier. Code, model and documentation go to your company, and there is no mandatory subscription. Ongoing support is available, but never required.


