For distributors and manufacturers on SAP Business One, Dynamics 365 Business Central, Sage, Odoo or a custom ERP

Emailed purchase orders become draft orders in your ERP. A person approves every one.

EDI covers your three biggest customers. The other two hundred still send PDFs, Excel files and free-text emails that someone re-types. ERPdraft reads them, matches the customer and their article numbers to your SKUs, flags what it isn’t sure about, and puts a ready-to-approve draft into your ERP. Nothing is posted without a human.

No mailbox access needed for the first step. Historical, anonymised files are enough.

What we measure on your first batch

  • Extraction accuracy per field
  • Customer and SKU match rate
  • Minutes saved per order
  • Share of orders that needed a human correction

Sound familiar?

  • Orders arrive as PDF, Excel, a scanned fax or one sentence in an email — and every customer uses their own article numbers.
  • Someone in sales support spends one to two hours a day copying them into the ERP. Typos surface later as wrong deliveries and credit notes.
  • The one person who knows every customer’s quirks is on holiday, off sick, or about to leave — or you have been recruiting their replacement for four months.
  • EDI was set up for the key accounts. Nobody is going to do EDI for a customer who orders twice a month.

How it works

  1. Read. The email and its attachments — PDF, Excel, scans, free text — are turned into line items.
  2. Match. The customer is identified; their article numbers are mapped to your SKUs using your master data and a mapping table that learns from every correction.
  3. Check. Prices, units, quantities, delivery dates and your business rules. Anything uncertain is flagged, not guessed.
  4. Draft. A draft sales order appears in your ERP with the source document attached. Your team approves, edits or rejects it in one click.
From: bestellung@kunde-gmbh.de   Subject: "PO 4711 attached"

Customer   Kunde GmbH — matched by sender domain + PO header      ✔
Line 1     "Art. K-2210, 40 pcs"  →  SKU 100-2210                  ✔  mapping learned 12 May
Line 2     "Dichtung 80mm, 200 Stk"  →  3 candidates               ⚠  needs review
Delivery   15.09.2026                                              ✔
Prices     Price list 2026-B, 2 lines differ from PO by < 1 %      ⚠  shown for approval

→ Draft sales order 20026531 created in SAP Business One · awaiting approval

Human in the loop, by design

  • Nothing is posted without approval. The system prepares; your people decide.
  • Confidence thresholds: orders the system is sure about go straight to the approval queue; uncertain fields are highlighted.
  • Every correction is remembered. The second time a customer writes “Dichtung 80mm”, it is matched automatically.
  • Full audit trail: source email → extracted values → rule decisions → who approved what, and when.

Your data stays in the EU

  • Hosted on servers in the EU — or deployed inside your own Microsoft 365 / Azure tenant, or on-premises if your policy requires it.
  • Read-only access to one dedicated mailbox or folder. No access to anything else.
  • Your documents are never used to train models. Every customer runs in its own isolated environment.
  • NDA before we look at a single file. Data processing agreement (DPA) before any live connection.

Integrations

SAP Business One (Service Layer / DI API) · Microsoft Dynamics 365 Business Central (API) · Sage · Odoo · custom ERP via REST or CSV import.

If your ERP has an API or an import format, it can receive drafts.

From first call to production

  1. 20-minute walkthrough. You show one recent order, from inbox to ERP. Free.
  2. Proof on your files. You send 30–50 historical orders (anonymised is fine). Within a week you receive a report: accuracy per field, match rate, estimated minutes saved. Free.
  3. Paid pilot. Four weeks, live read-only mailbox, drafts into your ERP, your team approving. Fixed price, agreed up front.
  4. Subscription. Monthly, based on order volume. Includes monitoring, mapping maintenance and new document formats.

Pilot: fixed price from €2,500. Subscription: from €490 per month, volume-based. No per-seat fees.

Used only to send the checklist.

Design partner programme

I am looking for three companies to shape ERPdraft with. Design partners get the pilot at cost, priority on features for their ERP, and pricing locked for 24 months. In return I ask for candid feedback and, if the results are good, a reference.

Who is behind ERPdraft

Sergey Vareyko — 15 years of building integration-heavy enterprise software in Java, with recent work on LLM-based document understanding and human-in-the-loop operations tooling.

ERPdraft is operated by [Legal entity name], registered in Tbilisi, Georgia. Clients in Germany, the Netherlands and Poland are served remotely during the CET working day.

Questions we get asked

We already have EDI.
EDI stays. ERPdraft handles the customers who will never do EDI and the orders EDI rejects.
What happens when it gets something wrong?
It is flagged for a person before anything is posted, and the correction feeds the mapping table. You see the accuracy numbers on your own orders before you decide anything.
Does this replace our sales-support team?
It removes the typing, not the judgement. Teams use the time for the backlog, the exceptions and the customer calls that were waiting.
What do we need to provide to start?
30–50 old orders together with the ERP entries they became. That is all step two needs.
How long until it is live?
Proof in a week, pilot in four weeks. In most cases no customisation of your ERP is required.
Which languages and formats?
Documents in German, English, Dutch and Polish. PDF, Excel, scans, email body text, screenshots.
Where are you based?
The company is registered in Georgia and works remotely with EU clients. All processing runs on EU infrastructure or inside your own tenant — your data does not leave the EU.

Send me 30 of your old orders.

You get an accuracy report within a week — before anyone talks about money.

Book 20 minutes