Shopify product pages are where shoppers decide whether a garment is worth the risk of shipping and a possible return. Photos and size charts help, but they’re still stand-ins for “how does this look on me?” Closku adds a try-on step on the PDP: the shopper uploads a full-body photo and sees that SKU on their own body before Add to cart.
You don’t install Closku from the Shopify App Store. You export a CSV, import it into Closku, and paste one script into your theme. This guide walks through that path for product pages specifically.
Why put try-on on the product page
Campaign imagery sells the brand; the PDP sells the decision. When someone is comparing sleeve length, hem, or drape, another static photo rarely closes the gap. Try-on on the same page as price and variant picker keeps the shopper in flow—they don’t leave for a separate tool or guess from the model’s body.
For the broader Shopify story—merchant pain, pricing, and platform context—see Virtual try-on for Shopify stores.
Export your catalog from Shopify
From Shopify admin, export products to CSV with the fields you already use for other tools: titles, SKUs, and image URLs Closku needs to match each garment. You don’t need every variant on the first pass; many merchants start with bestsellers or high-return SKUs.
When you add products, change images, or retire SKUs, export again and re-import into Closku. There is no live sync from Shopify yet—that’s an honest limit, not a hidden step.
Import into Closku
In your Closku workspace, import the CSV and confirm the rows you want available for try-on. The import maps names, SKUs, and images to the renders shoppers will see on the storefront. Account setup, API details, and day-to-day operations are documented in the docs.
Starter is $49 a month for 145 try-ons; unused try-ons don’t roll over. Compare Growth, Scale, and Enterprise on pricing if you need more volume. Yearly billing saves 20%.
Paste the script in your theme
Closku gives you one script snippet to add to your Shopify theme—typically in the layout or template that wraps product pages. Paste it once; the docs describe where merchants usually place it and how to verify it loaded. You’re not waiting on App Store approval; you control when the snippet goes live.
The same CSV-plus-script pattern works on WooCommerce, BigCommerce, and custom storefronts if you add channels later. Shopify is just the export source in this walkthrough.
Where the try-on button appears
After the script is live, eligible product pages show a try-on entry point near the purchase decision—alongside variant selection and Add to cart, not buried in a footer link. The shopper opens try-on, uploads one full-body photo, and sees the garment from your catalog on themselves.
If a product isn’t in your last CSV import, it won’t offer try-on until you add it in Closku and refresh the catalog. That’s why testing one known SKU first saves debugging time across the whole theme.
Honest limits
Closku is not on the Shopify App Store yet, and there is no live automatic sync from Shopify admin. You re-import CSV when your catalog changes. If your team requires a marketplace install and hands-off sync today, this setup isn’t the right fit yet.
We also don’t publish made-up return-rate percentages or App Store rankings here. What try-on does on the PDP is concrete: let shoppers see the garment on their body before they pay. What that means for your returns depends on your catalog and traffic, not a number on a landing page.
Test one SKU before you scale
Pick one product page, confirm the CSV row, deploy the script, and run through upload and render yourself. Check mobile and desktop, then share the URL with someone on your team. When that loop works, import the rest of the catalog and roll try-on out to more PDPs.
Need help with theme placement or a oddball catalog format? Email hello@closku.com. Ready to start? See pricing and create an account from sign up.