Why wholesalers struggle with pricing.
A typical wholesaler serves 50-500 customers across multiple tiers. Tier 1: large distributors getting 4-8% off list. Tier 2: established retailers getting 2-4% off. Tier 3: walk-in retailers at list. Tier 4: occasional buyers at list-plus-cash-only. Plus regional differences (different states or provinces), seasonal promotions, and special deals for the customer who has been a partner for 20 years.
On a spreadsheet, this is unmanageable. The salesperson at the counter has to remember which customer is which tier, apply the right discount, hope to remember promotions, and try not to undersell. Mistakes cost margin. Inconsistency damages relationships ("you charged him less than me last week"). And the owner has no real visibility into actual realized prices versus list.
How tier pricing is structured properly.
A clean tier pricing system has three layers. Customer segment: every customer is assigned to exactly one segment (e.g. "Tier 1 Distributor", "Tier 2 Retailer", "Walk-in"). Price list per segment: each segment has its own price list, defined either as discount-from-list or as absolute prices per SKU. Override authority: managers can override at the line level for a specific quote, with reason logged.
When a customer comes in, the system identifies them, pulls the segment, applies the right price list automatically, and the salesperson sees the right price on the screen. No memory, no notepad, no awkward "let me check with the boss". Margin is protected, relationships are consistent, and exceptions are visible to management.
- Customer segment: assigned once, drives default pricing
- Segment price list: discount or absolute price per SKU per segment
- Promotional override: time-bound with start/end dates
- Manager override: single-quote, logged with reason
Volume tier pricing on top of segment.
Some wholesalers add volume tiers within a single transaction: buy 10 cases, get 2% off. Buy 50, get 5% off. This works alongside customer segments — Tier 1 customer buying 50 cases gets the segment discount AND the volume discount, or whichever is greater, per business rules.
Setup: define volume thresholds per SKU or per category. Apply automatically on the invoice line based on quantity. Decide upfront whether volume and segment discounts stack or whichever is greater applies. Both are valid; consistency is what matters. Document the rule and apply it everywhere. Nonari supports both modes per SKU configuration.
A worked example: building materials wholesaler.
A Hamburg cement and tile wholesaler serves 200 customers in 3 tiers. Tier 1 (12 large distributors): 8% off list on cement, 6% off on tiles. Tier 2 (60 established retailers): 4% off cement, 3% off tiles. Tier 3 (128 occasional retailers and walk-ins): list price.
Volume tiers on cement: 50+ bags = additional 1% off. 200+ bags = additional 2% off. 500+ bags = additional 3% off. Tier 1 customer ordering 300 bags gets 8% + 2% = 10% off. Tier 3 customer ordering 300 bags gets 0% + 2% = 2% off. The Tier 1 customer is rewarded for the relationship plus the volume; the walk-in gets only the volume reward. The system applies both automatically; the salesperson does not need to compute anything.
Promotional pricing on top.
Beyond standard segment and volume discounts, time-bound promotions add a third layer. End-of-year promotion: 3% extra off all SKUs for two weeks. New product launch: 10% off the new SKU only for a month. End-of-quarter: clear specific dead stock at 25% off. These layer on top of segment pricing or replace it, per business rules.
A clean system lets you define a promotion with start and end dates, applicable SKUs or categories, applicable customer segments (sometimes a Tier 1 customer is excluded from a sub-tier promotion), and stack rules. The salesperson sees the promotion applied at point of invoice. The owner sees the promotional revenue and discount cost in reporting.
Common mistakes wholesalers make.
Mistake 1: re-quoting from memory. The salesperson tells customer X a price from memory; the system has a different price; the customer is invoiced at one of the two; nobody is sure which is right. Fix: the system price is the only price.
Mistake 2: backdated discount changes. The owner tells the system to drop a customer's tier; the change applies retroactively to invoices already issued. Pricing changes should be effective from a date, not retroactively. Mistake 3: using credit notes to disguise pricing. A salesperson invoices at list, then issues a credit note to bring it down to the agreed tier price. This makes margin reporting impossible and is a red flag in audits. Either the price list is right or it is not — credit notes are for genuine returns and corrections, not for hidden discounting.
How nonari handles wholesale pricing.
Nonari supports customer segments with assigned price lists, volume tiers per SKU, time-bound promotions, and manager override authority — all at the customer record and invoice line level. When a customer is selected on a sales order, the system automatically applies the segment price, then layers volume and promotion logic per the configured rules.
Nonari also produces a realized-price report — average actual selling price per SKU per customer segment compared to list. The owner sees where margin is leaking, which customers are getting unusual discounts via override, and which segments are under-priced relative to others. Wholesale margin is small and competitive; visibility at this level often pays back the system within months by surfacing pricing leaks that were invisible before.