Why B2B portals fail when they copy consumer ecommerce

Consumer ecommerce is built around a clean story: one person, one basket, one card, one order, delivered to one address. Almost every design decision — the account, the checkout, the order history — follows from that story. It works beautifully, which is exactly why it is so tempting to reuse it for business customers.

The trouble is that a B2B relationship does not fit the story. The “customer” is an organisation, not a person. The order may need approval. The price is specific to that account. Several people act on behalf of the same buyer, each with different authority. When a portal quietly assumes the consumer story anyway, it does not fail loudly — it just makes everyone's day slightly harder, forever.

The account is an organisation, not a person

In consumer ecommerce, the account is the person. In B2B, the account is the business, and people are members of it. That single shift changes almost everything downstream: who can see which orders, whose address book is whose, what “my orders” even means when the person who placed an order has left the company.

A portal that models only individual accounts forces businesses into ugly compromises — shared logins passed around a team, or a separate account per person with no shared view of the relationship. Both undermine exactly the thing a portal is meant to provide: a single, trustworthy view of the account.

Multiple users mean permissions, not just seats

Once you accept that several people use one account, you inherit permissions. Not as a bolt-on, but as a core part of the model:

• A buyer may place orders but not change company details.
• A manager may approve orders above a threshold, but not below.
• A finance contact may see invoices and statements, but not place orders at all.
• An administrator may add and remove colleagues without being able to see every order.

Consumer platforms have nowhere to put this, so teams end up encoding it in email etiquette and habit. A B2B portal has to make roles and permissions real, because getting them wrong is not a small annoyance — it is a customer seeing something they should not, or being unable to do their job.

Quotations and approvals are part of the journey

Consumer checkout assumes the decision to buy has already been made; its job is to remove friction between decision and payment. B2B frequently inverts this. The order is often a request that becomes a commitment only after a quotation is accepted or an approval is granted.

In B2B, the interesting states are not “in basket” and “paid”. They are “quoted”, “awaiting approval”, “approved”, and “on account” — and a portal that cannot express them pushes that work back into email.

If the portal cannot represent a quote, an approval step, or an order placed on account rather than paid immediately, all of that essential activity moves off the platform and into inboxes — which is precisely the fragmentation the portal was supposed to end.

Repeat ordering is the main event, not a convenience

For a consumer, re-ordering is a nice-to-have. For a business that buys the same things on a rhythm, it is the main event. Reorder from history, saved lists, standing orders, and fast bulk entry are not garnish — they are the difference between a portal people use and one they abandon for a phone call.

Documents, support and the parts nobody demos

A great deal of a B2B relationship is documents and exceptions: invoices, statements, delivery notes, proof of purchase, and the messy business of when something goes wrong. A portal that handles the happy path but has no home for “where is my invoice?” or “this delivery was short” sends users straight back to email and phone — and the internal team back to spreadsheets.

What good looks like

A B2B portal that respects its own domain starts from the organisation, models people and permissions honestly, treats quotes and approvals as first-class states, makes repeat ordering effortless, and gives documents and exceptions a proper home. None of this is exotic. It simply requires designing for the relationship in front of you rather than borrowing a model built for a different one.

The consumer patterns are not wrong — they are just answers to a different question. The work of a good B2B portal is to ask the right question first, and to build the account, the permissions and the workflow around the way businesses actually buy.