Manufacturing / Dynamics 365 order automation
Dynamics 365 order entry automation
For teams on Dynamics 365 Supply Chain Management who still key email and PDF orders into sales orders by hand. Mirage reads each order, resolves the customer, the items and the units against your Dynamics master data, and creates the sales order through the standard sales order entities, with every doubtful line held for a person.
The same order-reading layer runs on SAP Business One at Biodéal.
The reality
Customer orders arrive as PDFs and emails in every layout. Someone opens each one, finds the customer account, translates the customer's part numbers into your item numbers, checks units and prices, and types the lines into a sales order, one order at a time.
What Mirage does
Email orders into Dynamics 365 Supply Chain Management
Mirage sits in front of Dynamics, not inside it. It reads the order, resolves it against your master data and creates the sales order through the interfaces Microsoft documents.
Standard sales order entities
Header and lines are created through the sales order header and sales order line data entities over OData, as a Microsoft Entra application registered in Dynamics and tied to a dedicated service account. High volumes can go through the batch data API instead.
Your customers' item numbers
Supply Chain Management keeps external item numbers per customer. The agent uses them, with your units and prices, to turn a line written in the customer's terms into your item. From version 10.0.45, order lines can also be looked up by the external number.
Exceptions held, not guessed
A line with an unknown item, a unit with no conversion or a price outside the agreement is held back with the reason. The review gate Supply Chain Management provides is the order hold, which stops the warehouse from processing the order.
Which Dynamics 365, and what to settle first
Dynamics 365 names several products. This page covers Supply Chain Management, part of Microsoft's finance and operations apps.
Business Central is a different ERP
It has its own API, with sales quotes and sales orders, and Microsoft ships a Sales Order Agent for it that reads a mailbox and always starts with a sales quote. On Business Central, evaluate that agent first.
Dynamics 365 Sales is not the ERP
It is the customer engagement app, built on Dataverse. Alongside Supply Chain Management, inventory and fulfilment stay in Supply Chain Management and sales invoices are created there, so orders are written where fulfilment happens.
Throttling and versions
Supply Chain Management applies service protection limits and answers 429 with a Retry-After header when a limit is reached; the integration waits and tries again. Check your version: features such as the lookup by external item number depend on it.
How the hold is set
Microsoft's public documentation shows no data entity for applying an order hold through the API, so the review gate is agreed with your partner: a hold applied by a rule in Dynamics, or a review step before the order is created.
WHICH DYNAMICS 365
Which Dynamics 365 product, which interface, which review gate?
Three Microsoft products carry the Dynamics 365 name and a different answer each. Every fact in the table is from Microsoft's own documentation, read on 5 October 2026; Mirage has no Dynamics 365 deployment published and says so.
| Product | What it is | Order interface | Review gate | What to do |
|---|---|---|---|---|
| Dynamics 365 Supply Chain Management | The ERP, part of the finance and operations apps | Sales order header and line data entities over OData, as a Microsoft Entra application; the batch data API for high volume | The order hold, which stops the warehouse; no documented entity to apply it through the API, so the gate is agreed with your partner | This page: Mirage reads the order and writes it through the entities |
| Dynamics 365 Business Central | A different ERP, with its own API | Sales quotes and sales orders through the Business Central API | Microsoft's Sales Order Agent reads a mailbox and always starts with a sales quote | Evaluate Microsoft's agent first; Mirage can sit in front of the API where it does not cover your formats |
| Dynamics 365 Sales | The customer engagement app on Dataverse, not the ERP | Not where orders are fulfilled; dual-write links it to Supply Chain Management | n/a | Write orders where fulfilment happens, in Supply Chain Management |
Check your version before the pilot: the lookup of order lines by external item number, for example, is documented from 10.0.45.
The output
Dynamics 365 order entry, field by field
An illustrative order, with invented values.
| Field | On the purchase order | In the Dynamics sales order | Status |
|---|---|---|---|
| Customer account | Buyer name and VAT number | Customer US-0412 | Matched |
| Delivery address↳ The order carried no address code. Its delivery address matched one of the customer's addresses exactly. | Plant 2, receiving dock | The customer's second delivery address | Matched by address |
| Line 1 | Customer ref. 88-120-B, 40 | Item 4000217, 40 ea | External item number |
| Line 2↳ The customer ordered in boxes and the item has no conversion from boxes. The line is held with the reason instead of a guessed quantity, and the other lines are created. | Bearing 6204 2RS, 12 boxes | No box-to-each conversion for this item | Held for a person |
Proof
Order entry automation in production, on another ERP
Mirage has not published a Dynamics 365 deployment. The order-reading layer is the one running at Biodéal, an organic dairy distributor, on SAP Business One.
Biodéal (SAP Business One)
48 seconds median from email received to order ready in the ERP
2,943 orders created automatically, from 113 distinct customers
About 7% of orders flagged for a person to check
Dynamics 365 order entry, on your own orders
Send us a batch of real customer orders and tell us your Dynamics 365 product and version. We come back with each one as a sales order, field by field, with what we would hold flagged, and what the connection involves on your environment.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
FAQ
Frequently asked questions
Put a layer in front of Dynamics that reads incoming orders, resolves customers, items and units against your master data, and creates the sales order through the sales order header and line data entities, as a Microsoft Entra application registered in Dynamics. Lines it cannot resolve are held for a person with the reason.
Dynamics 365 Supply Chain Management, part of the finance and operations apps. Business Central is a different ERP with its own API, and Microsoft ships a Sales Order Agent for it: evaluate that first. Dynamics 365 Sales is the customer engagement app, not the ERP where orders are fulfilled.
Mirage has not published one. Its order entry deployment in production is on SAP Business One at Biodéal. The reading and matching layer is the same; the writing side follows the interfaces Microsoft documents for Supply Chain Management.
Yes. Supply Chain Management's order hold stops the warehouse from processing an order until the hold is cleared. Microsoft documents no data entity for applying a hold through the API, so the gate is agreed with your partner: a hold rule in Dynamics, or a review step before the order is created.
A Microsoft Entra application using client credentials, registered in Dynamics in the Microsoft Entra applications form and tied to a dedicated service account, with security roles limited to the customer, item and sales order data the workflow uses.
A proof of concept on your own orders one week after the first meeting, and the first workflow in production in 4 to 6 weeks. Work spanning several systems can take longer and is scoped at the first meeting.
A fixed-price pilot on a batch of your real orders first, which you can stop after. Then an annual subscription priced by volume, quoted in the first conversation.