Pricing is the hardest part of B2B and most brands underestimate it. The configuration looks straightforward in the admin (catalogs, price lists, customer assignment) and gets complicated fast when real customer requirements meet the platform's model. Volume breaks. Customer-specific overrides. Contract pricing that the sales team negotiates per account. ERP-driven dynamic pricing. The first three months of a B2B operation typically reveal pricing edge cases the original configuration didn't account for.
This piece is the practical implementation guide for B2B custom pricing on Shopify Plus. The four levels of pricing complexity, what the native model handles, where it hits limits, the apps and integrations that close the gap, and the decision framework for choosing the right architecture before you start configuring. If you're planning a Shopify Plus B2B setup or fixing a pricing implementation that's not working, the patterns below should help.
Why B2B pricing is hard
B2C pricing is mostly simple. Everyone pays the displayed price. There are sales and discounts but no per-customer negotiation. The pricing engine is a thin layer over the catalog.
B2B pricing is the opposite. Customers negotiate pricing per account. Volume discounts kick in at thresholds that vary by customer. Strategic accounts get contract-specific pricing that overrides standard tiers. New customers get introductory pricing for 90 days. Distributors get a different model than direct buyers. The pricing engine becomes a decision layer that combines customer attributes, product attributes, quantity, contract terms, and sometimes real-time inventory or supply costs.
Shopify Plus B2B handles a good chunk of this complexity natively. The native model handles standard tiered pricing, volume breaks, and customer-specific catalogs cleanly. The model starts to creak when you stack customer-specific overrides, blended volume rules, or ERP-driven dynamic pricing on top.
The four levels of pricing complexity
Most B2B pricing implementations fall into one of four levels of complexity. Each level has a corresponding architecture pattern.
Level 1: Tiered pricing
A few standard tiers (Standard, Strategic, Distributor). Each tier has a fixed discount off retail or a specific price list. Customers are assigned to a tier and pay the tier price. No customer-specific overrides.
Architecture: native Shopify Plus B2B catalogs + price lists. One catalog and one price list per tier. Customers assigned to their catalog at setup. Done.
Implementation time: 1-2 weeks of configuration.
Suitable for: most mid-market B2B operations with $5M-$30M revenue and relatively standard pricing structures.
Level 2: Tiered + volume pricing
Same tier structure as Level 1, with quantity-based price breaks layered on top. Buy 1-9 units at the tier price, 10-49 at a discounted price, 50+ at a deeper discount.
Architecture: native Shopify Plus B2B catalogs + price lists with quantity price breaks. Configure the volume tiers per SKU within the price list. The customer sees the appropriate price based on their cart quantity automatically.
Implementation time: 2-3 weeks (the configuration work scales with SKU count and the complexity of the volume rules).
Suitable for: B2B operations where volume is a meaningful pricing lever. Common for wholesale brands and distributor operations.
Level 3: Tiered + volume + customer-specific overrides
Most customers fit the standard tier model. A handful of strategic accounts have negotiated contract pricing that overrides specific SKUs or categories. You need both the standard model and the per-customer exceptions.
Architecture: native catalogs and price lists for the standard tiers, plus a dedicated catalog or app-based override layer for the strategic accounts. Two common patterns:
Pattern A: dedicated catalog per strategic account. Each strategic customer gets their own catalog and price list. Works cleanly for up to 20-30 strategic accounts. Beyond that, the admin overhead becomes unmanageable.
Pattern B: app-based pricing override. Use a B2B pricing app to layer customer-specific overrides on top of standard tier pricing. The app handles the override logic and the storefront displays the correct price per customer.
Implementation time: 4-6 weeks including configuration and testing.
Suitable for: B2B operations with 10-50 strategic accounts that need specific pricing on top of standard tiers.
Level 4: ERP-driven dynamic pricing
Pricing logic lives in the ERP. The ERP calculates each customer's price based on contract terms, volume history, current inventory, supply costs, or any other variable. Shopify Plus displays the price the ERP returns, in real-time or near-real-time.
Architecture: API integration between Shopify Plus and your ERP. When a customer views a product, the storefront calls the ERP to get the current price for that customer and SKU. The price is rendered in the storefront. The same pricing applies at cart and checkout.
Implementation time: 6-12 weeks including the integration build. This typically sits inside a broader ERP integration project (NetSuite, Dynamics 365 F&O, or similar).
Suitable for: enterprise B2B operations with complex pricing logic that can't be modeled cleanly in Shopify Plus B2B catalogs. Brands with hundreds of customers and contract-specific pricing per account.
How the native model actually works
The Shopify Plus B2B pricing model in 2026 has three layers.
Catalogs control which products a customer can see. Settings > Products > Catalogs. Each catalog is a curated subset of your product catalog with custom pricing applied via a linked price list.
Price lists define what customers pay. Settings > Products > Catalogs > (catalog) > Price list. Each price list can apply a percentage discount across the catalog, or specific prices per product, or volume-based pricing per SKU.
Customer assignment links customers to catalogs. Customers > B2B customers > (company) > Catalog. Each company is assigned to one catalog. When users from that company log in, they see the products and prices from the assigned catalog.
The model is clean for Levels 1 and 2. The friction shows at Level 3 when you need many customer-specific exceptions, and at Level 4 when the source of truth needs to live elsewhere.
The architecture decision
Three questions determine the right architecture for your B2B pricing.
How many distinct pricing structures do you actually have? Not how many you think you have, but how many your customers actually buy under. Most brands have 3-5 real pricing tiers, even if their internal pricing structure has accumulated more on paper. Simplify before configuring.
How often do you negotiate customer-specific pricing? If the sales team negotiates per-account pricing weekly, the native catalog model won't keep up. You need either app-based overrides or ERP-driven pricing. If customer-specific pricing is rare (once a quarter or less), you can manage it through targeted price list updates.
Where do you want the source of truth? In Shopify (simpler, lower integration cost, but limited to what catalogs and price lists model). In the ERP (more powerful, real-time, but requires integration investment). The decision shapes the rest of the architecture.
Common pitfalls
Four patterns from B2B pricing implementations we've seen go wrong.
Over-engineering the catalog structure. Brands create 8-12 catalogs trying to model every pricing variation. The admin overhead becomes unsustainable. Start with 3-5 catalogs covering major tiers. Add complexity only where the business actually needs it.
Treating B2B pricing as a Shopify configuration job. The actual work is mapping how the sales team prices customers in practice, then translating that into the Shopify model. Skip the mapping and you configure a model that doesn't match how customers actually buy. We covered this in detail in the first 30 days of B2B setup.
Forgetting checkout, cart, and email rendering. The pricing displays correctly on the PDP but breaks at cart, checkout, or in order confirmation emails. Test the full flow end-to-end with a real customer login at each pricing tier.
Underestimating the ongoing maintenance. Pricing changes happen constantly in B2B. New customer pricing, contract renewals, price increases across categories. The pricing model needs to be maintainable by ops or finance, not just by your developer. Build for ongoing edit workflow, not just initial configuration.
Implementation patterns we use
For Level 1 and 2 implementations, we configure natively in Shopify. The native catalog + price list model is the right tool.
For Level 3 with 10-30 strategic accounts, we typically use dedicated catalogs per strategic account. The admin overhead is real but bounded.
For Level 3 with 30+ strategic accounts or Level 4 with ERP-driven pricing, we recommend ERP integration with real-time pricing sync. The pattern is similar to the NetSuite integration or Dynamics 365 F&O integration we covered separately, with pricing as one of the synced object types.
Where to start
If you're planning a Shopify Plus B2B pricing implementation, four moves order the work.
One: map how the sales team actually prices customers. Not how the pricing spreadsheet looks. How real customers actually get priced when they place real orders. This is the input to any architecture decision.
Two: count the real number of distinct pricing structures. Aim for the smallest number that covers 90% of customer scenarios. Strategic accounts can be handled as exceptions; you don't need a tier for every variation.
Three: pick the architecture level. Levels 1 and 2 are native Shopify configuration. Level 3 is native + apps or dedicated catalogs. Level 4 is ERP-driven. Match the architecture to the real complexity.
Four: budget for ongoing edit workflow. The team that maintains the pricing model after launch needs to be able to make changes without engineering involvement. Build the workflow into the implementation.
Talk to our team if you want help mapping your B2B pricing architecture or running the implementation. We've shipped B2B pricing implementations across Levels 1-4 and the patterns are consistent enough that the early architecture conversations save weeks of mid-project rework.
What's the difference between catalogs and price lists in Shopify Plus B2B?
A catalog defines which products a customer can see. A price list defines what they pay for those products. Each catalog can be paired with one price list. Customers see only the products in their assigned catalog and pay only the prices in the linked price list. Most mid-market implementations have 3-5 catalogs (one per pricing tier) with paired price lists. The model is clean for standard pricing structures and starts to creak when you have many customer-specific overrides.
Can I do volume pricing natively on Shopify Plus?
Yes, via quantity price breaks on price lists. Configure tiered pricing per SKU (e.g. 1-9 units at price X, 10-49 at price Y, 50+ at price Z). The customer sees the appropriate price based on the quantity in their cart. The native implementation handles most standard volume scenarios. For more complex volume logic (different breaks per customer, blended volume across multiple SKUs), you'll need an app or middleware.
How do I handle customer-specific contract pricing?
Three options. First, dedicated catalog per customer (works for high-value accounts but doesn't scale beyond 20-30 customers). Second, custom price list per customer (more flexible but the admin overhead is real). Third, ERP-driven pricing where the customer-specific price is calculated in the ERP and synced to Shopify in real-time. The third option is the cleanest at scale but requires integration investment.
Should pricing live in Shopify or in my ERP?
Depends on complexity. Simple tiered pricing (3-5 tiers, mostly static): keep it in Shopify. Complex pricing with customer-specific overrides, volume blending, or contract-specific rules: keep the source of truth in your ERP and sync to Shopify. Brands that try to manage complex pricing in Shopify hit the limitations of the catalog/price list model around 50-100 unique customer pricing configurations.
How long does B2B custom pricing implementation take?
For native Shopify Plus B2B pricing (catalogs + price lists + volume): 1-2 weeks of configuration. For app-based extensions (volume blending, advanced rules): 3-4 weeks. For ERP-driven pricing with real-time sync: 6-12 weeks including the integration build. The pricing implementation usually sits inside a broader B2B setup project, so the timeline overlaps with the 30-day B2B setup we covered separately.
What apps extend Shopify Plus B2B pricing capability?
Several. Sniptt, B2B Volume Pricing, Wholesale Bear are common for volume and tiered pricing extensions. Bold Custom Pricing and other custom-pricing apps handle customer-specific overrides. The right app depends on your specific scenarios. The default position is to use native B2B catalogs and price lists first, add an app only when the native model can't handle a specific requirement. Apps add ongoing cost and a layer of complexity.
How do customers see their custom pricing in the storefront?
Automatically once they log in. The B2B section of the theme detects the logged-in customer, identifies their assigned catalog, and renders prices from the linked price list. The customer sees only their pricing without seeing other tiers. The implementation work is theme-level: making sure the price display, cart, and checkout all show the correct customer-specific prices and don't fall back to retail.
What's the most common mistake in B2B pricing implementation?
Over-engineering the catalog structure. Brands create 8-12 catalogs trying to model every pricing variation, then discover the admin overhead is unsustainable. The right starting point is 3-5 catalogs covering the major pricing tiers, with customer-specific exceptions handled through targeted price overrides or ERP sync. Simplify first, add complexity only where the business actually needs it.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- B2B pricing on Shopify Plus has four levels of complexity. Each level has a corresponding architecture pattern.
- Level 1 (tiered pricing): native Shopify Plus B2B catalogs and price lists. 1-2 weeks of configuration.
- Level 2 (tiered + volume): native model with quantity price breaks. 2-3 weeks.
- Level 3 (tiered + volume + customer-specific overrides): dedicated catalogs per strategic account, or app-based override layer. 4-6 weeks.
- Level 4 (ERP-driven dynamic pricing): API integration with real-time pricing sync. 6-12 weeks inside a broader ERP integration project.
- The most common mistake is over-engineering the catalog structure. Start with 3-5 catalogs covering major tiers. Add complexity only where the business actually needs it.
