Virtual Try-On for PrestaShop Clothing Stores

PrestaShop stores tend to be customised, multilingual and quietly proud of it. A try-on button is welcome. A try-on button that breaks the French checkout is not.

Can you add virtual try-on to PrestaShop?

You can, in two ways. Install a ready made try-on module if one suits your catalog, or connect a try-on API to your product pages through a module of your own.

Corlen fits the second way. We build a Shopify app and a WordPress plugin, not a PrestaShop module, and it is kinder to say so before you brief a developer.

What are your options on PrestaShop?

• A ready made module: quickest to start, but you inherit its design, its limits and its pricing model.
• A try-on API inside your own module: more work up front, full control over button placement, copy and flow.
• An agency build: the same API route, with someone else carrying the development and the testing.

A packaged module saves time if it renders your garments well. The API route suits stores that already have a PrestaShop developer, or want the button to look like part of the theme rather than a guest.

How does the API route work in a PrestaShop module?

PrestaShop's developer documentation describes displayProductAdditionalInfo as a product page hook that receives the product, called from the theme's product template. A module registers the hook when it installs, and if the module skips that step, PrestaShop never calls it. That is the usual place to put a button.

1. Create a module that registers the product page hook and renders a try-on button and photo upload.
2. Send the shopper's photo, with the product's garment image, to an endpoint in your module.
3. Have that endpoint call the Corlen API with your key and start a job.
4. Poll the job status, then show the finished image on the page.

The key stays on the server. Put it in the page script and anyone with dev tools can copy it, which is a pricey way to learn how browsers work. The API guide for developers walks through the request flow, and the docs list the exact fields.

Check the hook name and template against your own theme and PrestaShop version. Custom themes sometimes skip a hook, and community guides also report two modules fighting over the same hook, so look at the module positions page if your button shows up twice.

What should you test before launch?

Start with the free live demo to see how your garments render, before any developer time goes into it.

• Garment photos: flat, whole, plain background. Our guide to photographing clothing for virtual try-on has the checklist.
• Your hardest pieces: layered looks, long hems, heavy prints.
• Languages: button text, privacy notice and error messages in every language your store runs.
• Page speed: load the script only on product pages and only when the shopper clicks the button.
• Caching: test with your cache enabled, since it can interfere with a job status request.

If the demo mangles your best seller, no module will fix that. Better to learn it in ten minutes than in a release cycle.

Should you build it or buy a module?

Buy if you have no developer and a packaged module renders your garments well. Build if you want control over the experience or already have technical help. Our post on build versus buy for virtual try-on covers that decision in more detail, and the Magento guide shows the same API pattern on another custom platform.

Either way, measure it. Pick a handful of products, compare returns against a similar period, and follow the steps in how to measure virtual try-on results. When you want to see your own pieces rendered, try Corlen on your own photo.