The PO itself is the easy part. Any half-decent system can raise a PO. The real problem is the supplier price list: 40 suppliers, 40 different CSV formats, prices changing quarterly, contract rates that diverge from list rates, and a buyer trying to know whether the £4,000 going out today is the agreed price. Automate the PO without solving that and you have built a faster way to overpay. Here is what costs what, and where Tradogram or Procurify stops being enough.
Most UK SMEs do not have a PO problem. They have a supplier-price-list problem with a PO symptom. The shape repeats: the buyer raises a PO using last quarter's price list, the supplier accepts at the current (higher) price, the GRN matches the quantity, the invoice comes in 4 percent higher than the PO, the AP clerk pays it because the variance is below the chase-threshold, and a year of those silent 2-to-5 percent drifts is the difference between profit and loss.
The arithmetic that makes PO automation pay back: on a £3m a year procurement spend, a 2 percent silent price drift is £60,000 a year leaking. The investment to fix it (live supplier price lists, variance flagging at PO time, three-way matching at invoice time) is £8,000 to £20,000 one-off, and a small monthly run cost. The payback is usually under a year, and the second-order benefit (buyers stop being scared of catching price changes) compounds.
Before any procurement automation, there are usually two workbooks taped together. The first is the supplier price list workbook. The second is the open-PO tracker. The shape:
This pair of workbooks breaks at: 500+ active POs a year, multi-branch ordering, any supplier that changes their price-list format, any quarter where the rebate calc is queried by a supplier, and the moment the buyer goes on holiday and the next person cannot find the latest version on SharePoint.
These are illustrative shapes drawn from UK SME workflow patterns. The fixed-quote bands are the real ranges we quote for builds of this shape; the workflows described are the patterns that fit each context. The pattern that creates payback is volume of POs times average margin compression from price drift, plus the cost of stockouts when the buyer is too busy chasing PO admin to spot a supply problem.
Profile: a £6m turnover groundworks contractor raising 80 to 200 materials POs a month across 25 to 40 merchants and specialist suppliers. Prices move on steel, timber, aggregates, fuel constantly. The shape that fits: PO automation that pulls latest merchant prices (often by scraping the supplier portal, sometimes by EDI where available), checks each PO line against current price, flags variance against the project budget, ties materials cost back to the job-costing system. Typical band: £8,000 to £15,000 fixed quote. Expected outcome: routinely catches £20,000 a year of price drift on a £2m materials spend.
Profile: a 4-site restaurant group ordering fresh produce, dry goods, drinks, cleaning chemicals from 30+ suppliers daily. Most still ordered by WhatsApp or phone, with PO paperwork done retrospectively. The shape that fits: an automation that gives each head chef a tablet PO form pre-populated with their site's standard order, pulls supplier prices nightly, runs the order through approval, reconciles against the delivery note. Typical band: £10,000 to £18,000 fixed quote. Expected outcome: cuts food cost percentage 1 to 3 points, which on a £4m food revenue is £40,000 to £120,000 of margin.
Profile: a 5-home care group ordering PPE, incontinence products, medical consumables, food, and household goods across multiple suppliers, against tight budgets per home. The shape that fits: PO automation that enforces per-home spend limits, requires a registered manager approval over £500, splits cost coding by home for the management accounts, and reconciles against goods-in to catch supplier short-deliveries (a chronic 1 to 4 percent leakage in this sector). Typical band: £8,000 to £14,000 fixed quote. Expected outcome: registered managers stop spending evenings chasing supplier orders.
Profile: a light engineering or food manufacturer with 40 to 200 active SKUs needing raw materials POs tied to the production schedule, the BOM and supplier MOQs. The shape that fits: an automation that looks at the schedule, the BOM explosion, current stock, supplier lead times, and either suggests POs the buyer approves or auto-raises within agreed limits. Typical band: £12,000 to £22,000 fixed quote. Expected outcome: cuts emergency air-freight on missed parts (a chronic hidden cost) and reduces working capital tied up in over-stocked components.
Profile: a regional builders' merchant or plumbing wholesaler with 3 to 8 branches and 5,000+ SKUs running a reorder process that is part-spreadsheet, part-buyer-instinct, part-supplier-rep-phoning. The shape that fits: PO automation that looks at sell-through per branch, lead times, MOQs, rebate thresholds (it pushes you over the rebate line on purpose where it pays), suggests POs ranked by margin impact. Typical band: £12,000 to £25,000 fixed quote. Expected outcome: cuts dead stock 15 to 30 percent, lifts in-stock rate on top sellers, recovers six-figure rebate income that was previously left on the table.
Four routes get you to PO automation. The honest comparison, without the vendor pitches:
| Route | When it fits | Real cost |
|---|---|---|
| DIY (Xero PO, QuickBooks PO, a shared spreadsheet) | Sub-50 POs a month, a handful of suppliers, single site, one approver. Genuinely fine at small scale. | £0 to £30/mo (included in accounting subscription) |
| Mid-market procurement SaaS (Tradogram, Procurify) | 50 to 500 POs a month, multi-approver, multi-site, you want an off-the-shelf approval workflow and supplier catalogue. Solid step up from spreadsheets. | £20 to £100/user/month |
| Enterprise procurement (Coupa, SAP Ariba) | £20m+ procurement spend, regulated industry, dedicated procurement team, multi-country. Real capability, real cost, real implementation. | £40,000 to £200,000/yr |
| Low-code (Power Automate + SharePoint, Power Apps) | You are Microsoft 365, you have an internal owner. Works well for approval flows, less well for supplier-price-list automation. | £8,000 to £25,000 build + licences |
| Custom build (us, or an equivalent shop) | You have specific rules the SaaS does not handle (multi-branch stock replenishment, project-specific budgets, rebate-aware ordering, multi-supplier price reconciliation, sector logic like CIS retention or care-home cost coding). | £4,000 to £25,000 fixed quote |
We turn down PO automation work that does not fit. The patterns:
"A procurement system that handles all our spend categories." Office supplies, materials, services, capital equipment, marketing, software, energy: these are completely different procurement workflows. Trying to build one system for all of them produces a tool nobody uses for anything. Pick the category where the leakage is largest and build for that.
"Auto-raise POs from the stock system without a buyer in the loop." The pattern works in narrow cases (replenishment of staple SKUs with stable demand and reliable suppliers). Outside those, automated POs raise problems faster than they save time: bad demand signals cause over-ordering, supplier price drift goes unchecked, missed seasonal patterns leave stockouts. Keep a human in the loop, make the loop fast.
"Force every PO through the same approval workflow." A £200 stationery order does not need three sign-offs. A £40,000 plant order needs more than one. The good PO automations have tiered approval rules with auto-approve thresholds, contract-rate auto-pass, and exception escalation. The bad ones grind to a halt because somebody copied an enterprise template.
Every project is scoped and fixed-quoted before any work starts. The bands below are the real ranges we quote for builds of this shape.
| What it is | Timeline | Fixed quote |
|---|---|---|
| Small focused PO workflow (one supplier list, one approver tier) | 2 to 4 weeks | £3,000 to £8,000 |
| Multi-supplier PO with price-list automation | 3 to 6 weeks | £4,000 to £12,000 |
| PO assistant with approval routing and exception queue | 4 to 8 weeks | £6,000 to £15,000 |
| Procurement portal with three-way match and rebate tracking | 6 to 12 weeks | £12,000 to £40,000 |
| Ongoing tech partnership (we run, monitor, improve) | Monthly, no lock-in | £450 to £1,500 / month |
The shape of an engagement is on the AI implementation page. The ongoing version, where we keep your procurement automation tracking supplier price changes as they happen, is on the tech partnership page. Bigger custom portals are on app builds and the broader portfolio is on projects.
POs sit upstream of AP and downstream of demand planning. The two guides that come up most often in the same scoping conversation:
A focused PO automation that takes a request, runs an approval, raises the PO into your accounting or ERP system and tracks goods-received runs £4,000 to £12,000 fixed-quote. A bigger build that adds a supplier-price-list workflow, multi-branch logic, three-way matching against invoices and a supplier portal is £8,000 to £25,000. Tools like Tradogram or Procurify sit at £20 to £100 per user per month. Enterprise procurement platforms (Coupa, SAP Ariba) start at £40,000 a year and assume you have a procurement team to run them.
For a small business raising 5 to 50 POs a month with a simple supplier list, the built-in PO in Xero or QuickBooks is genuinely fine. You hit the wall when you need supplier-specific pricing (contract prices vs. list prices, volume rebates, regional rate cards), real approval workflows beyond one approver, or three-way matching at scale. A dedicated tool (Tradogram, Procurify) or a custom build is the answer at that point.
Three-way matching means the PO, the goods-received note (GRN) and the supplier invoice all agree on what was ordered, what was delivered and what was billed. You need it the moment your supplier invoice volume crosses 200 a month or your spend leaks become visible (delivered short, billed full; price drift between PO and invoice; missing receipts). Without it you are paying for goods you may not have received and accepting price increases nobody approved. The automation is straightforward; the discipline of capturing GRNs at the point of delivery is the harder part.
A single-supplier-list focused build ships in three to five weeks. A multi-supplier, multi-branch automation with approval routing and three-way matching takes six to ten weeks. The blocker is rarely the build. It is supplier data: getting current price lists from 30 suppliers in usable formats, normalising part codes across them, and agreeing the rules when a supplier changes their pricing format mid-year.
Yes, and this is where the highest payback sits. A wholesale distributor with 3 branches and 8,000 SKUs runs reorder spreadsheets that break every month. The custom automation pulls stock levels per branch, last 90 days of sales, supplier lead times, MOQs, and recommends a PO the buyer approves with one click. Routinely cuts dead stock 15 to 30 percent and reduces stockouts on top-selling lines simultaneously. The off-the-shelf procurement tools are not built for this; they are built for office-supply ordering.
It has to. Raising POs in a separate system that does not write back to Sage 200, Xero, NetSuite or your industry ERP is worse than no PO system because you now have two sources of truth. Every PO automation we ship reads stock and supplier data from the source-of-record system and writes the approved PO back. Where the ERP does not have a usable API, we work around it: SFTP, scheduled CSV exchange, occasionally screen-scraping, never an island that does not connect.
Tell us your supplier mix, the volume, and where the leakage is. We will tell you honestly whether Tradogram or Procurify gets you there, and if a custom build is the right call, scope and quote it before any work starts.
Email oliver@digitalsignet.com