The store's search engine should also help if the customer does not know the exact product name. Particular attention is required to make a mistake, empty results and return to browsing the catalogue.
Collect Customer Language
Before selecting the search engine, list examples of queries. Include trade names, codes, common terms and questions received by the user. Cataloguing data may use vocabulary that buyers simply don't know.
Do not promise that the search engine will recognize each phrase. Set up priority scenarios and check them on real products. A good demonstration should also include queries harder than accurate copying of the name from the card.
Show recognizable results
In the list of results, information is needed to distinguish similar positions. Sometimes a photo and variant are enough, another time the code or application is important. The number of results does not replace their readable description.
For example, searching for parts after a fragment of the marking should allow you to check the full code before opening the card. If several items look identical, the image enlargement itself will not solve the problem.
Design an empty result
The message about the lack of products should explain the situation and suggest a sensible next step. You can allow to change your password, change to the right category or contact with the service. Do not present random products as if they correspond exactly to the request.
Check:
- a lettering request;
- the general name and product code;
- no match;
- an active performance limiting filter;
- change the query on your phone;
- return from the card to the previous list.
Use post-start observation
Collect available information about the difficulties of searching and reporting from employees. Repeated password without results may indicate a lack of goods, other naming or data problem. Each reason requires a different solution. Do not automatically expand the matching without evaluating the quality of the results. store filters and comparison of products.
