Before choosing a virtual try-on solution, write down the task the technology should perform: show how clothing may look on a person or recommend a size for a specific item. With some visualization tools, the image does not show the exact fit or size. So do not treat an appealing demonstration as proof that an item will fit a customer.
Before commissioning development, get the provider’s description of the required product data, technical conditions, and availability for a Ukrainian store and customers in Ukraine. Then compare demonstrations using the same set of items. Based on the results, decide whether the solution meets your needs and what else you need to clarify before implementation.
Assess how the clothing looks and the size recommendation separately
Visualization is an image of how clothing may look on a person. Possible errors in body shape, personal features, and clothing details have been described for some image-generation tools. Clarify the limitations of the specific solution being offered to you.
If you need a size recommendation, ask the provider to explain what data it uses and which product categories the feature supports. Separately request a description of how accuracy was checked: what the recommendations were compared against, which items were used, and which errors were taken into account.
If a confidence indicator appears alongside the recommendation, ask what it means and how it is calculated. Do not use it as proof of accuracy without an explanation of the methodology. In the project requirements, record the expected visualization outcome and the expected size-selection outcome separately.
Agree on product data before preparing the demonstration
Ask an employee to prepare a list of test items. For each item, record the model, color, size, and material. Check the entries against the actual product and its photos so that any comments after the demonstration refer to a specific item.
Before preparing files, ask the provider for a specification—a list of required data and rules for formatting it. Ask questions such as:
- Which clothing categories does the solution support, and what exceptions are there?
- Which photos and angles are needed for each item?
- Which product attributes are required?
- If a size chart is needed, which fields, units of measurement, and measurement rules should be used?
- How should different colors and sizes of the same model be identified?
- How does the provider report missing or unsuitable data?
Agree on the requirements for the chosen solution. Do not transfer file formats, attributes, or measurement rules from another service’s documentation.
Check availability and how it works on your store’s website
Ask for a written explanation of the terms of use for a store in Ukraine and, separately, for its customers. Request a demonstration of the Ukrainian interface if your site needs one. Do not assume these terms are agreed just because the service has a webpage or a demonstration.
| What to check | What to request |
|---|---|
| Regions and languages | List of supported countries and languages, and customer access conditions |
| Devices and accounts | List of browsers and devices, and sign-in requirements |
| Website compatibility | Description of how it connects to your platform and a demonstration of how it works |
| Images and files | Allowed formats, resolution, and file size |
| Request handling | Load conditions, waiting time, and behavior when an error occurs |
| Payment | Fees, billing unit, and usage limits |
Ask your website developer to assess the proposed connection method. Request a demonstration of the entire flow: opening a product, starting the feature, waiting for the result, and displaying an error message.
Compare demonstrations using the same criteria
Give providers the same items and original product photos. For images of people, use demonstration materials supplied by the providers. Do not use photos of your store’s customers for this preliminary assessment.
Prepare a checklist in advance: whether the color, print, garment length, and cut details are preserved. Record specific differences alongside the original image and the result. If a result is ambiguous, ask for the demonstration to be repeated and for the differences to be explained.
Hypothetical example: a store owner selects two printed T-shirts, two plain shirts, and two dresses—six items in total. Both providers receive the same product photos. An employee records where a print changed, a pocket disappeared, or the length differs. This is an example of how to organize a comparison; six items is not an established testing standard.
Use the results to assess how the clothing looks. Evaluate size recommendation accuracy using a separate methodology that the provider should explain. Do not draw conclusions from the demonstration about future reductions in returns.
Prepare product attributes in Torgsoft
A consistent product list is needed for comparison. In Torgsoft, you can create product cards with size, color, model, and material. Use these attributes as the basis for the list of items in the demonstration.
Ask an employee to check the entries in the cards against the actual items and photos. The owner will be able to link each comment on a result to a specific model, color, and size.
Use the cards to organize product attributes. Agree separately with the provider on the requirements for transferring this data. Assess the virtual try-on result using the agreed demonstration criteria.
Go back to the previous step