Loading...
Blog
  • Wholesale
  • Operations
  • Order Management
  • B2B Ordering

Managing Multiple Price Lists Without Losing Your Mind

You have 40 customers. Not one of them pays the same price. And the record of who pays what lives across a spreadsheet, an email thread, a laminated sheet from 2021, and someone's memory. That's not a pricing system. That's a liability.

OT
Orderverse Team
·3 min read

You have 40 customers. Not one of them pays the same price.

Three are on Tier A. Seven are on Tier B. A handful got a custom rate negotiated two years ago by a rep who no longer works here. And the rest are somewhere in between, in a spreadsheet that someone updated last quarter.

This is normal wholesale pricing. It's also completely unsustainable as a manual process.


Where the Price List Actually Lives

In most wholesale businesses, pricing doesn't live in one place.

It lives across multiple versions. A master spreadsheet on the shared drive. A printed sheet someone laminated three years ago that's still being referenced. A note in a customer record that says "always give 8% off." An email thread from January where you agreed to a special rate on one SKU. The memory of the person who handles that account.

None of these are the same source. None of them are reliably in sync.

The problem isn't that you have multiple price lists. The problem is that no one knows which one is current for any given customer on any given day.


The Mistake That Happens More Than You Know

A new team member processes an order. They find the most recent price list, apply it, and send the invoice.

The customer calls. That's not my price.

It's not a big deal the first time. You fix it, raise a credit note, resend.

Here's what actually happened:

  • 20 minutes to find the correct rate
  • 15 minutes to raise the credit note
  • 5 minutes to resend and confirm
  • One small, quiet erosion of trust

Do that three times in a month and the customer starts wondering if you have your act together. Do it once with a new account and they might not come back.


The Spreadsheet Problem Specifically

Spreadsheets feel like the right tool because they're flexible. You can add rows, add columns, filter, sort. They're fast to update.

But that flexibility is exactly what makes them dangerous.

When the spreadsheet lives on a shared drive and three people can edit it, version control is your honour system. When a new SKU gets added and only one price tier gets updated, the inconsistency sits quietly until someone catches it during an order dispute.

The average wholesale business with 50+ active customers and 3+ price tiers has between 8 and 12 pricing inconsistencies sitting undetected at any given time. That's what surfaces when businesses move to structured order management and run their first data audit.


What Managing Price Lists Actually Requires

When it's working properly, price management isn't a task. It's a system.

Each customer is linked to exactly one price tier. Each tier has one current version. When a product price changes, that change flows to every invoice for every customer on that tier.

No manual cross-referencing. No checking the email thread. No relying on whoever handled the account last time to remember the rate.

The gap between spreadsheet pricing and system pricing isn't just operational. It changes how much you trust your own numbers — and how much your customers trust you.


The Compounding Cost

Every pricing inconsistency costs time. Roughly 45 minutes per incident to identify, correct, and document.

If you have 12 undetected inconsistencies per month and catch half of them before they cause customer issues, that's 6 incidents × 45 minutes = 270 minutes. More than 4 hours a month, just on pricing errors.

That's not counting the ones you didn't catch.

The answer isn't to be more careful with the spreadsheet.

The answer is to stop letting the spreadsheet be the source of truth.

Get started

Build a cleaner ordering workflow

See how Orderverse helps teams reduce manual order handling and keep pricing logic reliable at scale.

Related articles