For manufacturers and distributors: customer orders from any inbox, entered in your ERP without retyping. Your team only checks the lines Mirage cannot confirm.
Mirage Metrics builds and operates AI agents that enter customer orders in a manufacturer's or distributor's ERP. PDFs exported from a customer's ERP, Word tables, scanned forms, plain email text: today someone reads each order and keys it in by hand.
An order arrives by email: a scanned form from a customer's purchasing office. The agent reads it, finds the customer in your file, matches each line to your catalog, works out a missing unit from the price and applies the customer's discounts. The confirmed order is written into the ERP. A line it cannot confirm goes to a person, with the original document attached and a suggested fix.
The email and its attachment, in whatever format the customer sent: PDF, Word or ODT table, scan or plain text.
The customer and every line against your customer file and catalog: exact, then close, then by delivery address.
Units inferred from the price, then warehouse, document series and cascading discounts.
The order is created in the ERP through its API. A line that cannot be confirmed goes to a person, with a diagnosis and a suggested fix.
Biodéal, an organic dairy distributor supplying retail chains, bakeries and wholesalers, has its customers' email orders entered in SAP Business One. John Cockerill, an industrial engineering group, has its fabrication bills of materials drawn from its piping drawings.
Median seconds from order email to order ready in SAP
Orders processed automatically
Order lines entered automatically
Of orders flagged for a human check
Biodéal, figures since go-live on 22 July 2025, the date of the first real order processed.
“The involvement of the forward-deployed engineers helped us get our agent up and running smoothly, which let us start benefiting from it as fast as possible.”
Also in production at
Mirage connects directly to the systems you already run. No ERP migration required.
Dynamics
Where a documented interface exists, Mirage connects to it. Where none exists, our engineers build the connector during deployment.
The same five steps for every deployment, in every sector.
TimelineMost deployments go live in 4 to 6 weeks. Parallel processing during the first two weeks confirms accuracy before full cutover.
Engineers spend time with operational teams before writing anything, to see how work is actually done.
Time with the people who enter orders today.
Workflows, exceptions, data sources, manual validations and escalation points get identified with your team.
Your order channels, customer formats, exceptions and the checks your team does by hand.
Systems get designed around the constraints observed on site, not an idealized process diagram.
Real orders, and access to your ERP through its API, EDI or flat files.
The system runs in production with human supervision and feedback loops from day one.
People to review the orders routed to them.
Once a workflow is trusted, the same engineering team moves to the next one.
The next workflow you want to hand over.
Access permissions, validation workflows and audit logs remain fully controlled by your organization. Signed NDA on request.
Cloud, private cloud, your own cloud account, sovereign cloud, on-premise, or edge and offline environments.
Role-based access, human approval flows and configurable autonomy for each workflow.
Full audit history, with every agent action traceable to the input and the rule that produced it.
The same platform, on the other documents a manufacturer or distributor runs on.
Piping, boilermaking and structural steel drawings measured and turned into separate MTO and BOM outputs, with no 3D model to rebuild first.
At John Cockerill: a fabrication bill of materials ten times faster.
Once the order exists in the ERP, the confirmation can go back to the customer automatically, with no manual entry.
A direct API connection where the ERP has one, EDI or flat files where it does not. No ERP replacement and no migration.
AI order entry automation is software that reads incoming purchase orders from any channel (email, PDF, EDI, or phone), extracts the required fields, validates them against ERP master data, and creates confirmed order entries automatically without manual data entry.
At Biodéal, Mirage reads a Microsoft Outlook inbox through Microsoft Graph: every incoming email starts processing within seconds, a queue absorbs volume spikes, and each processed email is tagged in Outlook so the team sees what has been handled. Another mailbox or a customer portal is connected the same way as an ERP: through its documented interface where it has one, and otherwise through a connector our engineers build during deployment.
Mirage reads documents in the formats and languages they arrive in. At Biodéal, in France, orders arrive in French, each customer with its own layout and quantity conventions. Mirage has clients in France, Spain, Morocco, Egypt, Saudi Arabia and the United States, and offices in Paris, Barcelona and Casablanca.
OCR converts document images to text but does not understand what the data means. RPA follows fixed scripts that break when formats change. Mirage reasons over document content, handles format variability natively, and connects directly to your ERP via API rather than through screen automation. See the full AI agents vs RPA comparison
Most deployments go live in 4 to 6 weeks. Mirage connects to SAP, Oracle, Microsoft Dynamics and the other ERPs listed on this page through their documented interfaces, and where none exists, our engineers build the connector during deployment. Parallel processing during the first two weeks confirms accuracy before full cutover.
Mirage connects to the ERP you already run through the interface it documents: an API where there is one, EDI or a flat file import where there is not. In production today, it writes orders into SAP Business One through the Service Layer at Biodéal. The SAP and Dynamics 365 pages describe how the connection works with each of those systems.
At Biodéal, an organic dairy distributor running SAP Business One, the median time from an order email arriving to the order being ready in SAP is 48 seconds. About 7 percent of orders are flagged for a human check; the rest go from inbox to ERP with no manual entry: 2,943 orders and 12,993 lines since July 2025.
A line Mirage cannot confirm never blocks the whole order and never disappears. The other lines are entered in the ERP, and the doubtful one goes out as an alert, as soon as the email is processed, with the original document, a diagnosis and a suggested fix. At Biodéal, the sales administration team picks it up: it completes the line in SAP or corrects the customer's rule, then reprocesses the original email through a tool that runs the same checks as production. That is about 7 percent of orders.
Mirage layers on top of your existing ERP through API or EDI integration. There is no replacement, migration, or modification of your current systems. The agent reads from and writes to your ERP without changing how it works.
Mirage is built for manufacturers and distributors who receive high volumes of purchase orders from multiple customers in multiple formats. HVAC distributors, industrial suppliers, MRO distributors, building materials companies, and electrical distributors are among the primary use cases.
Mirage is deployed within your existing operational environment and integrates with your current systems without requiring an ERP replacement. Access permissions, validation workflows, and audit logs remain fully controlled by your organization. Every action performed by the agent is traceable and can be reviewed at any time. See how order exceptions are handled before ERP entry
Mirage will map the workflow, identify what can be automated and define the fastest path to production.
Tell us where your team loses time. We send back which workflows are worth automating, what a deployment involves on your systems and the shortest path to production. No commitment.
30 minutes with a Mirage engineer.
