Email and PDF orders straight into the ERP
Orders reach us as PDFs in four languages and we type them in again by hand.
- What we do
- An AI tool reads each order that reaches the mailbox, written in the email or in an attached PDF, checks it against your customers, your items and your price lists in the ERP, and proposes the order lines for a person to confirm.
- How we do it
- First we gather with you a sample of real orders from your customers, as they arrive, written in the email or in an attached PDF and in each language, together with each order as your team entered it in the ERP. We work out how the codes and descriptions each customer uses match the items in your ERP, and we write those matches down. Then we connect the tool to the mailbox where orders arrive and to the ERP, to read customers, items and price lists and to write the confirmed order. We test with the sample alongside your order processing team: we compare each proposed line with the one your team entered at the time, fix the matches that fail and, once the proposals line up, we start on real orders.
- What you receive
- The flow up and running: a person confirms each order instead of copying it.
- What changes for you
- Your order processing team stops copying each order by hand, line by line, in every language. Anything that does not match your customers, your items or your price lists arrives flagged before the order is confirmed, and no order enters the ERP without a person having confirmed it.
- What we need from you
- A sample of real orders from your customers, in every language and every form in which they arrive, with each order as your team entered it in the ERP; the code matches you already use, if you have them; access to the mailbox where orders arrive and to your ERP, to read customers, items and price lists and to write the confirmed orders; and one person from the order processing team who knows the customers and reviews the first proposals with us.
- Who it is for
- Order processing
- How you buy it
- At a fixed price, plus a recurring fee: the price and the fee are both written down before we start and we give them to you when you ask.
Example use cases
These are examples: they do not describe a real client.
An industrial valve maker in Italy with distributors in Spain, France and Chile
The situation
The distributors send their orders by email, each in their own way: some as a PDF their own system produces, others written in the email itself, in Spanish or in French, and almost always with their own item codes. The order processing team reads them one by one, looks up each code in a spreadsheet of matches and types every line into the ERP again. When a distributor uses an old code, the mistake comes to light once the goods have already left.
What we do
The tool reads each order, in Spanish or in French, and looks up the distributor, each item and its price in the ERP, using the code matches we wrote with the order processing team. The person sees the original order next to the proposed lines, confirms the ones that line up and corrects the flagged ones, such as an old code with no match. The confirmed order enters the ERP without anyone typing it in again.
A food wholesaler in Italy that sells to shops and restaurants in Spain and the United States
The situation
Many orders arrive as a list written in the email itself, in Italian, Spanish or English, with the product name instead of the code and no price. The order processing team has to guess which pack size of each product the customer wants and look up which price list applies to them, and now and then an order goes out with the wrong pack size.
What we do
The tool recognises each product by its name in the customer's language and looks it up among the wholesaler's items. When a name matches more than one pack size, the line arrives flagged with the possible pack sizes and the person picks the right one; if a name matches no item, the line arrives flagged too. The price comes from that customer's price list in the ERP, and the person confirms the whole order before it goes in.
Frequently asked questions
Can the tool misread an order?
Yes: it can misread a detail that looks right, such as a quantity. That is why the person sees the original order next to the proposed lines, and no order enters the ERP without their confirmation.
What happens when something does not match?
The order or the line arrives flagged with whatever does not match: a customer who is not in the ERP, a code with no match, a price that differs from your price list, or a quantity the tool cannot read. The person corrects what is flagged, and can confirm a price that differs from the list if it is the one agreed. A new customer is set up in the ERP as today, before their order is confirmed.
And if an email is not an order, or the document cannot be read?
The tool proposes no lines, and your team handles it as today. A change to an order already in the ERP, or its cancellation, is also handled by your team.
Do my customers have to change the way they send orders?
No. Orders keep arriving as they do today, written in the email or in an attached PDF. That is why the test is done with a sample of real orders from your customers.
Do I have to change my ERP?
No. The tool reads customers, items and price lists from your ERP, and writes the confirmed orders into it. Before we start we check that those data can be read from it and the orders written into it.
Where is the data processed?
In the AI service we choose with you before we start: the written scope says which one it is, in which region it processes the data and which data it receives. The account for that service is in your name from day one.