The design of the store should be checked on products that will actually be sold. The length of names, variants and availability influence the layout more than an impressive picture of the sample collection.
Select a sample of products
You do not need to prepare the entire catalog at once, but the sample should show its variety. Include a product with a long name, several variants, lack of availability and a position requiring additional explanation. If you sell sets, show what the customer needs to know about their content.
For the store run by the Warsaw company there may also be different means of reception. If the offer actually includes a stationary point, the model should clearly distinguish the availability for shipment from the reception conditions. Do not design such a message without confirming the process on the team side.
Rate list, card and basket together
On the list, the customer recognizes the right product. On the card he checks the details and in the basket confirms the choice. These views should use consistent names and data. Changing the variant designation in the middle of the path can cause uncertainty despite the correct operation of the system.
For example, the person choosing the lamp in a certain colour and size should recognize both parameters also after adding it to the basket. The general title of the product itself may not be enough to check the order.
Prepare tasks to go through
Instead of asking a test person if the store is nice, ask them to do the job. Watch the place of hesitation without hinting at the right button.
- Find a product that meets two selected conditions.
- Check the difference between similar variants.
- Change the number of pieces and remove accidentally added position.
- Find out the information you need before you buy it.
- Return to the catalogue without losing your choice orientation.
Improve the Cause of Difficulty
If the user does not understand the filter name, the larger button will not solve the problem. If he does not see the difference of products, the content or lack of comparable parameters may be the cause. Save observations along with the screen and the task to which they relate.
The mock-up allows you to agree on the rules in advance. The ready-to-implement test is still needed, especially for payments, delivery and system messages. See data flow in the store and determining the scope of the first version.
