Do SuiteCommerce's bulk-pricing tables (common in B2B/wholesale setups) migrate to Shopify B2B's volume-pricing rules, or do they need rebuilding?

The capacity worry is the wrong worry

The first question everyone asks is whether Shopify holds enough tiers. It does. Shopify states "You can add up to 10 price breaks per product which are applied to each variant" (per Shopify Help Center, September 2026). NetSuite's quantity pricing schedules state the opposite constraint: "You can only have 4 non-zero quantity levels" (per Oracle NetSuite documentation, September 2026).

Ten is more than four. The tier table fits with room. Then the real differences begin.

Four mismatches, in the order they will hurt

1. What quantity the discount is calculated against. This is the big one. A NetSuite quantity pricing schedule carries a Calculate Quantity Discounts setting with four options: By Line Quantity, By Overall Item Quantity, By Overall Parent Quantity, and By Overall Schedule Quantity (per Oracle NetSuite documentation, September 2026). Only the first has a Shopify equivalent.

Shopify quantity rules and volume pricing apply at the variant level within the order. Shopify's own example is unambiguous: "Customers can't combine 5 gray hats and 5 blue hats to meet an increment of 10 hats" (per Shopify Help Center, September 2026). A buyer who earns a tier in NetSuite by ordering 500 units across a schedule of items earns nothing in Shopify unless 500 of one variant are in the cart.

If your wholesale customers buy assortments, this is not a data-mapping problem. It is a commercial-terms problem, and somebody on the business side has to decide what the new offer is before anybody writes a mapping.

2. Marginal rates. NetSuite's Use Marginal Rates option applies each discount only to the units inside its bracket, so the first 100 units bill at list and the next 50 at 5% off. Shopify's break model applies the qualified break's price to the qualifying units in that line. Graduated and flat tier pricing produce different invoice totals from the same tier table, and the difference grows with order size. Reprice a sample of last year's real orders both ways before committing.

3. Schedules are shared templates; Shopify breaks are per product. A NetSuite quantity pricing schedule is "applied to as many items as you want," so a single schedule can govern thousands of SKUs and one edit changes all of them. Shopify holds breaks on the product inside a price list. Migrating 1 schedule across 4,000 items produces 4,000 break tables, and a future change to that one schedule becomes a bulk operation rather than one edit. Plan for how you will maintain it, not just how you will load it.

4. Price levels far exceed catalogs. SuiteCommerce documents "up to 1,000 price levels, enabling you have to granular control over the level of discounting," and NetSuite supports up to 1,000 active price level records (per SuiteCommerce developer docs and Oracle NetSuite documentation, September 2026). Shopify gives you 3 active catalogs on Basic, Grow and Advanced, unlimited on Plus, and 25 per company location either way. That is the collapse exercise described on this page's parent, and it is where most of the work lives.

A migration order that works

1. Export the schedules with their settings, not just the tiers. Capture Use Marginal Rates and Calculate Quantity Discounts for each.
2. Segregate by calculation basis. By Line Quantity schedules are portable. The other three need a commercial decision, and that decision is the long pole.
3. Reprice a sample of historical orders under the proposed Shopify model. Compare invoice totals. Show the delta to whoever owns wholesale margin.
4. Collapse price levels into catalogs using the effective-price hash from the parent page.
5. Load the breaks. Admin CSV import handles quantity rules and volume pricing, and priceListFixedPricesAdd accepts a maximum of 250 prices per request for API-driven loads (per Shopify developer docs, September 2026).
6. Reconcile. Re-export from Shopify and diff against the source. A pricing migration signed off on spot checks is one that gets discovered by a customer.

When NOT to migrate the tables as they are

• When any schedule uses a non-line calculation basis. Porting the tiers without porting the basis silently changes what customers pay.
• When tiers exist that nobody has qualified for in two years. Migration is the cheapest moment to retire them.
• When the schedule is really a contract. Named-account pricing belongs in fixed prices, not in a volume table.