---
title: How to set wholesale prices across multiple accounts
Metadescription: Keeping ten or more wholesale price deals straight - lists as tiers, prices derived from one Default catalogue, and what a manual override does.
author: Dan Edwards
author_role: Founder
author_url: https://danedwardsdeveloper.com
author_linkedin: https://www.linkedin.com/in/dan-edwards-developer
published: 2026-08-26
---

Token estimate: ~930

# How to set wholesale prices across multiple accounts

Past about ten accounts the difficulty is recall rather than arithmetic - what each customer was promised, and when. Wholesale Handler holds trade prices as [price lists](https://wholesalehandler.com/articles/how-price-lists-work-on-wholesale-handler) rather than per-customer deals. Each customer is assigned to one list, a list derives its prices from a single Default catalogue by percentage, and any price typed in by hand is labelled as an override so it can be found again.

By **[Dan Edwards](https://wholesalehandler.com/about)**, Founder.

## Lists are tiers, and each customer sits on one

A price list is a tier rather than a customer record. Twenty accounts on four lists is the normal shape, and Wholesale Handler is built for it - the cap is 20 lists including the Default, against 50 customers.

Assignment is not optional. Every customer has a list, and a Default list is there whether or not you make others, so no account is left without prices. Looking up what somebody pays is a question about which list they are on.

## Prices derive from the Default list

Each list other than the Default carries a percentage of it - 90 for 10% off, 110 for 10% above - and its prices are worked out from that. The Default holds the real numbers and the tiers follow.

Update a price on the Default and Wholesale Handler shows what the change does to every percentage-based list before it writes anything. Keeping the existing prices on those lists is one of the options.

## A typed price stops deriving

Enter a price directly onto a derived list and that row stops tracking the Default. It stays where you put it, and later recalculations skip it.

Each row on a list shows where its number came from - derived rows carry the percentage, overridden rows are marked custom and show what the price works out at against the Default. So the overrides are visible on the page rather than held in memory.

## Changing a list's percentage

Changing the percentage on an existing list records the new figure but does not move the prices already derived from the old one. The number is worth getting right when the list is created.

## Moving a customer to another list

Customers are reassigned in bulk, in one action. The list is a property of the account rather than a copy of the prices, so a move applies from the customer's next order and there is nothing to rebuild.

Orders already placed are unaffected. An [order](https://wholesalehandler.com/articles/how-orders-work-on-wholesale-handler) line records both the price paid and the list it came from at the moment it was placed.

## Q&A

**Q: How many price lists should I have?**
A: There is no correct number. The test is whether you can say what separates two lists without naming a customer - volume, sector and a negotiated rate are three distinct tiers, while twenty lists named after twenty accounts is a ledger.

**Q: Can two customers on the same list pay different prices?**
A: No. The price belongs to the list, so every customer assigned to it pays it. An account needing its own number needs its own list.

**Q: Do customers see it when I put a price up?**
A: Yes, while they are ordering. For thirty days after a price changes the order form shows the old price struck through next to the new one.