Customer Portal vs ERP User Licences: Which Is More Cost-Effective?

Every UK manufacturer and distributor running a modern ERP faces the same question at some point: "How do we give our customers and suppliers access to their data without breaking the bank on user licences?"

It is a deceptively expensive problem. A handful of external users here, a few supplier accounts there — and before you know it, you are spending tens of thousands of pounds per year on ERP user licences for people who use less than 5% of the system's functionality. Your customers just want to check order status and download invoices. They do not need a full ERP licence to do that. But that is often the only option ERP vendors give you.

This article compares the total cost of ownership of two competing approaches: provisioning ERP user licences (CALs and SULs) for external parties versus building a purpose-built customer portal that connects to your ERP via its REST API. We will look at the direct costs, the hidden costs, the functional differences, and the security implications. The numbers may surprise you.

If you are a finance director, IT manager, or operations director at a UK manufacturer or distributor, this comparison is directly relevant to your budget. By the end of this article, you will know exactly which approach makes financial sense for your organisation and how to calculate the saving for your specific situation.

The Licensing Problem: Why External Users Cost More Than You Think

ERP licensing models were designed for internal employees who need full access to the system day in, day out. They were not designed for the occasional external user who just wants to check an order status, download an invoice, or update their delivery address. Yet the licensing structure treats both types of user identically.

The problem starts with how ERP vendors define a "user." In most licensing frameworks, any individual who authenticates against the ERP system requires a licence — whether they are a full-time employee or a customer who logs in three times a month. This one-size-fits-all approach is the root cause of the unnecessary expenditure.

Consider a typical mid-market manufacturer. You have perhaps 200 customers who regularly place orders. You have 50 key suppliers who need to see purchase orders and delivery schedules. If you give each of them a user licence, you are looking at 250 external licences on top of your internal employee count. At an average cost of £800 per user per year, that is £200,000 annually for external access alone.

And that is before you factor in the administrative burden of provisioning those users, managing their passwords, resetting forgotten logins, and deprovisioning accounts when relationships change. Every customer churn event creates IT overhead. Every supplier onboarding process consumes time from your already stretched team.

The standard approach for many organisations has been to simply buy additional user licences for customers, suppliers, and third-party logistics partners. It feels like the simplest solution because it requires no new software, no procurement process, and no internal development. But it is also the most expensive route over any meaningful time horizon.

ERP User Licence Pricing by Platform

To make the numbers concrete, let us look at the actual licence costs across the major ERP platforms used by UK SMEs. These are the prices you would typically pay for a named user licence (or the equivalent annualised cost for perpetual licences with maintenance).

Note: These figures are indicative. Actual pricing varies by partner, region, negotiation, and the specific licensing agreement your organisation has in place. Some vendors also impose minimum user counts (e.g., five-user minimum on certain licence types), which inflates costs further if you only need two or three external accounts. Volume discounts may reduce per-user costs at scale, but the overall trajectory remains the same.

At these prices, the annual cost for even a modest external user base adds up fast. A manufacturer with 30 customer accounts and 10 supplier accounts spending £800 per licence is looking at £32,000 per year — every year, with no cap and no end date. Over three years, that is nearly £100,000 spent on giving external parties access to an interface they were never meant to use.

The Hidden Costs of ERP Licences for External Users

Beyond the direct licence cost, several hidden expenses rarely appear in the initial comparison but significantly impact the real total cost of ownership:

• Administrative overhead. Every new external user requires IT setup, licence provisioning, password management, MFA enrolment, and offboarding when a customer switches supplier. At an estimated £50–£150 per user for setup and £20–£50 per user per year for ongoing administration, these costs are small per user but significant at scale.
• Training and support. External users are not familiar with your ERP's interface. They call your support team for help navigating screens designed for internal staff. "Where do I find my invoices?" "How do I see the delivery status?" "I cannot log in." Every one of those calls costs time and money.
• Security surface area. Each external ERP user is a potential attack vector. They authenticate directly against your ERP instance. They have access to parts of your ERP that they do not need, simply because ERP permissions are role-based rather than customer-record-based by default.
• Compliance risk. External users with ERP access can accidentally (or deliberately) see data belonging to other customers unless you have painstakingly configured record-level security — which most ERP systems handle poorly and which requires ongoing maintenance.
• Scaling cost. Adding users is linear. Fifty external users at £800/year costs £40,000 per year. One hundred external users cost £80,000. Two hundred cost £160,000. There is no economy of scale in the licensing model.
• Opportunity cost. Every hour your IT team spends managing external user accounts is an hour not spent on strategic projects that add value to your business.

