Choose off-the-shelf ERP when your processes are close to standard and you want a vendor to own the roadmap. Choose bespoke ERP when the work that makes your business different is what packages force you to work around, and you want to own the system. For UK businesses, both routes must also handle Making Tax Digital for VAT, payroll reporting and bank integration.
This guide is written for UK finance directors, operations leads and owners comparing the two. It does not repeat the general build-versus-buy argument, which is covered in ERP vs custom development. It focuses on the decision itself and on the UK-specific checks that apply to either route. If the answer is clearly "bespoke", our custom ERP software page explains how we deliver it; if it is clearly a package, our ERP implementation services cover selection and rollout.
What is the difference between off-the-shelf and bespoke ERP?
Off-the-shelf ERP is a packaged product that many businesses license and configure; bespoke ERP is built for one organisation. Our explainer on what a bespoke ERP system is covers the definitions in detail. In practice the difference shows up in five places:
| Factor | Off-the-shelf ERP | Bespoke ERP |
|---|---|---|
| Process fit | You adapt to the vendor's process | Software follows your process |
| Time to first use | Often quicker for standard finance and stock | Depends on scope; phased delivery brings first modules forward |
| Cost profile | Subscription or licence per user, plus implementation and add-ons | Build and maintenance; no per-user licence for the custom system itself |
| Upgrades | Vendor schedule; customisations must be retested | You decide when and what changes |
| Ownership | Licensed; data is yours, code is the vendor's | Code ownership agreed in contract; data is yours |
| Vendor risk | Product direction, pricing and support set by vendor | Dependence on your development partner or in-house team |
Neither column is cheaper by default. Compare total cost over several years, including licences, implementation partners, add-ons, internal time and maintenance. Our guide to ERP total cost of ownership sets out what to include.
Which should you choose? A decision table
Score each statement for your business. The pattern of answers usually makes the choice clearer than any single factor.
| Statement | Points to off-the-shelf | Points to bespoke |
|---|---|---|
| Our finance, sales and stock processes are similar to others in our sector | Yes | |
| Our core operation (hire, jobs, production, contracts) is unusual | Yes | |
| We run several entities or sites with different rules | Often | |
| We need to be live on standard processes within months | Yes | |
| Shortlisted packages need custom code for our main workflow | Yes | |
| We have no one to own process decisions day to day | Yes, with a strong partner | |
| Per-user licensing is a problem (field staff, partners, seasonal workers) | Yes | |
| We want to own the code and hosting choice | Yes | |
| A specialist package exists for our exact sector | Yes |
If most answers sit on the left, shortlist packages and spend effort on configuration and data. If most sit on the right, cost a bespoke or hybrid option. Mixed answers often point to a hybrid: a package for accounting and payroll with bespoke operational modules integrated to it.
How does Making Tax Digital affect the choice?
Both routes must support Making Tax Digital for VAT; the question is how. HMRC's VAT Notice 700/22 (checked October 2026) says all VAT-registered businesses must keep certain records digitally and file VAT returns using functional compatible software, which must be able to send returns to HMRC through its API.
The detail that affects ERP design is the digital links rule. HMRC states that once records are in your software, transfers between programs that make up your functional compatible software must be digital, and that copy and paste does not count as a digital link. HMRC lists acceptable links such as CSV or XML import and export, automated data transfer and API transfer.
What this means for each route:
- Off-the-shelf: check that the package, in the edition you will use, submits VAT returns to HMRC directly or through recognised bridging software, and that any add-ons feeding it are digitally linked.
- Bespoke: either build the MTD submission into the system, or, more commonly, post transactions to an accounting product that already submits returns and connect the two by API or file import, never by retyping or copying.
- Hybrid: document every hop from operational module to VAT return and confirm each is a digital link under HMRC's definition.
Ask your accountant or tax adviser to confirm your approach. A well-built system is designed to support your obligations, but responsibility for the return stays with the business.
How do payroll and banks fit in?
Most UK businesses connect ERP to a payroll product and to their bank rather than rebuilding either. That is often the right decision for both routes.
Payroll and RTI
GOV.UK guidance (checked October 2026) says employers must send HMRC a Full Payment Submission on or before each payday, reporting payments and deductions for every employee. Payroll is therefore a specialist area with frequent rule changes. Packaged ERPs often integrate with or include a payroll module; bespoke projects usually integrate with an established UK payroll provider and pull back journals and costs, rather than writing RTI submission from scratch.
Bank integration
Bank links typically cover statement import for reconciliation and payment file export for supplier runs. Confirm what your bank supports (file formats, API access through open banking providers, approval workflows) before assuming either route will handle it. Bank integration is usually a small piece of work, but it touches cash, so it needs approval controls and testing with real files.
How should UK organisations procure ERP?
Private businesses can run any fair process, but a structured one reduces risk: requirements, longlist, scripted demos, reference checks, then a pilot or proof of concept.
Public bodies are different. GOV.UK guidance states that the Procurement Act 2023 and its regulations came into force on 24 February 2025, replacing the Public Contract Regulations 2015 for procurements started from that date. Public sector buyers should involve their procurement team early, whichever route they take.
Procurement checklist
- Written requirements covering processes, entities, reports and integrations (see our ERP RFP template)
- Scripted demos using your own scenarios, not the vendor's standard demo
- MTD for VAT approach confirmed, including every digital link
- Payroll and bank integration approach confirmed
- Data migration plan and who reconciles each load
- Ownership of code, configuration and data stated in the contract
- Exit plan: how you get your data out, in what format
- Support model, response times and who handles upgrades
- Reference calls with organisations of similar size and complexity
What should you ask each type of supplier?
Ask package vendors and bespoke suppliers different questions, because their risks sit in different places. The aim is the same: written answers you can compare.
| Topic | Ask the package vendor or partner | Ask the bespoke supplier |
|---|---|---|
| Fit | Which of our scenarios need custom code rather than configuration? | Which of our scenarios are you least sure about, and why? |
| Tax | How does the edition we would buy submit VAT returns, and what links feed it? | Will you submit MTD returns or post to our accounting product, and by what link? |
| Upgrades | How often are releases applied, and who retests our extensions? | How are frameworks and libraries kept up to date, and who pays for it? |
| Ownership | What do we own: configuration, extensions, data? | When does the source code transfer, and in what form? |
| Exit | How do we export all data and documents if we leave? | Could another team take over the code, and what documentation will they get? |
| Support | Who answers first-line questions: vendor or partner? | What are the support hours, response times and escalation route? |
| Evidence | Can we speak to customers in our sector and size? | Can we see working software for our own process before committing? |
Two answers matter more than the rest. From a package vendor, the honest list of scenarios that need custom code tells you how far the product really fits. From a bespoke supplier, the willingness to show working software early tells you how much risk you are carrying.
Red flags on either route
- Demos that avoid your scripted scenarios
- No clear answer on how the VAT return is produced
- Vague ownership or exit terms
- Data migration described as "straightforward" before anyone has seen your data
- One named person holding all the knowledge
When is bespoke the wrong answer for a UK business?
Bespoke is the wrong answer when a package already fits your sector well, when you need standard processes live quickly, or when nobody internally can own the requirements. It is also the wrong answer for areas where specialist UK products are mature and heavily regulated, such as payroll; integrate with them rather than rebuild them.
Off-the-shelf is the wrong answer when every demo ends with "that would need custom development" for your core workflow. At that point you are paying for a package and a bespoke build, and inheriting the upgrade burden of both.
Illustrative scenario
A UK manufacturer with two sites runs a mainstream accounting package that already handles MTD submissions. Production planning, batch traceability and customer-specific pricing live in spreadsheets. Packages on the shortlist need heavy customisation for the production workflow. A hybrid route keeps the accounting package, builds production and traceability modules as bespoke software, and posts journals to the ledger by API, so the VAT digital link chain stays intact.
How to start
Write down your entities, sites, core processes, the spreadsheets that hold them together, and every system you must connect to, including payroll, banks and HMRC submission. Our software requirements brief template gives a structure. Then test both routes against the same scenarios. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, which lets you compare a working bespoke option against package demos. Discuss the project when you have a draft brief.