Plenty of views and no buyers: is it your price or your page?

The pattern is always the same. One product collects the views, the buyer count underneath it barely moves, and by Friday you have talked yourself into taking twenty per cent off. Sometimes that is the right call. More often the number was never the problem, and cutting it removes the clearest signal you had about what actually is.

Why the price gets blamed first

Price is the only part of a product page that is a single number. Everything else, from the cover image to the first line of the description to the length of the order form, is a judgement you have already made once and would rather not reopen. The number takes the blame because the number is the only thing you can change in four seconds.

The genuinely hard part is that you cannot see why anyone left. Analytics of any kind tell you what happened, never what someone was thinking. A visitor who arrived from a story link, glanced for three seconds and swiped away looks identical in the totals to a visitor who read every word, reached the payment step and decided it was too much money. Those two people need opposite fixes, and the ratio treats them as the same person.

What you can do is narrow it down. store.fan reports views, buyers and revenue per product rather than for the store as a whole, and shows where the traffic came from, so you can rule things out in order. Ruling out in order is the entire job. Full analytics sit on the paid plans, so check pricing to see what you have available before you start.

Reading a product line instead of a monthly total

Most price cuts are made from one figure: money in, this month, everything added together. That figure hides the only detail that matters, which is where the traffic landed. Here is the difference between guessing from a total and reading a product line. If you want the full list of what is reported, the analytics feature page sets it out.

Four checks, in this order

Do all four before you open the price field. Each takes a few minutes in the dashboard, and not one of them costs you margin.

1. 1Open your analytics and look at the product line rather than the store total. If views are spread thinly across five products, you do not have a price problem on one of them; you have a storefront that does not point anywhere in particular.
2. 2Check the traffic source sitting next to those views. People arriving from one link in a story behave nothing like people arriving from search. A page that converts search traffic poorly usually needs a clearer promise, not a smaller number.
3. 3Open your own storefront the way a stranger does, on a phone, and stop at the first screen. If the product's promise is not readable before you scroll, those views were never real consideration in the first place.
4. 4Read the first two lines of the product description out loud. If they describe the format, a 42-page PDF or a 90-minute call, rather than the outcome, most visitors decided before the price was ever relevant.
5. 5Walk your own checkout once, all the way to the payment step. Count what you are asking for. On a booking, count the order-form questions; a long brief in front of a small price loses more sales than the price does.

A worked example

Suppose you sell a template pack at £29 and a checklist at £9. Over a month the template pack shows a few hundred views and a handful of buyers, while the checklist shows a fraction of the views and a similar number of buyers. Read as one total, that says the expensive product is overpriced. Read per product, it says something else entirely: nearly all your traffic lands on the expensive page first, and the cheap page quietly converts the small number of people who go looking for it.

The fix there is not a price cut. It is a first screen that offers the checklist as the obvious entry point and the template pack as the step up, so the traffic meets a decision it is ready to make. Had you dropped the pack to £19 instead, you would earn less on every sale and still not know whether anything improved, because you changed the number and the running order in the same week. Change one thing, let it run a fortnight, then read the same line again.

The mistake nearly everyone makes

The mistake is treating the price as a dial rather than a claim. A lower number does not only ask for less money, it tells the visitor the thing is worth less, and it says so before they have read a word about what it does. When a cut appears to work, it very often worked because a clearer promise and a better first screen arrived in the same week and got none of the credit. That is why the order matters: a page fix keeps paying at every price, while a price fix has to be paid for again every month afterwards. If you do want to move a number temporarily, discount codes and countdown campaigns on Pro let you do it with an end date attached, which you can see on the features page.

Cutting is a decision you can make in a second and then live with for a year. Spend an hour on the page first: the first screen, the promise, the proof, the payment step. If the ratio moves, you have kept your margin and learned something. If it does not, you now have a price question you can answer with evidence instead of nerves.