Shopify B2B catalogs are no longer just a Plus-only concern. In April 2026, Shopify announced that merchants on Basic, Grow, and Advanced plans can use key native B2B features, including company profiles, payment terms, volume pricing, and up to three active B2B catalogs assigned through Markets. Shopify Plus still carries important catalog advantages, including unlimited catalogs and direct catalog assignment to companies and company locations.
That change makes Shopify B2B more accessible, but it also raises a practical operating question: how should a merchant structure catalogs before pricing, product visibility, and customer-specific terms become hard to govern?
For B2B companies, catalog design is not only a merchandising choice. It affects contract pricing, buyer eligibility, sales exceptions, ERP alignment, market expansion, customer service troubleshooting, and the confidence buyers have when they place self-service orders. A clean catalog model lets buyers see the right products at the right prices. A messy one creates discount leakage, missing SKUs, support tickets, and manual quote work that the ecommerce program was supposed to reduce.
Why catalog governance matters more as Shopify B2B adoption expands
B2B ecommerce growth is increasingly tied to self-service buying and hybrid sales motions. Buyers want to research, reorder, and purchase online without waiting on a rep, but they still expect their negotiated pricing, account-specific availability, and purchasing rules to follow them. Catalogs are one of the main ways Shopify B2B turns a shared storefront into a buyer-specific experience.
Shopify defines B2B catalogs as the control layer for the products and pricing B2B customers can access. Catalogs can include or exclude products, set customer-specific pricing, apply overall percentage adjustments, set fixed prices, and support volume pricing and quantity rules. Those capabilities are powerful, but they need an operating model behind them.
The core governance question is simple: should a pricing or availability rule apply to a broad B2B segment, a region, a market, a company, a company location, or one specific contract exception? If the answer is not clear before launch, the catalog structure often becomes a pile of one-off fixes.
Start with the buyer account model, not the product list
A common mistake is to design Shopify B2B catalogs by starting with product groups. Product availability matters, but B2B catalog governance should start with how customers actually buy.
For each major account segment, map the buyer model first:
- Which companies buy from the store, and do they have multiple locations?
- Do locations share the same pricing, or do branches have local agreements?
- Are there regional product availability differences?
- Do some buyers purchase contract items while others buy from a general wholesale assortment?
- Are prices owned by ecommerce, sales, ERP, a pricing team, or a contract-management process?
- Which exceptions should be temporary, and which should become part of the standard catalog model?
This planning step prevents the catalog model from mirroring internal chaos. If sales agreements, ERP customer records, and Shopify company locations do not line up, catalog assignment becomes a symptom of a deeper data problem.
Use Markets for broad catalog strategies
For merchants using Shopify Markets, B2B market catalogs are useful when many customers or company locations should share the same product and pricing strategy. Shopify describes market catalogs as a fit for broader strategies, such as managing pricing for all B2B customers in a region or creating a general All B2B catalog that separates wholesale availability from DTC availability.
This is especially important for Basic, Grow, and Advanced plans, where B2B catalog assignment is handled through Markets and the active catalog limit is three across all B2B markets. That limit forces prioritization. A merchant on those plans should avoid creating a separate catalog for every small exception. Instead, the team needs a compact catalog model that covers the most common buyer groups.
A practical starter model might look like this:
· All B2B catalog: the baseline assortment and pricing all wholesale buyers can access.
· Regional catalog: pricing or availability differences for a market such as Canada, Europe, or a distributor territory.
· Strategic segment catalog: a catalog for dealers, contractors, healthcare accounts, education buyers, or another segment with meaningful pricing and assortment differences.
The exact model depends on the business, but the principle is consistent: use market-level catalogs for repeatable, segment-wide logic. Do not spend a scarce catalog slot on a customer exception that should be handled through contract review, a quote, or a Plus-level direct assignment strategy.
Use direct company or location catalogs for true customer-specific pricing
On Shopify Plus, merchants can create unlimited B2B market catalogs and assign catalogs directly to specific companies or company locations. That direct assignment option is the better fit when pricing is truly customer-specific, when one branch has different terms than another, or when a negotiated agreement should override broader market pricing.
The important word is "true." Direct assignment should not become the default answer for every account request. If every special price becomes a new direct catalog, the team eventually loses track of which rules are standard pricing, which are negotiated contracts, which are temporary concessions, and which are outdated.
Before using direct company or location catalogs, define governance rules such as:
- Who can request a customer-specific catalog?
- What commercial reason justifies direct assignment instead of market-level pricing?
- Where is the source of truth for fixed prices and volume breaks?
- How long should the customer-specific price remain active?
- Who reviews expired agreements, margin exceptions, and duplicate catalogs?
- How are company locations matched to ERP customer accounts, ship-to records, or contract IDs?
Customer-specific catalogs are most valuable when they express a controlled commercial agreement. They become risky when they are used as a workaround for missing pricing governance.
Understand how Shopify resolves overlapping catalog rules
Catalog overlap is where many B2B pricing surprises begin. Shopify documentation notes several important behaviors: a company location can have multiple catalogs assigned, a product can appear in more than one catalog, and pricing display depends on the type of overlap.
If multiple catalogs assigned to the same company location include the same product at different prices, Shopify displays the lowest price for that item. If a catalog is assigned directly to a company location and another catalog applies through a matching B2B market, Shopify displays the more specific company-location price for overlapping products.
Those rules are reasonable, but they mean teams need to test catalog interactions before launch. A pricing manager might assume a market catalog sets the final price. A sales rep might assume a direct customer catalog always wins. A buyer only sees the result. Governance has to account for that result.
At minimum, test these scenarios:
- A product available in a baseline B2B catalog and a regional market catalog.
- A product with a fixed price in one catalog and an overall percentage adjustment in another.
- A company location assigned to both a market catalog and a direct customer catalog.
- A product with volume pricing or quantity rules in overlapping catalogs.
- A B2B-only product that should not appear to DTC customers.
The goal is not just to confirm Shopify behavior. It is to make sure sales, ecommerce, operations, and finance all understand the commercial outcome.
Connect catalog governance to ERP and pricing ownership
Most B2B catalog problems are not caused by Shopify alone. They come from unclear ownership between ecommerce and backend systems. If the ERP owns contract pricing, Shopify needs a reliable process for receiving, formatting, testing, and retiring those prices. If ecommerce owns a promotional B2B catalog, finance still needs visibility into margin impact. If sales owns negotiated exceptions, operations needs a way to prevent stale catalogs from living forever.
For implementation teams, define the integration pattern early:
- Which catalog fields are maintained manually in Shopify, and which are imported or synchronized?
- Will customer-specific fixed prices come from ERP, a pricing file, middleware, or a contract system?
- How will product availability exclusions map to ERP item status, customer eligibility, or regional restrictions?
- What happens when an ERP price is missing, expired, or lower than expected?
- Who receives alerts when a catalog import fails or creates unexpected price variance?
A catalog governance model should include exception reports, not only setup documentation. Teams need to know when a buyer sees a product they should not see, when a contract SKU is missing, when a catalog price conflicts with ERP, or when a direct catalog has not been reviewed in months.
Build a catalog naming and lifecycle system
Catalog sprawl becomes much easier to control when names and lifecycle states are standardized. A useful catalog name should communicate the assignment level, business purpose, market or segment, effective period, and owner.
For example:
- B2B-Market-US-Dealer-Baseline-2026
- B2B-Market-Canada-Distributor-2026
- B2B-Location-Acme-East-Contract-2026Q3
- B2B-Segment-Healthcare-Restricted-Assortment-2026
The naming system does not need to be beautiful. It needs to be searchable, auditable, and understandable by support teams. When a buyer calls about a missing item or unexpected price, the support person should be able to identify which catalog applies and who owns the rule.
Catalog lifecycle rules should answer:
- Draft: Who can create a new catalog, and what approval is required before activation?
- Active: Which team monitors assignments, price variance, and buyer complaints?
- Review: How often are customer-specific catalogs audited?
- Sunset: What happens when a contract ends, a customer changes tiers, or a market strategy changes?
- Archive: How are old catalog decisions retained for reference without cluttering the active model?
When to keep the model simple and when to move to Plus
Shopify B2B on Basic, Grow, and Advanced plans can work well for merchants with a limited set of wholesale segments and relatively standardized pricing. The three active B2B market catalog limit can even be helpful because it forces discipline. For many emerging wholesale programs, the best first move is to build a clean market-based structure rather than overfitting every customer.
Shopify Plus becomes more compelling when the business requires unlimited B2B catalogs, direct company or company-location catalog assignment, customer-level pricing at scale, more complex payment options such as deposits or partial payments, or deeper contextual checkout and storefront customization. The decision should be operational, not just feature-based.
Signals that the catalog model may be outgrowing non-Plus constraints include:
- More than three meaningful B2B pricing or assortment segments are required.
- Customer-specific pricing cannot be represented cleanly through broad markets.
- Company locations need different catalogs under the same parent company.
- Sales is maintaining too many quote-based exceptions because catalog assignment is too limited.
- Support teams frequently investigate missing products, unexpected prices, or incorrect volume breaks.
- ERP contract pricing needs a direct, repeatable assignment pattern in Shopify.
A practical launch checklist for Shopify B2B catalogs
- Map company and company-location structure against ERP customer records before assigning catalogs.
- Define which rules belong at the B2B market level and which require customer-specific assignment.
- Document catalog precedence and overlap behavior in plain language for sales, support, and finance.
- Create test buyers for every major account type, region, and pricing scenario.
- Validate product visibility, fixed prices, percentage adjustments, volume pricing, and quantity rules before launch.
- Confirm how B2B-only products are hidden from DTC shoppers while remaining visible to eligible B2B buyers.
- Create a naming convention that identifies segment, market, customer, effective period, and owner.
- Set review dates for direct company or location catalogs, especially contract-specific catalogs.
- Build exception reporting for missing SKUs, expired prices, unexpected discounts, and catalog import failures.
- Train support and sales teams on how to identify which catalog a buyer is seeing.
FAQ: Shopify B2B catalog governance
What are Shopify B2B catalogs?
Shopify B2B catalogs control which products and prices B2B customers can access. They can be used to customize product availability, fixed pricing, percentage adjustments, volume pricing, and quantity rules for wholesale buyers.
How many B2B catalogs are available on non-Plus Shopify plans?
Shopify documentation says Basic, Grow, and Advanced plans can assign up to three active catalogs across all B2B markets. Shopify Plus supports unlimited B2B market catalogs and direct catalog assignment to companies and company locations.
When should a merchant use Markets instead of direct company catalog assignment?
Markets are best for broader strategies, such as regional pricing, baseline wholesale pricing, or customer segments that share the same assortment and pricing rules. Direct company or company-location assignment is better for customer-specific pricing and is available on Shopify Plus.
What happens when multiple catalogs include the same product?
For multiple catalogs assigned to the same company location, Shopify displays the lowest price for the overlapping product. When a direct company-location catalog and a matching B2B market catalog both include the product, Shopify displays the more specific company-location price.
What is the biggest risk in Shopify B2B catalog setup?
The biggest risk is catalog sprawl: too many overlapping catalogs, unclear ownership, stale contract pricing, and no shared understanding of which rules control the buyer experience. Governance should be designed before the catalog model scales.