Virtual Try-On for BigCommerce Stores: What Your Options Are

Most try-on content assumes you run Shopify. If your clothing store lives on BigCommerce, you have been politely ignored by about half the internet. Here is what actually works.

Can you add virtual try-on to a BigCommerce store?

You can, in two ways. Install a try-on app from the BigCommerce App Marketplace if one fits, or wire a try-on API into your product pages yourself.

Corlen fits the second way. We build a Shopify app and a WordPress plugin, not a BigCommerce app, and it is better to say so now than after you have booked a developer.

What are your options on BigCommerce?

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

A marketplace app saves time if it handles your garments well. The API route makes sense when you want the button to look like part of your store, or you already pay a developer.

How does the API route work?

BigCommerce's own documentation describes a Scripts API and Script Manager that can load a script on specific page types, including product pages, without editing theme files. That gives you a place to put the button.

1. Add a script to the product template through Script Manager that renders a try-on button and a photo upload.
2. Send the shopper's photo, with the product's garment image, to an endpoint on your own server.
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 in the page.

The key stays on your server. Put it in the page script and anyone can open dev tools and copy it, which is a very expensive way to teach a lesson about browsers. The API guide for developers walks through the request flow, and the docs have the exact fields.

One catch from BigCommerce's docs: scripts added through the Scripts API do not render when you develop locally with Stencil CLI. Test on a staging copy of the live storefront.

What should you test before launch?

Start with the 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.
• Mobile: most shoppers will upload from a phone, so test the upload there first.
• Wait time: show a clear loading state, since the job takes real seconds.

If the demo mangles your best seller, no integration will fix that. Better to learn it in ten minutes than in a sprint review.

Should you build it or buy an app?

Buy if you have no developer and a marketplace app 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.

Whichever route you pick, 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 are ready to see your own pieces rendered, try Corlen on your own photo.