All insights

Sales order automation: getting orders into your ERP

Sales order automation means an order that arrives by email, from your web shop or over the phone becomes a sales order in your ERP without anyone retyping it, carrying the same customer account, prices and reference your team would have used. Done well, nobody downstream can tell whether a person or a system created it.

There are three common ways to get there: a connector app built for your ERP, a general-purpose automation tool, or a managed platform with an integration set up for you. Each is the right answer for some businesses. Whichever you pick, whether it works comes down to what gets mapped onto the sales order, what stays in the ERP and what happens when something fails.

If you use Unleashed specifically, our post on automating order entry into Unleashed goes into its fields and statuses in detail.

Where do sales orders come from before they reach the ERP?

Most wholesalers and distributors have at least three order channels, and they arrive in very different shapes:

  • Web shop orders are already structured. Every field has a name, the customer has paid or is on account, and the product codes are yours.
  • Emailed purchase orders are unstructured. A PDF from a buying system, a spreadsheet, a scanned form or a few lines typed into the body of an email, often using the customer’s own product codes.
  • Phone and counter orders are taken by your own staff, who know the products but still have to key the order somewhere.

The difference matters because a structured order can go almost straight into the ERP, while an emailed one has to be read, checked and matched first. Many automation projects stall because the tool chosen handles the first channel well and the second not at all.

Three ways to automate sales orders into an ERP

Native connector app General automation tool Managed platform
Typical set-up Install and configure Build your own flows Integration set up for your systems
Ongoing cost Monthly subscription Monthly subscription, often by volume Monthly price, scaling with order volume
Web shop orders Usually very good Good for simple cases Good
Emailed PDFs and spreadsheets Rarely covered Limited without extra services Designed for it
Checks before the order is created What the app offers What you build into each flow Whatever your process needs
Unusual business rules Hard to change Possible, but flows get fragile Set up in your integration
Who fixes it when it breaks The vendor Whoever built the flows The provider, as part of the monthly price

Native connector apps

Many ERPs and inventory systems have marketplace apps that sync orders from popular web shop platforms. If your orders come mainly from a supported web shop and land in a supported ERP, a connector is usually the cheapest, quickest and most sensible option. You get a maintained product and somebody else worries about API changes.

The limits show up at the edges. Connectors are built for the common case, so they tend to assume one warehouse, one price list and a straightforward mapping of shipping lines. They rarely help with emailed orders at all.

General-purpose automation tools

The “when this happens, do that” platforms are flexible and inexpensive to start with. For a simple rule, such as creating a sales order when a form is submitted, they work well, and someone in the office can often build it.

They become harder work as the rules pile up. Matching an email sender to a customer account, checking every line against stock and price, and holding an order for review all add steps, and a long chain of steps is difficult to test and easy to break silently. Pricing often rises with volume too.

A managed platform

A managed platform brings a ready-made core for reading, checking and approving orders, and an integration configured for your channels, your ERP and your rules. It costs more to start than installing an app, and the monthly price only makes sense if the volume and the awkwardness of your orders justify it. Where it earns its place is with emailed orders, customer-specific checks, and processes that no packaged connector quite fits. Ours starts with the Essentials plan at £295 a month ex VAT, plus setup from £1,500 ex VAT that the Growth plan waives, all on a 12-month minimum term.

What should be mapped on each sales order?

Whichever route you take, the quality of the result depends on field mapping. These are the fields that cause trouble most often.

  • Customer. The sender’s email address is not a customer account. The integration needs a reliable way to match the order to the right account, including branches and sites that share a parent, and a sensible route when no match exists.
  • PO reference. The customer’s purchase order number should land in whichever ERP field appears on your paperwork and can be searched. It is also the key for spotting the same order sent twice.
  • Delivery address. Use the address on the order, compared against the addresses held on the account. A new address should raise a warning for someone to check.
  • Product codes. Customers often use their own codes or descriptions. Map them to yours before the order is created, and keep the mapping so the next order from that customer matches automatically.
  • Prices. Decide whose number wins. Our default is the ERP price on the line, with any difference from the customer’s PO shown to a person before approval.
  • Warehouse or location. If you hold stock in more than one place, the order needs the right location from the start, or stock will be allocated from the wrong building.
  • Delivery charge. Map it to the ERP’s own delivery or freight line, not a made-up product, so it reports correctly. If the customer’s PO states a delivery charge, keep it visible so it can be checked against the real carrier cost later. Our post on checking carrier costs before invoicing covers that step.
  • Required date and instructions. Delivery dates and notes such as “tail lift needed” belong on the order where the warehouse will see them.

What should you leave to the ERP?

An integration should create sales orders the way your staff do, then step back. Leave these where they already live:

  • Invoicing and credit notes, raised by the ERP from the order as they are today.
  • Price lists, discounts and product data, maintained by your team in one place.
  • Stock allocation rules, unless there is a specific reason to override them.
  • Credit control, including account holds, which the integration can read but should not change.

Keeping the ERP as the system of record also gives you a safe fallback. If the integration were switched off, your team could key orders by hand again and nothing else in the business would need to change.

What happens when the ERP rejects an order?

Every integration fails sometimes. A product is discontinued between review and approval, an account goes on stop, or the ERP is briefly unavailable. Without good failure handling, your team will soon stop trusting the integration.

  1. Check before sending. Validate product codes, customer, stock and prices against live ERP data at review, so most problems are caught while a person is looking at the order.
  2. Never send twice. Record that an order has been created, with the ERP’s own order number, so a retry cannot produce a duplicate sales order.
  3. Make failures visible. A rejected order should sit in a clear list with the ERP’s reason, not in a log file nobody reads.
  4. Retry the temporary, stop on the permanent. Retry a timeout automatically. A closed account needs a person.
  5. Keep a full audit trail. Who approved the order, what was sent and what came back should all be recorded against it.

Which route fits your business?

If almost all your orders come from a web shop and your ERP has a well-reviewed connector for it, start there. If you have a handful of simple, structured triggers and someone who enjoys building flows, a general automation tool is a fair choice. If a large share of your orders arrive by email, need checking against customer prices and stock, and go to an ERP with its own quirks, that is where a managed platform usually pays for itself, and where avoiding double entry has the biggest effect on the office.

Our ERP integration page covers how the connection works, and pricing compares the three plans. If you’d like to talk through your own channels and ERP, a discovery call is the easiest place to start.