When you add these hidden costs, the real annual cost of an external ERP user can be 20% to 40% higher than the licence fee alone suggests. That turns a £40,000 annual licence bill into a £48,000 to £56,000 real cost.

What a Customer Portal Costs Instead

A purpose-built customer portal takes a fundamentally different approach. Instead of provisioning a full ERP licence, you build (or subscribe to) a web application that connects to your ERP via its REST API. External users log into a branded interface that is designed specifically for their needs — nothing more, nothing less.

The portal does not replace your ERP. It sits alongside it, reading and writing data through your ERP's API in real time. Your ERP remains the system of record. The portal is simply a better interface for the specific subset of functionality that external users need.

Here is the cost structure for a typical Sysgraft customer portal:

That last line is the critical differentiator. A portal subscription allows unlimited users. Once the portal is built and connected to your ERP, adding customer number 101 costs exactly the same as adding customer number 1. The marginal cost is zero. This is the fundamental economic advantage of the portal approach.

To put it in perspective: the build cost of a portal is roughly equivalent to the cost of 30 to 40 external ERP user licences for a single year. After year one, the portal subscription is less than the cost of 15 licences — and covers every single one of your customers and suppliers. The breakeven point typically arrives within 12 to 18 months, even for relatively small external user bases.

3-Year TCO Comparison: ERP Licences vs Customer Portal

To make this concrete, let us compare the three-year total cost of ownership for a typical UK manufacturer or distributor with 50 external users (a mix of customers and suppliers who need order tracking, invoice access, and account management).

We assume the following realistic figures:

• ERP licence approach: 50 external users at £800/user/year (blended average across BC, Sage 200, OrderWise, SAP B1). Total annual licence cost: £40,000.
• Portal approach: Fixed-price build of £25,000 (includes API integration, React/Next.js frontend, unlimited user accounts) plus £800/month subscription (hosting, security, API maintenance, support). Total year-one cost: £34,600. Ongoing: £9,600 per year.
• No additional IT overhead assumed for portal administration (self-service onboarding reduces internal support burden).

The saving widens dramatically as your external user base grows:

• At 10 users: ERP = £24,000 over 3 years. Portal = £53,800. ERP is cheaper at very small scale, though the portal also delivers better UX and security.
• At 30 users: ERP = £72,000. Portal = £53,800. Portal saves £18,200 over 3 years. Breakeven is around 18 months.
• At 50 users: ERP = £120,000. Portal = £53,800. Portal saves £66,200. Breakeven at approximately 14 months.
• At 100 users: ERP = £240,000. Portal = £53,800. Portal saves £186,200.
• At 200 users: ERP = £480,000. Portal = £53,800. Portal saves £426,200.

This is the core economic argument for a portal: ERP licence costs scale linearly with users; portal costs are all but fixed regardless of how many customers you onboard. The more external users you have, the more compelling the portal economics become.

And these figures do not even account for the productivity gains your internal team will experience when customers stop calling to ask for order status and start self-serving through the portal. Our experience with clients suggests that a customer portal typically saves 15 to 30 minutes per staff member per day in query handling alone.

Functional Comparison: What Each Approach Delivers

Cost is only half the story. The two approaches also differ significantly in what they can actually deliver to external users. Here is a head-to-head functional comparison across the capabilities that matter most for customer and supplier self-service.

The portal wins on virtually every customer-facing capability. The ERP licence approach only wins if the external user genuinely needs access to the full breadth of your ERP system — which, for almost all customers and suppliers, they simply do not. They need their orders, their invoices, their deliveries, and their account. A portal serves those needs faster, better, and more securely.

One capability worth highlighting is the bottom row: multi-language support. For UK manufacturers with international customers or suppliers, a portal can present the interface in the user's preferred language without requiring any changes to your ERP configuration. This is a feature that ERP licences typically handle poorly, requiring global language packs that apply to all users rather than per-user language preferences.

