Solution · Sales
Orders that arrive already typed.
Your customers order the way they always have — a written email, a PDF from their own system, a photo of a paper form. That will not change, and it shouldn't have to. What can change is the part where someone in sales reads each one and retypes it into the gestionale. We read the order, match it to your catalogue and price list, and create it as a draft — so a person confirms instead of copying.
Free, 30 minutes, no obligation.
What gets automated
- Recognising order emails among everything else in a shared inbox
- Extracting customer, products, quantities, dates and delivery address — from text, PDF or photo
- Matching each line to your catalogue and the customer's price list
- Creating the draft in the gestionale and, where relevant, the e-commerce back office
The problem
Every customer orders differently. Sales retypes all of them.
A wholesaler's inbox on a Monday morning: a few orders written as plain text, a few PDFs generated by the customer's purchasing system, one photo of a paper order form from a customer who has never done it any other way. Each is a real order. Each is read by a person and keyed in by hand, line by line, before anything can be picked or shipped.
Today
- 1Orders arrive mixed in with quotes, complaints, newsletters and everything else in the shared inbox
- 2Someone in sales opens each one and works out what was actually ordered, in what quantity, for delivery where
- 3Products are looked up by description or by the customer's own code and retyped into the gestionale
- 4Prices are checked against the customer's agreement — or assumed to be right
- 5A wrong quantity or a similar-looking product code surfaces at dispatch, or when the customer calls
With Reviamo
- 1Order mail is recognised the moment it lands and separated from the rest of the inbox, whatever the format
- 2Customer, products, quantities, dates and address are extracted and matched to your catalogue and the customer's price list — an ambiguous code or an unusual quantity is flagged for a person
- 3The order is created as a draft; once confirmed, it flows to the gestionale and the e-commerce back office without being typed again
The customer keeps ordering by email. The order still ends up in your system. The only thing that disappears is the retyping in between.
How it works
Recognise, read, match — and a person who confirms.
-
1
Recognise
We connect to the mailbox where orders arrive — usually a shared one that also receives everything else. Each incoming message is classified: order, or not an order. Only the orders go further; the rest stays where it was.
-
2
Read
Whatever the format — text in the email body, a PDF attachment, a photo of a paper form — the order goes through document extraction that pulls out the customer, the product lines with quantities, requested dates and the delivery address. A PDF from the customer's own system reads cleanly; a photo depends on how it was taken, which is why every line is checked against the catalogue and that customer's order history before it is trusted.
-
3
Match
Each line is matched to your catalogue: by your product code, by the customer's own code where they use one, or by description. The price comes from that customer's price list, not from the email. A line that could mean two products is a flag, not a guess.
-
4
Confirm
The order is created as a draft. Anything clean is ready to approve in one click. Anything flagged — an ambiguous code, a quantity outside what this customer usually orders, a delivery address we have not seen before — is shown with the reason, and a person resolves it.
-
5
Create
The confirmed order lands in the gestionale as a real sales order, and in the e-commerce back office if that is where fulfilment runs. The original email and attachment are stored with a link back to the order, so the paper trail is there without anyone building it.
Illustrative run. Every row is a step the automation actually performs; the flagged one is what your sales team sees first.
Plugs into
Where orders arrive and where they end up
- Gestionali & ERP
- TeamSystem, Zucchetti, Danea EasyFatt, Fatture in Cloud, Odoo
- E-commerce back office
- PrestaShop, WooCommerce, Shopify, Magento
- Mailboxes & CRM
- Microsoft 365, Google Workspace, HubSpot, Pipedrive, Zoho
- Catalogue & price lists
- Your ERP, an exported CSV, or the spreadsheet sales keeps today — wherever they live
Not on the list? If it exports CSV or has an API, it is almost certainly fine. The one exception is SAP — we don't integrate with it, and we say so up front.
Who it's for
-
Wholesalers and distributors
Regular customers, recurring products, orders arriving by email every day of the week — and one or two people keeping up with them.
-
Manufacturers selling to trade
Customers with their own product codes and their own order forms, which nobody is going to persuade them to stop using.
-
Companies running B2B on PrestaShop or similar
Some customers order on the site; the ones who matter most still send an email. Both should end up in the same back office.
-
Agents and sales teams on the road
Orders taken on paper or by phone and sent in as a photo or a note. They should be in the system before the agent is back in the car.
Questions
The questions people ask about order automation.
Do our customers have to change how they order?
No, and that is the point. They keep sending emails, PDFs and photos exactly as they do now. The automation adapts to what arrives; it does not ask the customer to fill in a portal or use a template. A customer who has always ordered on the same paper form will not notice anything different.
How does it know which emails are orders?
Each incoming message is classified before anything else happens — by sender, subject, content and attachments. A customer's regular purchasing address is a strong signal; so is a PDF that looks like a purchase order. Anything uncertain is left in the inbox for a person rather than treated as an order. We tune this on your real mail during setup, not on examples.
How well does it read a photo of a paper form?
A clear photo of a printed form — flat, in focus, the whole page in frame — reads well. A poor one is not guessed at: any line that cannot be read with confidence is flagged in the draft with the reason, the same way a code that matches two catalogue items is, and the rest of the order is matched normally. Handwritten quantities and codes are always confirmed by a person before the order is created, because a misread figure can look perfectly plausible. Whatever the source, every line is still matched to the catalogue and checked against what that customer usually orders. A person picks the right item once, and the next time that customer uses the same code it can be remembered.
Can it also read invoices, or is that a different setup?
It is the same extraction mechanism pointed at a different document and a different system. This page is about sales orders going into the gestionale; how supplier invoices are matched to purchase orders is the sibling process on the purchasing side, and the two are naturally built together.
Our orders also need a confirmation or a delivery note sent back. Is that included?
It can be. Once the order exists as a structured record, generating the order confirmation, the delivery note or a proforma from it is a short additional step — see documents generated from the records you already have. Whether it is in scope is something we decide in the audit, with a fixed price.
How long does it take to set up, and does it run alongside what we do now?
We start with a free consultation, then a paid process audit that ends in a fixed price. The first order pipeline runs in parallel with manual entry until your sales team trusts it — drafts are created, people compare them against what they would have typed, and only then does manual entry stop. The steps are described on how we work.
Related solutions
What an order feeds, and the mechanism it shares.
Finance
Supplier invoice automation
The same reading-and-matching mechanism on the purchasing side. If orders are already going into the gestionale cleanly, the supplier invoices that follow have something exact to be matched against.
Read moreOperations
Documents that write themselves
A confirmed order is a structured record — which means the order confirmation, delivery note and any certificate the customer asks for can be generated from it rather than typed a second time.
Read moreAll solutions
See everything we automate
Six of the processes we're asked for most, each compared before and after.
Back to services
Free consultation
Tell us how orders reach you, and who types them in.
Tell us how orders usually arrive and roughly how many a week, and thirty minutes online is enough to say whether reading them automatically is worth it. No preparation needed.