Custom Order Management System (OMS)

An order management system is the operational spine of any business where an order is more than a checkout. If your orders involve configuration, lead times, deposits, delivery, installation, sign-off and a stack of documents, then the order is not an event — it's a process that runs for weeks or months. Most UK businesses in that position manage the process in a shared spreadsheet supplemented by email, and it holds together far longer than it should, right up until the order book grows past what one coordinator can hold in their head.

The Symptoms of Outgrowing the Spreadsheet

There's a fairly reliable set of signals. Nobody can answer "where is my order?" without asking at least two colleagues. The same order data is typed into three places — the spreadsheet, the accounting package and a Word document. Two people editing the file at once produces a version conflict and a quiet argument. A customer produces a quote with a price nobody can explain and there's no record of who approved it. And most tellingly: one specific person cannot go on holiday without the order process degrading, because the rules live in their memory rather than in any system.

None of these is individually fatal. Together they impose a tax on every order you process, and that tax grows faster than headcount, because coordination cost scales worse than volume does.

Where This Works Best

Equipment distribution through dealer networks — dealer-specific price lists, order tracking dealers can self-serve, stock allocation across branches, and warranty registration tied to serial numbers. The dealer portal alone usually removes a meaningful share of inbound phone traffic.

Made-to-order manufacturing — configured products where the order determines the production spec. The value is a single unambiguous record of what was ordered, so remakes caused by a misread spec stop being a monthly occurrence.

Installed products — windows, kitchens, HVAC, solar — where the order carries a survey, a manufacturing slot, a delivery and an installation date, plus deposit and balance payments. This is the case where an OMS and field service management genuinely belong together.

B2B trade supply — account customers with credit terms, negotiated pricing, part deliveries and back orders. Standard e-commerce platforms model none of this well; an OMS models all of it as first-class concepts.

Documents Are Usually the Fastest Win

When I map a client's order process, document generation is almost always the first thing worth automating. Quotes, order confirmations, contracts, delivery notes, handover acts, warranty certificates — assembled by hand from the last similar document, which means every one carries the risk of a stale price, a wrong address or a clause from a different customer's deal.

Generating documents from order data removes an entire class of error and typically saves hours per week per person, but the real benefit is downstream: once documents are generated rather than authored, they're consistent, they're versioned, and they're admissible when a dispute arrives eighteen months later. It's also the module that builds internal trust in the new system fastest, which is why I usually ship it first.

Custom OMS vs Off-the-Shelf

The honest position: if you sell standard products through a standard checkout, you don't need this. Shopify, WooCommerce and their ecosystems handle that well, and bolting a custom system onto a solved problem is a waste of money.

A custom OMS earns its cost when the order has a long life after payment, when your pricing and approval rules are specific to your business, when the process spans teams that currently work in separate tools, and when the system must integrate with things you already run rather than replace them. The alternative — a full ERP implementation — solves the problem too, but at several times the cost and with a change-management burden that mid-sized businesses routinely underestimate.

Integration, Not Replacement

The most common mistake I see is scoping an OMS to replace everything. It shouldn't. Your accounting package is fine — Xero, QuickBooks and Sage all have solid APIs and your accountant knows them. Your storefront is fine. Your warehouse system, if you have one, is probably fine too.

The OMS should own the order lifecycle and become the system of record for commercial truth, then push and pull cleanly across the boundaries. That keeps the build scoped, keeps the risk bounded, and means the project can be stopped or paused at a module boundary with something valuable already delivered. Replace-everything projects don't offer that, which is exactly why so many of them fail expensively.

What It Costs and How Long It Takes

A fixed-price discovery — mapping the order flow, agreeing the status model and data model, and producing a costed build plan — starts around £3,500 and takes about a week. An MVP covering order intake, the status model, document generation and spreadsheet migration typically runs £30,000–£60,000 over 8–14 weeks. A full platform adding stock allocation, dealer portal, pricing approvals and two-way accounting integration generally sits between £80,000 and £160,000 across 6–12 months.

Those ranges are wide because scope genuinely varies. What doesn't vary is the sequencing: intake and documents first, because that's where the daily pain lives and where trust in the new system gets built.

Getting Started

The starting point is one real order, traced end to end. Every hand-off, every document produced, every point where the same information is typed a second time. That exercise usually takes a day and produces both a costed build plan and a short list of fixes worth making immediately, before any software exists.

Based in Manchester, I work with distributors, manufacturers and installation businesses across the UK. If your order book lives in a spreadsheet that's become too important to trust, let's map it out and see what the honest options are.