For example, a distributor orders 5,000 units of a single SKU at SGD 10 each (hypothetical numbers). At 10,000 units the price drops to SGD 9; at 20,000, SGD 8. Each bracket carries its own per unit price, and units in each bracket are charged at that bracket’s rate.
That is B2B tiered pricing in its simplest form: the per unit price falls in steps as ordered volume increases. In B2B selling, a tiered pricing structure sets price tiers by the quantity on an order line, by the order total, by customer groups and by unit of measure, such as each, box or carton.
The term has a second meaning. In software as a service, tiered pricing means plan tiers: good-better-best packaging such as a basic tier, a standard tier and premium tiers, feature based pricing that keeps basic features in the basic tier and advanced features or premium features in paid tiers, per-user tiers that charge by the number of users, usage based tiers that charge by consumption, and freemium plans aimed at converting free users into paying customers. SaaS companies set those price points by the perceived value of each plan and what customers are willing to pay, and many combine recurring subscriptions with usage based pricing. This article covers physical goods and consumables sold through B2B ecommerce, not SaaS plans.
It is written for owners, sales directors and operations leads at wholesalers, distributors and manufacturers who sell to business buyers online, where a pricing rule that is wrong in the system becomes a margin problem on every order.
What is B2B tiered pricing and when does it help?

Tiered pricing sets multiple price points by order quantity, and each tier typically lowers the price per unit as quantity increases. In B2B, pricing tiers are usually quantity thresholds on a purchase order, though they can also be tied to customer segments across the customer base or to annual spend.
The benefits of tiered pricing in B2B come down to three reasons, which is why wholesalers, distributors and manufacturers adopt this pricing model. First, larger orders reduce cost per unit: fewer shipments, less handling, better production scheduling. Tiers pass some of that saving to the buyer.
Second, buyers expect tiered pricing. Trade purchasing has always worked in carton, pallet and truckload increments, and pricing tiers mirror those breakpoints.
Third, pricing tiers protect profit margins. A flat discount, or a single price point for everyone, gives margin away; a tiered pricing strategy rewards commitment while preserving the selling price for smaller orders.
One production insight is worth stating early. If tier cut-offs, group overrides and contract tables are not synchronised between your ERP and your storefront, the same SKU can show different price points on adjacent days, because one system reads a cached price and the other reads the live ERP. That drift is how margin leakage starts and buyer trust erodes.
How does B2B tiered pricing work in practice?
Tiered pricing works by defining thresholds (quantity, spend or customer class), each with a specific per unit price. When an order spans multiple tiers, the system can calculate tiered pricing: it allocates units across brackets and charges each bracket’s rate.
Three core levers drive most tiered pricing structures in B2B:
- Quantity breaks: laddered price points such as 1 to 99 units at base rate, 100 to 499 lower, 500+ lowest. Tiered pricing incentivises buyers to raise the quantity purchased to reach a lower price.
- Price group tiers: dealer, distributor and key account buyers see different base tiers for the same catalogue, mapped from CRM or ERP classifications. A small trade buyer sees one set of breaks; a national chain sees deeper ones.
- Contract-specific overrides: a framework agreement fixes prices for certain SKUs or baskets, often time-bound, and falls back to defaults on expiry.
Rules for pricing tiers should be deterministic conditions: SKU, price group, date range, channel or region. Given the same inputs, the system must always return the same price.
If it does not, the cause is usually a caching inconsistency or an ambiguous rule overlap, and the symptom is a support ticket from a confused buyer.
Types of pricing tiers you can actually maintain
Most wholesalers end up with a few tier patterns that cover most of their price logic. Mixing many different pricing tiers usually comes from historical deals, not design. Each tiered pricing model below has a use case and a failure mode.
Quantity-break tiers per order line
Per-product ladders such as 1 to 49, 50 to 199 and 200+ apply to the quantity on one order line. A fast-moving consumable sold to retailers is the classic case, with the tiers shown on the product page before the buyer adds to cart.
This works when breakpoints match carton sizes or standard pack quantities. If a case holds 30 units but the second tier starts at 25, buyers order 25 and the warehouse picks a partial case. Rounding rules, per carton or per unit, cause support tickets if not locked down early.
Order-total tiered pricing
Some sellers set the tier on the whole order, for example a hypothetical 3% off orders above SGD 5,000. These price tiers are easy to explain but harder to account for: the discount has to be spread across lines, or a partial return produces a credit note that matches neither order nor invoice.
Price group tiers by customer segment (dealer, distributor, key account)
Same catalogue, different tiered pricing per group: a standard discount for a small trade buyer, deeper breaks for a regional distributor, the lowest base price for a national chain. These groups usually live in the CRM or ERP and sync to the store.
The risk is misalignment between ERP customer IDs and store accounts. A duplicate login or stale group flag can move a buyer into the wrong group overnight, and they log in to default pricing, which damages customer loyalty and triggers urgent calls to sales.
Unit-of-measure tiers (each, box, carton)
The same item is often sold by the each, the box and the carton, and under tiered pricing each unit of measure can carry its own price and breaks. That price has to be stored per unit, not derived from the single-unit price, and the cart has to convert back to the stock unit. When a buyer orders three cartons and the system reads three pieces, the invoice and the pick are both wrong.
Contract tiers and project price lists
Contract tiered pricing uses customer-specific price lists for framework or project deals, for example a two-year contract for a construction group with fixed prices on a basket of SKUs and a separate table for spot orders. They override group tiers while active and fall back on expiry.
Date ranges and contract status must be part of rule evaluation; an expired contract that keeps applying causes losses or disputes. When override tables multiply and reps apply rules from memory, consolidation into one hierarchy is usually the only path forward.
Spend based pricing tiers (rebates and bonuses)
Tiers on annual or quarterly spend, for example rebates that rise beyond SGD 250k, SGD 500k and SGD 1m, reward the largest accounts in the customer base and are usually settled outside checkout through credit notes at year-end.
Portals can show progress, such as “You are SGD 18,000 from the next rebate level”, which encourages customer growth and order consolidation. The trap is mixing invoice and delivery dates in spend calculations, which produces audit disputes about the fiscal period.
Tiered pricing vs volume pricing for B2B orders

