Skip to content

Email orders · PDF · ERP

The order is already written in the email. Why retype it into the ERP?

Customers order by email, in free text or with a PDF attached, and someone copies everything line by line. We build the missing piece: AI reads the order, software checks customer, items and quantities, and a person confirms before it enters the ERP.

Public prototype 10 emails read in 19.4 seconds, for $1 to $2 per 1,000 emails.

  • AI prepares, a person confirms
  • When in doubt it asks, it does not guess
  • On the ERP you already have

Order proposalPick a row

It enters the ERP only after you confirm

The customer wrote“60 of the 40 brackets”, then “make the brackets 80” In your catalogue40 mm bracket, code ST-40 To confirm

Example with data that is not real. Customers, codes and rules are the ones in your ERP.

$1 to $2 per 1,000 emails read: the AI cost in the test

19.4 seconds to read and classify 10 emails in 7 conversations

60 of 60 checks passed on the demo emails

Measured on Inbox to Order, our prototype with public code, on emails written for the test. On your emails the numbers are measured with a trial.

Free check

Free check: can your email orders be automated?

Tell us how many orders you receive by email, in what form they arrive and which ERP you use. We reply in writing: whether it pays off, what it takes to connect it and where to start.

Ask for the check Free, with no commitment.

What it costs today

Put your own numbers in. See what retyping orders costs.

Orders that arrive by email every day, times the minutes it takes to enter one. With a proposal already prepared, a person is left with the check.

Count the orders someone reads from an email or a PDF today and retypes into the ERP.

Try it with your numbers

An estimate: set it yourself, including contributions and overheads

a year of work back to the team

Today
After
Let us talk about these numbers
How the sum works

The sum: orders a day times minutes per order, over 240 days. After, about a quarter of the time stays, which is checking and confirming each proposal. These are reference values: yours are measured with a trial.

The problem

The order arrives written. Then someone writes it again.

Every customer orders in their own way: a line in an email, a PDF, a reply to an old conversation. The ERP wants precise codes, units and quantities.

The road an order travels, by hand todayPick a stop

Email ERP

Orders stuck in the inbox. If the person who enters them is away, the orders wait. And the customer waits with them.

Where reliability is decided

Six things the system must do well, besides reading.

Reading an email is the easy part today. A wrong order in the ERP costs more than an order entered by hand, so the real work is in the checks.

An order proposalPick an item

Recognising the customer

From the sender, the signature or the customer number. If the sender matches no customer, the order stops and a person sees it.

For exampleA new email address for the same customer does not create a duplicate customer: the system proposes the match and someone confirms it.

These are the six places where an order read well can still become a wrong order. Each has its own check.

A morning of orders

What happens to the emails that reach the orders inbox.

Every conversation ends in a clear state. A person is left with confirmations and the real doubts.

TimeEmailWhat it readOutcome
08:12Order in free textCustomer C-0412 · 3 lines Ready to confirm
08:40PDF attachedOrder 4500123 · 12 lines Ready to confirm
09:05Reply to yesterday’s orderLine 2 from 60 to 80 pieces Change to confirm
09:30“12 blue labels”2 possible items To clarify, to a person
10:10Unknown senderNo customer matched To match, to a person
10:25A supplier’s promotionNot an order Skipped, stays in the inbox

Example with data that is not real, built on the states of our prototype.

Who does what

An AI that does everything alone, or a system that checks?

The same model can read an order in two very different ways. What stands around it makes the difference.

AI left on its own

  • Picks the most likely item and moves on
  • Writes straight into the ERP
  • If it is wrong, you hear it from the customer
  • No trace of why

The model interprets, the code checks, the person confirms

  • AI reads and proposes, with read-only access
  • Software verifies customer, item, unit and quantity
  • When in doubt it stops and asks a person
  • Every value shows which words it comes from

If your customers already order through a portal, a B2B ecommerce or EDI, the data arrives structured: a traditional connection is usually enough, with no AI.

How we start

First a trial on your emails, then the connection.

Nothing is connected to the ERP until the numbers on your emails are clear.

  1. 01

    Free check

    You tell us volumes, formats and ERP. We reply in writing whether it pays off and what it takes.

  2. 02

    Trial on your emails

    A sample of real orders, anonymised: we measure how many proposals come out right. Fixed price, deducted from the project if you go ahead.

  3. 03

    Connection to the ERP

    First read-only or on a test company, then in use with a person confirming.

Where the data goes

You decide where the model runs.

To read an email, its text has to reach an AI model. Where that model sits is a choice made at the start and written in the proposal.

  • Outside AI serviceIt costs very little per email and needs no hardware. The text of the orders goes through that service, under its data terms.
  • Model on your own serversThe text does not leave the company. Hardware that fits the model is needed, and accuracy is measured with the same trial.
  • Minimal permissionsThe mailbox is connected read-only, the AI has no commands to write orders, and every confirmation is recorded with who gave it.

Before you write to us

With a few orders a day, you do not need it.

It makes sense if

  • You receive dozens of orders a day by email or PDF
  • Every customer writes in their own way
  • Someone spends hours retyping them into the ERP
  • Changes by email create errors and duplicates

You do not need it if

  • You receive a few orders a day
  • Customers already order through a portal, a B2B ecommerce or EDI
  • You want a system that enters orders with no check at all

Tell us about your case

What clients say

Verified clientClient, PDF data extraction
He understood the assignment, he asked good relevant questions and delivered excellent work that did not need correcting.
Custom development, 2025 (extract)

Verified review, anonymised for privacy.

Frequently asked

Questions on this topic.

Which ERPs does it work with?

With those that allow reading customers and items and writing an order, through an API, a database or an import file. We verify it at the start, on your ERP. The part that reads the emails stays the same, the connection changes.

How accurate is AI at reading orders?

It depends on how your customers write, which is why it is measured with a trial on a sample of real emails, anonymised. In our prototype, on emails written for the test, it passed 60 checks out of 60: a good sign, not a promise about your emails.

What happens when the AI is wrong or unsure?

Software checks every proposal against customers, catalogue, units and quantities. If a value does not match or several items are possible, the proposal stops and a person decides. Nothing enters the ERP without confirmation.

What does the AI cost each month?

Little. In the prototype reading one email cost about $0.001 to $0.002, that is $1 to $2 per 1,000 emails. The real cost of the project is the connection to your ERP, which has a fixed price agreed upfront.

Does it read scanned PDFs or photos too?

PDFs with text are read directly. Scans and photos need an OCR step, which is added if your customers really use them.

Do my customers’ emails go to an outside service?

It depends on the choice you make at the start. With an outside AI service the text of the selected emails is sent to that service. If it must not leave, a model running on your own servers is used, on adequate hardware.

Do I have to change mailbox or ERP?

No. The mailbox is connected read-only and the ERP stays the one you have. The emails stay where they are.

Is it a ready product to install?

No. Inbox to Order is our prototype, with public code: it shows how it works. In your company it is built on your ERP, your codes and your rules.

Start with the problem

Tell us how many orders you receive by email and which ERP you use.

We tell you in writing whether automating them pays off and where to start.

  • The first check is free and commits you to nothing
  • Every message gets read, there is no call centre
  • Fixed price and payment by milestone
  • Italian and English, VAT invoices
  • No phone call unless you want one
  • If nothing should be built, we will say so

Prefer to write directly? [email protected]

No newsletter, no unsolicited calls. A direct reply from the developer, within one working day.