The Wholesale Wall: B2B Pricing Is Not a Retail Cart With Coupons

Wholesale looks simple until you build it.

At first, it sounds like bulk discounts. Add a quantity break, hide a few prices, maybe make a coupon for a trusted buyer. That works for a brochure-level store. It does not hold up once wholesale becomes a real sales channel.

In my cap-commerce work, wholesale touches the whole system: catalog visibility, buyer accounts, quote requests, price tiers, margin rules, production capacity, invoices, repeat orders, and staff review. It is not a checkout tweak. It is a different operating model.

That is the wholesale wall.

Retail Assumptions Break B2B

Most carts assume the buyer is a retail customer:

• One public catalog.
• One visible price.
• Immediate payment.
• A simple shipping address.
• A one-time order.
• Minimal staff involvement.

Wholesale buyers do not behave that way.

They may need a private catalog. They may see prices the public never sees. They may request a quote before paying. They may use purchase orders or net terms. They may reorder from an old design. They may ask staff to adjust lead time, delivery method, artwork status, or invoice format.

If the platform only understands retail checkout, every B2B requirement becomes a patch.

Why Patches Pile Up

The usual workaround is plugins: wholesale pricing plugin, quote plugin, role plugin, invoice plugin, customer-group plugin, maybe a custom checkout plugin. Each one solves a slice. None of them owns the whole workflow.

That creates awkward questions:

• Which price wins when a role discount and quantity tier both apply?
• Can a buyer request a quote without exposing public checkout?
• Can staff convert a quote into an order without re-entering data?
• Can invoices reflect the negotiated price and the production notes?
• Can supplier-facing views hide buyer margin?

If those answers live across separate plugins, the workflow becomes fragile.

The Custom-System Difference

In a custom system, wholesale can be modeled directly.

Buyer accounts can have tiers, catalogs, margin rules, credit terms, and approval requirements. Quotes can be their own stateful objects instead of abandoned carts. Staff can review, adjust, and convert them into orders. Production notes can follow the order. Invoices can be generated from the same source of truth.

That structure matters because wholesale is relationship-driven. The system should remember the relationship, not just the transaction.

What I Build Around

A good B2B commerce model usually needs:

• Buyer roles and account approval.
• Private or tiered catalogs.
• Quantity and customer-specific pricing.
• Quote-to-order conversion.
• Artwork and proof status.
• Invoice generation.
• Reorder history.
• Staff-only margin visibility.
• Supplier-safe handoff views.

This is not glamorous. It is the boring operational layer that makes wholesale work.

The Practical Rule

Do not force wholesale through retail concepts.

If the business depends on B2B, model B2B directly. Build the account rules, quote lifecycle, approval flow, and invoice data into the core app. Then the storefront becomes a surface on top of the workflow instead of a retail cart pretending to be a wholesale platform.

That is how you get past the wholesale wall.