B2B customer portal: features, CRM sync and how to set one up

Ask any account manager at a distributor or manufacturer where the week goes, and you will hear the same list: "where is my order", "can you resend that invoice", "what did we pay for this last time", "please add our new warehouse address". None of it is selling, all of it is necessary, and most of it can be answered by the customer in thirty seconds if they had a place to look. That place is a B2B customer portal.

A portal is not a feature you switch on. It is a small product that sits between your customers and your CRM, ERP and billing systems, and it is usually the first piece of software a sales team has to own. Many teams launch on a packaged portal module; when account-specific pricing, approval chains or ERP data don't fit what is in the box, a custom web portal build on top of the CRM's API is the realistic next step. Either way, the hard part is the same: deciding what customers can do on their own and how that activity gets back to the people who sell.

This guide covers what a portal is, how it differs from a web store and a CRM, the features buyers actually use, how to sync it with your CRM, the buy vs build choice, the metrics that show it works and a 30-day plan for a first release. If you are still mapping how your systems connect, our CRM integration guide is a useful companion.

What is a B2B customer portal?

A B2B customer portal is a secure, account-based website or app where business customers manage their relationship with you. Each customer company gets its own space, with its own users, prices, documents and history. Inside it, a buyer can typically:

• see contract prices and the catalog their account is allowed to order from;
• place new orders and reorder from past ones;
• track order status, shipments and backorders;
• download invoices, statements, certificates and product documents;
• pay invoices or check credit balance;
• open and follow support cases or returns;
• manage their own users, addresses and approval rules.

The key word is account-based. A consumer site treats each visitor as one person. A B2B portal models a company with several people in it: a purchasing manager who approves, a warehouse lead who reorders, an accountant who only needs invoices. That structure is what makes a portal different from a login box on your website.

How is a customer portal different from a web store and a CRM?

The three overlap, and vendors use the words loosely. This table separates them by the job each one does.

In practice a portal often contains a store (ordering) and reads from a CRM (accounts and contacts). The distinction matters when you choose a tool: an ecommerce platform with a login is not automatically a good portal, and a CRM's portal module is not automatically good at ordering.

Why do B2B buyers want a portal?

Because business buyers increasingly prefer to get routine things done without a call. A Gartner survey published in 2026 found that 67% of B2B buyers prefer a rep-free experience. That does not mean they never want to talk to you. It means they don't want to wait for you to answer a question they could answer themselves.

The benefits show up on both sides:

• For customers: answers at any hour, no back-and-forth email, one place for every document, and reorders that take minutes instead of a phone call.
• For sales: fewer interruptions, more time for new business and renewals, and a live record of what each account is ordering and asking about.
• For service and finance: fewer "where is my order" tickets, faster invoice payment and fewer keying errors, because the customer enters the order and the system checks it.
• For the business: stickier accounts. When a customer's order history, documents and approval rules live in your portal, switching to a competitor costs them effort.

Which features does a B2B customer portal need?

Feature lists from vendors run to dozens of items. For a small or mid-size business, these are the ones buyers use week after week, grouped by job.

Ordering

• Account-specific catalog and pricing. Each company sees only the products and prices agreed in its contract. This is the feature that most often forces a custom build.
• Quick reorder. Repeat a past order or a saved list in one click. For distributors this is often the most used button in the portal.
• Bulk order entry. Paste SKUs and quantities or upload a spreadsheet, because B2B orders have many lines.
• Approval rules. Orders above a set value go to a manager before they reach you.

Order and account visibility

• Order status and tracking. Confirmed, picked, shipped, delivered, with backorder dates.
• Invoices and statements. Download copies, see what is due, pay online if your billing system allows it.
• Documents. Contracts, price lists, spec sheets, safety data sheets, certificates of conformity.

Service

• Cases and returns. Open a ticket or return request, attach photos, follow its status.
• Knowledge base. Answers to common product and account questions.
• Contact the account team. A visible name and a direct way to reach them, so self-service never feels like being shut out.

Administration and security

• Multi-user accounts with roles. Buyer, approver, finance, admin.
• Self-managed users and addresses. The customer's admin adds colleagues and ship-to locations without asking you.
• Single sign-on and two-factor login for larger customers with their own security rules.
• Audit log. Who ordered, approved or changed what, and when.

How does a customer portal sync with your CRM?

This is where most portal projects succeed or fail, and where competitor guides say the least. A portal that is not connected to the CRM creates a blind spot: the customer is active, but the rep can't see it.

Think of the sync in two directions.

Four rules keep the sync clean:

1. One owner per field. If the CRM owns the account name and the portal owns the delivery address, write that down. Two systems that can both edit a field will eventually overwrite each other.
2. Use a stable ID. Match records on the CRM account ID, not on company names or email domains. Our guide to what a CRM database is explains why clean IDs matter.
3. Push events, not snapshots. Send "order placed", "invoice viewed", "case opened" as activity on the CRM timeline. Reps act on events; they ignore nightly data dumps.
4. Turn activity into tasks. A big account that hasn't logged in for 60 days, or one that suddenly orders a new product line, should create a task for the rep. That is where the portal starts feeding the pipeline instead of just saving time.

