B2B E-commerce Features: What Wholesale and Trade Buyers Expect

A consumer store is built around one person, one basket and one card payment. A wholesale or trade buyer works differently: they order for a company, at prices agreed in advance, usually the same items again and again, and they expect an invoice rather than a card form. Put that buyer in front of a standard consumer checkout and they go back to emailing a spreadsheet to your sales rep.

This guide explains the B2B e-commerce features that trade buyers expect, which of them the main platforms provide out of the box, and where e-commerce development work is usually needed to close the gap. It is written for wholesalers, distributors and manufacturers in the US and UK who are planning a trade portal or adding wholesale to an existing store.

How B2B buying differs from consumer shopping

Four differences drive almost every B2B feature. First, the customer is a company, not a person. Several people buy on its behalf, often from different branches, and someone in finance pays the bill. Second, the price is negotiated. Two customers looking at the same product may see different prices, and some may not be allowed to see the product at all.

Third, orders repeat. A trade buyer rarely browses; they know the part numbers and want to get forty lines into a cart quickly. Fourth, payment is on account. The buyer raises a purchase order, you ship, you invoice, and they pay within agreed terms. Each feature below follows from one of these four facts.

Company accounts, buyer roles and approvals

The foundation is a company account: one customer record that holds several users, several delivery addresses and shared settings such as price list and payment terms. Without it, every buyer at the same customer is a separate stranger to your system, and none of the other features can be applied consistently.

On top of that sit roles and approvals on the buyer's side. A junior buyer can build an order, but orders above a set value need sign-off from a manager before they reach you. This is the customer's own internal control, not yours, and larger customers will ask for it. Adobe Commerce is a good reference for how it works: company users set up their own approval rules based on order total, shipping cost or number of SKUs, and choose who must approve.

Customer-specific pricing, catalogs and quantity rules

Trade pricing has three layers. A customer-specific price list sets the agreed price for each company or customer group. A customer-specific catalog controls which products that company can see and buy, which matters for own-brand lines, regional restrictions or products that need a license to purchase. Quantity rules then shape the order: price breaks at volume, minimum order quantities, and case or pallet increments so nobody orders seven units of something sold in boxes of twelve.

The practical question is where these prices live today. If they are maintained in your ERP or accounting system, the store should read them from there rather than hold a second copy that drifts out of date.

Quick order, reorder and quotes

Speed matters more than merchandising for repeat buyers. The features to look for are a quick order form where the buyer types or pastes SKUs and quantities, saved lists for regular orders, and one-click reorder from order history. Some businesses also need CSV upload for very long orders.

Quotes cover the orders that do not fit the price list: unusually large volumes, project pricing, or custom items. A proper quote workflow lets the buyer request a price from the cart, lets your sales team respond and revise it, and converts the accepted quote into an order without retyping. If your sales reps close most large deals by phone, also check whether they can log in and place an order on the customer's behalf.

Purchase orders, credit terms, invoicing and tax

Paying on account needs more than a "pay by invoice" button. You need payment terms stored per customer (net 30, for example), a purchase order number captured at checkout, a credit limit that can block or hold an order, and an invoice the customer can view and pay online. Many trade stores keep card payment as well, for new accounts or customers on credit hold.

Tax handling also changes. In the US, many trade buyers purchase for resale and can be exempt from sales tax when they provide the right certificate; in the UK, business customers expect VAT numbers and VAT invoices to be handled properly. The store needs a tax status per customer or per location and somewhere to record the supporting evidence. The rules vary by state and country, so treat this as a prompt to consult your accountant or tax adviser, not as legal or tax advice.

Which platforms include B2B features natively

The statements below come from each vendor's documentation as read in October 2026. Plans and features change, so confirm them before you commit.

• Shopify. Shopify states that B2B is available on the Basic, Grow, Advanced and Plus plans, with companies, catalogs, net payment terms, quantity rules, quantity price breaks and a quick order list on all four. The limits matter: the three lower plans allow up to 3 active catalogs, while Plus allows unlimited catalogs and direct assignment to individual companies and locations. Deposits and partial payments are Plus only. A company can have several locations, each with its own tax ID, tax exemptions and payment terms.
• Adobe Commerce. Adobe's B2B documentation lists company accounts with a company hierarchy, shared catalogs with custom pricing per company, quick order, requisition lists, negotiable quotes, purchase orders and payment on account against a company credit line. It refers to installing and enabling a B2B extension, so this is an add-on to the core product rather than something every installation has switched on.
• BigCommerce. BigCommerce documents B2B Edition as including company accounts, sales quotes, invoice management for purchase orders paid on net terms, user roles, sales staff assigned to accounts, and a Buyer Portal for company users.

All three document company accounts and payment on terms. The differences are in limits, depth and plan level, so start the comparison from your own requirements.

When custom development is needed

Native features handle the common case. Custom work tends to appear in four places. The first is ERP and accounting integration: syncing customers, prices, stock, orders, invoices and payments between the store and systems such as NetSuite, SAP, Microsoft Dynamics, Sage, Xero or QuickBooks. This is usually the largest and riskiest part of a B2B project, because it depends on how clean your data is and which system owns each field.

The second is pricing logic the platform cannot express, such as contract prices with expiry dates or prices calculated from cost plus a customer margin. The third is approval or credit rules beyond what the platform offers. The fourth is anything specific to your trade: product configurators, scheduled or split deliveries, punchout connections to a customer's procurement system. If several of these apply, a custom build on a framework such as Laravel can cost less over time than bending a platform against its design.

Common mistakes

• Launching every feature at once instead of the ones your top customers use weekly.
• Keeping prices in two systems and reconciling them by hand.
• Treating the ERP integration as a final step, when it shapes the data model from day one.
• Forgetting the sales team, who need to quote and order for customers and will bypass a portal that slows them down.
• Migrating customers without checking contacts, terms and tax status, so the first login shows the wrong price.

What to do next: phase the rollout

Start by listing how your ten largest customers actually order today, and what your team re-keys by hand. That list is your requirements document. Then phase the work. Phase one is company accounts, customer-specific pricing, reorder and order on account with a purchase order number, launched to a small group of friendly customers. Phase two adds the ERP or accounting sync in both directions, online invoices and credit limits. Phase three adds quotes, buyer approvals and trade-specific features once real usage shows which are worth building.

Each phase should remove a manual task you can name. If it does not, it can wait.

Conclusion

B2B e-commerce is not a consumer store with a discount code. It is built on company accounts, agreed prices, fast repeat ordering and payment on terms, and the major platforms now provide much of that natively at different plan levels. The work that decides whether a project succeeds is usually the integration with your ERP or accounting system and the handful of pricing and approval rules that are specific to your business.

If you would like a second opinion on which features your platform covers and what would need to be built, you can send Entrant Technologies your requirements.