info@toimi.pro
Thank you!
We have received your request and will contact you shortly
Okay
Web development

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

17 min
Web development

Start a B2B dealer portal with a repeat order that uses current contract prices, checks account limits and reaches the ERP once. Add status and document access around that path. Complete the permission and approval matrix below before deciding which features belong in the first release.

For help defining the scope, bring the matrix to a discussion about building a B2B platform around your ordering process.

Which repeat orders should you automate first?

Use your support log to select a repeat-order path: find an earlier order, check today's contract price, submit it, track delivery and retrieve the invoice. Pick a pattern sales can describe and accounting can verify. Include exceptions such as a discontinued item, a changed price or an account on hold.

Who approves prices and credit limits?

Separate the dealer's purchasing approval from the manufacturer's decision to extend credit. Name the person authorized to approve an exception and a substitute. Record triggers such as order value, product category or cost-center budget. Log each decision with the approver and time. Include every control required for the selected order in the first release.

Which system owns stock and account data?

Use the system map below to name one owner for each field. Agree the maximum stock delay, display its timestamp and define the reservation point. Recheck availability at submission where required by that workflow; otherwise use an agreed pending state until confirmation. Check account status at the agreed point too. A timestamp alone cannot authorize an order.

What can dealers do without a sales rep?

Assign account administration, buying, approval, accounts payable and view-only access by task. Let the dealer's authorized admin manage its users. Apply least privilege as defined by NIST: give each user only the access needed for that task. Reference checked October 15, 2026.

Test isolation between companies. A warehouse viewer may need delivery status without contract prices. An accounts-payable clerk may need invoices without ordering rights. Hiding a menu item does not establish an access boundary.

Test order forms, approval screens and invoice tables for accessibility. WCAG 2.2 covers redundant entry (3.3.7), accessible authentication (3.3.8) and information relationships (1.3.1). Read the criteria and exceptions when defining acceptance. Reference checked October 15, 2026.

Dealer permission and approval matrix

Copy this matrix. Replace each blank with your policy and a test result. Add a named owner and evidence link before accepting the release.

Action Dealer role and permission Manufacturer owner Approval or rejection rule Acceptance evidence
Repeat an order … … Current price and available items: … Order and ERP acknowledgment: …
Change quantity or price … … Allowed change and approver: … Accepted and rejected cases: …
Exceed a credit limit … … Hold, reject or route for approval: … Account state and decision: …
View stock and submit … … Warehouse, permitted delay, reservation, recheck or pending: … Source timestamp and order-acceptance test: …
Download an invoice … … Company and document access: … Own-account and cross-account tests: …
Retry submission … … Same event versus new order: … One order after repeated delivery: …
Remove a user … … Revocation and active sessions: … Access rejected after removal: …

Fill the rule column with sales and finance first. Then turn each rule into an allowed and a forbidden test. Accept a row only when the expected result and its evidence are recorded. An empty cell is unresolved scope.

How do you test exceptions and duplicate prevention?

Test a changed contract price, unavailable item, blocked account, missing approver and unavailable ERP. Submit the same event again. Check that the agreed order identifier prevents a second order. Keep the buyer informed while processing is pending.

What belongs outside the first release?

Defer work that neither completes nor safeguards the selected order path. Optional quotes, advanced reports, recommendations, chat and extra document workflows can wait. Keep mandatory permissions, approvals and credit checks in scope. Estimate the release after assigning owners to the data questions and acceptance conditions below. Bring the completed matrix to the B2B portal discussion.

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, checked October 15, 2026).
  • The same survey found that 69% of buyers report inconsistencies between the seller's website and what sales reps tell them. Use this finding as a reason to check consistency between portal data and sales guidance. It does not establish the effect of a particular portal.
  • 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, checked October 15, 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 to check the feature scope against your order path. The suggested sequence is conditional: a feature required to authorize or complete the selected order belongs in the first release. The matrix above records its rules and acceptance evidence.

