Customer portal
A customer portal is a logged-in area of a company's website where existing customers see their own information: orders, documents, support tickets, pricing or account history. It replaces the emails and phone calls people currently make to ask questions the company could answer automatically.
In practice
In practice a B2B portal is defined by what it exposes rather than by the software behind it. A distributor's portal usually shows order history, shipment status and account-specific pricing. A manufacturer's shows drawings, certificates of conformance and warranty records. A professional services firm's is mostly documents and approvals. Those are four different products that all get sold under one name, which is why comparing portal vendors on features rarely settles anything.
The economics work differently from most business software, and this is the part companies discover late. A portal has far more external users than internal ones, often by a factor of fifty, so a tool priced per seat is priced for the opposite of this job. Platforms that charge flat, or by records, or by a member count, stay affordable as the customer base grows. Getting that wrong is how a portal that looked cheap at launch becomes the largest line on the software bill.
The second constraint is where the data lives. A portal that shows order status has to read from whatever system holds orders, which for most established B2B companies is an ERP that was never designed to be read by a website. That integration is the project, and it is usually built through an API rather than a native connector. A portal with no live data behind it is a document folder with a login.
Portals are also a retention tool more than an acquisition one. Nobody chooses a supplier because of the portal, but customers who use one call less, chase less, and are measurably harder to displace, because switching means giving up a working system as well as a relationship.
A test you can run in ten minutes: list the five questions your customers phone or email you most often. If three or more are questions about their own account, orders or documents, those are answerable without a person and a portal will pay for itself. If they are mostly technical or pricing questions on new work, a portal will not help and the effort belongs on the public site instead.
Common questions
What is the difference between a customer portal and a client portal?
Very little, and vendors use the terms interchangeably. Client portal tends to describe document exchange with a defined list of accounts, common in professional services. Customer portal more often means self-service access to orders or support at higher volumes. The distinction that matters commercially is not the label, it is how many external users you expect, because that decides which pricing model works.
Should we build a customer portal or buy one?
Buy, in most cases. A configured platform is live in weeks against months for a build, and someone else maintains the authentication, permissions and security patches. Building makes sense when the portal is the product customers pay for, when it has to live inside an existing application, or when the data model is genuinely unlike anything a platform expects.
Can a customer portal connect to our ERP?
Some can, and this requirement eliminates most options. Database-first platforms can hold synced data and show it per account, usually through an API or a middleware service rather than a native integration. Support-led portals are not built for it. If live order or account status is the point, test that path before comparing anything else.
Do customers actually use portals?
They use them when the portal answers a question faster than a phone call and not otherwise. Adoption tracks usefulness rather than design: a portal showing live order status gets used daily, and a portal showing static documents someone already has by email gets logged into once. Decide what it answers before deciding what it looks like.