A price list belongs to an account, not to a catalogue
The list is the wrong way round from how most people picture it. You are not pricing products, you are pricing relationships - the same case of the same product is one price to the cafe that takes two a month and another to the group that takes forty a week.
That is why a supplier with sixty products and twelve customers has three or four price lists rather than twelve. Accounts get sorted into a handful of tiers, and each tier is one list.
What belongs on the list, and what does not
Keeping the second column off the list is what lets one list serve many customers. Two accounts can pay the same prices while one takes Tuesday deliveries on 30-day terms and the other collects and pays on the day.
A trade price is worked back from the shelf, not up from cost
Cost plus a margin tells you the lowest price you can accept. It does not tell you the price a retailer will pay, because they are working out whether your product clears at their shelf price and still earns them a living.
So set the retail price you want to see first, then work back. Halving it is the usual starting point in general retail - the retailer doubles what they pay - though fresh categories with waste and short shelf life often need more room than that. A trade price that leaves the buyer under their normal margin gets declined even when it is comfortably above your cost.
Changing a list does not reprice orders already placed
A price list is live, so an update takes effect on the next order rather than the last one. Wholesale Handler snapshots the price onto every line the moment an order is placed, so a Tuesday price change cannot silently rewrite Monday's unshipped orders or the invoices behind them.
Check this before you trust any system with your prices. If yesterday's orders move when you edit a price today, your invoices are being written by whoever edited last.
Wholesale Handler



