What is a customer portal? Explanation, types and examples

A customer portal is a secure online environment where customers log in and handle their own business: placing and tracking orders, downloading invoices and documents and checking the status of a request. A good customer portal pulls that data live from the systems you already use, such as your ERP, accounting software or CRM.

The trigger is usually familiar. Customers email for a copy invoice, call about the status of their order or send an order in Excel that someone retypes. The answer is already in your own systems, but only your own staff can get to it.

A portal isn't a goal in itself. We start with the questions coming in now: which come up most, who answers them and where does the answer live? Sometimes the outcome is a portal. Sometimes the customer area in your existing software is enough, or a well-run shared inbox.

What exactly is a customer portal?

A customer portal is a protected part of your website, or a separate web application, where each customer only sees their own data. The difference from a website: there, everything is for everyone. The difference from a web shop: there, a visitor buys; in a portal, a regular customer manages their account.

You'll also see it called a client portal or self-service portal. A web portal is broader: any portal in the browser, including environments for staff, partners, dealers or suppliers. You know the principle from your bank, your energy supplier or your insurer: log in and see what's going on, without picking up the phone.

What can you do with a customer portal?

Anything a customer now emails or calls about where the answer is already in a system. The most common features:

• Ordering and reordering, with their own product range and pricing agreements.
• Tracking order status and deliveries.
• Downloading invoices, quotes, certificates and other documents.
• Submitting a request, report or ticket and following its status.
• Updating their own details, such as addresses and contacts.
• Uploading documents, for example for a file or an application.
• Viewing overviews and reports, such as usage, maintenance history or project progress.

A first version rarely has more than a few of these. Start with the features that remove the most questions and build on what customers actually use.

What types of portals are there?

There are four common types: the self-service customer portal, the B2B or ordering portal, the dealer or partner portal and the supplier portal. They differ mainly in who logs in and what they're allowed to see.

• Self-service customer portal: customers see their invoices, documents, requests and status. The best-known type.
• B2B or ordering portal: business customers order at their own agreed prices, with several colleagues in one account, each with their own role.
• Dealer or partner portal: resellers and partners find stock levels, price lists, marketing material and their own orders. A dealer sees their own prices, not another dealer's.
• Supplier portal: suppliers see purchase orders, confirm delivery dates and submit invoices and documents.

It often starts with one group and a second follows later. So set up the roles from the start in a way that lets a new group join without rebuilding the portal.

Examples of a customer portal

A few illustrative examples of what a customer portal looks like by sector:

• Wholesale: regular customers order the same items at agreed prices, see their order history and download invoices. The order goes straight into the ERP, without retyping.
• Installation and maintenance: customers report a fault, see when the engineer is coming and find maintenance reports and certificates per installation.
• Accountancy or bookkeeping firm: clients upload paperwork, see what's still missing and download their reports.
• Professional services: clients follow project progress, approve a quote and find all documents in one place.

An example from our own work: for VIRPP we built a label dashboard where record labels log in and search the catalogue of artists on the platform. Each label works in its own environment, and adding a new label is a matter of configuration, not building. Several labels have discovered and signed new talent through the dashboard.

What does a customer portal deliver?

Fewer questions by email and phone, no retyping of orders and customers who can find the answer themselves at any time. Your team spends its time on the work itself instead of looking things up and forwarding them.

How much that saves depends on how many questions come in now and how long looking things up takes. Count for a few weeks: how many emails and calls are about invoices, status or documents? The manual work calculator turns that time into an amount.

When do you need a customer portal?

When the same questions come back every day, when customers order by email or Excel and someone retypes it, or when your team spends more time looking things up than doing the work. If you have ten customers who ask something twice a month, a good shared inbox will do.

It also tips when customers ask for it themselves. Business customers increasingly expect to check their invoices and orders without having to email.

Buy a customer portal or have one built?

Buy one if the customer area in your ERP, CRM or accounting package does what your customers need. Have one built if it doesn't fit how you work: pricing agreements per customer, data from several systems in one overview, or an ordering or request process that works differently for you.

There are roughly three routes:

• The portal module of software you already have. The cheapest, and nothing to maintain, but you're limited to what the package can do.
• Off-the-shelf portal software as a service. Quick to launch, but connecting it to your own systems and non-standard processes often costs more than expected.
• A custom customer portal. Exactly what your customers need, connected to your own systems, but a bigger project and you need to arrange upkeep.

How to work through that trade-off over several years is covered in custom software or an off-the-shelf package. If custom comes out on top, you can have a customer portal built that connects to your own systems.

Which integrations does a customer portal need?

With the systems where the data already lives: your ERP, your accounting software and your CRM. They stay the source. The portal shows what's in them and writes back what the customer does.

A portal that keeps its own copy of the data soon falls behind. Then the customer sees a different status from your account manager, and calls anyway. So invoices come from, for example, Exact Online or AFAS, customer details from HubSpot and order status from your ERP. We can connect any system. What an integration costs and what drives that is covered in what an integration between systems costs.

What does the cost of a customer portal depend on?

Not on how it looks, but on what's behind it: the number of roles, the number of integrations, the data that needs migrating and features like payments or e-signing.

• Roles and permissions: one type of user is simpler than buyers, finance teams, dealers and your own account managers side by side.
• Integrations: every system the portal reads from or updates, and whether that system has a usable API.
• Data: what needs cleaning up or migrating before customers see it.
• Features: ordering with agreed prices, payments, e-signing or document uploads each add something.
• Upkeep: updates, monitoring, removing old accounts and adjusting when your ERP's or CRM's API changes.

A portal with a login, documents and one integration is a different project from a B2B portal with pricing agreements from your ERP. On the web application cost page you answer a few questions and get a reasoned estimate.

How secure is a customer portal?

As secure as its design. Define per role who can see what, let customers log in with a second factor or with their own Microsoft or Google account, and log who ordered or changed what.

Because it holds customers' personal data, the GDPR applies. Test permissions and security before go-live, and remove accounts when a customer or employee leaves. Your Tech Club is ISO 27001 and ISO 9001 certified. That certification covers our organisation and way of working; the requirements a portal itself must meet are agreed per project.

How do you go about it?

Start with the questions coming in now, not with a feature list. Then the systems, then the roles, and only then the screens.

• List which questions customers ask, who answers them and which system holds the answer.
• Choose one customer group and a few features for the first version.
• Define roles and permissions, together with the data model.
• Connect the portal to your ERP, accounts or CRM and test each integration separately.
• Go live with a small group of customers and act on their questions and sticking points.
• Invite the rest in groups and build on what people ask for.

Not sure yet whether a portal is the right answer? The AI Opportunity Audit first maps where manual work gets stuck. The outcome can also be that you don't need a portal. If you are sure, you can have us build your customer portal.