Did your price change actually work? How to read units before and after

Changing a price takes a minute. You bump an item up a dollar, or knock a few off something that’s been sitting, and move on. What almost never happens next is the part that matters: going back a few weeks later to see whether the change did what you hoped. Most price decisions are made on a feeling and then never checked, so you never really learn whether the last one helped or quietly cost you customers.

The tricky thing about pricing is that the receipt can lie to you. Raise a price and each sale brings in more, so the till looks healthier even on a day you sold to fewer people. Whether the change actually worked depends on two numbers moving together — how many you sold, and how much came in — not on either one alone.

Why checking is worth the ten minutes

A price change you never review becomes a permanent decision made on a hunch. If a small increase held your units almost steady, you’ve just found free money you could apply to other items. If it pushed a chunk of buyers away, you want to know now — before the drop hardens into “that product just doesn’t sell anymore” and you stop reordering it. The cost of not checking isn’t one bad price; it’s repeating the same guess across your whole shelf.

Checking also teaches you how sensitive your customers actually are, item by item. Some products barely flinch at a higher price. Others lose a third of their buyers over fifty cents. You can’t feel that difference from behind the counter, but it’s sitting in your sales data, and one honest look tells you which items you can price up and which you shouldn’t touch.

What a price change that didn’t work looks like

You’re watching for a gap between what the money says and what the units say. When those two disagree, the units are usually telling the truth.

• Revenue on the item is flat or up, but units sold dropped clearly after the change — you’re earning the same from fewer customers.
• Units fell and revenue fell together after a price increase, which means the higher price didn’t cover the buyers you lost.
• You dropped a price to move stock, but units barely moved — the discount gave away margin without winning sales.
• The item quietly slid down your best-seller list in the weeks right after you repriced it.

How to check a price change in your data

You don’t need a spreadsheet full of formulas. You need one item, two equal stretches of time, and two numbers for each: units sold and revenue. The comparison does the rest.

1. Write down the date you changed the price. Everything before it is your baseline; everything after is the test.
2. Pick equal windows on each side — four weeks before against four weeks after works well, and avoids comparing a normal stretch to a holiday one.
3. For that one item, pull units sold and revenue for each window from your Clover reports or an export.
4. Read units first: did you keep, lose, or gain customers? Then read revenue: did the change bring in more money, less, or about the same?
5. Decide from the pair. Units steady and revenue up is a clear win. Units down and revenue down is a clear miss. Units down but revenue up is the judgment call — you’re trading some customers for a fuller till, and only you know if that’s the trade you want.

The mistakes that hide the real answer

The most common mistake is reading dollars only. Revenue can hold flat or rise while a price increase quietly sheds customers, and those lost buyers don’t show up until you look at units. A price that earns the same from fewer people is not the same as a price that’s working — the smaller crowd is a warning about next month, not a win.

The second mistake is comparing unequal or badly chosen periods — a full month against a partial one, or the promo week itself against a quiet week. If the windows aren’t the same length and roughly the same kind of weeks, the difference you see might just be the calendar. The third is expecting the numbers to prove profit. Units and revenue tell you how customers reacted, but the final word on whether a price move made you money depends on your cost, which lives in your supplier invoices, not in Clover. Read the units and revenue for the reaction, then layer your own cost on top before calling it profitable.

Consider a boutique with a scarf stuck at $30 that sold maybe two a week. The owner cut it to $20 to clear the shelf. Units jumped to nine a week and the scarves were gone in a month — revenue over that stretch actually climbed, and the space went to something that sold. The discount worked, but only the unit count made that obvious; the dollar figure alone would have looked like giving product away.

Where CornerPilot fits

Every sale before and after your price change is already in Clover — the work is lining up the same item across two equal windows and reading units and revenue side by side, which is exactly the comparison people skip when it means rebuilding an export by hand. CornerPilot connects to your Clover data and lays product sales out across periods in one place, so a before-and-after read is a quick look instead of an afternoon. The sync is scheduled rather than live, which is fine here: you’re judging a change over weeks, not chasing the last hour. CornerPilot shows you units and revenue, not margin — it won’t decide profit for you, because your cost isn’t in the register.

The takeaway

A price change is only worth making if you’re willing to check it, and checking is simpler than most merchants assume: one item, equal windows before and after, units first and revenue second. Steady units with more revenue is money you left on the table before; falling units are customers telling you the price went too far. This week, pick one item you’ve repriced in the last couple of months and compare four weeks before against four weeks after — read the units before you read the dollars, and let the pair tell you whether to keep the new price, split the difference, or put it back.

To see how the before-and-after view works across periods, take a look at the features page, or check the pricing.