Read, mapped to your own part numbers, checked against the agreed price, and created. Proven on 500 of your own orders in 14 days, before you commit to the build.
Fixed pilot fee. Below the accuracy threshold we agree together, you pay nothing. No licences, no per-order pricing.
What order entry really costs
Your customers order by PDF because their procurement system exports PDFs. Somebody in order processing turns that into an ERP order, and until they do, nothing downstream can start.
per order to map customer part numbers to yours, check quantities and confirm the delivery date is one you can hold.
entry error rate on part numbers and quantities. The wrong variant reaches production and the correction costs a rescheduling round.
typical delay between an order arriving and being confirmed, which is a day of quoted lead time you are giving away for nothing.
who knows which customer's legacy article numbers map to which of your current parts, and who has that mapping in their head.
Three fields. This is what keying sales orders costs you per year.
Excludes rescheduling caused by a wrong variant reaching production, and excludes the lead time you lose while an order waits to be confirmed.
The mechanism
The reading is the easy half. The half that decides whether this works is mapping the customer's article number to your part, and noticing when the price on their order is not the price you agreed.
Line items, quantities, requested dates, customer article numbers and their free-text descriptions, taken from the PDF layout the customer's procurement system happens to produce this quarter.
Customer article numbers are resolved against your cross-reference, and the ordered price is checked against the agreed price list. A line that maps to a discontinued variant does not quietly become the successor part.
The order is created with every line traceable to its source line in the PDF, and any line that failed a check is held with the reason stated, so order processing reviews exceptions rather than everything.
A customer purchase order on the left. What the layer extracts and checks on the right. Illustrative example with fictional data.
| Pos | Artikel / Bezeichnung | Menge | Preis |
|---|---|---|---|
| 10 | VT-88420 Lagerbock, Guss | 120 | 38,40 |
| 20 | VT-88431 Passfeder 12x8x56 | 500 | 1,15 |
| 30 | VT-90007 Dichtsatz, alte Ausf. | 40 | 22,90 |
SO-26-04417 · cust 20114 · PO 4500891233 · 2 lines confirmed · 1 line held · req. 28.08.2026 · FCA
The offer
One fixed fee. Fourteen days. Your real customer orders. A number at the end that settles whether the full build is worth commissioning.
Not a slide deck. The pilot ends with your own orders created in an ERP test client and a line-level accuracy breakdown you can challenge.
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 clerk | Customer portal / EDI | Braynex pilot → build | |
|---|---|---|---|---|
| Works with customers who send PDFs | ✕ manual forever | ✓ by typing | ✕ needs them to adopt it | ✓ takes what they send |
| Cost over 3 years | rising with order volume | €120–170k+ | €15–40k + per-customer onboarding | known, fixed, quoted |
| Catches a price that does not match the agreement | ✕ found at invoicing | ✓ if they check | ✓ enforced by the portal | ✓ checked per line |
| Handles retired article numbers | ✕ | ✓ from memory | ✕ rejects the line | ✓ holds it and names the conflict |
| Proof before commitment | - | ✕ | ✕ pilot with a willing customer | ✓ measured on your real mix |
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
Because the customers who will not move are usually the ones generating the awkward orders. EDI handles your top ten well and stalls below that. This picks up the remainder without asking a single customer to change anything, and the two approaches coexist perfectly well.
The line is held and the conflict is named, as in the worked example above. Automatically substituting a successor part is exactly the kind of helpful behaviour that produces a warranty argument eighteen months later, so it is not done. A human decides, with the difference spelled out.
Creating them in a test client is part of the pilot, in week one. Mid-market ERPs differ enormously in how writable they are. If yours has a blocker, the fixed fee has bought you that finding early, which is worth considerably more than four months of a build discovering it.
Then buy it. Several mid-market ERPs have capable capture add-ons, and if the pilot shows one covers your order mix, the report says so and we part as friends. We only recommend a build where the measurements support one, and a fixed fee for that answer is cheaper than finding out the other way.
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 which ERP the orders have to land in. You will hear back from an engineer within one business day, with a candid view on whether your order mix justifies a pilot.
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.