What features does a B2B customer portal need? 12 that buyers actually use

Short answer: the first four features

A customer portal earns its keep when a purchasing manager stops calling your sales rep for routine work. Four jobs generate most of those calls. "What did we order last time?" "What is our price?" "Where is my order?" "Can you resend the invoice?"

Each of the four features answers one of those questions without a human. Everything else on the list is useful. None of it matters if these four are slow, wrong or missing.

One warning up front. All four depend on data you already have somewhere else. Order history, contract prices, shipment status and invoices usually live in the ERP or accounting system. The portal is a window onto that data. If the window shows stale or wrong numbers, buyers go back to the phone.

What B2B buyers expect from self-service

The research is consistent on one point: buyers want to do routine work themselves and talk to a person for the hard parts.

• In Gartner's survey of 632 B2B buyers, fielded August through September 2024, 61% said they prefer an overall rep-free buying experience (Gartner press release, June 25, 2025, as of September 30, 2026).
• The same survey found that 69% of buyers report inconsistencies between the seller's website and what sales reps tell them. A portal that shows the contract price from the ERP closes exactly that gap.
• McKinsey's 2024 B2B Pulse, with nearly 4,000 decision makers in 13 countries, found buyers use an average of ten interaction channels in their journey, up from five in 2016 (McKinsey, "Five fundamental truths," September 12, 2024, as of September 30, 2026).
• McKinsey also reports a "rule of thirds": at any stage, about one-third of customers want in-person contact, one-third want remote contact and one-third prefer digital self-serve. Among sellers that offer e-commerce, more than one-third of revenue now comes through it.

Read those together and the brief writes itself. The portal takes the repeat, low-judgment work. Your reps keep the new accounts, the custom deals and the complaints. Nobody is asking you to replace the sales team. They are asking you to stop making them retype order numbers.

The 12 features, ranked

Use this table as your working document. Copy it into a spreadsheet, then change the "MVP or phase 2" column to fit your business. The ranking below reflects one logic: features that remove the most routine calls and need data you already hold go first.

What each feature does, and the pain it removes

1. Quick reorder and order history. Many B2B purchases repeat. Show the last orders with a one-click reorder and let the buyer edit quantities. This kills the "send me what we got in March" email.

2. Account-specific catalogs and contract pricing. Each account sees its own assortment and its own negotiated prices. It sounds simple. It shapes the whole data model, so decide it first. A wrong price on screen does more damage than no price at all.

3. Quick order by SKU and CSV upload. Experienced buyers know part numbers. Give them a grid where they type SKU and quantity, plus a CSV import for the 200-line restock. Validate every line and show errors next to the row.

4. Order status and shipment tracking. Show the status from your ERP and the tracking link from the carrier. Split shipments and backorders must be visible. Hiding them just moves the question to the phone.

5. Invoices, statements and online payment. Accounts payable staff want PDFs, open balances and a way to pay by card or ACH. This is often the feature that gets a second department to log in.

6. Quotes and RFQ. For custom or large orders, the buyer submits a request and your rep answers inside the portal. An accepted quote should turn into an order with one click. Otherwise it lives in email forever.

7. Multi-user accounts, roles and approval limits. One customer company, many people. This one gets its own section below.

8. Document library. Spec sheets, compliance certificates and safety data sheets, filtered to the products the account buys. If you ship hazardous chemicals, US rules already require an SDS with the initial shipment and the first shipment after an update (29 CFR 1910.1200(g)(6), as of September 30, 2026). A portal gives buyers one place to find the current version.

9. Returns and support tickets. Let buyers open an RMA against a specific order line. Pre-fill the order data so they never retype it. Route the ticket to the right team.

10. Stock availability and lead times. Show real availability or a clear lead time. If your inventory syncs once a night, say so on the page. Stale stock numbers destroy trust fast.

11. Notifications. Order confirmed, shipped, invoiced, overdue, approval needed. Keep them few and useful. Let each user choose which ones they get.

12. Spend reports and exports. Finance and procurement want spend by site, by category and by month, exportable to a spreadsheet. Build it after you have real order data flowing. Early dashboards show empty charts and teach nobody anything.

Roles and approvals: one company, many users

