A wholesale price increase is a planned change to the prices you charge approved retailers and distributors on your wholesale price list. Done well, it protects gross margin when costs rise. Done poorly, it creates spreadsheet mismatches, margin fights on open orders, and avoidable churn.
This guide covers notice, blanket versus tiered rises, open-order price protection, and how to update portals and multi-currency catalogues without chaos.
What is a wholesale price increase and when should brands use one?
A wholesale price increase is a formal revision of B2B selling prices—list, tier, or customer-specific—effective from a stated date for new orders (and, if agreed, for some open ones). Brands typically use one when supplier costs, freight, packaging, FX on landed cost, or sustained labour and energy pressure make current net prices unsustainable.
It is not the same as a short promotion ending, a one-off quote, or a quiet edit to one retailer’s spreadsheet. Treat it as a commercial programme: reason, scope, notice, systems cutover, and a single source of truth for what buyers will see next.
Use an increase when you can explain the drivers at SKU or category level, honour existing commitments where you promised price protection, and still leave distributors a workable path to their own shelf prices. If only a few lines are underwater, a targeted correction often beats a catalogue-wide shock.
Cost pressure flowing into a wholesale price list
How much notice should you give retailers before a wholesale price increase?
Give enough wholesale price increase notice for buyers to review the list, update their own pricing, and place fair last orders under old terms if your policy allows it. In ongoing supply relationships, notice is both a contract issue and a trust issue: check framework wording and local rules on varying price in continuing agreements, then choose a commercial window that operations can actually support.
Practical notice usually means a dated letter or portal announcement, a full file or portal preview of new prices, and a clear effective date and time zone. Longer windows help seasonal or imported ranges; shorter windows may fit fast-turn goods if cost spikes are sudden—but surprise is what drives churn, not the existence of a rise.
State what happens to orders submitted before the cut-off, backorders, and blanket POs. If sales historically “held” old prices in inboxes, replace that habit with written rules before the announcement goes out.
Should you use a blanket increase or tiered price changes by SKU and channel?
A blanket increase applies the same percentage or amount across a wide catalogue. A tiered price change varies by SKU, category, brand tier, or channel because SKU-level cost drivers differ—fabric versus trim, ambient versus cold chain, domestic versus import, heavy versus light freight.
Blanket rises are simple to message and easy to load when almost everything moved together. They punish lines that were already healthy and can under-correct lines that absorbed the real hit. Tiered changes take more analysis and a cleaner master data set, but they read as fairer and protect mix.
Work from cost and margin waterfalls, not gut feel: landed cost, tariff or freight shifts, pack configuration, and minimum order patterns. Then decide whether channel or region needs a different list (for example domestic versus export) without inventing parallel unofficial prices in email.
| Approach | Best when | Watch-outs |
|---|---|---|
| Blanket | Costs moved broadly; simple catalogue | Over-prices healthy SKUs; feels blunt |
| Tiered by SKU/category | Cost drivers uneven | Needs clean data and clear comms |
| By channel / currency | Markets diverge on FX or terms | Keep one controlled master per market |
Tiered versus blanket price change as two paths
How do you communicate a wholesale price increase without triggering churn?
Distributor price change communication should be direct, specific, and early. Lead with the effective date, the scope (whole list, categories, or named SKUs), and how open orders and quotes are treated. Follow with a short rationale tied to real cost drivers—not vague “market conditions” alone.
Give account managers a one-page script, FAQs, and the exception path (who can approve temporary holds, and until when). Share machine-readable lists or portal previews so buyers are not re-typing from PDFs. If you offer a last-order window at old prices, cap volume where abuse is likely and say so upfront.
Avoid surprising key accounts after smaller ones already know. Sequence: internal lock of numbers → sales briefing → written notice to all active accounts → portal publish on the stated date. Pair the message with help on assortment, MOQs, or payment terms only where you truly intend to flex—do not bargain the list back to the old net in side deals.
What happens to open orders, quotes, and backorders when prices change?
Price protection on open orders means defining which commitments keep the old price. Typical split: confirmed orders with an order confirmation at the old price stay old; new lines and new orders after the effective date take the new list; quotes follow their stated validity; backorders follow either original confirmation or a written backorder rule—pick one and apply it consistently.
RFQ and quote validity should already show an expiry. When you announce a rise, freeze or shorten validity so sales cannot extend expiring quotes without a deliberate exception. For blanket or standing POs, reconfirm remaining quantity and price in writing before go-live.
Finance and ops need the same rule in the ERP and the portal: if the warehouse ships a protected order, invoicing must not silently pick up the new list. Document the audit trail—who approved any manual override—and keep it rare.
Open orders shielded while new orders take new prices
How do you update B2B portals, price lists, and multi-currency catalogues cleanly?
A clean B2B price list update uses one master wholesale catalogue, effective dating, and a single publish event—not staggered spreadsheet emails. In a branded B2B storefront or distributor portal, load the new list with the future effective date, test visibility by customer group, then switch so every approved buyer sees the same truth at go-live.
Multi-currency catalogue updates need the same discipline: decide whether foreign-currency prices are derived from a base list plus agreed FX rules or maintained as separate market lists, and publish them together so EUR and SEK buyers do not drift. Guidance on structure lives in our multi-currency B2B pricing guide; the operational point is simultaneous cutover and no “temporary” side files.
Sync list prices to Fortnox or your ERP so order-to-invoice does not re-key. If you use customer-specific pricing, re-base those agreements on the new list (percentage off new list, or renegotiated nets) in the same window—see customer-specific pricing. Platforms such as Brandgate keep controlled catalogues, portal prices, and order flow in one place so effective dates and account-level prices match what finance invoices.
How do framework agreements and discount policies affect price increases?
Wholesale framework agreements often set notice periods, index or cost-pass-through clauses, and caps on mid-term changes. Read them before you design the rise: some accounts need formal variation notices; others only need the standard list update.
Your wholesale discount structure, rebate schemes, and promotional mechanics sit on top of list. If list goes up but rebate tiers stay fixed on old assumptions, net revenue may not recover. Align rebate baselines, settlement timing, and any volume commitments with the new list so sales does not “give back” the increase in unstructured off-invoice deals.
Where selective or exclusive distribution applies, keep the same effective date across the territory unless contracts force staggered terms—uneven go-lives invite grey pricing debates between neighbours.
What timeline and checklist keep finance, sales, and ops aligned on go-live?
A simple programme timeline keeps the wholesale catalogue price update boring—in a good way.
Before announcement
- Lock SKU-level costs, target nets, and margin floors.
- Choose blanket versus tiered scope and currencies in scope.
- Draft open-order, backorder, and quote rules; get finance sign-off.
- Check framework and rebate impacts per key account.
Announcement window
- Brief sales with scripts and exception limits.
- Send dated notice plus full price file or portal preview.
- Freeze uncontrolled quote extensions.
Systems cutover
- Load effective-dated lists in portal and ERP (including Fortnox price sync where used).
- Test customer-specific prices, order confirmation text, and invoice net.
- Confirm warehouse and CS use order-confirmation price for protected lines.
After go-live
- Monitor overrides, credit notes, and dispute themes for a short period.
- Close temporary exception powers on a stated date.
- Archive the old list and the approval pack for audit.
Keep ownership clear: commercial owns the why and the story, finance owns margin and invoice integrity, ops owns cutover, sales owns account conversations—not private price files.
When notice, tiering, open-order protection, and portal publish run as one programme, a wholesale price increase lands as a controlled list change rather than a relationship crisis. If you want those price lists, effective dates, and distributor orders in one branded portal with order-to-invoice flow, Book a demo.