Volume pricing applies one lower price to the entire order once a threshold is crossed. Tiered (graduated) pricing charges each bracket’s rate only on units within that bracket. Volume pricing, sometimes called banded or flat-rate pricing, is simpler: at 500 units, every unit costs the same.
The graduated tiered pricing method tends to appear in catalogue price lists with many incremental orders, where margin protection matters. Volume based pricing shows up in simple wholesale discount tables for large one-off orders, where buyers want one unit cost for their costing sheets.
Finance teams usually prefer the volume pricing model for forecasting: one rate per band. Sales teams push for the tiered model because graduated discounts feel fairer than all-or-nothing.
Tiered pricing examples: one order, two pricing models
These tiered pricing examples use hypothetical numbers and are illustrative, not a recommendation. One SKU has these pricing tiers:
- 1 to 199 units at SGD 10 per unit
- 200 to 499 units at SGD 9 per unit
- 500+ units at SGD 8 per unit
An order of 750 units is priced as follows:
| Pricing model | How units are charged | Total cost | Effective per-unit cost |
|---|---|---|---|
| Tiered (graduated) | 199 × SGD 10 + 300 × SGD 9 + 251 × SGD 8 | SGD 6,698 | ~SGD 8.93 |
| Volume (flat at 500+) | 750 × SGD 8 | SGD 6,000 | SGD 8.00 |
The hypothetical SGD 698 difference on one order is why the distinction matters for buyer decisions and margin calculations.
Buyers complain when they cannot see the tier table in the portal: they cross a threshold without realising it and the checkout total surprises them. Clear pricing tiers on the product page, with a running total, reduce support tickets and improve customer satisfaction.
Which price wins when tiered pricing, contract prices and promotions overlap
Whatever the tiered pricing model, most pricing disputes start where two rules apply to one line: a dealer has a contract price on a SKU that also has quantity breaks, and a promotion is running. An effective tiered pricing strategy needs one written order of precedence, applied the same way on the web, in the rep’s quote and in the ERP.
A common order is contract price, then price group tier, then quantity break, then public list. Promotions need their own decision: on top of contract prices, only on list and group prices, or lowest price wins. Each answer can be defended. Leaving it undecided cannot.
For example, with hypothetical numbers: a contract price of SGD 8.50 and a 10% promotion on a SGD 10 list price. If promotions stack, the buyer pays SGD 7.65, possibly below the margin floor. If lowest price wins, they pay SGD 8.50.
A one-off price agreed by phone is still customer-specific pricing. Enter it as a dated contract line, not a cart edit, so the rule order can explain it later.
How tiered pricing rules are set up in a B2B ecommerce platform
The storefront is one view on pricing. The pricing brain normally sits in ERP or a pricing engine, which the store queries live or syncs from. The goal is one rule order, whether the buyer orders on the web, through a dealer portal, or via EDI.
Price lists as the foundation of tiered pricing
In any B2B pricing model, a price list is a named set of net prices or discount rules for a catalogue slice, usually in one currency, arranged in a hierarchy: global, regional, price group, contract.
Exporters either store a base currency and convert at checkout, or store explicit prices per currency to avoid exchange-rate surprises. Either works if the decision is made once.
Cascading lists need explicit “stop inheritance” flags, or editing a regional list can ripple into a contract list and surface later as a buyer complaint.
Price groups and segment flags
Customers are grouped by industry, region, channel or size and mapped to price lists; a Singapore reseller group might map to an “SG-Dealer-2026” list with its own GST handling.
Sync these groups from ERP or CRM, not a separate list in the store. Tiered pricing only works across customer segments when segment data agrees across systems, and asynchronous syncs can briefly show default prices between cycles.
Minimum order quantities and pack sizes
MOQs exist at product and tier level: a base MOQ of 20 units, with higher tiers only at full-pallet quantities. Volume discounts and tiered discounts interact with MOQs directly.
Buyers order by case while pricing is per unit, so the platform enforces pack-size increments. A cart-level MOQ across mixed SKUs can block checkout for key accounts ordering many small lines; evaluate MOQs per line.
Common tiered pricing mistakes and what they cost