Which type of portal fits your business?

Portals come in three broad shapes. The right one depends on what your customers do most.

• Ordering portal. For distributors, wholesalers and manufacturers with repeat orders. Centre of gravity: catalog, pricing, reorder, order status. Usually tied closely to the ERP.
• Service portal. For companies selling equipment, software or ongoing services. Centre of gravity: cases, documents, knowledge base, contracts and renewals. Usually tied closely to the CRM or help desk.
• Partner or dealer portal. For businesses that sell through resellers. Centre of gravity: deal registration, shared leads, marketing materials and partner pricing. Tied to the CRM's partner records.

Many businesses need a mix, but pick one primary job for the first release. A portal that tries to be all three on day one usually ships late and does none of them well.

Should you buy a portal or build your own?

There are three realistic routes, the same three that apply to the CRM itself, which we cover in depth in build vs buy CRM.

A simple test: if your pricing and ordering rules can be described in a page and match how most of your industry works, buy. If explaining your account rules takes a whiteboard session and the answer is "it depends on the customer", a packaged tool will force workarounds, and building the portal layer (while keeping the CRM and ERP you have) is often cheaper over three years.

How do you choose a B2B customer portal?

Run every option, bought or built, through the same checklist.

1. Fit to the top three jobs. Can a real customer reorder, check status and download an invoice without help? Test with a customer, not a demo account.
2. CRM and ERP integration. Native connector or API? Which direction does each object sync, and how often? Ask to see the field mapping.
3. Account model. Can one company have many users, roles, ship-to addresses and approval limits?
4. Pricing logic. Can it show contract prices, volume breaks and customer-specific catalogs without manual uploads?
5. Security. Single sign-on, two-factor login, role-based access, audit log, data location.
6. Mobile use. Warehouse and site staff will reorder from a phone. Check the portal on one.
7. Branding and domain. Your logo, your colours, your subdomain. Customers trust a portal that looks like you.
8. Licensing model. Per customer login pricing can get expensive fast once every buyer at every account has access. Model the cost at your real user count.
9. Exit plan. Can you export orders, cases and users if you switch?

Which metrics show the portal is working?

Pick a handful and report them monthly to sales and service leads.

• Active accounts. Share of invited customer companies that logged in during the month.
• Self-service order share. Orders placed in the portal as a share of all orders from portal-enabled accounts.
• Routine request volume. Order status, invoice copy and price check emails or tickets per month, compared with the baseline you tagged before launch.
• Order entry errors. Credits and corrections caused by wrong items, quantities or prices.
• Days sales outstanding. Whether invoices get paid faster once customers can see and pay them online.
• Rep time back. Ask reps once a quarter how many hours a week the portal saves them. Rough, but persuasive.
• Retention of portal accounts compared with accounts that never adopted it.

A 30-day launch plan for a first release

This plan assumes you have chosen a tool or a build partner and want a working pilot fast.

1. Days 1 to 5: scope. Use your tagged inbox to pick three jobs. Write the field ownership table between CRM, ERP and portal. Choose five to ten friendly customer accounts for the pilot.
2. Days 6 to 12: data. Clean the pilot accounts in the CRM: correct contacts, roles, ship-to addresses and IDs. Check that their prices and order history come through correctly.
3. Days 13 to 20: configure and connect. Set up catalog, pricing, permissions and the CRM activity feed. Create the rep tasks for inactivity and new product interest.
4. Days 21 to 25: test with real people. Sit with two customers while they place a reorder and find an invoice. Fix whatever made them hesitate.
5. Days 26 to 30: launch to the pilot group. Invitations go from the account manager, not a no-reply address. Add the portal link to invoices, shipping emails and support signatures. Book a review at day 60 with the metrics above.

For field teams who still take orders in person, the portal and the rep's own tools should share the same catalog and order history. Our guide to order-taking apps for sales reps covers that side.

Common mistakes that sink customer portals

• Launching empty. If a customer logs in and sees no orders, no invoices and wrong prices, they won't log in twice. Pre-load history before the invite.
• Leaving the CRM out. A portal that reps can't see from the account record turns into a service tool sales ignores.
• Too many features in release one. Chat, AI search and analytics can wait. Reorder and order status can't.
• No owner. Someone on your side must own the portal roadmap, user feedback and data quality, or it decays within a year.
• Hiding the humans. Self-service works best when the account manager's name is one click away. Buyers use the portal more when they know they can still reach a person.
• Not telling customers why. Explain what they gain: faster answers, order history, invoices at any hour. "Please use our new portal" is not a reason.

A good portal is quiet. Customers stop emailing about order status, reps stop forwarding invoices, and the CRM fills up with signals about which accounts are growing. When that happens, the portal is doing its job.

Questions

Try it on your own pipeline14-day trial, no card needed.

Start free