Fictional sample project

A look inside a
purchase journey report.

Three findings about a product page and cart. Each includes a recommendation, suggested verification and limits to the conclusion.

Read the sample report Go to the Purchase journey check

Symbolbild zur Leistung Fictional purchase journey report

SAND & MEHR / Working example

Purchase journey check.
Product page & cart.

FICTIONAL
SAMPLE PROJECT

The starting question

Can someone choose a suitable product size, find that selection in the cart and change it understandably if needed?

This example uses an invented product page with three sizes. It shows a report's structure without using data from a real shop.

Scope of this sample

Journey reviewed: One product page → one cart
Perspectives: Mobile and desktop
Data basis: Fictional interfaces, no analytics data
Outside the scope: Checkout, payment processing and technical implementation

The method

How to read
the findings.

Observation. What appears on the page, what is missing and where?

Interpretation. Which difficulty do we suspect for the selected task?

Recommendation. Which change do we suggest and how will it be checked?

The findings in detail

What stands out in the example.

The order reflects the task each location affects. It is not a calculated revenue priority.

Product page · Mobile

The size guide is not beside the selection.

Priority: Before the next user test

Observation

The product page offers three sizes. The measurement table is further down inside the collapsed ‘More information’ section. There is no reference to it at the size selector.

Possible meaning

To compare sizes and measurements, the person must move between two places. Our assumption: help directly beside the selector shortens this path.

Recommendation

Add a brief size guide beside the selector and link to the full measurement table.

Next check

Ask a participant to choose the right size for a given need. Can they find the guide without prompting?

Limit of the conclusion: How often visitors search or abandon at this point is unknown.

Basket · Mobile and desktop

The selected variant is hard to identify in the basket.

Priority: Check alongside the first change

Observation

The basket shows the product name and image. The chosen size M appears below the title as ‘VAR-02’.

Possible meaning

Without knowing the product, the code cannot be matched to the chosen size. We suspect buyers may return to the product page to check their selection.

Recommendation

Show ‘Size M’ in the basket too. Label the variant adjustment link ‘Change size’.

Next check

Ask a participant to identify their size in the basket and then change it. They should not need an explanation.

Limit of the conclusion: The rest of the checkout has not been examined.

Basket · Feedback

After a change, the state remains unclear.

Priority: Check the technical process specifically

Observation

Changing a variant updates the basket. The interface gives no message confirming whether the change was applied.

Possible meaning

This feedback is particularly absent when the changed area is outside the screen. Whether a person clicks again must be observed in a test.

Recommendation

Show an appropriate status message after a confirmed change. Agree with development how it can be perceived using a keyboard and screen reader.

Next check

Perform a successful and a failed change in staging. Does the message match the saved state?

Limit of the conclusion: The backend was not examined. This finding concerns visible feedback.

From findings to tasks

How we would prepare
the changes.

The implementation team checks the existing system for affected functions and the work involved.

Effort estimates can be added only after that assessment.

Product design / UX

Design the size guidance.

Design the content and location of size guidance. Define a suitable test task.

Design & frontend

Make the selection unambiguous.

Align variant naming and editing across the product page and cart.

Frontend & technical review

Show success and failure.

Reproduce success and failure in a test environment before releasing a change.

What this example does not show

What still needs checking
about the effect.

Whether the changes make buying easier would need investigation on the implemented page. Conclusions about orders or revenue would additionally need suitable data.

This sample contains no measured customer results. Checkout, technical implementation and legal questions are outside the described check.

Compare your own financial assumptions

A look inside a purchase journey report.

Purchase journey check. Product page & cart.

The starting question

Scope of this sample

How to read the findings.

What stands out in the example.

The size guide is not beside the selection.

Observation

Possible meaning

Recommendation

Next check

The selected variant is hard to identify in the basket.

Observation

Possible meaning

Recommendation

Next check

After a change, the state remains unclear.

Observation

Possible meaning

Recommendation

Next check

How we would prepare the changes.

Design the size guidance.

Make the selection unambiguous.

Show success and failure.

What still needs checking about the effect.

Would you like your purchase journey reviewed?

Purchase journey check

A look inside a
purchase journey report.

Purchase journey check.
Product page & cart.

How to read
the findings.

How we would prepare
the changes.

What still needs checking
about the effect.