This is the part of a portal most often left half-done. A single customer account can hold a buyer who places orders, a manager who approves them, an AP clerk who pays, and a warehouse lead who only checks deliveries. Each needs a different view.

Start with a plain role model:

• Account admin adds and removes users for their own company.
• Buyer builds carts and places orders, sometimes only up to a limit.
• Approver releases orders above that limit.
• AP clerk sees invoices and statements and pays them. No catalog access needed.
• View-only tracks orders and downloads documents.

Two design rules keep this sane. First, apply least privilege: each user gets the minimum access needed for their tasks, the principle NIST defines in its security glossary (as of September 30, 2026). A warehouse lead does not need to see your contract prices. Second, let the customer's own admin manage users. If every new hire requires a ticket to your team, the portal becomes a chore.

Approval limits deserve care. Decide what triggers an approval: order total, specific product categories, or a monthly budget per cost center. Decide what happens when the approver is on vacation. Log every approval with a name and timestamp. Procurement teams ask for that audit trail sooner or later.

Accessibility lands here too. Order forms, approval screens and invoice tables are the heart of the portal. WCAG 2.2 adds two criteria that hit portals directly: Redundant Entry (3.3.7), so users are not forced to retype information they already gave in the same process, and Accessible Authentication (Minimum) (3.3.8), which limits login steps that rely on memorizing or solving puzzles (W3C WCAG 2.2, Recommendation dated December 12, 2024, as of September 30, 2026). Tables also need real header markup under 1.3.1 Info and Relationships.

Integrations: where the data comes from

Every feature in the table reads or writes data owned by another system. Map those systems before a single screen is designed. The list is short:

• ERP holds customers, items, price lists, orders, invoices and usually stock. It is the system of record for most of the top five features. Plan early for connecting the portal to your ERP, including what happens when the sync fails.
• CRM holds contacts, account owners and open quotes. It decides which rep a quote request goes to.
• PIM holds product descriptions, images, specs and documents. Without one, product content often sits in spreadsheets, and the portal inherits that mess.
• WMS and carriers hold picking status and tracking numbers.
• Payment gateway processes card and ACH payments and reports them back to accounting.

Two questions decide most of the budget. Is the sync real time or batch? And which system wins when two disagree? Write the answers down. Orders placed in the portal must land in the ERP with failure handling: retries, alerts and a visible "pending" state for the buyer.

Before the spec: six data questions

Answer these before you ask anyone for an estimate. They surface the work that is invisible in a feature list.

1. Where do contract prices live today, and who changes them?
2. Who owns the product catalog, and is it complete enough to show customers?
3. How often does stock update: every few minutes, hourly or nightly?
4. Can your ERP accept orders through an API, or only by file import?
5. How are customer accounts structured: one record per company, or per ship-to location?
6. Which documents must buyers see, and where are the current versions stored?

What to build first: MVP vs phase 2

Ship the smallest portal that removes routine calls. In practice that means features 1 through 5, basic roles from feature 7, and email notifications. Add stock visibility if you sell from inventory. Toimi's B2B portal page lists a launch window of 6–10 weeks. What fits in that window depends on how clean your ERP data is.

Phase 2 is quotes, approval limits, the document library, returns and reports. Build it once you see how buyers behave in the MVP. Their questions to support will tell you which phase 2 feature to ship first.

A few things to skip at launch. Personalized recommendations need order history you do not have yet. Chat widgets duplicate your reps without the context. Custom dashboards per account are expensive to maintain and rarely opened in month one. Price is the same story: any honest figure comes as an estimate after a brief, once the six data questions are answered.

How to know buyers use it

A portal can go live and still fail quietly. Track adoption from the first week, and compare against the months before launch.

• Share of orders placed in the portal. The main number. Track it per account, since a few large customers can hide a lot of nonuse.
• Repeat orders through the portal. A buyer who orders twice has changed a habit. One order can be curiosity.
• Routine calls and emails to reps. Tag "where is my order," "resend invoice" and "what's my price" requests in your helpdesk or inbox. They should fall.
• Invoices paid online. If AP clerks log in, a second department depends on the portal.
• Active users per account. One login per company usually means the admin never invited the team.
• Failed syncs and price disputes. These are quality alarms. One wrong price can undo a month of adoption work.

Review these monthly with sales. Reps know which customers still phone in orders. Ask those customers why.