We measure it on 500 of your own customer orders in 14 days, scored field by field, before you commit anything to the full build.
Fixed pilot fee. Fall short of the accuracy we agree upfront and the pilot costs you nothing. No licences, no per-order pricing.
What manual order entry really costs
Orders land between six and nine in the morning, all at once, in whatever format each customer prefers. The planning cannot start until they are in the system. That queue is the real cost, not the keystrokes.
per order to read the PDF, check the addresses against the customer's own naming, and key the stops into the TMS.
entry error rate on postcodes, time windows and pallet counts. Each one becomes a failed delivery or a waiting-time claim.
of the planning day typically lost to entry before the first route is optimised, at exactly the hour when replanning is still cheap.
who knows that this customer's 'Werk 2' means the ramp round the back, and who is not always in.
Three fields. This is what keying transport orders costs you per year.
Excludes waiting-time claims and failed deliveries traced back to an entry error, and excludes the planning quality lost to starting ninety minutes late.
The mechanism
The difficulty in road freight is not reading the PDF. It is that the same consignee is written five ways by five customers, and that a time window written as 'AM' means something specific at each site.
PDF attachment, order in the mail body, or the customer's own spreadsheet. All three are handled, and where a customer sends the same order twice in two formats, the duplicate is recognised rather than planned twice.
Consignor and consignee addresses are matched to your existing address book, not created as new entries. Postcodes, ramp references and opening hours are checked, and an unknown address stops the order instead of spawning a duplicate record.
The job is created with stops, time windows, goods lines and references, each traceable to the line of the document it came from, so a planner can audit any field without reopening the email.
A customer's transport order on the left. The job it produces on the right. Illustrative example with fictional data.
| Pos | Von / Nach | Zeitfenster | Ladung |
|---|---|---|---|
| 1 | Abholung: Waiblingen, Werk 2 | 06.08. vormittags | 6 Europaletten |
| 2 | Zustellung: Venlo, DC Noord | 07.08. 08:00-12:00 | 1.840 kg |
| 3 | Hinweis: Ladehilfe erforderlich | - | Hebebuehne |
Job 26-11907 · K-2214 · Waiblingen → Venlo · 6 EPAL / 1,840 kg / 2.4 ldm · tail lift · DAP
The offer
One fixed fee. Fourteen days. Your real customer orders. An accuracy number at the end that tells you, and us, whether the full build earns its cost.
Not a workshop. The pilot ends with your own orders created in a TMS test environment and a per-customer accuracy breakdown.
Against a problem costing most clients €40,000–70,000 a year.
Credited in full against the build if you proceed within 90 days.
No software to install, no workshop series, no project team on your side. Your people keep working; we work on copies.
Before we start, we agree the accuracy threshold that makes this worth deploying. Together, in the engagement letter. If the measured result on your documents comes in below it, the pilot is free. We can offer this because we scope honestly: if we don't think your document mix can hit the number, we decline the pilot and tell you why.
Pilots run one at a time per engineer, so they start in the order requests arrive. Current lead time: about two weeks
Your actual alternatives
| Do nothing | Hire another dispatcher | Customer EDI portal | Braynex pilot → build | |
|---|---|---|---|---|
| Works with customers who will not change | ✕ manual forever | ✓ by typing | ✕ needs their cooperation | ✓ takes what they send |
| Cost over 3 years | rising with volume | €115–165k+ | €10–30k + onboarding per customer | known, fixed, quoted |
| Time to first benefit | - | recruitment plus training | ✕ one customer at a time | ✓ whole order mix at once |
| Proof before commitment | - | ✕ | ✕ pilot with a willing customer | ✓ measured on your real mix |
| Admits when a field is ambiguous | - | ✓ asks the customer | rejects the message | ✓ creates and flags |
Why believe us
AI that converts medical records into legally defensible timelines. Accuracy-critical, regulated, every extraction traceable to its source page.
Client meeting recordings become compliant advisory documents automatically, adopted across the practice for every client meeting.
Production vision-AI moderation for marketplace listings: real ML in production at volume, not an API wrapper.
Swiss entity (Zug) · EU-region hosting · GDPR & revised FADP compliant · named senior engineers you meet before signing
Fair questions
For your top customers, yes, and you should keep going. EDI stalls on the long tail: the customer sending forty orders a month has no appetite for an integration project, and that tail is usually where your dispatchers lose their mornings. This covers the tail without asking anything of the customer.
An address that does not resolve to an existing record stops the order rather than creating a new entry. Duplicate master data is a slower and more expensive problem than manual entry, so the system is deliberately biased against writing anything new. The pilot reports how often that happened.
That is the case in the worked example above, and it is the honest limit of what any system can infer. "Vormittags" at a site with a two-hour ramp slot is not a time window. It gets flagged with the customer's exact wording rather than converted into a plausible-looking 08:00-12:00 that your driver then misses.
Sometimes you should. If your order mix is dominated by a few stable formats, a template-based product may well cover you at lower cost, and the pilot report will say so plainly. Either way the fixed fee has bought you a decision you can defend.
EU-region hosting, a GDPR-compliant processing agreement, and a contract with our Swiss entity in Zug. Nothing trains a public model. Your own compliance lead can review the setup before the pilot starts, and the pilot sample can be narrowed to a subset you are comfortable sharing.
Because we are structured for exactly this engagement size. The large consultancies staff €60k projects with juniors or decline them; we deliver them with the people you actually meet. That is the trade we have built the company on.
Start here
Tell us your order volume and how the orders arrive. One engineer reads it and answers within a business day, including if the answer is that your order mix is too clean to be worth automating.
Lead Engineer · runs your pilot
The people on this page are the people on your project. No handover to a delivery team you never met: the engineer who scopes your pilot is the engineer who builds it.
Braynex
Prishtina, Kosovo · Zug, Switzerland
Contact: contact@braynex.ai
Responsible for the content of this page: Braynex. Further statutory details (register entries, VAT identification) are available on request and via the main website at braynex.ai.
The contact form on this page sends your entries directly to contact@braynex.ai by email. We use the data you provide solely to respond to your enquiry; it is not shared with third parties, used for advertising, or added to any mailing list.
This page is hosted in the EU region and sets no marketing cookies. For questions about your data or to request deletion of correspondence, write to contact@braynex.ai.