Virtual Try-On for Made-to-Measure and Tailoring

A made-to-measure configurator asks the customer to assemble a garment from parts: a fabric swatch, a lapel, a button stance, a lining. Nobody can hold that in their head. Virtual try-on renders the configured garment on the customer, from one photo, before anything is cut.

The problem

Made-to-measure is the hardest visualisation problem in apparel, because the thing being sold does not exist yet. There is no photograph of it, and there never will be until it is made. What the customer gets instead is a grid of fabric swatches, a set of option names, and a price that rises as they click.

A swatch photographed flat tells you almost nothing about how a cloth will look as a finished jacket on a particular person. Weight, pattern scale and shade all read differently at garment size than at swatch size, and a check that looks restrained in a two-inch square can be loud across a chest.

The commercial consequence is specific to this sector. The garment is cut to one person, so it cannot be resold, which makes a disappointed customer an expensive customer. And the hesitation this produces is quiet: the customer does not complain, they simply do not complete the configuration.

How it works here

  1. Start from the cloth and garment photography you hold. Tailoring businesses already photograph their cloths and their finished house styles. That imagery is the input, with no 3D pattern to build per option.
  2. The customer uploads one photo. A single photograph, no app and no body scan. The measurement appointment is unaffected and happens as it always did.
  3. Render the configuration on them. The customer sees the garment on themselves rather than as a swatch and a list, at up to 4K, so cloth and detail hold up at full size.
  4. Keep it on the page. The try-on sits inside the existing configurator with a single script tag on any platform, or through the REST API for a custom-built one.
  5. Measure where configurations stall. The analytics dashboard reports try-on engagement and conversion impact, which in a configurator shows you which choices customers could not commit to.

What matters in this sector

Cloth at garment scale. Pattern scale and shade are the whole decision in tailoring. A check, a chalk stripe or a herringbone has to read at the size it will actually be worn, not at swatch size.

Structure above all. A jacket is a built object: canvas, padding, a rolled lapel, a set sleeve. It holds its line away from the body. Any system that renders tailoring as cloth draped on a torso will look wrong immediately to the customer who cares most.

Drape by weight. A 250g tropical wool and a 450g flannel hang differently on the same frame. Viewrobe's models cover 17 fabric types, and weight behaviour is the thing to test with your own cloths.

The customer's own build. Tailoring exists because bodies differ. A render that quietly standardises the customer's shape defeats the category it is being sold into.

Detail that survives the render. Lapel width, button stance, pocket style and trouser break are the options being paid for; they have to stay legible in the output.

Where it stops

Virtual try-on does not take measurements and does not replace the fitting. Made-to-measure is cut from a measured pattern and finished at a fitting; what the try-on changes is the confidence with which a customer commits to a cloth and a configuration.

It does not predict how a specific cloth will age, press or wear, which for a tailoring customer is part of the decision and still belongs to the conversation.

And it is bounded by the imagery it is given. A cloth photographed badly will render badly, which in this sector means photographing cloths consistently is worth doing properly once.

Written by Viewrobe. Published 6 October 2026, last reviewed 7 October 2026.

Questions from this sector

Does this replace the measurement appointment?

No. Measurements and fittings are unchanged. The try-on works earlier, when the customer is choosing cloth and options and cannot picture the result.

Can it show a specific cloth on a specific customer?

Yes, that is the use. The customer uploads one photo and sees the configured garment on themselves rather than as a flat swatch.

Will it work inside our existing configurator?

Yes. It attaches with a single asynchronous script tag on any platform, and a custom or headless configurator can call the REST API directly.

We photograph our cloths ourselves. Is that enough?

Usually yes. Consistent, evenly lit photography of cloths and house styles is the input; the image requirements page covers what helps.

Is customer imagery kept?

No. A customer photo is used only to generate the requested try-on, permanently deleted within 24 hours, and never used to train AI models.

See it on your own catalogue

Book demo