Shopify Plus B2B has matured substantially over the last two years. The platform’s customer-specific pricing capabilities are now strong enough to handle the majority of mid-market B2B scenarios cleanly, which is a meaningful change from the situation in 2023, when sophisticated B2B pricing on Shopify required substantial app and customization investment. For retailers evaluating Shopify Plus against Adobe Commerce for B2B operations, the pricing capability is one of the most important variables, and the honest evaluation requires understanding both what the platform does well and where it still has limits.
This article walks through how Shopify Plus customer-specific pricing actually works in 2026, the scenarios it handles cleanly, and the scenarios where it forces compromises or requires app-based extensions. The framing here reflects the implementation work Bemeir’s Shopify Plus practice has done for B2B retailers running production Shopify Plus stores.
The native B2B pricing architecture
Shopify Plus B2B uses a model built around three core entities: companies, locations, and price lists. A company is a B2B customer organization. A company has one or more locations (typically representing physical stores, branches, or buying entities). A price list is a set of product prices that can be applied to specific companies or locations.
Price lists support several pricing strategies:
- Fixed price per product: explicit price for specific SKUs
- Percentage discount off retail: e.g., “Company X gets 15% off all products”
- Percentage discount off retail per product category: e.g., “Company X gets 20% off Category A, 10% off Category B”
- Quantity-based volume pricing: e.g., “1-9 units at retail, 10-49 units at 10% off, 50+ units at 20% off”
- Custom price lists per company/location: full flexibility within the price list model
A single company can be associated with multiple price lists, and Shopify applies the most favorable price when a customer adds to cart. Currency-specific pricing is supported through Shopify Markets, which allows companies operating in different currencies to see prices in their native currency.
According to the Shopify B2B documentation, the price list architecture is designed to support B2B scenarios where buyers belong to organizations with negotiated pricing, and the implementation handles the common patterns well.
What works cleanly
Several B2B pricing patterns work cleanly on Shopify Plus without significant customization:
1. Negotiated customer-specific pricing. A wholesale retailer with 50-500 B2B customers, each with negotiated pricing, can be implemented natively. Each customer maps to a Shopify company, with a price list reflecting their negotiated terms. The pricing applies automatically when the customer logs in and shops.
2. Tier-based volume discounts. Quantity-based pricing tiers work natively per product, with the ability to set tier-specific quantities and discounts. The implementation handles cart-level recalculation when quantities change.
3. Customer-group pricing through Markets. Shopify Markets enables price segmentation by region, currency, and customer segment. B2B customers in different markets can see appropriately localized pricing without separate stores.
4. Multi-location pricing. Companies with multiple buying locations can have different pricing per location, useful for franchise networks, multi-branch wholesale customers, or international B2B distribution.
5. Catalog-level price adjustments. A blanket discount applied to a customer’s entire catalog access is a simple price list configuration. Useful for tiered customer programs (gold/silver/bronze pricing levels).
| B2B pricing scenario | Native Shopify Plus support | Adobe Commerce comparison |
|---|---|---|
| Negotiated price per customer (fixed prices) | Strong native support | Strong native support |
| Tier-based volume discounts | Strong native support | Strong native support |
| Customer-specific catalog access (price visibility) | Moderate (requires policy work) | Strong native support |
| Quote-to-order workflow with negotiated pricing | Moderate (Shopify B2B drafts) | Strong native support |
| Multi-tier pricing with complex rules | Moderate (some scenarios need apps) | Strong native support |
| Real-time ERP-driven pricing | Weak (requires app + middleware) | Moderate (custom integration work) |
| Customer-segment dynamic pricing | Moderate (Markets + price lists) | Strong native support |
| Approval workflows for non-standard pricing | Weak (requires app or custom dev) | Strong native support |
Where Shopify Plus has limits
Several B2B pricing patterns either require app-based extensions or force compromises:
1. Real-time ERP-driven pricing. Retailers whose B2B pricing is calculated in real time by an ERP system based on customer-specific factors (account-specific contracts, deal-specific pricing, time-bounded promotions) often find that Shopify Plus’s price list architecture doesn’t fit cleanly. The native model assumes pricing is set in advance and stored as price lists; real-time pricing requires either pre-syncing every possible price into a price list (often impractical) or using an app-based extension that intercepts cart calculation to call the ERP.
Adobe Commerce, by comparison, has stronger native support for real-time pricing through its observer and plugin architecture, which can hook into cart calculation in ways the Shopify model does not directly support.
2. Complex multi-rule pricing with dependencies. Scenarios like “Customer X gets 15% off Category A and 10% off Category B, except for Brand Y which has a flat 20% discount, except during promotional periods when the deeper discount applies” can be modeled in Shopify Plus but the configuration becomes brittle. Adobe Commerce’s catalog rule engine handles these scenarios more cleanly.
3. Customer-specific catalog visibility. Shopify Plus B2B can restrict which products a customer sees through catalog-level access controls, but the configuration is more limited than Adobe Commerce’s customer-segment-based catalog visibility. Retailers with strict customer-specific catalog requirements may need app-based extensions or workarounds.
4. Quote-to-order with negotiated pricing. Shopify Plus B2B supports draft orders for quote-like workflows, but the implementation is lighter than Adobe Commerce’s native quote workflow. Retailers whose B2B operations depend on formal quote-to-order processes with multi-level approval often find the Shopify model requires app-based extensions or custom development.
5. Approval workflows for non-standard pricing. Some B2B retailers require approval workflows when a customer requests pricing outside standard tiers (e.g., a sales rep negotiating a special deal that requires management approval). Shopify Plus does not natively support this kind of approval workflow; the implementation typically requires custom apps or process workarounds.
The implementation effort for a typical mid-market B2B retailer
For a mid-market B2B retailer (200-2,000 customer accounts, moderate pricing complexity, standard integration patterns), a Shopify Plus B2B pricing implementation typically takes 8-14 weeks of project work, costing $80,000-$150,000 inclusive of theme work, B2B configuration, customer migration, and pricing setup. The cost compares favorably to an equivalent Adobe Commerce implementation, which typically runs $100K-$200K for comparable scope.
For B2B retailers whose pricing complexity exceeds the native Shopify Plus model, the cost expands meaningfully. App-based extensions for real-time pricing, custom catalog visibility, or approval workflows typically add $20K-$80K to the project depending on the depth of customization required. At the high end of this range, the cost advantage over Adobe Commerce starts to compress, and the platform decision becomes more nuanced.
What good implementation looks like
The B2B Shopify Plus implementations that succeed share a few characteristics. They commit early to the native pricing model rather than fighting it. They simplify the pricing structure where possible to fit Shopify’s patterns, accepting some pricing model rationalization as part of the migration. They use apps and customization sparingly, only for the gaps where the native model truly cannot accommodate. And they integrate carefully with whatever ERP or backend pricing source the business uses, syncing pricing into Shopify price lists rather than trying to calculate pricing at request time.
The implementations that struggle, by contrast, try to replicate every nuance of a previous Adobe Commerce or custom-built pricing system on Shopify Plus, without rationalizing the model first. The result is heavy app dependency, brittle integrations, and ongoing operational pain.
Decision implications
The platform decision implications are honest enough to state directly. For mid-market B2B retailers with moderate pricing complexity that fits within Shopify Plus’s native B2B model, Shopify Plus is now a viable and often economically advantaged platform choice. The native B2B pricing capabilities are strong, the implementation cost is reasonable, and the steady-state operational cost is materially lower than Adobe Commerce.
For B2B retailers with complex pricing models — real-time ERP-driven pricing, complex multi-rule pricing with dependencies, custom catalog visibility, formal quote-to-order workflows with approvals — Adobe Commerce remains the better fit, and the cost advantage of Shopify Plus diminishes once the necessary app-based extensions and custom development are included. Bemeir’s B2B Adobe Commerce practice sees this pattern consistently: the simpler the B2B requirements, the stronger the Shopify Plus case; the more complex the requirements, the stronger the Adobe Commerce case.
The right way to make this decision is to write down the actual pricing requirements before evaluating platforms, then assess each platform against those documented requirements rather than against vendor positioning. According to Forrester’s research on B2B eCommerce platform selection, the platform decisions that produce the best three-year outcomes are anchored on documented business requirements rather than on vendor capability comparisons. The discipline of writing down the requirements first is what produces a defensible platform choice.
Bemeir’s platform evaluation engagements for B2B retailers facing this decision typically run as four-to-six-week paid engagements that produce a documented requirements analysis, a gap assessment against both platforms, and a recommendation grounded in the retailer’s specific operational model. The cost is bounded; the clarity is what makes the platform decision sustainable over the next five years.
