Product page checklist A product page checklist helps shoppers find facts, compare options and buy with less doubt.
Few pages in a shop work as hard as the product page. It must help somebody decide whether an item suits them, state what the purchase really costs and carry that decision into checkout without introducing a surprise. A polished photograph cannot compensate for a missing measurement, an ambiguous variant or a delivery charge revealed too late.
Review the page as a customer with no knowledge of the catalogue. Use a real phone, choose an awkward variant and follow the journey through to the final payment step. The questions below are designed for that practical review.
Start with the buying decision
Put the information that changes the decision near the product title and selection controls. That usually means the exact product name, key differences between variants, current availability and the main reason one option suits a particular use. A customer should not need to decode an internal stock label.
Show what is included in the box and what is not. If a photographed accessory is sold separately, say so beside the image or option rather than hiding the point in a general terms page. For products that must fit, provide dimensions in a familiar unit and explain how to measure.
Inspect every factual claim
UK product labelling guidance says claims about matters such as quantity, size, material and capability must be accurate. Turn that principle into an evidence check. Match copy against the approved specification, packaging or supplier record, then remove adjectives that nobody can substantiate.
Images are claims too. Check that colour treatment does not materially misrepresent the item and that the gallery shows the actual variant where possible. Write useful alternative text for informative images. Avoid repeating the product title in every image description when a view or feature can be identified instead.
Make price and availability unambiguous
The total price should be clear before the customer commits. The Competition and Markets Authority explains that mandatory charges, fees and taxes must be included in the displayed total. If delivery cannot be calculated yet, explain how it is calculated and make the available information prominent.
Do not preselect paid optional extras or allow a crossed-out price to imply a saving that is not genuine. Where a promotion has conditions, put the important condition beside the offer. Stock messages should distinguish available now, made to order, back order and unavailable rather than using one vague “in stock” badge.
Make selection errors recoverable
Test all combinations of size, colour, quantity and subscription choice. A sold-out combination should be disabled or explained before the buy button is pressed. Error text must identify the field, describe the correction and remain visible to keyboard and screen-reader users.
GOV.UK guidance on online selling says customers must be able to correct order errors before placing an order. In practice, the basket and final review need to show the chosen item, variant, quantity, recurring commitment where relevant, delivery option and price in plain language.
Answer delivery and returns questions in context
Give a realistic dispatch or delivery range and state important geographic limits. Do not promise a date that the fulfilment process cannot support. Link to the full delivery policy, but keep the headline timing and charge close to the purchase control.
Summarise the applicable returns position without claiming that store policy removes statutory rights. Products can have different rules because of their nature or customisation. the wording needs an owner and a documented review. The full policy should be reachable before purchase.
Run a five-minute page test
- Can a new visitor identify the exact product and intended use?
- Are materials, dimensions, compatibility and care details accurate?
- Does changing a variant also update its image, stock state and price?
- Are the total cost and unavoidable charges clear at the right time?
- Can every field and control be used without a mouse?
- Do delivery and returns links open the policy a customer expects?
- Does a test order create the correct confirmation and operational record?
Repeat the test with slow mobile data and an expired basket. These less convenient journeys often expose stale availability, double submissions and missing messages that a normal desktop test will not find.
Record the sign-off
Name the person who approved specifications, pricing, policy wording and fulfilment behaviour. Save the test order number and date. That small record makes later catalogue changes easier to investigate and prevents everybody assuming somebody else checked the page.
Running the checklist on one page
Take a product page for a cast-iron casserole dish selling at £89. It has eight photographs, a paragraph of atmospheric copy and a specification table.
Working through the checklist turns up four gaps. The table gives capacity in litres but not the hob diameter, which is the number people measure against their own cooker. "Suitable for all hob types" appears in the copy but induction is not named. induction owners are the ones who check. The price shows but delivery cost only appears at the second checkout step. And the returns line reads "30-day returns", which does not say who pays for a 4kg parcel to come back.
None of these are design problems. All four are answerable in a sentence each. each one is a reason somebody currently closes the tab.
Sources and further reading
- GOV.UK guidance for online and distance selling — the source for pre-order information, correcting errors, optional charges and order confirmation.
- CMA summary on clear and accurate prices — current UK guidance on total prices, unavoidable charges and drip pricing.
- GOV.UK product labelling guidance — the reference for accurate product descriptions and required information.
Our ecommerce service can turn this review into catalogue, interface and checkout work. For a specific store, send one representative product and its current checkout journey.
Quick product page checklist action plan
- Use a clear product name. Write down the result. Name one owner.
- Show price and stock near the top. Test this step. Keep proof of the test.
- Add sharp images from key views. Use real data. Check each fact.
- State size and material facts. Ask one user. Note what feels hard.
- Explain delivery before checkout. Fix each fault. Run the check again.
- Make the return route easy. Set a due date. Review the result.
- Use one clear buy button. Write down the result. Name one owner.
- Test the full page on a phone. Test this step. Keep proof of the test.
- Choose one clear goal. Use real data. Check each fact.
- Name the owner for each task. Ask one user. Note what feels hard.
- Test the full path before launch. Fix each fault. Run the check again.
- Set the next review date. Set a due date. Review the result.
- Keep the plan where staff can find it. Write down the result. Name one owner.
- Use plain words in each note. Test this step. Keep proof of the test.
- Save proof for each key check. Use real data. Check each fact.
- Fix one issue at a time. Ask one user. Note what feels hard.
- Check the result with a real user. Fix each fault. Run the check again.
- Remove work that does not help the goal. Set a due date. Review the result.
- Share each major change with the team. Write down the result. Name one owner.
- Run the same checks after each update. Test this step. Keep proof of the test.
- Check the source of every key fact. Use real data. Check each fact.
- Keep private data out of public notes. Ask one user. Note what feels hard.
- Plan what to do when a check fails. Fix each fault. Run the check again.
- Give each choice a clear reason. Set a due date. Review the result.
- Keep old files until new work is proven. Write down the result. Name one owner.
- Ask for help when the risk is high. Test this step. Keep proof of the test.
- Check phone and desktop views. Use real data. Check each fact.
- Make the next step easy to find. Ask one user. Note what feels hard.
- Track the result that matters most. Fix each fault. Run the check again.
- Close each task when proof is saved. Set a due date. Review the result.
Use this product page checklist plan as a live check. Keep the notes short. Review the work after each major change.
