A wholesale website can advertise “10 or more at 9” while its developer calculates only the tenth unit at 9. Before approving a B2B catalogue, name the pricing model and test the threshold. A correct minimum quantity does not prove that the price calculation follows the approved offer.
Primary evidence and claim boundaries
Shopify’s B2B documentation distinguishes quantity rules from volume-price breaks and allows them together or independently. Actual catalogue availability and compatible features must be checked for the store’s current configuration. Primary reference · Read 18 October 2026.
Filled acceptance example
Original synthetic teaching scenario, not a client case, provider integration test or business result. The example policy needs the actual owner’s approval; scroll the table on narrow screens.
| Input and state | Declared check | Expected output and decision |
|---|---|---|
| Synthetic approved all-unit price:1–9 at 10,10+ at 9 | Quantity9 | 9×10=90 |
| Same all-unit model | Quantity10 | 10×9=90 |
| Alternative graduated model: first 9 at 10, rest at 9 | Quantity10 | 9×10+1×9=99; different offer |
| All-unit model; quote total99 for10 | Compare with approved model | Reject mismatch; do not change the offer to fit the code |
Practical handover procedure
- Have the merchant approve a named model, currency, variant, catalogue/customer eligibility and tax/shipping treatment. Treat the numbers here as synthetic net item prices only.
- Test below, at and above each threshold, including quantity 9,10 and 11. Compare product page, cart, quote and actual eligible test checkout.
- Record which platform or app implements the approved rule. If plan/catalogue support is unknown, keep implementation approval pending rather than asserting every Shopify store supports it.
Interpret the outcome
Under the stated all-unit offer,9 and 10 units both total90; this is intentional, not a calculation defect. Under the alternative model10totals99. The filled comparison turns ambiguous marketing shorthand into a concrete commercial decision before integration.
Acceptance decision
Approve one explicit model and require matching threshold outputs across eligible surfaces. Quantity increments and minimums remain separate checks.
Limits and unverified work
Hypothetical prices, no quote, tax calculation or purchase. This article does not establish a store’s plan eligibility, compatible app or legal pricing obligations.
Download the filled bilingual acceptance record — Contains the inputs, steps, expectations and limits. This is a teaching record, not an executable production integration.