In the late twentieth century, wholesale commerce still moved at the speed of paper. A buyer faxed a purchase order, a sales representative checked a spreadsheet, an accounts team approved credit, and someone entered the order into an internal system. The process was slow, but its logic was clear: pricing, payment terms, inventory, and authorization lived in separate human-controlled steps.

Then came the web storefront, which first carried consumer retail habits into business purchasing without removing the old machinery underneath. Today, that arrangement is being reconsidered. Gartner reported in 2025 that 61% of B2B buyers prefer a rep-free buying experience, while Forrester's 2024 research found that 86% of B2B purchases stall during the buying process. The self-serve wholesale portal is therefore not a sudden novelty. It is the latest answer to a long-standing problem: how to preserve commercial controls while removing avoidable dependence on manual administration.

Before the portal: why wholesale became a paper process

Wholesale developed around relationships rather than standardized checkout. A retailer might receive one price, a department store another, and a trusted distributor a third. Payment could be due in 30, 60, or 90 days, with credit limits negotiated account by account. Purchase orders created an audit trail, but they also created queues.

Email and spreadsheets shortened those queues without changing the underlying structure. Sales teams still translated conversations into orders, finance still checked terms, and operations still reconciled mismatched product codes. This is why many B2B brands have historically treated ecommerce as a catalogue or lead-generation layer rather than a true ordering system: the commercial rules existed elsewhere.

The cost became more visible as product ranges widened and buyers expected consumer-grade convenience. Every manual quote, price correction, and reorder introduced a small opportunity for delay or error. The old process could support a limited number of accounts through personal attention, but it became difficult to scale without adding more people or more disconnected software.

The first digital shift: storefronts without commercial memory

The first generation of ecommerce solved product discovery and card payment, but wholesale often remained an exception. A public store displayed retail pricing, while wholesale customers received PDFs, emailed spreadsheets, or hidden collections. Some brands created a second store, then a custom portal, then a connector to an enterprise resource planning system. Each addition answered a local problem, but the total architecture became harder to maintain.

The second shift has been more architectural than visual. Modern B2B commerce places the buyer, company, company location, catalogue, price, payment term, and order approval into a connected account model. The storefront remains the visible layer, but the rules that once lived in inboxes can now be represented as structured data.

Shopify's official B2B feature overview describes company profiles and company locations that can carry separate payment terms, shipping addresses, catalogues, tax settings, and checkout controls. The platform also supports customer-specific product publishing, quantity rules, volume pricing, purchase order numbers, reorders, and draft orders. This is why the modern wholesale portal looks less like a separate website and more like a controlled extension of the existing commerce stack.

Price lists moved from spreadsheets into catalogues

Wholesale pricing usually begins with segmentation. A brand may sell one collection to independent boutiques, another to distributors, and selected products to regional partners. The historical spreadsheet expressed those differences manually; a Shopify catalogue expresses them through product availability and assigned pricing.

Shopify supports fixed prices, percentage adjustments, volume pricing, and quantity rules, although the number and assignment options vary by plan. According to Shopify's documentation, Basic, Grow, and Advanced plans allow up to three active catalogues across B2B markets, while Shopify Plus supports unlimited catalogues and direct assignment to company locations. That distinction matters because a small wholesale programme may fit native tools, whereas complex regional or account-level pricing may require an app, custom development, or a more advanced plan.

The sensible sequence is to define the commercial model before selecting the interface. Product eligibility, minimum order quantities, case packs, currencies, and discount logic should be documented first. Once those rules are stable, the storefront can expose quick order lists, clear availability, and account-specific pricing without duplicating the product catalogue in another system.

Net terms and approvals became workflow, not correspondence

Net terms are among the clearest examples of wholesale logic becoming software. Shopify supports Net 7, Net 15, Net 30, Net 45, Net 60, Net 90, due on fulfillment, and due on receipt, with terms assigned by company location. Shopify's payment terms guidance explains that these settings determine how long a company has to pay and allow orders to be tracked and collected as they become due.

That does not mean every credit policy becomes automatic. Finance still decides eligibility, limits, deposits, and exceptions. The difference is that the approved policy can be attached to the account instead of retyped for every order. Shopify Flow can also trigger payment reminders, while invoices and manual payment methods can support customers who do not pay by card.

Approvals follow a similar path. Company locations can be configured so orders are submitted as drafts before confirmation, allowing sales or operations teams to review quantities, pricing, inventory, or freight. A buyer retains self-serve access, but the organization keeps a checkpoint where the commercial risk requires it. This is the important distinction between digitizing a wholesale workflow and simply removing human oversight.

The practical launch model: extend the stack before replacing it

A Shopify B2B wholesale launch can usually proceed in three layers. First, the data layer maps companies, locations, contacts, products, inventory, tax rules, price lists, and payment terms. Second, the experience layer designs login, account navigation, quick ordering, reorder paths, approval messages, and mobile behavior. Third, the operations layer connects fulfilment, accounting, ERP, customer service, and reporting.

The objective is not to reproduce every historical exception on day one. A contained pilot with a few customer segments can reveal which rules are genuinely necessary and which survived only because the old process made change difficult. Existing customer and order history can be migrated into company records, while B2B APIs and integrations can connect Shopify to ERP or accounting systems when native functionality is insufficient.

This approach avoids forking the stack. Instead of maintaining a separate wholesale storefront, the business can evaluate Shopify's commerce platform as the shared foundation, then add only the extensions required by verified workflow gaps. A custom headless storefront remains possible through Shopify's Storefront and Customer Accounts APIs, but custom architecture should follow proven commercial requirements rather than precede them.

The implication for the next wholesale build

For brands moving from emailed POs to self-serve purchasing, the central decision is not whether wholesale should become digital. That transition is already underway. The decision is where authority should live: in people and documents, or in clearly designed rules that people can inspect and amend.

If the commercial model is documented first, a Shopify B2B portal can preserve price lists, net terms, purchase orders, and approvals inside a familiar operating environment. The result is not the erasure of the sales relationship. It is a more precise division of labour, where buyers handle routine orders, teams handle exceptions, and the stack grows around the business instead of splitting it in two.

For a brand, this is where design and development meet operational history. The most effective portal does not pretend the fax machine never existed. It keeps the useful controls that emerged from that era, removes the waiting, and gives the next order a clearer route from intention to fulfilment.