How to plan a B2B ecommerce website.

Decide what the website should do in the sales process

B2B ecommerce can mean public self-service purchasing, private customer portals, online quoting, assisted ordering, repeat-order tools, dealer access, or a combination. Start with the commercial model: who can see products and prices, who can buy, when sales staff intervene, and which orders should remain offline.

Choose the first release around valuable, repeatable journeys. Trying to automate every exception can make the project too large to validate. Keep an assisted route for complex orders while moving clear, frequent tasks online.

Model companies, roles, and permissions

A business customer may include buyers, requesters, approvers, finance staff, site managers, and administrators. Define who creates the company account, verifies eligibility, invites colleagues, sees negotiated terms, places orders, approves spend, manages addresses, and views invoices or order history.

Map account states and exceptions: pending approval, suspended credit, departed staff, several branches, shared budgets, purchase limits, and customers belonging to more than one entity. Authentication and account recovery must be usable without exposing another customer's prices or records.

Make complex products and terms understandable

Define customer-specific catalogues, contract prices, quantity breaks, minimums, packs, lead times, stock availability, substitutes, technical documents, certifications, and delivery restrictions. Decide which system owns each value and when it updates.

Buyers often know a SKU and need speed, while new specifiers need education and comparison. Support search by the identifiers customers use, category navigation, filters based on selection criteria, bulk entry, saved lists, and useful product detail. The general guide to ecommerce website requirements covers the retail foundations that still apply.

Design ordering around real procurement rules

Map quick order, reorder, quote request, sample request, saved cart, approval, purchase order, card or account payment, tax exemption, credit terms, delivery scheduling, split shipment, collection, confirmation, changes, returns, and invoice access. State which journeys are available to each account type and market.

Do not force every visitor into checkout. A high-value configurable order may need a clear handoff to sales with the selected products and account context preserved. Conversely, routine repeat orders should not require a call when the business has already approved the customer and terms.

Treat integration and adoption as part of the design

Map CRM, ERP, product information, pricing, stock, tax, payments, credit, fulfilment, customer service, identity, and analytics. For every connection, define source of truth, direction, timing, failure handling, and manual fallback. Prototype the hardest rule before committing to the full interface.

• Interview customers and sales: compare stated needs with actual ordering work.
• Test realistic accounts: include negotiated prices, multiple users, and exceptions.
• Plan onboarding: decide how existing customers activate access and learn the new route.
• Keep ownership visible: assign teams for catalogue, accounts, orders, content, and support.
• Measure adoption: track completed self-service journeys and the reasons people still need help.