Recommendations for store owners, merchandising teams, and operations staff managing quantity pricing at scale.
Tier design
Use non-overlapping ranges
Design clean breakpoints:
1-9 → $10
10-49 → $9
50+ → $8Warning Overlapping ranges work but the highest min_qty wins – which can confuse customers and staff.
Choose the right pricing type
| Strategy | Best type | When |
|---|---|---|
Wholesale price list |
Fixed price |
You publish exact unit prices |
Catalog changes often |
Percentage |
Discount stays proportional to list price |
Simple “$X off” message |
Fixed discount |
Clear per-unit savings |
Every qty has explicit rule |
Fixed from min qty 1 |
No gap to catalog price |
Anchor tier at min qty 1
If you want quantity pricing for all quantities, include a tier starting at min qty 1. Otherwise, quantities below your first tier’s min use catalog price.
Naming & documentation
Rules have no name field in Admin. Track externally:
| Spreadsheet column | Example |
|---|---|
Product ID |
prod_01TEE |
SKU / product name |
Organic Honey |
Currency |
usd |
Tier structure |
1-9 / 10-49 / 50+ |
Effective date |
2026-01-01 |
Owner |
Merchandising team |
Testing
Always test at tier boundaries:
| Test quantity | Why |
|---|---|
min |
Tier starts |
max |
Tier ends |
min – 1 |
Falls to previous tier or catalog |
max + 1 |
Next tier starts |
Open-ended min |
e.g. 51, 100, 500 |
Also verify: each variant, each currency, guest vs B2B customer group.
Performance
| Practice | Benefit |
|---|---|
Manage rules on product page |
Faster for large catalogs |
Cache tier table on PDP |
One API call per page load |
Recalculate only on qty change |
Fewer API calls |
Remove rules for discontinued SKUs |
Leaner database |
Avoid conflicts
| Risk | Prevention |
|---|---|
Overlapping tiers |
Design non-overlapping ranges |
Wrong currency |
Double-check |
Discount without base price |
Set Medusa prices or reference list price |
Cart shows catalog price |
Integrate Store API in cart |
Double discount with promotions |
Coordinate with Medusa promotions team |
Stale storefront cache |
Invalidate after rule changes |
Organizational roles
| Role | Responsibility |
|---|---|
Merchandising |
Define tier strategy |
Operations |
Create/edit rules in Admin |
Development |
Storefront + API integration |
Finance |
Approve margin impact |
Support |
Answer customer tier questions |
Go-live checklist
- [ ] Tiers tested on staging
- [ ] Storefront shows tier table
- [ ] Cart applies correct unit price
- [ ] Checkout total verified
- [ ] Support team briefed
- [ ] Multi-currency rules verified (if applicable)