With thousands of SKUs, hundreds of contracts and several regions, a tiered pricing model shows failure modes that testing misses. Multiple tiers that overlap cause decision paralysis for buyers, and internal teams lose confidence in their own pricing strategy.
Wholesale buyers seeing retail prices
When a trade account loses its group through a failed sync, the portal falls back to the public list. The buyer orders at retail and disputes the invoice, or goes back to phoning sales. An alert whenever a logged-in trade account is priced from the public list catches it.
Too many overlapping tiers and exceptions
Ad-hoc discounts layered over group tiers, layered over promotions, until the pricing structure cannot explain why one buyer pays one price for one SKU. Buyers get confused and customer satisfaction drops; sellers get inconsistent margins and slow carts as every line triggers dozens of rule checks.
Tiers that ignore carton, pallet or production units
A tier break at 230 units that matches no pack size makes buyers order odd quantities. Allocation rounds back to logistics units, and short-ships or over-picks erode the margin the tier was meant to protect.
Sales reps quoting a different price from the web
Separate spreadsheets for sales and ecommerce diverge: manual re-entry, missing contract IDs, partial syncs. One hierarchy with web prices tied to the ERP ends this dispute, and contract IDs on each order line make it auditable.
Invoices that do not match the order
If the invoice re-reads the price list at dispatch, any change since the order makes the invoice differ from what the buyer approved. Finance issues credit notes and the buyer stops trusting the portal.
Surprises at tier boundaries
Under volume pricing, going from 499 to 500 units drops the total abruptly; under tiered pricing it changes gradually. If one extra unit lowers the total, the UI must show it, or buyers find the pricing structure opaque. Cache price points per quantity range so large carts do not slow on every keystroke to the point where buyers abandon the session.
Trade-offs in a tiered pricing strategy

