Why the order of a store's sections changes conversion — Learn

What this lesson teaches

Order page sections by the objection they resolve, not by convention
Give a stated reason for every section's position
Know how much traffic it takes to prove a section-order change, and what to do without it

A visitor arriving on a product page is running an interrogation they will never voice: What is this? Why would I want it? Why should I believe you? What will it cost me in total? What happens if it is wrong? The page answers those questions in the order it happens to be arranged, and the visitor leaves at the first question that goes unanswered too long.

Order by objection, not by convention

One defensible ordering, with the reason each position exists.
Position	Section	The question it closes
1	What it is, in a sentence, with the item visible	Am I in the right place?
2	The single strongest specific benefit	Why would I want this rather than nothing?
3	Price, and total delivered cost	What will this actually cost me?
4	Proof — provenance, specification, evidence	Why should I believe the claim above?
5	The objection you know is coming	The reason I was about to close the tab
6	Returns, delivery times, guarantee	What happens if I am wrong?
7	Detail for the reader who is still reading	Everything else

Two positions in that list are frequently argued about, and the argument is usually resolvable. Price high on the page loses the visitors for whom the number is disqualifying — and it loses them before they have consumed the case, which is a saving, not a loss, unless the case is what changes their mind about the number. Price is placed low only when the page genuinely contains an argument that alters what the price means. If it does not, hiding the number merely postpones the exit and wastes the visitor's time along with your attention.

The honest limit on measuring this

Section order is exactly the kind of change that A/B testing is meant to settle, and exactly the kind of change most stores cannot afford to test. From the previous lesson's arithmetic: separating a 2.0% conversion rate from a 2.3% one requires on the order of 35,000 sessions per variant. A store with 8,000 sessions a month would spend most of a year on one such comparison, during which the product, the season and the traffic mix would all have changed.

The consequence is not that order does not matter. It is that below a few tens of thousands of sessions per month, section order must be decided by argument rather than by measurement — and the discipline that replaces measurement is writing the reason down. A page whose every section has a stated reason for its position can be revised when the reason turns out to be wrong. A page arranged by taste cannot be revised at all, only rearranged.

What you can measure at low traffic

Not conversion rate, but behaviour: how far down the page people scroll, which section they stop at, where they leave, what they ask in support messages. A recurring question in the inbox is a section in the wrong position, and it needs a sample size of about five to be worth acting on.

Figures in this lesson are illustrative inputs chosen so the arithmetic can be checked. They are not measurements. What FlowFinds Solutions actually measures is published, with its artifacts, in research.