The Security Argument: Portal Users Never Touch Your ERP

There is a compelling security argument for the portal approach that rarely gets enough attention in cost comparisons. It is worth examining in detail because it addresses one of the most significant risks in modern ERP operations.

Every external ERP user is an inherent security risk. Here is why:

• They authenticate directly against your ERP instance using the same authentication system your internal staff use. If their credentials are compromised, an attacker has a valid login to your core business system.
• They navigate your ERP's native interface, which means they have visibility of your system's menus, navigation structure, and potentially other customers' data if your permissions are not meticulously configured and maintained.
• They exist in your ERP's user directory alongside your employees. Any vulnerability in your ERP's authentication or authorisation system affects them equally.
• Each external user represents an additional attack surface for phishing, credential stuffing, and social engineering attacks targeting your ERP.

A customer portal eliminates this risk through architectural separation:

• Portal users authenticate against the portal application, not your ERP. Their credentials never touch your Business Central, Sage 200, OrderWise, or SAP Business One instance. There is no pathway from a compromised portal account to your core ERP.
• The portal communicates with your ERP via a single, service-to-service API connection using short-lived OAuth 2.0 tokens with scoped permissions. There is no direct user-level access to the ERP from any portal account.
• Data isolation is architectural, not configurational. Each portal user sees only the data scoped to their customer record. There is no way for one customer to see another customer's data, regardless of how permissions are set. It is not a permissions configuration that could be misconfigured — it is a fundamental property of the application architecture.
• If a portal user's account is compromised, the blast radius is limited to that customer's data. The attacker never gains access to your ERP, never sees other customers' information, and never touches your financial data or general ledger.
• Your external attack surface shrinks dramatically. Instead of maintaining dozens or hundreds of external ERP user accounts with full ERP authentication pathways, you maintain one API integration with a single, audited, and monitored authentication flow.

For organisations subject to Cyber Essentials Plus, GDPR, or ISO 27001, this architectural separation is a significant compliance advantage. It simplifies your compliance posture because external user access is contained within a dedicated, restricted application rather than your core ERP system. Your auditors will thank you.

There is also the question of data residency and sovereignty. A portal can be hosted in a UK data centre with full control over data storage, backup, and disaster recovery. This can be simpler to manage and audit than ERP access that spans multiple Microsoft or third-party data centres depending on your deployment model.

When You Need ERP Licences for External Users

Despite the cost, security, and functional advantages of a portal, there are legitimate scenarios where provisioning ERP user licences for external parties remains the right choice. It is important to be honest about when each approach makes sense.

Staff and internal team members. Your employees need full ERP access to do their jobs. A portal is a supplement for specific use cases, not a replacement for internal user licences. Do not try to run your warehouse operations through a customer portal.

Third-party logistics partners who need operational access. If your 3PL needs to process pick lists, update inventory movements, manage bin locations, and process shipments within your ERP, they likely need some form of full user access. However, a dedicated supplier portal can often handle a surprising proportion of these workflows without requiring a full licence.

Value-added resellers or distributors who manage inventory on your behalf. Partners who need to raise purchase orders, check stock levels across multiple locations, manage backorders, and process returns may require the full ERP feature set. In these cases, the breadth of functionality justifies the licence cost.

Short-term project access. If a consultant, contractor, or implementation partner needs full ERP access for a defined period (e.g., configuring a new module, performing data migration, or conducting an audit), a short-term user licence is the simplest route. Just set a calendar reminder to deprovision it when the project ends.

Users who need access to multiple customer records simultaneously. If an external user genuinely needs to view data across multiple customer accounts (for example, a group purchasing organisation or a shared service centre), an ERP licence with appropriate permissions may be the most practical solution, though a well-designed portal can often handle multi-account scenarios too.

In these cases, the cost of a full ERP licence is justified because the user genuinely needs the breadth of functionality that the ERP provides. The key strategic insight is distinguishing between users who need the ERP and users who just need their own data. For most external relationships, the answer is the latter.

When a Portal Is Enough

For the vast majority of external relationships, a portal is not just enough — it is better. Here is a practical guide to who should use a portal:

