What an Ecommerce ERP Really Costs: A Guide to Total Cost of Ownership

You will get a quote, and it will be one number, usually monthly. What you are actually committing to runs over three years and arrives in pieces.

That is not a criticism of how software is sold. A licence fee is the one part a vendor can quote cleanly before knowing much about your business, and the rest genuinely depends on your data, your channels and how much of the work your own team takes on. It does mean the comparison you make on a spreadsheet of monthly figures is not the comparison that matters.

Panorama Consulting's 2026 ERP Report, which surveyed organisations between January 2025 and January 2026, found that more than a quarter of projects ran over budget, most often because the organisation needed technology it had not planned for. That is usually a scoping gap rather than a pricing one, and it is the sort of thing a thorough evaluation catches.

Here is how to build the full picture before you sign.

The Cost Lines

• Licence or subscription. The headline number. Check what it is calculated on, because that determines how it behaves later.
• Implementation. Configuration, data migration, integrations, testing and training. Ask whether the figure is fixed or estimated, and what would change it.
• Partner fees. Some systems are implemented by third-party partners rather than the vendor's own team. Both models work, they are just different contracts at different rates.
• Integrations. What connects natively, what needs a connector or middleware subscription, and what needs building. A build is a cost now and a maintenance commitment later.
• Data migration. Products, customers, open orders, stock, supplier records and history. Most of the effort goes into cleaning the data rather than moving it.
• Training. Initial training, and the version you will want for people joining next year.
• Internal staff time. Rarely on a quote, because it is not the vendor's to quote. Someone on your team will give several months of partial attention to this, out of their existing job.
• Changes after go-live. A new channel, warehouse, carrier or price list. Worth knowing who makes those changes and what each one involves, because this is the line that compounds.
• Support. What is included, what response times apply, and what a higher tier costs.

‍

How Pricing Models Behave as You Grow

The model matters more than the opening number, because it decides what year three looks like.

• Per user. Predictable while the team is stable, and it rises with headcount. It can also shape behaviour, because teams start sharing logins or leaving warehouse staff off the system, which works against the single source of truth you bought it for.
• Per order or per volume. Scales with the business, which many operators prefer, and it means your software cost rises in the months you are busiest. Check how the tiers step and what a peak month looks like.
• Per module. A lower entry point, with more to map out. Work through your requirements against the module list so you are comparing the same scope across vendors.
• Bespoke. Quoted against your business rather than a published tier. It fits businesses that do not sit neatly in a standard band, and it means you will want to ask what moves the number up or down so you have a reference point.

‍

A Three-Year Worksheet

Take each vendor on your shortlist and put a figure against all ten lines below, three times over: year one, year two and year three. Year one carries the implementation weight, and years two and three show you the shape.

Against each line, the question to settle with the vendor:

• Licence or subscription. What is it calculated on, and what happens if that doubles?
• Implementation. Fixed or estimated, and what would change it?
• Partner fees. Who does the work, and at what rate?
• Integrations, one-off. What is native, what needs a connector, and what needs building?
• Integrations, recurring. Which third-party subscriptions are needed?
• Data migration. What is included, and what counts as cleaning our data?
• Training. Included or charged, and what about new starters next year?
• Internal staff time. How many days of our team's time, and from which roles?
• Changes after go-live. Can our team make changes, or does each one go through the vendor?
• Support. What is included, and what does a higher tier cost?

Then add up all three years for each vendor, and compare the totals rather than the monthly figures. A system with a higher subscription can land lower over three years if more of the work is included in it.

‍

The Three Lines Worth the Most Attention

Internal staff time. If one of your people will spend a third of their week on this for four months, put a number on it. It is the cost that decides whether the project keeps moving.

Changes after go-live. Ask what happens when you add a sales channel in eighteen months. A system your own team can configure behaves differently over three years from one where each change goes through the vendor, and either can be right depending on your team.

The second system. If the ERP does not cover something you need, you will buy a tool for it and maintain the connection. Surfacing those gaps during evaluation is easier than finding them in month seven.

‍

What Brightpearl's Pricing Includes

Published tiers make comparison quick and often fit nobody precisely. Quoted pricing fits the business and asks a little more of the buyer during evaluation.

Brightpearl by Sage takes the second approach, describing a bespoke set-up for every customer with tailored pricing so you never pay for more than you need. A few details are worth knowing when you fill in the worksheet above, all from Brightpearl's own pricing and implementation pages:

• Unlimited users are always part of the deal, at no extra cost. That takes the per-user line out of your calculation, and removes the reason to keep warehouse or seasonal staff off the system. As Owen Simpson, Commercial Director at Henchman, puts it: "All our team members can have access to Brightpearl, at no extra cost, and when new people join us, they get up to speed quickly."
• Implementation and onboarding sit alongside the product, covering scoping through to configuration, training for the whole team and access to Brightpearl's online learning platform.
• A fixed cost quote before contract. Brightpearl provides a Technical Solution Proposal setting out how the system will be configured for your workflows, and a fixed cost quote before you sign, which puts the largest uncertainty in most ERP budgets on the table early.
• Support is 24/7 and unlimited, with ongoing consulting and health checks from a dedicated Customer Success Manager.
• Customers go live in 90 to 120 days on average, with a 97% implementation success rate.

Those are Brightpearl's own figures, so use them as a starting point and confirm the detail against your own requirements.

Whichever systems you are comparing, the worksheet is the useful part. Ask each vendor to help you complete it, and you will have a decision you can explain to your board.

Ready to see the whole cost rather than the headline?

Discover how Brightpearl prices against your business, with implementation and unlimited users included. Book a demo today.

‍