# Feature Who uses it Data it needs MVP or phase 2 Adoption metric
1 Quick reorder and order history Buyer ERP orders MVP Share of repeat orders placed in the portal
2 Account-specific catalogs and contract pricing Buyer, your sales rep ERP price lists, PIM MVP Price disputes per month
3 Quick order by SKU and CSV upload Buyer ERP items, PIM MVP Lines per order via SKU entry or upload
4 Order status and shipment tracking Buyer, AP clerk ERP, WMS, carrier API MVP "Where is my order" calls and emails
5 Invoices, statements and online payment AP clerk ERP or accounting, payment gateway MVP Invoices paid online, days sales outstanding
6 Quotes and RFQ Buyer, your sales rep CRM, ERP pricing Phase 2 Quotes converted to orders in the portal
7 Multi-user accounts, roles and approval limits Approver, buyer CRM accounts, portal user store All roles, limits and approvals required for the selected order in MVP; optional extensions later Active users per account
8 Document library (spec sheets, certificates, SDS) Buyer, safety or quality staff PIM, document storage Phase 2 Document requests to support
9 Returns (RMA) and support tickets Buyer ERP, helpdesk Phase 2 RMAs opened in the portal
10 Stock availability and lead times Buyer, your sales rep ERP, WMS Required availability checks in MVP: agreed delay, reservation, recheck or pending Availability questions to reps
11 Notifications (email and SMS) Buyer, approver, AP clerk Events from all of the above MVP (email), phase 2 (SMS) Opt-out rate, click-through to order
12 Spend reports and exports Approver, finance Portal order data, ERP Phase 2 Monthly report downloads

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. Implement the role and approval rules recorded in the matrix. Required credit limits and approvals belong in the first release. Optional extensions can follow.

  8. Document library. Keep product specifications, certificates and safety data sheets connected to the right products. Assign an owner and version rule. For US hazardous-chemical requirements, check the applicable hazard communication standard with your responsible specialist.

  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. Agree the permitted delay and show the stock timestamp. Define when stock is reserved and rechecked, or keep the order pending until confirmation. Nightly synchronization is usable only if that delay and order-acceptance behavior fit the agreed workflow.

  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.

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.

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

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. Compare repeat use with the account’s ordering frequency. A second order alone does not establish a lasting change.
  • Routine calls and emails to reps. Tag "where is my order," "resend invoice" and "what's my price" requests in your helpdesk or inbox. Compare the result with your baseline.
  • Invoices paid online. If AP clerks log in, a second department depends on the portal.
  • Active users per account. Compare active users with the account’s purchasing roles. Ask whether limited use reflects the team size, access problems or missing invitations.
  • Failed syncs and price disputes. These are quality alarms. Investigate every price dispute.

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

FAQ

What is the difference between a B2B customer portal and a B2B e-commerce site?

A customer portal sits behind a login and serves existing accounts. A public B2B store may also sell to anonymous or new visitors. The portal shows contract prices, account-specific catalogs, invoices and order history. Many businesses combine both on one platform, but the portal features depend on account data from the ERP. Assess integration effort before approving the scope.

Do small distributors need a customer portal?

Yes, if repeat orders and invoice questions eat a noticeable share of rep time. Size matters less than order pattern. Compare the frequency of repeat orders with the cost of the proposed workflow. Start with reorder, order status and invoices. Defer optional reports. Keep any approval required by your pricing, credit or purchasing rules in the first release.

Should the portal show real-time inventory?

Only if your systems can keep it accurate. Agree the permitted delay, display the timestamp and define the reservation point. Recheck availability at checkout where the workflow requires it; otherwise keep the order pending until the agreed confirmation. Ask how often your ERP or WMS can publish stock, and what load frequent calls would put on it. A nightly timestamp alone is insufficient.

Can buyers pay invoices by ACH in a portal?

Yes, if your payment gateway supports ACH debit, and many list it next to cards. Check that before you design the payment screen. The portal passes the invoice to the gateway and records the payment back in your accounting system. Keep card data off your own servers by using the gateway's hosted fields or payment page. Confirm fees and settlement times with your provider.

How do you get customers to switch from email orders to the portal?

Make the first login easy and the first order faster than an email. Pre-load each account's order history and contract prices before inviting anyone. Have reps walk key buyers through one real reorder. Keep accepting email orders for a while, but reply with a link to the same order in the portal.

Top articles ⭐

All categories
Denver web development companies: compare 3 teams
Compare Aten Design Group, Chromedia and Neon Rain by the implementation you need: a content platform, a custom application or a business website. Their published work supports different questions. Start with the three-team table and use one shared specification to request comparable proposals. Compiled by Toimi editorial team. Research checked…
October 31, 2025
7 min
0
All categories
Website design for conversion growth: key elements
Your website is a complex ecosystem of interconnected elements, each of which affects how users perceive you, your product, and brand. Let's take a closer look at what elements make websites successful and how to make them work for you. Artyom Dovgopol Web design is not art for art’s sake,…
May 30, 2025
11 min
0
All categories
User account development for business growth
A personal website account is that little island of personalization that can make users feel right at home. Want to know more about how personal accounts can benefit your business? We’ve gathered everything you need in this article – enjoy! Artyom Dovgopol A personal account is your user’s map to…
May 28, 2025
15 min
0
All categories
Website redesign strategy guide
The market is constantly shifting these days, with trends coming and going and consumer tastes in a state of constant flux. That’s not necessarily a bad thing — in fact, it’s one more reason to keep your product and your website up to date. In this article, we’ll walk you…
May 26, 2025
13 min
0
All categories
Rebranding: renewal strategy without losing customers
Market success requires adaptation. Whether prompted by economic crisis, climate change, or geopolitical shifts, we'll explain when rebranding is necessary and how to implement it strategically for optimal results. Artyom Dovgopol A successful rebrand doesn’t erase your story; it refines the way it’s told. Key takeaways 👌 Rebranding is a…
April 23, 2025
13 min
0
All categories
Website development cost 2026: pricing and factors
We've all heard about million-dollar websites and "$500 student specials". Let's see what web development really costs in 2026 and what drives those prices. Artyom Dovgopol Know what websites and cars have in common? You can buy a Toyota or a Mercedes. Both will get you there, but the comfort,…
January 23, 2025
7 min
0
Your application has been sent!

We will contact you soon to discuss the project

Close