Order processing

How to get emailed PDF purchase orders into Sage 50 without re-typing them

By · Published · Updated

Sage 50 has no web API, so nothing can push an order straight into it the way it could into Xero or Sage 200. Emailed PDF orders still get in without re-typing by one of three routes: an import file built from the PDF, Sage Data Objects under Sage's Developer Programme, or an established third-party connector. Whichever route you choose, a person should approve each order before it is written.

It is 7.40 on a Tuesday morning. Sandra has the order inbox open on one screen and Sage 50 on the other. The first email is from a café group, with a PDF purchase order attached. She opens it, finds the customer’s account in Sage and starts typing. Product code, quantity, tab. Product code, quantity, tab. The customer has written “semi-skimmed 2L x6”. Sage knows it by a different code, and after 14 years on the order desk Sandra knows which one. She checks the delivery day against the cut-off, which she carries in her head, saves the order and opens the next email. The warehouse cannot start picking until she has keyed them all.

Sandra is made up. Her inbox is not.

Sage 50 has no API, which is a way for one program to talk to another, so Sandra is the connection. On the assumptions further down, that costs 720 hours of her year.

Key facts

  • Sage 50 (UK) has no web API, so the routes in are Sage Data Objects under the Developer Programme, CSV and import tools, or third-party connectors.
  • ODBC, which lets other programs look at Sage 50’s data, is read-only and unsupported, so it cannot create an order.
  • Sales Order Processing is only in Sage 50 Professional, so your edition decides whether there is a sales order to create at all.
  • Reading the PDF and writing into Sage are two separate jobs, usually done by two separate pieces of software.
  • A person approving each order before it is written is what makes any of these routes safe.

Why does Sage 50 have no API, and why does it matter?

Sage 50 is desktop software. It keeps its data in files on your own PC or server, and Sage has never published a web API for it. Xero, QuickBooks Online, Business Central and Sage 200 each have one, which is why so many tools plug into them and so few plug into Sage 50. Sage’s own knowledgebase and integration specialists such as Hyperext describe the same position. There are three supported ways in. Sage Data Objects (SDO) is Sage’s official way for another program to read and create Sage 50 records. The product has its own file import. And a third-party product may already have done the SDO work for you. ODBC is read-only and Sage does not support it.

One Sage 50 user asked on Sage’s own forum how to “automate the process of manually entering sales orders from PDF purchase orders received via email” (Sage Community Hub). The replies were about Excel imports and OCR, which is software that reads text off a scanned page, because those are the tools that exist.

Two things follow for Linda, who owns the business and would pay for the fix. General-purpose connectors such as Zapier cannot reach a copy of Sage 50 running in her own office, however many other apps they list. And any product that promises to drop orders straight into Sage 50 is using one of the three routes above underneath. Ask which, because it decides what the product can and cannot do.

The Sales Order Processing module is only in Sage 50 Professional. If the firm runs Standard, Sandra’s orders go in as invoices. The routes are the same. The record is different. Our Sage 50 systems page covers the editions.

What are the realistic routes into Sage 50?

There are three ways to write an order into Sage 50 and one way to get the order out of the PDF in the first place. A working set-up pairs one of each.

Route What it is Suits
CSV and import tools Sage 50’s own import of CSV files, which are plain spreadsheet files, and the tools built around it (Adept Tools, PostTrans and Excel2Sage are the names that come up) that take a spreadsheet and create records Orders you already have in Excel, or can get into Excel cheaply
Sage Data Objects (SDO) Sage’s official way for another program to create and read records directly, licensed under the Developer Programme Made-to-measure work, higher volumes, anything that reads from Sage as well as writing to it
Third-party connectors Hosted services that have built on SDO and give other software a way to talk to Sage, or a plug-in for your web shop Web shops and online tools that expect the accounts software to have an API
Bespoke reader with human approval Software that reads the PDF, matches customer and products to your Sage records, and shows a person the result before writing through one of the routes above Emailed PDFs in several layouts, your own rules, the odd order that does not fit

What do CSV and import tools cost, and what is the catch?

The tools are licensed per user or per year and are the cheapest way in. The catch is that someone still has to produce the spreadsheet. That is easy when customers send Excel. Sandra’s customers send PDFs, so she would be typing each PDF into a spreadsheet, which is the re-keying you set out to remove. The other risk is silence. A column pointed at the wrong field creates a wrong order, and nobody notices until the customer rings.

What does Sage Data Objects cost, and what is the catch?

SDO needs membership of the Sage Developer Programme, which Sage prices at £3,438 a year plus VAT from 1 August 2026, plus a developer who knows it. Most firms get SDO access through a developer or a product that already holds membership, and do not join themselves. The catch is that SDO is Windows software that has to run on a machine with Sage 50 installed. It normally takes a Sage user licence while connected, and a Sage version upgrade can break it until the software is updated. It can do more than the other routes, and it needs an engineer behind it.

What do third-party connectors cost, and what is the catch?

Connectors are sold as a monthly subscription, and prices vary enough between vendors that we will not quote a figure here. They are the quickest way to connect a web shop or an online tool to Sage 50. The catches are that you add another supplier to the chain and your order data passes through their servers. If the connector does not carry something you depend on, such as a customer’s own product name or a carriage line, you have no way to add it.

What does a bespoke reader cost, and what is the catch?

A reader that takes PDFs from the order inbox, reads the lines, matches them to your accounts and products and lines them up for approval is usually a quick win at £1,500 to £3,000 for one kind of order into one system. Several customer layouts, customer-specific product names or rules such as cut-off times and minimum order values push it into the £3,000 to £7,500 band. Those are the rules Sandra carries in her head today. The reader writes to Sage through an import file or SDO, so it inherits that route’s limits. The catch is that PDF reading is never perfect. The approval screen, and somewhere for doubtful orders to wait for a person, are part of the build. Customers also change their PO layouts from time to time, which is what a support plan at £150 to £1,500 a month exists for.

How much time would it actually save? A worked example

Every number below is an assumption, labelled so you can swap in your own. The formula is Better Systems Co.’s own, and the ROI calculator does the arithmetic for you.

Assumptions:

  • Say Sandra keys 30 emailed PDF orders a day, five days a week, so 150 a week.
  • Each one takes her 6 minutes, including opening the email, finding the account and checking the codes.
  • 48 working weeks a year.
  • A cost to the firm of £16 an hour. Hull sales order processor roles are advertised at £12.21 to £15 an hour (Michael Page, Adecco), and £16 allows for employer costs on the upper figure.
  • After automation, she spends 1 minute approving each order on screen.

Hours spent keying today: 150 × 6 ÷ 60 × 48 = 720 hours a year.

Hours spent approving afterwards: 150 × 1 ÷ 60 × 48 = 120 hours a year.

Hours released: 600 a year, which at £16 an hour is £9,600 of capacity.

That £9,600 is capacity released, not cash saved. Sandra’s salary does not fall. What changes is that 600 hours of a trained person’s year become available for chasing late deliveries, ringing customers who have gone quiet, or clearing the pro-forma backlog. Linda has been trying to hire a second order processor and cannot find one. With 600 hours back, the desk may not need one.

Set against a build in the £1,500 to £7,500 range and a support plan, Linda can judge whether the project pays. At 10 orders a day the figures are a third of the size and the honest answer may be no.

A wholesaler that automates this also confirms orders sooner than one that types them, and customers notice.

What happens to an order the software cannot read?

It waits for Sandra, with the original PDF beside the best reading the software could manage. That rule is what makes the whole thing safe. The reader never guesses its way into Sage. An unknown product code, a missing quantity, a price that does not match the account’s price list, a duplicate PO number, a scanned image too faint to read. Each of these holds the order back and sends it to the person who would have keyed it anyway. On a good day nothing is waiting. On a bad day three orders are, and the other twenty-seven went through with one click each.

This is also why we would not let an AI model write to Sage directly. Models are strong at reading a messy PDF and poor at knowing when they are wrong. Ordinary software that follows your rules and uses a route Sage supports, with a person approving, is the safer arrangement. Our guide to what sales order processing automation is goes through where AI helps and where it does not.

What does Sandra’s Tuesday look like afterwards?

Same Tuesday, same 7.40 start. The overnight orders have already been read. Each is on her screen with the PDF on the left and the order as Sage will take it on the right, the café group’s “semi-skimmed 2L x6” already matched to her code. She reads down the lines and clicks approve. On the worked example’s assumptions, her 30 orders take half an hour, down from three hours.

Two orders are waiting with a flag, one with a product the software did not recognise and one under the customer’s minimum order. Those two needed her 14 years, and they get it. When she takes a week off, whoever covers the desk gets the same screen and the same rules.

What we would do

We would start with an automation audit at £500 to £1,250, credited against the build. We take fifty or so of your real PDF orders to find out how many layouts you receive, which Sage 50 edition and version you run, and whether an import file or SDO is the right way in at your volumes. You get the cost of the typing in pounds. Then we would build the reader and approval screen described on our sales order processing automation page, run it side by side with manual keying for a few weeks, and switch to approval only once accuracy on your own orders is proven. Still deciding whether the problem is big enough? Start with how to stop re-keying customer orders. If Sage 50 is one of several older systems you need to connect, see how to integrate a legacy system that has no API and our system integration service. Terms such as SDO and ODBC are explained in the glossary.

Sources

Questions people ask

Can Sage 50 import sales orders from a PDF directly?

No. Sage 50 cannot read a PDF on its own. Something else has to read the PDF and turn it into data, and that data then reaches Sage through an import file, Sage Data Objects or a connector. The reading and the writing are two separate jobs.

Does this work with Sage 50 Standard, or only Professional?

The Sales Order Processing module is only in Sage 50 Professional. On Standard there are no sales orders to create, so the same automation would create invoices or hold the order for a person to invoice. The routes into Sage are the same. Only the kind of record changes.

Will the automation need its own Sage user licence?

Usually yes, if it writes through Sage Data Objects, because the connection counts as a logged-in user. An import file is run by a member of staff under their own login. Check with your Sage reseller before buying, because it affects the running cost.

What if a customer changes the layout of their purchase order?

The reader will either still read it or will flag it as uncertain and hold it for a person. Nothing is written to Sage without someone looking at it. Updating the reader for a new layout is a small change, which is the kind of thing a monthly support plan covers.

Can AI just read the PDFs and type them into Sage for us?

AI models are good at the reading part, including messy or scanned PDFs. They should not be the thing that writes to Sage. That step belongs to ordinary software using a route Sage supports, with a person approving the order first. Treat the AI as a very fast reader, not as a clerk with the keys.

Related guides

Find out what the typing is costing you

A 20-minute call. You tell us about your Sandra, your Dave or your Phil, and how the job gets done today. We tell you honestly whether automating it would pay, and what it would cost.