Weekly ecommerce tips, deals & news.
A pricing error is when your store shows or charges a price you never meant to set. It can be a typo, a rule that fires for the wrong customer, or a discount that stacks too far. In a wholesale store, the classic version is a retail shopper paying the wholesale price, or the reverse.
A pricing error happens when the rules that build a price produce a number you didn’t intend. On a simple store, that’s usually one mistyped field. On a store with wholesale customers, several rules combine to build each price. As a result, there are more ways for it to go wrong.
Think of a wholesale price like a nightclub guest list. The bouncer only lets the right names through, so a single wrong name on the list causes trouble. In a WooCommerce store, these are the usual weak spots:
The tier problem catches a lot of stores by surprise. Wholesale Suite’s guide notes that, by default, general quantity discounts use the total quantity of all items in the cart. That’s often what you want. However, if you meant “50 units of one product,” a buyer mixing ten products reaches the tier far sooner.
A wholesale pricing error costs more because the gap between your two price lists is large. Wholesale Suite puts typical wholesale prices at 30-50% below the retail price. So when a retail shopper gets the wholesale price, you give away a big slice of every sale.
By contrast, the reverse error hurts in a different way. A wholesale buyer who sees retail prices thinks their account is broken. In practice, some will email you, but others will quietly order from a different supplier.
Caching is a common hidden cause of wholesale pricing errors. A page cache works like a photocopier. It saves one copy of a page and hands it to the next visitor.
That’s great for speed. However, a price that depends on who’s logged in shouldn’t be photocopied.
With role-based pricing, customers must be logged in to see wholesale prices. If a cache saves a page while a wholesale buyer is viewing it, a guest might get that copy. As a result, the guest sees prices meant only for trade accounts. This is a classic cache conflict, and it usually needs logged-in pages excluded from the cache.
A pricing error that raises the price at checkout costs you the sale. In Baymard’s checkout research, 40% of shoppers who abandoned an order blamed extra costs being too high. A price that jumps between the product page and the cart feels exactly like that.
On the other hand, an error that lowers the price costs you margin. Worse, nobody complains about a price that’s too low. So undercharges can run for weeks before anyone spots them in a report.
The best public data on pricing errors comes from physical stores, where inspectors compare the shelf price with the register. However, there’s no equivalent survey for online stores. So treat these figures as a reminder, not a benchmark.
For example, a 1998 FTC study found the wrong price was charged for about one in 30 items checked. More recently, a 2024 national survey checked 419,237 prices across 7,367 stores. In that survey, 23% of store inspections failed the accuracy standard. Under NIST’s guidance, a store fails when more than 2% of the prices checked differ from what’s charged.
A pricing error in practice often comes from a rule that was set up correctly for one case. Here’s a hypothetical example.
Imagine a WooCommerce store called Copper Kettle that sells coffee beans to cafés and home brewers. A bag retails for $20, and approved cafés pay a wholesale price of $12. On top of that, the owner adds a tier: 50 or more bags earns another 10% off.
The owner meant the tier for 50 bags of one blend. However, the tier still used its default setting, which counts every bag in the cart. So a café ordering five bags each of ten blends hit the tier too.
As a result, each of those mixed orders paid $10.80 a bag instead of $12. That’s $60 lost on a 50-bag order. Across 40 such orders a month, the store gave away $2,400 it never planned to.
Meanwhile, a second error was running on the retail side. A page cache served one wholesale-priced product page to guests for two days. In the end, several home brewers bought bags at $12 instead of $20.
First, the owner switched the tier to count each product separately. Next, they excluded logged-in pages from the cache and cleared it. Then they wrote a short checklist for every price change. Each time, they view one product as a guest, a retail customer and a café.
Finally, the owner decided to honor the guest orders already placed. After all, the loss was small, and the goodwill was worth more. The checklist takes ten minutes, which is far cheaper than another month of silent discounts.
You prevent a pricing error by testing every price the way each type of customer will see it. Most errors only show up for one role, so checking as the admin hides them. A short routine after every change covers the usual causes:
On top of that, a dedicated tool helps, because it keeps role pricing in one place. For example, Wholesale Prices Premium shows wholesale prices only to approved wholesale roles. Retail customers and logged-out visitors see your standard prices.
| What you’re comparing | Pricing Error | Price Mismatch |
|---|---|---|
| Where it lives | Inside your store’s own price rules | Between your store and a shopping feed |
| Who notices first | Customers, or nobody at all | The ad channel, which flags the listing |
| Typical cause | Wrong role, tier or bulk edit | A feed that hasn’t caught up |
| Main fix | Correct the rule and test each role | Refresh the feed so prices agree |
A pricing error means your store itself charges the wrong amount. A price mismatch means your store and your product feed disagree. In fact, a pricing error can cause a mismatch if the wrong price reaches your feed. So fix the store first, then refresh the feed.
There’s no single answer, because it depends on where you sell and what your terms say. NIST notes it’s unlawful in every US state to advertise an inaccurate price. So fix the error fast, then either honor the order or cancel it with a full refund. For anything costly, ask a lawyer about your local rules.
Guests usually see wholesale prices because a page cache saved a copy made for a logged-in buyer. Clear your cache and exclude logged-in pages from it. Then test in a private window. If the problem stays, check whether the product has a wholesale price entered in the regular price field.
Check prices after every change to a rule, a role, a tier or an import. Beyond that, a monthly spot-check of your best sellers is a sensible habit. Compare the price each customer type sees against your price list.
A pricing error matters because it loses either the sale or the margin. Worse, the margin loss is often silent. Wholesale stores feel it most, since their price lists sit far apart. A simple test routine for every customer type keeps your prices doing what you meant.
Copyright © StoreOwnerTips.com. All Rights Reserved.
