Customer specific pricing B2B wholesale is the practice of showing each approved retailer or distributor the products, prices and commercial terms that apply to its account. It gives a wholesale team operational control: one core catalogue, governed rules around it, and a clear record of approved exceptions.
The challenge is rarely deciding that a key account needs different terms. The challenge is applying those terms without duplicate price files, conflicting email instructions or a sales team guessing which spreadsheet is current. A durable approach separates shared pricing from account-specific rules, then makes the applicable result visible at the point of order.
What is customer specific pricing in B2B wholesale?
Customer-specific pricing is a pricing model in which a B2B account receives a defined set of product prices and terms based on its relationship with the supplier. The account may be a retailer, a distributor, a buying group or another wholesale customer.
It is broader than a discount. A customer-specific wholesale price list can also determine:
- which product catalogues, SKUs and variants the account may order;
- the currency used to display and invoice prices;
- volume-based pricing tiers and minimum order quantities;
- payment terms and delivery conditions;
- territory or channel restrictions; and
- approved negotiated prices for selected products or dates.
The aim is not to make every account unique. It is to define reusable rules for the accounts that share commercial conditions, and use tightly controlled exceptions only where they are genuinely needed.
A branching set of product boxes flowing into separate retailer and distributor pathways
Why do wholesale brands need customer-specific price lists?
Wholesale brands need customer-specific price lists because the same product can be sold through different relationships with different responsibilities. A distributor buying for a territory may have a different catalogue, currency and commercial arrangement from an independent retailer buying direct.
Without structure, those differences become manual instructions: a price sheet attached to an email, a discount entered in a sales order, or a note passed from one colleague to another. This makes it hard to answer basic operational questions: Which price was approved? When did it start? Does it still apply? Who can change it?
A governed model also protects the core catalogue. The standard price remains available as a reference, while customer groups and approved account rules apply only where intended. For a wider foundation, start with a documented wholesale discount structure and pricing policy.
Which pricing rules should you define for each retailer or distributor?
Define the account before defining the exception. Each approved customer record should have commercial, operational and access details that a sales, finance or operations colleague can understand without searching through correspondence.
Core account fields
At minimum, record:
- Account identity: legal entity, trading name, billing and delivery contacts.
- Account type: retailer, distributor, buying group or another defined customer class.
- Customer group: the reusable price-list or rule group assigned to the account.
- Territory and channel: where and through which route the customer may sell or receive goods.
- Catalogue access: eligible product ranges, SKUs, variants and any restricted lines.
- Currency: the currency for catalogue display, order totals and invoicing.
- VAT treatment: the account data and transaction context needed for the applicable invoice treatment.
- Payment terms: agreed payment method, due-date terms and credit controls where relevant.
- Ordering rules: minimum order quantities, order-value rules, pack sizes and order approval requirements.
- Commercial owner: the person responsible for requesting or approving changes.
Territory should not live only in a sales note. It can affect catalogue visibility, price lists, fulfilment routes and distributor permissions. A clear distributor territory management framework helps separate contractual rights from the daily rules used to process orders.
How should B2B brands structure wholesale pricing tiers?
A useful structure has layers. The base price establishes the product’s standard commercial starting point. Customer groups apply repeatable rules. Account-level pricing handles approved exceptions without changing either of the first two layers.
| Pricing layer | What it represents | Example use | Governance rule |
|---|---|---|---|
| Base price | The standard price for a SKU or variant in a defined catalogue and currency | Default price for eligible direct wholesale accounts | Product or commercial owner maintains it |
| Customer-group rule | A reusable rule for accounts with similar terms | A distributor group sees a defined price list and eligible range | Change is reviewed for every account in the group |
| Account-level override | A specific exception for one named account | A negotiated price for one SKU or a temporary launch arrangement | Requires a named owner, approval and end date where applicable |
| Volume tier | A price or benefit linked to an order quantity or threshold | Different unit price once a product quantity is reached | Define the unit, scope and interaction with other discounts |
This is a model, not a universal hierarchy. Your system must state the order in which rules are evaluated. For example, an account-level override may take priority over a customer-group rule, while a promotional price may have a different priority or be excluded from further discounts.
Make the precedence visible. If two active rules could apply to the same SKU, territory, currency and date, the order should either be blocked for review or the system should apply a documented priority. Silent conflicts are where margin and customer trust are lost.
Design volume-based pricing tiers carefully
Volume-based pricing tiers are price rules linked to quantity, order value or another defined buying commitment. They can be useful, but only if the basis is unambiguous.
Decide whether a tier applies per SKU, across a product family, across an order or across an agreed period. Also decide whether it combines with group discounts, account overrides and promotions. Pair the tier with minimum order quantities and pack-size rules so customers cannot accidentally reach a price intended for a different buying pattern.
Before publishing a tier, check its effect on the relevant product cost and commercial margin. The purpose is not to prevent every exception; it is to ensure the exception is deliberate. Use this process alongside the steps used to protect wholesale gross margin.
A set of neatly stacked price tags with a single approved tag placed on top
How do currencies and territories affect customer-specific wholesale pricing?
Currency and territory are pricing inputs, not formatting choices. A customer may need a catalogue priced in a particular currency because of its market, accounting process or negotiated arrangement. A distributor may also be entitled to order only the products and price lists assigned to its territory.
Avoid treating a converted amount as automatically equivalent to a local price list. A multi-currency wholesale pricing policy should specify whether prices are maintained directly by currency, reviewed on a set cadence, or calculated by a defined method. It should also identify the owner who approves changes and the date from which they apply.
VAT treatment belongs in the same operational workflow, but it should not be embedded in a product price note. Invoice treatment can depend on the transaction details, customer status and destination. [1] Capture the account and order information your finance process needs, validate it before invoicing, and seek appropriate tax guidance for the markets in which you trade. Read more about B2B multi-currency pricing and keep currency decisions separate from ad hoc sales discounts.
How can brands manage negotiated terms without creating catalogue conflicts?
Negotiated wholesale pricing should be an exception record, not a replacement catalogue. A good exception says exactly what is different, why it is approved, who owns it and when it ends or is reviewed.
For each negotiated term, record the scope:
- customer account and, where needed, its buying entity or delivery territory;
- SKU, variant, product family or catalogue to which it applies;
- currency and price basis;
- quantity condition or minimum order quantity;
- start date, end date and review date;
- whether it can combine with other rules;
- approval owner and supporting commercial rationale; and
- status: draft, approved, active, expired or withdrawn.
Effective dates are especially important for seasonal lines, price revisions and temporary arrangements. They allow the next price list to be prepared without prematurely replacing today’s prices. They also provide a traceable explanation when a customer asks why a price changed.
A simple approval workflow is usually enough: sales proposes the change, finance or a commercial owner checks margin and terms, then an authorised person publishes it. Restrict the ability to edit active rules, and retain a history of what changed. Auditability means a team can reconstruct the rule used for an order, including the version and approval behind it.
A calendar page connected to a locked folder of approved commercial terms
What should a wholesale pricing system record for every customer account?
A wholesale pricing system should record the account, the rules applied and the commercial context of each order. It should preserve both the current operating view and the historical record needed to understand past invoices.
For every order, retain the selected price list or rule, SKU and variant, currency, quantity, applicable tier, adjustment or override, effective date, and the resulting net line price. Keep the customer’s payment terms, VAT-related account details and delivery information with the order workflow rather than relying on a separate inbox.
This does not mean storing every possible scenario in one giant price table. It means linking a clean product catalogue to customer groups and explicit account rules. The fewer duplicated price files you maintain, the easier it is to update a SKU, launch a range or retire an expired exception without creating conflicting versions.
When should a wholesale brand move from spreadsheets to a pricing platform?
A spreadsheet can be adequate while prices are simple, a small team owns every change and customers do not need self-service access. It becomes fragile when price lists vary by account, currency, territory, catalogue or effective date, or when orders must be re-entered into finance systems.
The practical trigger is loss of control rather than a particular order volume. Consider a pricing platform when colleagues regularly ask which file is current, when sales needs manual checks before quoting, when account exceptions are hard to trace, or when finance must correct pricing details after an order is placed. These are common signs it may be time to assess when to move beyond wholesale spreadsheets.
A platform should support your policy rather than replace it. Start by cleaning product data, assigning customer groups, documenting precedence and putting an owner behind each exception. Then give approved customers access to the catalogue and terms that apply to them.
Brandgate provides a branded B2B storefront and distributor portal where approved retailers and distributors can view the relevant catalogue and pricing. It also supports order-to-invoice workflows, multi-currency catalogues, VAT-aware invoicing and Fortnox connectivity, helping wholesale teams connect commercial rules with the ordering process.
If you are mapping customer-specific price lists or replacing a patchwork of price files, book a demo to discuss the workflow. You can also see pricing.