Every tiered pricing strategy trades commercial flexibility against operational simplicity, and each new rule type adds maintenance for years. These are consequences, not a verdict.
Price simplicity vs sales flexibility
A small tier matrix matches customer expectations, speeds onboarding and cuts support questions. Sales teams want custom deals for strategic accounts, which drive customer lifetime value. A common tiered pricing strategy keeps a standard matrix plus a limited number of dated contract overrides. Hundreds of custom matrices are technically possible, but reporting and testing suffer long before the database does.
Customer feedback shows whether the matrix is clear or whether buyers phone sales because the portal confuses them.
Margin control vs competitive pressure
Aggressive higher tiers protect volume but erode margin where competitors push discounts deeper. Exporters need landed cost (freight, duties, insurance) in tier design, or higher priced tiers look profitable until the shipment is costed.
Track margin by tier, as well as by customer, so profitable pricing tiers can be told apart from unprofitable ones before a monthly finance check.
Static tiers vs data-driven adjustments
Static, annually reviewed tiers are predictable. Adjustments driven by demand, costs or customer behaviour capture more value but add catalogue updates, customer communication and contract checks.
A fixed review cadence beats constant tweaks, and every review should create a new price list version so historical orders can be credited and returned correctly.
Frequently asked questions about B2B tiered pricing
What is the difference between tiered pricing and volume pricing?
The tiered pricing method charges each bracket’s rate only on units inside that bracket; volume pricing applies the reached bracket’s rate to every unit. In the hypothetical example above, 750 units cost SGD 6,698 tiered and SGD 6,000 by volume.
Is B2B tiered pricing the same as SaaS tiered pricing?
It is a different practice under the same name. SaaS companies package basic features and advanced features into plans such as a basic tier, a professional tier and premium tiers, with free and paid tiers; B2B tiered pricing sets the price of the same physical item by quantity, order total, buyer group or unit of measure.
How many tiers should a B2B price list have?
Fewer, clearly separated breaks are easier to maintain and explain. Too many cause decision friction; too few leave bulk purchases unrewarded. Large tables of pricing tiers become unreadable on mobile and push buyers back to quote-based workflows.
How do I avoid conflicts between contract prices and tiered pricing?
Define a priority order: contract over group, group over public. Store contract IDs on every order line, enforce date validity, and replay known contract orders through the pricing engine after every rule change. If any output differs from the expected price, the change does not deploy.
Should I show tiered pricing publicly or only to logged-in buyers?
A hybrid is common: base tiers public, group and contract pricing behind login. Public quantity breaks attract customers with a clear value proposition, while personalised rates differ across different customer segments. Hiding all pricing often increases manual RFQ requests that bypass the ecommerce channel.
How often should B2B tiered pricing be reviewed?
Match the cadence to cost volatility and contract terms: annually for stable inputs such as fasteners or packaging, quarterly for metals or chemicals. Use margin reports per tier to pick which bands to adjust, and use customer feedback when buyers say a boundary feels arbitrary or a competitor’s pricing options are simpler.
What happens to an order’s price when the price list changes?
The order keeps the price captured at the moment of sale, provided each order line stores its own price, unit and tax. If the invoice re-reads the live list, the change flows into orders already placed.
The ERP as the price source for tiered pricing

A tiered pricing strategy requires one price source, so decide which system owns the price before any tier is built. In most wholesale businesses the ERP holds list prices, groups and contracts, and the store displays and applies them, so reps quoting from the ERP and buyers ordering online see the same number. If the store sets a price the ERP did not, the ERP must accept the line price; re-pricing silently changes what the buyer agreed to.
Two sync patterns dominate. In one, ERP is the pricing brain and the store queries it per request: accurate, but dependent on ERP uptime and latency.
In the other, price lists sync nightly or hourly: faster at checkout but possibly stale, so a wholesale ecommerce platform needs a stated rule for what buyers see between syncs. Contract prices originate in the ERP and are pushed out, not re-keyed.
Rounding differences between ERP (often four decimals) and storefront (two) accumulate into invoice mismatches over hundreds of lines and only show up at reconciliation.
Snapshot the price on the order line
Price lists are revised, contracts expire, promotions end. An order placed before the change must still be invoiced, part-shipped, credited and returned at the price the buyer accepted.
So each order line stores what was true at the moment of sale: unit price, unit of measure, tax, and the rule that produced the price, with its identifier. The invoice reads the line, not the current list.
A Malaysian paint manufacturer has run its orders and stock on a system KVY built and has operated since January 2025. Customer price groups are resolved per item and per unit of measure, and order lines keep a snapshot of price, unit and tax at the moment of sale.
How we approach B2B tiered pricing at KVY TECH
In B2B ecommerce development, KVY TECH treats tiered pricing as part of the architecture from the start. Work begins with a plan, before implementing tiered pricing, that maps the pricing model, contracts and ERP behaviour, including how many different tiered pricing models exist and which are inherited.
The build follows an explicit hierarchy (base list, price group, contract, promotion), with automated tests at tier boundaries and documentation so your team can adjust tiers after handover. Weekly updates come with a demo of real carts priced against your own rules, so discrepancies surface before launch.
If you are weighing this for your own business, start with a plan. In two to three weeks we map how the system would connect to your ERP, warehouse, payments and sales channels, set out the build in phases with the cost to run it over three years, and give a fixed quote for the first phase. You keep the plan whatever you decide.