The product page questions a buyer needs answered

A visitor on a product page has already decided they are interested. They arrived from a search, an ad or a link, and they are looking at the thing. What makes them leave is not a lack of enthusiasm; it is a question the page did not answer.

The questions are mundane and consistent. Will it fit. When will it arrive here. Can I send it back if it is wrong. Is this the size I need or the other one. Is this genuine. What is actually in the box. How do I reach a human if something goes wrong.

A feature list does not answer any of them, which is why pages full of features convert poorly while feeling thorough. The productive exercise is to write down the ten questions a real customer has asked you — on the phone, on a message, at the counter — and then check the page against that list. Almost every page fails on at least three, and the missing three are usually the same across an entire catalogue, which makes fixing them a template change rather than a per-product task.

First, identity and price: the product name as a customer would say it, the price, and whether that price includes tax. Ambiguity about tax at this stage produces an unpleasant surprise later, which is a common reason carts are abandoned.

Second, images that can be examined — enough resolution to zoom on the material or the finish, every variant shown, and at least one photograph that establishes scale.

Third, specifications as a scannable table, with the same field names used consistently across your catalogue so that two products can actually be compared.

Fourth, a description that addresses objections rather than restating the specification table in sentences. This is where you say who it suits, who it does not, and what the common mistake in choosing it is.

Fifth, the logistics and trust facts: delivery estimate, return window, warranty position, and a way to contact you. These are decision inputs, not legal boilerplate, and they belong on the page rather than behind a footer link.

The visible area on a phone before any scrolling is small, and what occupies it is a genuine decision rather than a consequence of the template.

Four things should be visible or immediately reachable: the product name, the price, the main image, and the way to buy. A single line with the delivery estimate and the return window earns its place there too, because those are the two facts most likely to be the blocker.

The common own goal is a full-height hero image that pushes the price below the fold. The visitor scrolls looking for it, and every additional interaction between arrival and the price is a chance to leave. A large image is worth having; it does not need to occupy the entire first screen.

Sticky elements help here. A price and add-to-cart bar that remains visible while the visitor scrolls through specifications means the decision is always one tap away, rather than requiring them to scroll back up — and on a long page with reviews and detail, scrolling back up is a real cost.

Product photographs are not decoration; they are the substitute for handling the item, and they should be judged by what they let a customer verify.

Scale is the most commonly missing one. A photograph of a brass lamp against a plain background tells you nothing about whether it is 15 centimetres or 50. A hand holding it, or a shot in a normal setting, resolves this instantly — and dimensions should also appear as text in the specification table, because an image is not searchable and not accessible.

Texture and finish need a close crop at enough resolution to survive zoom. This is where sellers of fabric, wood, leather and metal either succeed or generate returns.

Show every variant. A colour the customer cannot see is a colour they will not choose, and a variant that shows the wrong image is a return in progress. Show what is in the box, so the accessories that are and are not included are unambiguous. For clothing, both a flat-lay and an on-body shot, with measurements written as text rather than embedded in a size-chart image that cannot be read on a phone.

These two are frequently merged into one block that does neither job.

A specification table is for facts that are the same kind of fact across products: dimensions, weight, material, power, capacity, warranty period, country of origin. Its value comes from consistency — if one product lists 'Material' and another lists 'Made of', they cannot be compared, and comparison is exactly what a buyer is doing. Fixing field names across a catalogue is dull work with a direct payoff.

A description is prose, and its job is the part a table cannot carry: who this suits and who it does not, the situation it is for, the objection you know customers raise, and the choice people get wrong. 'Runs slightly small, so size up if you are between sizes' prevents a return and no specification field can express it.

The two failure modes are symmetrical. A description that restates the table in sentences has added nothing. A table written as flowing prose cannot be scanned, which defeats the only reason to have one.

The facts that decide a purchase should be where the decision happens, not in the footer.

A delivery estimate is more persuasive the more specific it is. 'Delivery in 3 to 7 days' is a range wide enough to be useless for someone buying for an occasion; an estimate against the customer's own pincode is far stronger. If you cannot compute that, stating your dispatch time — orders placed before a cut-off ship the same day — is honest and still useful.

The return position needs to be a sentence on the page, not a link. How long, who pays return shipping, and what condition the item must be in. A buyer who cannot find this assumes the worst, and the assumption is free for them and expensive for you.

Add the boring proofs that you are a real business: a phone number that is answered, an email, and whether a GST invoice is available — that last one decides the purchase outright for business buyers. None of this is persuasion. It is removing reasons to hesitate, which is most of what a product page can actually do.