• Customers who want to track orders. They do not need your ERP. They need to see their order status, delivery dates, carrier tracking information, and proof of delivery on their phone or laptop. A portal delivers this in seconds without consuming a single ERP licence and without your sales team spending 2–4 minutes per query navigating five ERP screens.
• Customers who need invoice and statement history. Instead of emailing your accounts team, they download invoices and statements from a portal whenever they need them. No licence cost. No staff time. No "accounts receivable, can you resend that invoice?" phone calls.
• Suppliers who need to see purchase orders and delivery schedules. A supplier portal gives them visibility of upcoming PO lines, delivery windows, quality expectations, and acceptance status without giving them access to your pricing, customer data, or financials. This is particularly valuable for manufacturers running just-in-time supply chains.
• Distributors who need live stock availability and pricing. They log into your portal, see their specific pricing and stock allocation, and place orders directly. The portal enforces their contract pricing and credit limits automatically. No Excel spreadsheets, no emailed price lists, no manual order entry.
• Any external party that currently gets emailed reports or spreadsheets. If your team is spending time pulling data from the ERP, formatting it, and emailing it to customers or suppliers, automate that through a portal. Your team stops acting as human APIs. Your external parties get self-service, real-time access to their data.

If the external user's needs can be summarised as "their data, their transactions, and nothing else," a portal is the right solution. It will deliver a better user experience, better security, and significantly lower cost than an ERP licence.

Our experience across dozens of implementations suggests that roughly 90% of external user relationships fall into this category. Only the remaining 10% genuinely need the full breadth of ERP access. That means there is a strong likelihood that you are overspending on ERP licences for a significant portion of your external user base right now.

FAQ: Customer Portals vs ERP User Licences

1. Can a portal really replace an ERP user licence for my customers?

For the vast majority of self-service use cases — order tracking, invoice access, stock checks, address updates, and simple order placement — yes, absolutely. A portal is designed specifically for these tasks and often delivers a better user experience than the ERP itself. The key test is whether the external user needs anything beyond their own data and transactions. If they do not, a portal is the better solution on cost, security, and user experience grounds.

2. What happens if a customer needs more functionality than the portal currently offers?

Portals are extensible by design. New features can be added as modules within the same application without architectural changes. If a customer needs a capability that your portal does not yet support, it can typically be built in a development sprint (1–2 weeks) without replacing the portal architecture. This is one of the key advantages of a modern, component-based frontend framework like React or Next.js.

3. How long does it take to build a customer portal?

A read-only portal (order status, invoices, statements) typically takes 4–6 weeks from kick-off to go-live. A full self-service portal with order placement, returns management, and account management takes 8–12 weeks. These timelines assume a fixed-price engagement with a dedicated team. This compares favourably to the 9–18 months typically required for a full ERP replacement project.

4. What if we already have ERP licences for our customers? Can we migrate?

Yes, and it is straightforward. You can migrate gradually: set up the portal, onboard customers in batches, and let the existing ERP licences expire as customers transition to the portal. The portal cost is offset by the licence savings from day one. Most of our clients achieve full migration within 3–6 months, realising net savings from month one.

5. Is a customer portal secure enough for regulated industries?

Yes. Portals built on modern frameworks with OAuth 2.0 authentication, encrypted data in transit (TLS 1.3), encrypted data at rest, and architectural data isolation meet or exceed the security requirements of GDPR, Cyber Essentials Plus, and ISO 27001. The architectural separation from your ERP is itself a security advantage that these frameworks recognise and reward during certification audits.

6. Does the portal add load to our ERP that could affect performance?

No. The portal reads and writes data through your ERP's REST API at the same rate as any other API client. There is no direct database access, no table locks, and no additional load beyond normal API rate limits. If anything, a portal reduces the overall load on your ERP because customers self-serve rather than calling your team, who then log into the ERP to look things up. One portal API call replaces one staff member navigating five ERP screens.

7. What if we switch ERP platforms in the future?

Because the portal connects to your ERP via its REST API, migrating to a new ERP platform requires only rebuilding the API adapter layer. The portal frontend — the interface your customers use — remains unchanged. This is a significant advantage over giving customers direct ERP access, which would require completely re-onboarding them onto a new ERP interface if you ever switch platforms.

---