Skip to content
DT Nova
Document workflow automation

Sales order automation: customer orders from inbox to ERP

Sales order automation removes the retyping from your order desk. Customer orders that arrive by email, PDF, Excel, portal or structured message are read, the customer's item codes are mapped to yours, prices, stock, delivery dates and credit are checked, and a sales order is created in your ERP with the confirmation sent. Your team handles only the orders that fail a check. We build order processing automation around the ERP you already use, hosted in the EU, and your company owns the code.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

An order desk, before and after

A typical wholesale or manufacturing order desk receives orders in every shape: a PDF purchase order from a large customer's procurement system, a photo of a handwritten list, an Excel file, a few lines in an email body, a reorder through a portal. Each one is read by a person and typed into the ERP line by line, with the customer's item codes looked up in a spreadsheet. Busy mornings create a backlog, errors in quantities and codes turn into wrong deliveries, and confirmations go out late.

StepManual todayAutomated
IntakePersonal and shared inboxesOne order queue for email, attachments, portals and EDI or Peppol messages
ReadingA person reads every orderCustomer, addresses, items, quantities and dates extracted with a confidence score
Item codesLooked up in a spreadsheetMapped from the customer's codes to yours, learned once and reused
ChecksWhen the order looks oddAgreed prices, minimum quantities, stock, delivery dates and credit limit
EntryTyped line by lineSales order created through the ERP interface
ConfirmationWritten when there is timeOrder confirmation sent with any changes highlighted

Sales orders are one of the document flows in our document workflow automation work; this page covers the order desk in detail.

What we build

Structured orders first

The order that needs no reading is the best one, so structured channels come first. Large customers often send EDI or can send Peppol orders. The Peppol BIS Ordering 3.3 specification describes a buyer issuing an electronic order that the seller may accept, accept with changes or reject, with reasons, so the buyer can issue a new order; it also lets the buyer give the information the seller is required to place on the invoice, to help automate invoice processing at the buyer's end (OpenPeppol, read on 12 November 2026). We connect those channels where they exist and use AI extraction for the email and PDF orders that remain, which in many companies is still the majority.

The invoice that follows the order matters too. Under the EU VAT in the Digital Age directive, invoices are to be issued as electronic invoices complying with the European standard from 1 July 2030 (Directive (EU) 2025/516, read via the EU Publications Office on 12 November 2026). Order data captured cleanly at the start, with the customer's reference, makes the structured invoice at the end straightforward.

Accuracy, honestly

How many orders go straight through depends on your customers: how many send structured messages, how consistent the PDFs are, and how many order with free text. We do not quote a rate before seeing your orders. The test version runs last month's real orders, and you see per field how often the value was right, how many orders needed a person and why. You set the threshold for automatic creation, and you can start with every order passing review and loosen it as the numbers show it is safe.

Some checks are better as rules than as AI: a price either matches the agreement or it does not. We keep the model for reading and use plain rules for checking, because rules are faster to run and easy to explain to the order desk.

Ready-made order automation or custom?

There are good products for order capture, such as Esker, Conexiom and the order modules of document AI platforms, and ERP vendors increasingly add their own. For a standard setup one of them may be the right choice. Custom automation pays off when your pricing agreements, customer codes, routes and ERP customisations are what the product cannot model, or when you want the flow and the data in your own account.

SituationReady-made order captureCustom automation
Standard ERP, few special rulesUsually a good fitRarely worth building
Customer-specific prices, packs and routesPartly configurableYour rules, as written
Customised or industry ERPConnector may be missingBuilt on the interfaces you have
Pricing modelPer document or subscriptionFixed price for the agreed scope, then maintenance
Data location and ownershipThe vendor's platformYour account, EU data region

If your customers would rather order themselves, a portal can complement the automation; see B2B ecommerce solutions. For automated replenishment orders from your own stock levels, see inventory management software.

How we build it

  1. Walk the order desk. Channels, order types, checks and ERP entry, mapped with the people who do the work today.
  2. Scope and fixed price in writing. Channels, rules, the ERP integration and what the first phase leaves out, with a fixed price for that agreed scope.
  3. A test version on real orders. Last month's orders run through intake, extraction, mapping and checks, with accuracy shown per field.
  4. Pilot and acceptance. One customer group or channel runs with every order reviewed, and the phase is accepted against the written scope.
  5. Roll out and measure. Time from order to confirmation, orders touched by a person and order errors compared with the numbers recorded at the start.
  6. Maintenance. Updates, monitoring, new customers and rule changes on a monthly plan you can cancel with one month's notice.

As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your name in an EU data region. The purchase side of the same chain is covered by accounts payable automation, and the interfaces by API integration. See prices.

Questions we get

What is sales order automation?

Software that turns incoming customer orders into sales orders in your ERP without retyping. It reads orders from email bodies, PDF and Excel attachments, portals and structured messages, maps the customer's item codes to yours, checks prices, quantities, delivery dates and credit, creates the order and sends the confirmation. People review only the orders that fail a check.

Can it read orders that every customer formats differently?

Yes. That is the reason to use AI extraction rather than a template per customer. The model finds the customer, delivery address, items, quantities and dates in each layout, and every value carries a confidence score. Orders below the threshold go to the order desk for a quick check with the original next to the extracted data.

How does it know our item codes?

From a mapping table that grows with use. Customers often order with their own article numbers, old codes or descriptions. The system looks up earlier mappings, suggests a match for new ones, and a person confirms it once. The next order with the same code goes through without help.

What happens when the price on the order is wrong?

The order stops in review with the difference shown: the customer's price, your agreed price list and the rule that applies. Your team decides whether to accept, correct or ask the customer. Nothing with a price difference above your tolerance posts on its own.

Which ERP systems does it work with?

Any ERP with an interface, which covers most of them, including Microsoft Dynamics 365 Business Central, SAP Business One and S/4HANA, NetSuite, Odoo and many industry systems. Orders are created through the ERP's own interface, so its pricing, stock and credit logic still applies.

Is this the same as order management software?

No. Order management software runs the whole order lifecycle, often for ecommerce. Sales order automation sits in front of the ERP you keep and removes the manual entry of orders that arrive by email, PDF and portals. For an ordering portal for business customers, see our B2B ecommerce work.

Who owns the system?

Your company. The source code sits in a repository in your own account, and the database and hosting are in your name in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote