What happens between the inbox and the ERP
Orders arrive in many forms. One customer sends a PDF from their purchasing system, another writes three lines in an email, a third sends a scan or a photo.
Almost always the order carries the customer's item number, and your ERP doesn't know it. So someone looks up the matching item, checks price and stock and types in the lines. Then the order confirmation goes out.
Mistakes happen in familiar places: the wrong variant, pieces instead of boxes, a price from an old contract.
What your sales back office sees at the end
In the ERP there's a draft order with customer, items, quantities, prices and requested date. Uncertain lines are marked, so your team checks those and talks to the customer when something is unclear. The aim is that nobody types in order lines any more.
- Mailbox
- PDFs and scans
- ERP
The agent
Reads, matches, checks
customer item numbersterms
Your sales back office approves itOnly then does the order confirmation go out
Underneath, always
- AccessOnly the mailbox and the ERP areas you allow.
- GuardrailsRules it works within.
- LogEvery step written down.
This is how the draft comes together:
- The agent reads the order mailbox and separates orders from invoices, advertising and attachments such as terms and conditions.
- It recognises the customer by sender, customer number or delivery address and reads item, quantity, unit, requested date and the customer's order number.
- Using your list of customer item numbers, it matches each line to your item. If a match is new, it suggests one.
- It applies the price from the customer's terms, checks stock and delivery date and creates the order as a draft.
At first the agent only suggests. Nothing is booked until your sales back office has approved it.
Before you start, note how many orders and lines come in each day and how often they're corrected today. Then you'll see later what has changed.
What has to be in order first
The agent matches what's in your master data. So these points come before the first draft:
- Customer master. Every buyer with their email address, every customer with their delivery addresses.
- A list of customer item numbers. Which customer number belongs to which of your items? The list grows with every order.
- Units and packaging. The item master says whether an item is sold by the piece, the box or the pallet.
- Terms per customer. Prices and discounts the ERP can read.
- A rule for unclear cases. Who decides when a line doesn't fit, and by when?
If an agent already prepares your quotes, part of this is in place, because the customers and items are the same.
What your software can already do
Microsoft has built an agent like this into its ERP, Business Central. Here's what Microsoft says about it in public:
Microsoft Dynamics 365 Business Central. The Sales Order Agent monitors a mailbox and analyses customer requests sent by email. It looks up the customer in Business Central, reads order details from PDF, PNG and JPG attachments and checks availability.[1]
As its first step it always creates a sales quote, and a designated person reviews and approves outgoing messages to customers first.[1]
It recognises the customer only by the email address on the contact card. Among the supported languages Microsoft lists German for Switzerland (de-CH), and usage is billed in Copilot Credits.[1][2]
Source: Microsoft Learn
If you use another ERP, ask your vendor what your version can do today. If your ERP can already do the job, you don't need an extra agent for it. In the trial run we put in writing what your software already does on its own.
More guides
Sources
Sources checked in November 2026.
