The Shopify Spring '26 Edition marks a pivotal shift in the platform's architecture. By moving business-to-business (B2B) primitives from the enterprise-only "Shopify Plus" tier into the core platform (Basic, Grow, and Advanced plans), Shopify has fundamentally changed how mid-market and SMB merchants approach wholesale.
For engineers and technical leads, this isn't just a UI update—it’s a realignment of the Shopify database schema and API accessibility.
1. The Core Realignment: B2B as a First-Class Citizen
Historically, B2B on Shopify required a $2,300/month Plus license. Merchants on standard plans relied on "workaround apps" that used tagged customer accounts and duplicate "wholesale-only" products.
In the Spring '26 update, the Company, CompanyLocation, and Catalog objects are now natively available across all plans. This means a single product variant can have multiple price points defined natively in the database, resolved dynamically at the checkout level based on the buyer's identity.
Key Architectural Differences
While the schemas are identical, Shopify uses "guardrails" to differentiate the tiers:
2. Implementing the "Three Catalog" Strategy
On standard plans, catalogs are inherited from the Market context. To implement wholesale pricing without a Plus contract, you must follow this logical flow:
companyCreate mutation to establish the business entity.Developer Pro-Tip: The Catalog Limit
Since you are limited to 3 catalogs on standard plans, you should use Percentage-Based Adjustments for broad tiers (e.g., "Silver", "Gold", "Platinum") rather than creating individual catalogs for every customer.
3. The GraphQL API Layer
Engineering teams can now integrate ERPs and CRMs with B2B endpoints on any plan. Here is how you initialize a wholesale price list adjustment via the API:
mutation UpdateCatalogPrice($priceListId: ID!) {
priceListUpdate(id: $priceListId, input: {
parent: {
adjustment: {
type: PERCENTAGE_DECREASE,
value: 15.0
}
}
}) {
priceList {
id
name
}
}
}
This mutation applies a 15% discount across the entire catalog relative to the retail price. For specific contract prices, you can still use priceListFixedPricesAdd to override specific variants.
4. Operational Guardrails and Incompatibilities
Moving B2B to core plans doesn't mean every feature is supported. High-complexity checkouts are still gated. Technical leads should be aware of these hard limits:
5. The June 30th Deadline: Scripts to Functions
Coinciding with this democratization is the final sunset of Shopify Scripts on June 30, 2026. All wholesale discounting logic must be migrated to Shopify Functions (WebAssembly).
The Cart Transform API is now the primary tool for B2B customization:
lineExpand: For expanding bundle SKUs into components for fulfillment.linesMerge: For consolidating multiple quantities into a single contract line item.Strategic Conclusion
The democratization of B2B features removes the "Plus gate" for growing brands. However, for developers, the challenge shifts from "how do we hack wholesale?" to "how do we optimize within the 3-catalog and 500-line-item limits?"
If your merchant’s B2B volume exceeds $1.5M/year or requires high-throughput API limits, the transaction fee savings and direct catalog mapping of Shopify Plus still represent the most efficient technical architecture.
