It is Monday morning at a sixty-person contract manufacturer, and the customer service rep has twenty-two new purchase orders to enter before the production meeting at ten. Thirteen arrived overnight as PDF attachments, each laid out differently. Five are sitting in customers' supplier portals, which means logging in to each one, downloading the order and reading it there. Four came from a maintenance buyer who calls or texts and says "same as last time, but forty." Every one of them ends up typed into the ERP as a sales order, line by line, by the same person.
Entering an order is four questions, not one
"Enter the PO" sounds like data entry. It is four separate questions, and they need different things.
What are they asking for? Reading the quantity, the requested date, the ship-to and the customer's part number off whatever arrived. That is clerical, and it is the part software reads well.
Which of our parts is that? The customer calls it 44-1180 Rev C; you call it something else. Answering that needs a cross-reference somebody built and keeps up. It is a lookup, not a judgment, but only if the table exists.
Can we do it at that price and by that date? Is the price on the PO the one in the customer's agreement, is the account on credit hold, is there stock or capacity for the date they asked for? Those are rules, and they are your rules.
Should we take it as written? A rush order from a customer who is ninety days late paying, or a price that matches last year's quote but not this year's. That is judgment, and it is the one question that needs the rep.
Most of the rep's morning goes on the first two, which are the least skilled. The fourth gets squeezed into whatever time is left.
What Microsoft shipped for the first two
Microsoft's Dynamics 365 Business Central already had a Sales Order Agent, in preview from March 2025 and generally available from November 2025 by Microsoft's release plan, that reads customer emails and turns them into quotes and orders. An update on Microsoft's roadmap, listed as of October 2026 with status "Launched" and release phase "General Availability", extends it. A company can now run several agents, each watching its own mailbox with its own rules and its own counts of emails received, quotes and orders created, and time saved. The agent now matches requested items in layers: first an exact lookup on item number, vendor item number, GTIN or cross-reference, then attributes it extracts from the message such as color, material and size, then a broader fuzzy search. The page limit for PDF attachments rose from ten to fifty, and when an attachment is skipped, the reason is recorded on the attachment record.
Only Microsoft's own account of this was available; nothing here has been independently confirmed.
For a manufacturer already on Business Central whose orders arrive by email, that covers the first question well, the second as far as the cross-reference table allows, and part of the third. It is a real reason not to build anything.
What it does not reach
The roadmap item describes an agent that watches a mailbox folder. Orders sitting in a customer's portal and orders taken over the phone never arrive there. Microsoft's own documentation, as of October 2026, goes further on the third question: the agent can check stock for the requested quantity and date before adding an item, pass shortfalls to a reviewer and, if set up, work out the earliest ship date. Microsoft labels the page behind that check a production-ready preview. Neither source describes checking the price the customer wrote on the PO against their agreement, or the account against your credit rules; those still sit with a person.
That gap is what would have to be built, and it has three parts. The first is intake: a scheduled download from each customer portal you deal with, plus a short form the rep fills in after a phone order, so that every order lands in the same structured shape the email path produces. The second is the checks: each line's price against the customer's agreement, the account against your credit rules, and, for orders the agent does not handle, the requested date against stock and the schedule, with each result written on the order. The third is the exceptions queue: anything that fails goes to the rep with the reason attached, and everything that passes goes into the ERP as a draft order for a final look.
Nothing we found sells that for a company this size. Each portal belongs to a different customer, not to any ERP vendor, and the price, credit and scheduling rules are yours.
The hard part is the part number
Reading the PO is the easy part. The dangerous step is the match. A job shop lives on revisions, and a fuzzy match that finds Rev B when the customer ordered Rev C has not saved time; it has scheduled the wrong part. Microsoft's layered matching falls back to attributes and fuzzy search when an exact identifier is not found, which is helpful for a distributor selling catalog items and risky for a shop making to print. The cross-reference table is what keeps it on exact matches, and in our experience that table is half-built and lives partly in the rep's memory.
Who will push back, and why they are right
The customer service rep will push back, and they are right to. They know which buyer always sends last year's price, which "ASAP" means Friday, and which ship-to is wrong on every PO from one customer. None of that is written down. If an agent creates the orders, the rep will reopen every one to check it, and you will have paid for the work twice. The production scheduler will push back too, because a requested date accepted automatically becomes a promise they did not make.
The honest no: if you take fewer than about fifteen orders a day, mostly from a handful of customers, the rep is faster than anything you could build. If your cross-reference between customer part numbers and your own is not kept current, fix that first, because every version of this, bought or built, depends on it. And if nearly every order already arrives by email and you run Business Central, the shipped agent does most of the job and the rest is a few minutes a day by hand.
If this is your Thursday afternoon, the ten agent roles are in the Library.