# LookCheck AI — Complete Website Copy & Documentation > Comprehensive full-text documentation of all LookCheck AI products, platform integrations, categories, hardware specifications, case studies, and security standards. --- Metadata for every route Ships independently of the rest of this deck. Titles sit under 60 characters once the template appends "| LookCheck", so do not add it yourself. Descriptions run 140 to 158 characters. | Route | Page Title | Meta Description | |---|---|---| | `/articles` | Latest Articles | Field notes, engineering walkthroughs, and practical guides on deploying AI virtual try-on and smart mirrors in physical and e-commerce retail. | | `/articles/smart-mirror-retail-store-install` | Smart Mirror in a Retail Store: What an Install Involves | Siting, catalogue connection, staff training and the first three weeks. What deploying a smart mirror in a retail store actually involves on the ground. | | `/` | AI Virtual Try-On for Fashion Retail | Let shoppers see your garments on their own body before they buy. Virtual try-on for Shopify, WooCommerce and Salla, plus AI smart mirrors in store. | | `/virtual-try-on-software` | Virtual Try On Software | Photorealistic AI try-on for fashion e-commerce. Every category, full outfits, and a widget that installs without touching your theme. | | `/virtual-try-on-shopify` | Shopify Virtual Try On App | Add photorealistic virtual try-on to your Shopify store in minutes. No 3D models, no new photography, no theme edits. Free plan available. | | `/virtual-try-on-woocommerce` | WooCommerce Virtual Try On Plugin | Virtual try-on for WooCommerce that renders off-site, so your storefront stays fast. Works with any theme, and your catalog stays yours. | | `/virtual-try-on-salla` | Salla Virtual Try On App | Virtual try-on for Salla merchants. Let shoppers see the garment on themselves before they order, and cut COD refusals across the Gulf. | | `/ar/virtual-try-on-salla` | Salla Virtual Try On App (Arabic) | Virtual try-on for Salla merchants in Arabic. Let shoppers see garments on themselves before ordering. | | `/virtual-try-on-unstitched-fabric` | Virtual Try On for Unstitched Fabric | Show a finished suit rendered from a length of lawn, khaddar or chiffon. Virtual try-on built for unstitched fabric retail. | | `/virtual-try-on-shoes` | Virtual Try On for Shoes | Let shoppers see footwear on their own feet before buying. Photorealistic rendering for sneakers, heels, boots and formal shoes. | | `/virtual-try-on-eyewear` | Virtual Try On for Glasses & Sunglasses | Frames rendered on a shopper's own face from a single photo. No AR app, no face scan, no special hardware needed. | | `/virtual-try-on-accessories` | Virtual Try On for Jewellery & Bags | Show necklaces, earrings, bags and hats on real people. One widget covers every category you sell, not just clothing. | | `/virtual-try-on-api` | Virtual Try On API | Render try-on images from your own stack. For custom storefronts, marketplaces and platforms without a native LookCheck app. | | `/mirror` | LookCheck AI Smart Mirror | A 4K in-store mirror that shows customers other sizes, colours and full outfits without leaving the fitting room, with AI size recommendation. | | `/mirror/specifications` | Smart Mirror Specifications | Screen sizes, camera, scanner, payment terminal, network, power and POS integration for a LookCheck AI Smart Mirror deployment. | | `/pricing` | Pricing | Start free with 20 try-ons a month. Paid plans from $54. See what each plan includes and what a single try-on actually costs you. | | `/demo` | Live Virtual Try On Demo | Try LookCheck yourself. Pick a model, build an outfit and see the render, with no signup and nothing to install. | | `/contact` | Contact Us | Talk to the LookCheck team about an online rollout, a smart mirror deployment, or anything the documentation does not answer. | | `/security` | Security & Data Handling | How LookCheck handles shopper photos: encrypted in transit, processed, then deleted. Rendream is ISO 27001:2022 certified. | | `/faq` | Frequently Asked Questions | How virtual try-on works, what it costs, which platforms we support, what happens to customer photos, and how long setup takes. | | `/press` | Press & Media | LookCheck AI in the press, plus logos, product images and company boilerplate for journalists and partners. | | `/case-studies` | Case Studies | How fashion brands in the UK, UAE and Pakistan use LookCheck across online storefronts and physical stores. | | `/case-studies/alex-rose` | Alex Rose London Case Study | A London bespoke tailoring house has run LookCheck online for over a year. What changed in revenue, delivery time and customer experience. | | `/case-studies/mushq` | Mushq Case Study | One of Pakistan's best-known fashion labels runs LookCheck online and in store, including unstitched fabric rendering. | | `/case-studies/siiine` | Siiine Case Study | A UAE womenswear label approached virtual try-on cautiously. What convinced them the render was good enough to put on their store. | | `/case-studies/breakout` | Breakout Smart Mirror Case Study | How a high-street fashion retailer put LookCheck AI Smart Mirrors on the shop floor. | | `/case-studies/narkins` | Narkin's Case Study | A Pakistani menswear brand launching LookCheck virtual try-on on Shopify. | | `/lookcheck-app` | The LookCheck App | A shopper app for trying on clothes from any store, coming soon. Join the waitlist to hear when it launches. | | `/privacy-policy` | Privacy Policy | How LookCheck collects, processes and protects data. Shopper photos are processed and then deleted, never retained. | | `/terms-of-service` | Terms of Service | The terms governing use of LookCheck virtual try-on software and LookCheck AI Smart Mirror deployments. | | `/return-refund-policy` | Return & Refund Policy | Refund eligibility, cancellation terms and how to request a refund on a LookCheck subscription. | The hub and the platform pages All four follow the skeleton in A2. Sizing appears on none of them. Each opens by linking up to the hub and closes with the self-serve install. D1Promote/virtual-try-on-software · ~950 words The hub page, currently orphaned with zero inbound links H1: Virtual try-on software for fashion stores Body: LookCheck renders your products on your customer's own body, from a single photo they upload. It runs on your product pages, it covers every category you sell, and it needs no 3D models and no new photography. CTA: Install on Shopify CTA: Try the live demo H2: The problem every fashion store has online Body: A shopper looking at a product photo is looking at somebody else. However good the photography, however detailed the size chart, the question they actually want answered is how the piece will look on their own body, and nothing on a standard product page answers it. Body: So they hesitate. Baymard Institute puts average cart abandonment at 70.22%, drawn from fifty separate studies. Of the orders that do complete, NRF and Happy Returns estimate 19.3% of online sales were returned in 2025. Fashion carries more of that than most categories, and a good share of it traces back to the same unanswered question. H2: What makes LookCheck different H3: Every category, one widget Body: Most try-on tools handle tops and stop. LookCheck renders tops, bottoms, dresses, outerwear, footwear, eyewear, jewellery, bags and hats. If you sell it and somebody wears it, it renders. For a store with a mixed catalog that matters more than it sounds, because a tool that covers a third of your products gets used on a third of your traffic. H3: Whole outfits, not single items Body: Shoppers combine pieces across your catalog and see the complete look in one render. That is a different behaviour from checking one item and leaving, and it pulls more of your catalog into the session. A customer who came for a shirt and rendered it with trousers and shoes has just looked at three of your products properly. H3: Real fabric behaviour Body: Satin, knit, chiffon, heavy denim and layered pieces all fall differently. The engine renders that difference rather than pasting a flat image over a body outline, which is what separates a result a customer trusts from one that makes them more uncertain than before. H3: Unstitched fabric Body: LookCheck renders a finished garment from a length of unstitched cloth, which is a different technical problem from mapping a photographed garment onto a body, and one almost nothing else in the category attempts. Link: "How unstitched rendering works" [/virtual-try-on-unstitched-fabric] H2: How it works H3: For your customer Body: They tap a try-on button on your product page, upload one clear full-body photo, pick the items they want to see, and get a render in seconds. No account with us, no app to download, no guided capture sequence. H3: For you Body: Install the app for your platform. It reads your product catalog, matches the widget to your theme, and adds the button. Most merchants are live in about five minutes, with no developer time and nothing to edit in theme files. H2: Where it runs Body: Native apps for Link: "Shopify" [/virtual-try-on-shopify] and Link: "Salla" [/virtual-try-on-salla] a plugin for Link: "WooCommerce and WordPress" [/virtual-try-on-woocommerce] and an Link: "API" [/virtual-try-on-api] for custom storefronts, marketplaces and platforms without a native app. H2: Built for the categories you actually sell Body: Beyond apparel, LookCheck has dedicated pages for Link: "footwear" [/virtual-try-on-shoes] Link: "eyewear" [/virtual-try-on-eyewear] Link: "jewellery and accessories" [/virtual-try-on-accessories] and Link: "unstitched fabric" [/virtual-try-on-unstitched-fabric] The same widget covers all of them, so a mixed catalog needs one installation rather than one tool per category. H2: Who gets the most out of it Body: Stores where the customer is judging how something looks on a body rather than what it does. Fashion, footwear, eyewear, accessories, and anything where fit and proportion are part of the decision. Body: It matters more the further your catalog sits from what a product photo can convey. A plain white t-shirt photographs honestly. A cut that sits differently on different bodies, a fabric whose fall is the point, a piece that only makes sense as part of an outfit, none of those do. H2: What it costs Body: A free plan gives you 20 try-ons a month on your real catalog, with no card. Paid plans start at $54 a month and are priced per render, because rendering costs real compute and we would rather charge for it visibly than cap you somewhere less obvious. Link: "Full pricing" [/pricing] H2: There is a version for your shop floor too Body: The Link: "LookCheck AI Smart Mirror" [/mirror] puts the same engine on a 4K display in your store, and adds AI size recommendation, which the online product does not do. H2: Questions merchants ask H3: Do I need special product photography? Body: No. LookCheck works from the catalog images you already have. H3: Will it slow my storefront down? Body: Rendering happens on our infrastructure, not in your customer's browser. The widget itself is a small script. H3: What happens to the photos customers upload? Body: They are encrypted in transit, processed to produce the render, and deleted. We do not retain them and we do not train on them. Rendream holds ISO 27001:2022. Link: "More on security" [/security] H3: Does it recommend a size? Body: Not online. AI size recommendation is a Smart Mirror feature. The online product is visual try-on. H3: Can I try it on my own products before paying? Body: Yes. The free plan runs on your real catalog. CTA: Install on Shopify CTA: See pricing D2Rewrite/virtual-try-on-shopify · ~1,150 words Shopify page, up from 327 words H1: Virtual try-on for your Shopify store Body: Add a try-on button to your product pages. Your customer uploads one photo, picks the items, and sees them rendered on their own body before they add to cart. Part of Link: "LookCheck virtual try-on software" [/virtual-try-on-software] Body: Free plan, 20 try-ons a month, no card required. CTA: Install on Shopify H2: Where Shopify stores lose the sale Body: You have spent money bringing someone to a product page. The photography is good, the description is complete, the size chart is accurate. They still leave, because none of it tells them how the piece will look on them specifically. Body: Baymard Institute puts average cart abandonment at 70.22% across fifty studies. NRF and Happy Returns estimate 19.3% of online sales came back in 2025. Fashion sees the sharp end of both, and size bracketing makes it worse: a customer who is unsure orders two or three variants intending to return most of them, which looks like a sale in your dashboard and costs you twice in logistics. Body: Both behaviours come from the same gap. Close the gap on the product page and you change what happens at the cart. H2: What your customer does H3: 1. Taps the try-on button Body: It sits on the product page, styled to your theme. Nothing loads until they ask for it. H3: 2. Uploads one photo Body: One clear picture showing their whole body, in a pose where the outline is visible. Higher resolution renders better. There is no guided capture sequence, no multi-step wizard, and no account to create on our side. H3: 3. Adds more items if they want the whole look Body: They can combine pieces from across your catalog and see the outfit together rather than one garment at a time. H3: 4. Gets the render Body: Photorealistic, in seconds, on their own body. Then they carry on shopping with the question answered. H2: What you do H3: 1. Install from the Shopify App Store Body: One click. No developer, no theme file access, no code. H3: 2. Let it read your catalog Body: The app syncs your products automatically and keeps up with changes. You do not prepare assets, upload 3D models or commission new photography. H3: 3. Match it to your theme Body: Set colours, fonts and button placement so the widget looks like part of your store rather than something bolted on. H3: 4. Publish Body: Most merchants are live in about five minutes. H2: Controls, because you are billed per render Body: Rendering costs real compute, so LookCheck charges per try-on rather than hiding the cost somewhere less visible. That makes usage controls part of the product rather than an afterthought. Body: Restrict try-on to logged-in customers. Restrict it to customers with a purchase history, so the feature works as a perk for people who already buy from you. Cap try-ons per person daily, weekly or monthly. Ask us for something more specific and we will configure it. Body: The result is a predictable monthly spend rather than a bill that moves with your traffic. H2: Every category you sell Body: Tops, bottoms, dresses, outerwear, footwear, eyewear, jewellery, bags and hats, all through the same widget and the same upload. See the category pages for Link: "shoes" [/virtual-try-on-shoes] Link: "glasses" [/virtual-try-on-eyewear] and Link: "jewellery and accessories" [/virtual-try-on-accessories] Body: If you sell unstitched fabric, LookCheck renders the finished garment from the cloth, which needs a short setup with our team first. Link: "Read about unstitched rendering" [/virtual-try-on-unstitched-fabric] H2: Getting your first real try-ons Body: Installing is not the same as being used, and the merchants who get value fastest do two things in the first week. Body: They put the button somewhere visible. Below the size selector works better than below the fold, because the try-on is what resolves the hesitation that the size selector creates. Body: They start with the products that carry the most doubt. Fitted pieces, anything where the drape is the selling point, anything a customer would normally order in two sizes. Those are where a render changes a decision, and the analytics will show you which of your products those are. H2: What it touches, and what it does not Body: The app reads your products and writes nothing back. It does not modify your theme files, does not change your checkout, and does not sit in the critical path of a purchase. If LookCheck is unavailable, the try-on button does not appear and the rest of your store carries on exactly as normal. Body: Uninstalling removes the widget and leaves your catalog untouched, because there was never a second copy of it. H2: Built for the Shopify stack Body: The app is native to Shopify, so it follows your theme, uses your product data as the source of truth, and does not ask you to maintain a second catalog. Rendering runs on our infrastructure, which means the work happens off your storefront and your page weight barely moves. Body: Analytics show which products get tried on and how often, so you can see which parts of your catalog carry the most hesitation. That is usually a more useful signal than it first appears, because the products people render most are often the ones your photography serves worst. H2: Questions merchants ask H3: How long does setup take? Body: Most merchants install, sync and go live in under five minutes. H3: Do I need product photos in a special format? Body: No. The app works from your existing catalog images. H3: Will it slow my store down? Body: Rendering happens on our servers, not in your customer's browser. The widget is a small script and nothing loads until a customer asks for a try-on. H3: What happens to the photos customers upload? Body: Encrypted in transit, processed to produce the render, then deleted. We do not retain them and we do not train on them. Rendream holds ISO 27001:2022. Link: "More on security" [/security] H3: Does it recommend a size? Body: No. The Shopify app is visual try-on. AI size recommendation is a Link: "Smart Mirror" [/mirror] feature. H3: What does it cost? Body: Free for 20 try-ons a month. Paid plans start at $54. Link: "Full pricing" [/pricing] CTA: Install on Shopify CTA: See pricing Removed, and why The title's "& AI Sizing", the description's "sub-inch AI sizing", the H3 "Sub-Inch AI Sizing", and the body line "With just two photos and their height, LookCheck calculates body measurements with an error margin of less than one inch". The Shopify app does none of this. The FAQ now answers the sizing question directly instead, which is better for the merchant and better for an answer engine reading the page. Screenshots are specified separately in D5 so they do not sit inside the copy a developer pastes. D3Rewrite/virtual-try-on-woocommerce · ~1,050 words WooCommerce page, up from 263 words H1: Virtual try-on for WooCommerce Body: A WordPress plugin that adds photorealistic try-on to your product pages, with rendering handled off-site so your storefront stays fast. Part of Link: "LookCheck virtual try-on software" [/virtual-try-on-software] CTA: Install the WooCommerce plugin H2: The WooCommerce problem is a weight problem Body: Fashion stores lose sales on the product page for the same reason everywhere: a shopper cannot tell how the piece will look on them. Baymard Institute puts average cart abandonment at 70.22% across fifty studies, and NRF with Happy Returns estimate 19.3% of online sales were returned in 2025. Body: On WooCommerce there is a second problem stacked on the first. A typical store runs a long list of plugins, and every one adds weight to pages that are already slower than a hosted platform's. So the honest objection to any new plugin is not whether it works, it is what it costs you in load time. H2: How LookCheck answers that H3: Rendering happens on our infrastructure Body: The plugin sends a request and receives a finished image. Your server is not doing the computing, your database is not storing renders, and your page weight barely moves. The widget itself is a small script that loads nothing until a customer asks for a try-on. H3: It works with your theme, not against it Body: The widget inherits your existing styles and can be placed with a shortcode or a block. It does not assume a particular theme structure or template hierarchy, which is where try-on plugins usually break on WordPress. H3: Your catalog stays yours Body: Products stay in your WooCommerce install. We read what a render needs and nothing else. There is no second catalog to maintain and no export step, and if you remove the plugin your store is exactly as it was. H2: What your customer does H3: 1. Taps the try-on button Body: Placed wherever you put the shortcode or block, styled to your theme. H3: 2. Uploads one photo Body: One clear full-body picture. No guided capture, no app, no account with us. H3: 3. Adds more items for a full look Body: Pieces combine across your catalog into a single render. H3: 4. Gets the render Body: Photorealistic, in seconds, on their own body. H2: What you do H3: 1. Install the plugin Body: From the WordPress plugin directory, the same way as anything else. H3: 2. Connect your catalog Body: The plugin reads your existing WooCommerce products. H3: 3. Place the widget Body: Shortcode or block, wherever it belongs in your template. H3: 4. Match your styles Body: Colours and fonts follow your theme. H2: Controls, because you are billed per render Body: Restrict try-on to logged-in customers, or to customers with a purchase history. Cap try-ons per person daily, weekly or monthly. Rendering is billed per use, so these controls are what keep a busy month predictable. H2: Every category you sell Body: Tops, bottoms, dresses, outerwear, footwear, eyewear, jewellery, bags and hats, through one widget. Link: "Unstitched fabric" [/virtual-try-on-unstitched-fabric] renders too, and needs a short setup with our team first because the mapping depends on how your pieces are cut and stitched. H2: Multisite, translation and the usual WordPress complications Body: A WooCommerce store is rarely just a WooCommerce store. Body: The widget follows whatever locale your site is serving, so a translated store shows translated interface text. On multisite, each site connects separately, which keeps catalogs and usage counts distinct rather than pooling them in a way that would make your billing impossible to reconcile. Body: If you run a page builder, the widget places as a block or shortcode inside it like any other element. It does not require a specific builder and it does not fight one. H2: What happens on update Body: Plugin updates follow the normal WordPress process. Because rendering runs on our side, an update to the plugin is a small change to a small script rather than a migration, and your existing renders and settings persist across it. Body: If you ever remove the plugin, your catalog is exactly as it was. There is no data to export and nothing to unpick, because we never held a copy of it. H2: Open source, and what that means here Body: You are running WooCommerce presumably because you wanted control over your own stack. LookCheck does not take that back. There is no lock-in on your product data, no proprietary format, and no requirement to move anything into our system. What we provide is the rendering, which is the one part you would not want to run yourself. H2: Questions merchants ask H3: Which WordPress and WooCommerce versions are supported? Body: We test against current releases. The tested-up-to version is shown on our WordPress.org listing and we keep it current. H3: Do I need to change my theme? Body: No. Place the widget with a shortcode or a block. H3: Does it slow the site down? Body: Rendering is remote. The plugin adds a small script and loads nothing until a customer starts a try-on. H3: What happens to the photos customers upload? Body: Encrypted in transit, processed, then deleted. We do not retain them. Rendream holds ISO 27001:2022. Link: "More on security" [/security] H3: Does it recommend a size? Body: No. The plugin is visual try-on. AI size recommendation is a Link: "Smart Mirror" [/mirror] feature. H3: What does it cost? Body: Free for 20 try-ons a month, then from $54. Link: "Full pricing" [/pricing] CTA: Install the WooCommerce plugin CTA: See pricing Ship the compatibility release with this page The WordPress.org listing currently shows the "not tested with the latest 3 releases" warning, which suppresses installs. This page will send traffic there. The FAQ answer is written so it never needs updating, but the warning itself still needs clearing. D4Rewrite/virtual-try-on-salla · ~1,050 words Salla page, up from 290 words H1: Virtual try-on for Salla merchants Body: Let your customers see the garment on themselves before they place the order. Native Salla app, installs in minutes. Part of Link: "LookCheck virtual try-on software" [/virtual-try-on-software] CTA: Install on Salla H2: Cash on delivery changes the maths Body: Across the Gulf, a large share of fashion orders are paid on delivery. That is convenient for the customer and expensive for you, because it moves the entire cost of an uncertain purchase onto the merchant. Body: A customer who is not sure still places the order. The decision gets deferred to the doorstep, where refusing costs them nothing and costs you the outbound shipping, the return leg, the restocking, and the sale. Body: On a prepaid order an uncertain customer at least pays first. On COD they do not, which is why the same hesitation that produces an abandoned cart elsewhere produces a refused parcel here. H2: The decision happens on the product page Body: The doorstep is where the refusal lands, but it is not where it starts. It starts when a shopper looks at a product photo on a model who is not them and cannot picture the piece on their own body, so they order half-committed. Body: Baymard Institute puts average cart abandonment at 70.22% across fifty studies, and NRF with Happy Returns estimate 19.3% of online sales were returned in 2025. Those figures describe the same underlying hesitation that COD converts into a doorstep refusal. Body: Virtual try-on moves that moment forward. The customer sees the garment on themselves before ordering, so the order they place is one they actually want, and the parcel that arrives is one they are expecting to keep. H2: What your customer does H3: 1. Taps the try-on button Body: On your Salla product page, styled to your store. H3: 2. Uploads one photo Body: One clear full-body picture. No guided capture, no app download, no account with us. H3: 3. Adds more items for the full look Body: Pieces combine across your catalog into one render. H3: 4. Gets the render Body: Photorealistic, in seconds, on their own body. H2: What you do H3: 1. Install the Salla app Body: Native to the platform, from the Salla app store. H3: 2. Let it read your catalog Body: Your products sync automatically. H3: 3. Match it to your store Body: Colours, fonts and placement follow your existing design. H3: 4. Publish Body: Most merchants are live in minutes. H2: Built for how the region actually dresses Body: Modest fashion, abayas, kaftans, layered pieces and full-length dresses render correctly. The engine handles length and layering rather than assuming a cropped Western silhouette, which is where try-on tools built for other markets tend to fall apart on exactly the pieces that matter most to a Gulf catalog. Body: Men's thobes and formal wear render the same way, and accessories, footwear and eyewear are covered by the same widget. H2: Arabic storefronts Body: The widget follows your store's language and layout direction, so an Arabic storefront gets Arabic interface text and a right-to-left layout rather than a left-to-right widget bolted into an Arabic page. Body: Product names and descriptions come from your catalog, so whatever language you have entered them in is what the customer sees. H2: Seasonal peaks Body: Gulf retail is concentrated. Ramadan, Eid and the wedding season put months of volume into weeks, and those are exactly the weeks when a refused delivery hurts most, because the item was bought for a date that has now passed and the return is a total loss rather than a restock. Body: Two things matter in those weeks. Rendering has to stay responsive under load, which it does because the work happens on our infrastructure rather than yours. And your spend has to stay predictable, which is what the usage controls are for. H2: Controls, because you are billed per render Body: Restrict try-on to logged-in customers, or to customers with a purchase history. Cap try-ons per person daily, weekly or monthly. Rendering is billed per use, so these keep your spend predictable through a busy season, when traffic can multiply without warning. H2: Fewer exchanges, not just fewer refusals Body: The refused parcel is the visible cost. The exchange is the quieter one. Body: A customer who accepts delivery and then wants a different size costs you a collection, an outbound leg, and the staff time in between, on an order you had already counted. Across a season that adds up to more than the refusals do, and it comes from the same place: a decision made without enough information. Body: Showing the garment on the customer before they order moves that decision to the point where changing it is free for everybody. H2: Questions merchants ask H3: How long does setup take? Body: Most merchants install, sync and go live in minutes. H3: Does it work with Arabic storefronts? Body: Yes. The widget follows your store's language and layout direction. H3: What happens to the photos customers upload? Body: Encrypted in transit, processed, then deleted. We do not retain them. Rendream holds ISO 27001:2022. Link: "More on security" [/security] H3: Does it recommend a size? Body: No. The Salla app is visual try-on. AI size recommendation is a Link: "Smart Mirror" [/mirror] feature. H3: Can I try it before paying? Body: Yes. The free plan gives you 20 try-ons a month on your real catalog. H3: What does it cost? Body: Free for 20 try-ons a month, then from $54. Link: "Full pricing" [/pricing] CTA: Install on Salla CTA: See pricing Two notes Removed: the description's "sub-inch sizing" and the H3 "Sub-Inch Sizing Precision". Salla is the online product. The Arabic answer needs checking. I have written that the widget follows store language and layout direction. Confirm right-to-left rendering actually works before publishing, and cut the answer if it does not. An Arabic version of this whole page at /ar/virtual-try-on-salla is the highest-value translation on the site, since Salla merchants search in Arabic and no competitor is serving them well. D5Asset specNot page copy Screenshots for the platform pages Four per platform page, placed in the "What you do" section. Captions and alt text are written here so design supplies images only. This lives outside the copy blocks deliberately, because in v1 it sat inside the text a developer would paste. #ShowsCaptionAlt text 1Widget live on a product pageThe try-on button on a live product page.LookCheck try-on button on a [platform] product page 2Admin view after installYour dashboard right after install.LookCheck admin dashboard inside [platform] 3Catalog sync runningCatalog sync, which runs on its own.LookCheck syncing a [platform] product catalog 4Theme matching panelMatching the widget to your theme.LookCheck widget styling matched to a store theme E Category pages Four search categories the site does not currently compete in at all, plus the one nobody else can compete in. E1New/virtual-try-on-unstitched-fabric · ~1,250 words The unstitched pillar H1: Virtual try-on for unstitched fabric Body: Show a customer the finished suit before a single cut is made. LookCheck renders a complete garment from a length of unstitched cloth, on the body of the person considering it. CTA: Talk to us about unstitched fabric H2: Selling cloth online is a harder problem than selling clothes Body: An unstitched three-piece is three flat rectangles in a photograph. In a shop, a customer holds the fabric against themselves, feels the weight, drapes a corner over an arm, and builds a picture of the finished piece. That entire process is missing online. Body: What they get instead is a flat lay and a colour swatch, and they are asked to spend real money on an act of imagination. The better your cloth, the worse this serves you, because the things that justify the price, the fall, the weight, the way it catches light, are exactly the things a flat photograph cannot show. Body: Every other virtual try-on tool on the market maps a photographed garment onto a body. Here there is no garment to map. That is the technical reason this category has been left alone, and it is why a customer shopping for unstitched cloth online is still guessing. H2: What LookCheck does instead Body: The engine renders the finished garment from the fabric itself, accounting for how that particular cloth behaves. Lawn hangs differently from khaddar. Chiffon behaves differently again. Heavier suiting holds a line that a summer cotton will not. Body: The result is not a generic silhouette in your colourway. It is a render of a finished shalwar kameez, kurta or three-piece, made from the cloth you are actually selling, on the body of the person deciding whether to buy it, from one photo they upload. H2: Who this is for H3: Unstitched and pret retailers Body: Brands in Pakistan and across South Asia selling lawn, khaddar, linen and chiffon by the suit. The category where the gap between what the customer sees and what they receive is widest. H3: Fabric houses selling online Body: Businesses whose product has always been sold by touch, now selling to customers who cannot touch it. H3: Menswear brands selling suiting cloth Body: Where the customer is choosing cloth and cut together, and the finished garment is the only thing they actually care about. H3: Anyone whose product becomes a garment after the sale Body: If what you ship is material rather than clothing, this is the problem you have. H2: Why it needs a conversation first Body: Unstitched rendering is not a self-serve install, and we would rather say so than have you find out after signing up. Body: The mapping from cloth to finished garment depends on how your pieces are cut and stitched, which varies by brand, by region and sometimes by collection. Getting that right takes a short setup with our team. A merchant who installs the app and tries unstitched cold will get a poor result and reasonably conclude the product does not work. Body: So the route in is a conversation. Tell us what you sell, send us a few pieces of cloth from your catalog, and we will show you a render of your own fabric before you commit to anything. H2: What the setup conversation actually involves Body: Worth being specific, because "talk to us first" can sound like a sales gate and this is not one. Body: We need to understand how your pieces are cut. An unstitched suit becomes a different garment in different hands, and the regional conventions for a kameez length, a sleeve, a trouser cut vary enough to matter. We ask what you actually offer. Body: We need samples of the cloth types in your catalog. Lawn, khaddar, chiffon, linen and heavier suiting behave differently enough that the engine is calibrated against real examples rather than assumed. Body: Then we render your own fabric and show you the result before you commit to anything. If it is not good enough, that is a useful answer and it costs you a conversation. H2: Fabrics we render Body: Lawn, which falls light and moves, and where the print carries most of the value. Body: Khaddar, heavier and with more texture, where the weave should read in the render rather than flattening out. Body: Chiffon and georgette, where the drape and the transparency are the product. Body: Linen and cotton, everyday weights across the widest range of cuts. Body: Suiting cloth, where the line the fabric holds is the difference between a good jacket and a poor one. H2: The rest of your catalog works the same way Body: Most unstitched retailers also sell pret, accessories and footwear. All of it renders through the same widget once you are set up, so this is not a separate tool bolted onto your store. Link: "See what LookCheck does across categories" [/virtual-try-on-software] H2: Why this category has been left alone Body: Virtual try-on has been built, almost without exception, for Western ready-to-wear. The technical assumption underneath every one of those tools is that a garment exists and has been photographed, and the job is to place it on a body. Body: Unstitched breaks that assumption at the first step. It is a harder problem and a smaller market in the places where most of these tools were built, so nobody solved it. Body: The market is not small where you are selling. It is the default way a very large number of people buy clothes, and it has been served online by flat lays and hope. H2: Running now Body: Mushq runs LookCheck across their online storefront and in store, including unstitched rendering. Link: "Read the Mushq story" [/case-studies/mushq] H2: Questions merchants ask H3: What do you need from me to set this up? Body: A conversation about how your pieces are cut, and a sample of the cloth types in your catalog. We do the rest. H3: How long does setup take? Body: Longer than the five minutes a standard install takes, and we will give you a realistic timeline once we have seen your catalog. We would rather quote it accurately than optimistically. H3: Does this work for men's suiting as well as women's? Body: Yes. Shalwar kameez, kurtas, three-piece suits and suiting cloth all render. H3: Can my customers see the fabric in different cuts? Body: That is the point of it. The same cloth rendered as the finished pieces you actually offer. H3: What happens to the photos customers upload? Body: Encrypted in transit, processed, then deleted. We do not retain them. Rendream holds ISO 27001:2022. Link: "More on security" [/security] H3: Can I just install the app and try it? Body: You can install LookCheck and use it for your stitched catalog immediately. Unstitched specifically needs the setup conversation first, for the reasons above. CTA: Talk to us about unstitched fabric Why this page never says "install" Every other online page pushes the self-serve install. This one must not, and the copy explains why in the page itself rather than just routing differently. A merchant who understands the reason will book the call. A merchant who is told nothing and installs cold will churn. E2New3 pages · ~450 words each Shoes, eyewear, accessories Same shape on each: H1, intro, the category's specific problem, what the render shows, how it fits the wider catalog, three FAQs, CTA. Roughly 450 words gives each page enough to stand on without padding. === /virtual-try-on-shoes === H1: Virtual try-on for shoes Body: Sneakers, heels, boots and formal shoes, rendered on your customer's own feet from one photo they upload. No AR app, no foot scan, no special hardware. CTA: Install on Shopify H2: Footwear has a styling problem, not just a fit problem Body: A shoe on a white background tells a customer nothing about whether it works with what they own. Height, proportion and how the shoe sits against a leg are all invisible in a product shot, and they are most of the decision. H2: What the render shows Body: The shoe on the customer's own feet, in proportion, in the context of what they are wearing. If they render it alongside trousers or a dress from your catalog, they see the combination rather than the object. H2: Part of the same widget Body: If you sell clothing as well, shoes combine into the same outfit render. One installation covers your whole catalog. Link: "See LookCheck across categories" [/virtual-try-on-software] H2: Questions merchants ask H3: Does the customer need a special photo of their feet? Body: No. The same full-body photo the rest of LookCheck uses. H3: Does it size the shoe? Body: No. This is visual try-on. AI size recommendation is a Link: "Smart Mirror" [/mirror] feature. H3: What does it cost? Body: Free for 20 try-ons a month, then from $54. Link: "Full pricing" [/pricing] CTA: Install on Shopify === /virtual-try-on-eyewear === H1: Virtual try-on for glasses and sunglasses Body: Frames rendered on your customer's own face, from one uploaded photo. No AR session, no camera permission prompt, no app to download. CTA: Install on Shopify H2: Frames are bought on the face, not the shelf Body: How a frame sits against someone's features is the thing they are actually judging, and a product photo on a model with a different face cannot help them. It is the category where the gap between the listing and the decision is widest. H2: What the render shows Body: The frames on their own face, in proportion, from the photo they already have on their phone. No live camera session to trigger, which also means it works for customers who will not grant camera access. H2: Part of the same widget Body: Eyewear renders alongside the rest of your catalog. If you sell clothing too, a customer can see frames with an outfit. Link: "See LookCheck across categories" [/virtual-try-on-software] H2: Questions merchants ask H3: Do I need a 3D model of each frame? Body: No. LookCheck works from your existing product images. H3: Does it measure pupillary distance or face width? Body: No. This is visual try-on, not optical measurement. H3: What does it cost? Body: Free for 20 try-ons a month, then from $54. Link: "Full pricing" [/pricing] CTA: Install on Shopify === /virtual-try-on-accessories === H1: Virtual try-on for jewellery and accessories Body: Necklaces, earrings, bags, hats and scarves shown on real people, from one uploaded photo. CTA: Install on Shopify H2: Accessory brands get left with flat product shots Body: Most try-on tools stop at clothing, so if you sell accessories you have been left out of the category entirely. Scale is the specific problem: a necklace photographed alone gives no sense of how it sits, and a bag on a plain background gives no sense of size. H2: What the render shows Body: The piece on the customer, at the right scale, in proportion to them. A bag against a body reads as a size. A necklace at a neckline reads as a length. H2: Part of the same widget Body: Accessories combine with clothing in a single render, so a customer can finish a look rather than judging one piece at a time. Link: "See LookCheck across categories" [/virtual-try-on-software] H2: Questions merchants ask H3: Does this cover bags and hats as well as jewellery? Body: Yes. Necklaces, earrings, bags, hats and scarves. H3: Do I need new photography? Body: No. Your existing catalog images are enough. H3: What does it cost? Body: Free for 20 try-ons a month, then from $54. Link: "Full pricing" [/pricing] CTA: Install on Shopify Each page needs its own demo assets At least three rendered examples per category. A page claiming eyewear support while showing only garments is not credible, and it is the first thing a merchant in that category will check. Design brief DES-10. E3New/virtual-try-on-api · ~550 words API and custom integrations H1: Virtual try-on API and custom integrations Body: Not on Shopify, WooCommerce or Salla? The same engine is available over an API, and we build custom integrations for teams running their own stack. CTA: Talk to us about an integration H2: What you control Body: You send a product image and a customer photo. You get a rendered result back. The interface, the caching, where the images live and how try-on appears in your storefront are all yours. We handle the rendering, which is the part you would not want to run yourself. H2: Who this is for H3: Retailers on Magento, BigCommerce or a bespoke platform Body: Anywhere there is no native LookCheck app, the API covers the same capability. H3: Marketplaces Body: Running try-on across many sellers, where each seller's catalog is separate but the rendering is shared. H3: Retail groups with an in-house team Body: Where the storefront is built and maintained internally and a third-party widget is not an option. H2: How it works in practice Body: Tell us what you are building and what your stack looks like. We scope the integration, give your team what they need to build against it, and stay involved through launch. Body: Volume pricing is matched to your expected render count rather than a fixed plan, because an API customer's usage pattern rarely fits the tiers built for app installs. H2: What the API does and does not do Body: It renders. Garments, footwear, eyewear, jewellery, bags and hats, on a customer photo, including whole outfits in one call. Body: It does not recommend sizes. AI size recommendation is a Link: "Smart Mirror" [/mirror] feature and is not part of the online product in any form, including the API. Body: Unstitched fabric rendering is available and, as with the apps, needs a setup conversation first because the mapping depends on how your pieces are cut. Link: "More on unstitched" [/virtual-try-on-unstitched-fabric] H2: Questions teams ask H3: Is there public documentation? Body: Not yet. We scope each integration with the team building it, and provide what your developers need directly. H3: What are the rate limits? Body: Set per integration against your expected volume. Tell us what you are planning for and we will be specific. H3: What happens to the photos? Body: Encrypted in transit, processed, deleted. We do not retain them and we do not train on them. Rendream holds ISO 27001:2022. Link: "More on security" [/security] CTA: Talk to us about an integration Deliberately no endpoint documentation The page describes the capability and routes to a conversation, because that is how API access actually works today. Publishing parameter tables for something a developer cannot self-serve creates a worse first impression than the honest version. If a public sandbox with self-serve keys ships later, this page gains a docs link and the CTA becomes "Get an API key". The homepage "View Developer Docs" button, which currently points at the WooCommerce page, repoints here. F Smart mirror Two pages with a clean division of labour. /mirror is the argument. /mirror/specifications is the reference sheet. In v1 they were 58% the same text, which would have had them competing with each other. F1Rewrite/mirror · ~1,200 words The mirror page H1: The fitting room, without the queue Body: The LookCheck AI Smart Mirror is a 4K display for your shop floor. A customer stands in front of it and sees themselves in garments they have not taken off the rail. Body: This is also the one place AI size recommendation lives. The mirror captures a front and side view, asks for height, and recommends a size accurate to under an inch. The online product does not do this. CTA: Book a mirror walkthrough H2: The fitting room is where in-store sales are lost Body: A customer picks up three items, queues, tries them, and finds two are wrong. Now they either queue again with different sizes or they leave with one item instead of three. Most leave. Body: The trip itself is the cost. It takes time, it takes staff attention to fetch alternatives, and every additional round makes the customer likelier to abandon the whole thing. Meanwhile the fitting room is a bottleneck at exactly the hours you most need throughput. Body: A mirror on the floor moves that filtering earlier. The pieces that are obviously wrong get ruled out before anyone queues, and the pieces worth trying properly are the ones that make it into the room. H2: What it does on the floor H3: Try before the fitting room Body: Scan an item or select it on screen and see it rendered on yourself. If the cut or colour is obviously wrong, that is a trip nobody made and a fitting room slot freed for someone else. H3: Size recommendation Body: Under an inch of error, from two captures and a height. No tape measure, no staff time spent guessing, and no reliance on the customer knowing their size in your particular brand. H3: Other sizes and colours, instantly Body: The size that is out of stock on the floor, the colourway that only exists online. Visible immediately, without anyone walking to the stockroom, which turns a lost sale into an order. H3: Whole outfits from your catalog Body: Complete looks rather than single items. A customer who came for a shirt sees it with trousers and a jacket, which is where basket size moves. H3: Assisted shopping without leaving the room Body: Customers request a different size or call for help from the mirror itself. Staff get the notification with the item and size already attached, so nobody is hunting for what was meant. H3: Checkout at the mirror Body: An integrated payment terminal means the customer can pay where they are standing. They can also send the render to their phone, which is how a good in-store moment travels. H2: What we need from your store Body: Less than most in-store technology asks for. H3: A power point Body: Standard 220v mains. H3: A network connection Body: Wifi works. Ethernet is better and we recommend it, because rendering is a network round trip and a wired connection stays consistent through your busiest trading hours, which is precisely when you do not want it hesitating. H3: A POS we can talk to Body: The mirror connects to your existing point of sale rather than running beside it, so staff notifications, inventory updates and completed sales all flow into the system you already use. Body: Everything else, including installation, is ours. Link: "Full specifications" [/mirror/specifications] H2: What your staff do differently Body: Almost nothing, which is the point. Body: The mirror handles the customer directly. Where it needs staff, it tells them specifically: a request for a size arrives with the item and the size already attached, so nobody is walking the floor trying to work out what was meant. Body: The one habit worth building is pointing customers at it. A mirror nobody is shown is a screen on a wall, and the stores that get the most from it are the ones where staff introduce it as part of how they help rather than treating it as furniture. H2: The floor space argument Body: A mirror occupies floor space, and floor space is the scarcest thing in a store, so the question is what it displaces. Body: The honest answer is that it pays for itself against the fitting room queue rather than against the rail it replaces. Every trip it prevents frees a fitting room slot at your busiest hour, and every size it shows without a stockroom walk is staff time returned to the floor. Body: If your fitting rooms are never busy, this is a weaker case and we would rather say so. H2: Where it fits in your stack Body: The mirror reads the same catalog as your online store, so a customer sees consistent product information on the floor and on their phone. If you also run Link: "LookCheck online" [/virtual-try-on-software] the two share an engine and your analytics cover both, which means you can see which products create hesitation wherever it happens. H2: Running now Body: Breakout has LookCheck AI Smart Mirrors in store in Pakistan. Mushq runs the mirror in store alongside Link: "LookCheck online" [/case-studies/mushq] H2: Questions retailers ask H3: How accurate is the size recommendation? Body: Under an inch of error, from a front capture, a side capture and the customer's height. H3: Does the customer need to undress? Body: No. The capture is taken as they stand, fully clothed, in front of the mirror. H3: What happens to the images? Body: Encrypted, processed to produce the render and the measurement, then deleted. Rendream holds ISO 27001:2022. Link: "More on security" [/security] H3: Which POS systems do you integrate with? Body: Tell us what you run and we will confirm. POS integration is scoped per deployment. H3: How is it priced? Body: Per deployment, because it depends on screen count, store layout, installation and POS integration. Tell us about your stores and we will scope it. H3: Can I see one working before committing? Body: Yes. That is what the walkthrough is for. CTA: Book a mirror walkthrough This fixes the section Rameel flagged v1 had a heading reading "What it needs from you" followed by a list of product specifications, which is the opposite of what the heading promises, plus a dangling "Full specifications." sentence with nothing attached. The section now lists what the retailer actually supplies, which is three things, and the specifications live on their own page with a real link to them. Also fix in the build: the H1 currently renders as only the two words "The Future of" to a crawler because the rest animates in. Two H2s on the page are empty strings and one heading block is duplicated. See ENG-21. F2New/mirror/specifications · ~600 words Specifications, and nothing that belongs on the mirror page This page is a reference sheet a buyer sends to whoever signs off on it. It repeats none of the argument from /mirror. H1: Smart Mirror specifications Body: Everything a store operations or IT team needs before approving a LookCheck AI Smart Mirror deployment. Link: "What the mirror does" [/mirror] H2: Display H3: Unit sizes Body: Two options, 6 foot and 7 foot. H3: Screen Body: 55 inch on the 6 foot unit, 65 inch on the 7 foot unit. 4K Ultra HD. H2: Camera Body: 4K Ultra HD, used for the guided front and side capture that produces the render and the size recommendation. H2: Scanning Body: Integrated barcode scanner. A customer or a staff member scans an item and it appears on the mirror immediately, with no search step and no typing. H2: Payment Body: Integrated POS payment terminal, so a customer can complete the purchase at the mirror rather than walking to a till. H2: Connectivity Body: Wifi and Ethernet both supported. Body: We recommend Ethernet. Rendering is a network round trip, and a wired connection keeps response times consistent during peak trading hours. H2: Power Body: Standard 220v mains supply. H2: POS integration Body: The mirror connects to your existing point of sale rather than operating as a separate system. That covers: Body: Staff notifications when a customer requests a size or asks for help, with the item and size attached. Body: Inventory updates, so what the mirror offers reflects what you actually hold. Body: Completed sales pushed into your system, so mirror transactions appear alongside everything else. Body: Which systems we integrate with is confirmed per deployment. Tell us what you run. H2: Catalog Body: The mirror reads your product catalog, the same source your online store uses where LookCheck runs online as well. No separate catalog to maintain. H2: Data handling Body: Capture images are encrypted, processed to produce the render and the measurement, then deleted. They are not retained and not used for training. Rendream holds ISO 27001:2022. Link: "Full security detail" [/security] H2: Installation Body: Installation is handled by the Rendream team. Scoping covers placement, power and network access, and POS connection. H2: Scoping a deployment Body: Tell us how many stores, your floor layout and which POS you run, and we will come back with a specification and a price for your sites. CTA: Book a mirror walkthrough Two things to add when you have them Qualify the 220v figure if you sell into North America or Japan. A US retailer reading 220v with no qualification will assume the product does not fit their stores, and that is a silent disqualification you will never hear about. Either state the supported range or write "mains supply, specified per region". Mounting, floor clearance, install lead time and support model are not on this page because they were not confirmed. The page reads complete without them and nothing is a placeholder, but these are the next four questions a retail operations team will ask, so add them when they are settled. Trust pages H1New/security · ~520 words Security and data handling H1: Security and data handling Body: Every merchant evaluating try-on asks the same question first. What happens to my customers' photos? Here is the complete answer. H2: What happens to a shopper's photo Body: It is encrypted in transit, processed to generate the render, and then deleted. Body: We do not retain it. We do not train models on it. If you asked us for a copy tomorrow, we would not have one to give you. H2: What we do store Body: The rendered output for as long as the session needs it, and usage counts for billing. Not the source photo. H2: Certification Body: Rendream holds ISO 27001:2022. H2: Who controls what Body: You are the data controller for your customers. We are the processor, acting on your instruction. The Link: "privacy policy" [/privacy-policy] sets out the detail. H2: The Smart Mirror Body: The same rule applies in store. The mirror's capture images are encrypted, processed to produce the render and the measurement, then deleted. Nothing is kept on the device. H2: Why zero retention is a design choice, not a policy Body: A policy can change. An architecture is harder to walk back, which is why this is worth understanding rather than just believing. Body: The render pipeline produces an output and discards the input. There is no photo store to secure, no retention schedule to enforce, no deletion request to process, and no archive that could be compromised later. The safest way to hold customer photos is not to hold them. Body: The practical effect for you is that a question about customer images has a short answer, and a request from one of your customers to delete their photo is already satisfied. H2: Questions procurement teams ask H3: Do you train models on our customers' images? Body: No. Images produce the render that was requested and are then deleted. H3: Where is processing done, and can we get a data processing agreement? Body: Both are handled per deployment. Tell us your requirements and we will send our current documentation before you commit to anything. H3: What is your incident response process? Body: Covered by Rendream's ISO 27001:2022 certification. We will walk your team through it on request. H3: Does the widget affect our own compliance posture? Body: The widget runs on your storefront but the processing runs on ours, so the photo does not rest in your systems either. Bring us your specific requirements and we will answer against them rather than in general terms. H3: Who do we contact? Body: Start at the Link: "contact page" [/contact] and mark your message as a security review. It reaches the team that can answer it rather than sales. CTA: Talk to us Wording that is already cleared "Images are encrypted, processed and deleted" is confirmed accurate and approved for use as written. Do not add a bare "GDPR compliant" claim, which is what llms.txt currently asserts without qualification. H2New/faq · ~700 words FAQ, the home for eleven questions currently in schema and rendered nowhere The site's FAQPage markup declares sixteen questions and renders five. Eleven are good content that exists only in markup. They belong here, grouped, with four additions the site does not answer anywhere. H1: Frequently asked questions H2: The basics H3: What is virtual try-on? Body: Software that renders a garment on a shopper's own photo so they can see how it looks on them before buying, rather than judging it from a product shot on a model. H3: How does LookCheck work? Body: Your customer uploads one photo on your product page, selects items, and the engine renders those items on their body in seconds. On the Smart Mirror the capture is guided and happens in store. H3: What kind of photo does a customer need to upload? Body: One clear picture showing their whole body, in a pose where the outline is visible. Higher resolution renders better. There is no guided capture sequence and no multi-step wizard online. H3: Can customers try on more than one item at once? Body: Yes. The mix-and-match engine combines tops, bottoms, shoes and accessories into a single render of the complete look. H2: Sizing H3: Does the online widget recommend a size? Body: No. Online is visual try-on. AI size recommendation is a Link: "Smart Mirror" [/mirror] feature. H3: How accurate is the Smart Mirror's size recommendation? Body: Under an inch of error, from a front capture, a side capture and the customer's height. H2: Setting it up H3: How long does setup take? Body: Most merchants install, sync their catalog and go live in under five minutes. H3: Do I need 3D models or new photography? Body: No. LookCheck works from your existing catalog images. H3: Which platforms do you support? Body: Native apps for Link: "Shopify" [/virtual-try-on-shopify] and Link: "Salla" [/virtual-try-on-salla] a plugin for Link: "WooCommerce and WordPress" [/virtual-try-on-woocommerce] and an Link: "API" [/virtual-try-on-api] for custom storefronts. H3: Will it slow my store down? Body: Rendering runs on our infrastructure, not in your customer's browser. The widget is a small script and loads nothing until a try-on starts. H3: What if I sell unstitched fabric? Body: LookCheck renders it, and it needs a short setup with our team first because the mapping depends on how your pieces are cut. Link: "More on unstitched" [/virtual-try-on-unstitched-fabric] H2: Cost H3: Can I try it on my own products before paying? Body: Yes. The free plan gives you 20 try-ons a month on your real catalog, with no card. H3: What does it cost? Body: Free for 20 try-ons a month. Paid plans from $54. Link: "Full pricing" [/pricing] H3: What counts as one try-on? Body: One render. Swapping an item and rendering again counts as a second. H2: Privacy H3: What happens to the photos customers upload? Body: Encrypted in transit, processed, then deleted. We do not retain them and we do not train on them. Rendream holds ISO 27001:2022. Link: "Security and data handling" [/security] H2: How LookCheck compares H3: How is this different from a standard try-on plugin? Body: Category coverage and outfit building. Most tools handle tops. LookCheck renders tops, bottoms, dresses, outerwear, footwear, eyewear, jewellery, bags and hats, and combines them into one look. It also renders unstitched fabric, which is a different technical problem. H3: How is this different from an open-source demo? Body: Research demos render one image at a time with no hosting, no catalog integration, no usage controls and no support. LookCheck is the production version of that idea, with the parts a retailer actually needs around it. H3: Is the quality good enough for luxury? Body: That is a judgement for you to make rather than a claim for us. Render your own pieces on the free plan, including the difficult fabrics, and decide from the output. Link: "Try the live demo" [/demo] H3New/press · ~250 words + list Press and media H1: Press and media Body: Coverage of LookCheck AI, plus everything a journalist or partner needs to write about us accurately. H2: In the press Body: [LIST: one row per piece. Publication, headline as a link to the article, date, one-line summary. Newest first.] H2: Boilerplate Body: Use this wording as written. "LookCheck AI is a virtual try-on platform for fashion retail, built by Rendream. It renders garments, footwear and accessories on a shopper's own photo online, and runs AI Smart Mirrors in physical stores. LookCheck is live with brands including Alex Rose in London, Siiine in the UAE, and Mushq, Narkin's and Breakout in Pakistan. Rendream is ISO 27001:2022 certified. lookcheck.rendream.com" H2: Assets Body: Logos in light and dark, product photography, Smart Mirror images, and founder headshots. [LINK: media kit download] H2: Enquiries Body: Press enquiries go through the Link: "contact page" [/contact] marked as press. Two rules for whoever maintains this Ask every outlet to link to lookcheck.rendream.com, not rendream.com. The parent domain currently passes almost nothing, so a link to the wrong domain is close to a wasted mention. Send the boilerplate with every outreach email. Identical wording across publications is what lets a search engine and an answer engine resolve the mentions to one company rather than several. The Featured On strip on the homepage pulls from this page. I Case studies Five studies, each on its own URL, replacing three anonymous ones headed "Case A", "Case B" and "Case C". Every study follows the same four-part shape so they read as a set. I1Rewrite/case-studies The index page H1: Case studies Body: Five brands, two products, three countries. Each of these is a named business rather than an anonymised composite, because a result with nobody attached to it is not evidence. H2: Online H3: Link: "Alex Rose, London" [/case-studies/alex-rose] Body: Bespoke tailoring. Over a year live, and our longest continuous deployment. H3: Link: "Siiine, UAE" [/case-studies/siiine] Body: Womenswear. Approached virtual try-on cautiously and needed convincing on render quality. H3: Link: "Narkin's, Pakistan" [/case-studies/narkins] Body: Menswear on Shopify. H2: Online and in store H3: Link: "Mushq, Pakistan" [/case-studies/mushq] Body: One of Pakistan's best-known labels, running LookCheck online including unstitched fabric, and on the shop floor. H2: In store H3: Link: "Breakout, Pakistan" [/case-studies/breakout] Body: LookCheck AI Smart Mirrors on the shop floor. CTA: Install on Shopify CTA: Book a mirror walkthrough What comes down "Case A / Case B / Case C" and their unattributed 42%, 18%, 38% and 21% figures. Precise numbers with no brand attached are the weakest proof available. Two of those stories also credited sub-inch sizing to online Salla and WooCommerce deployments, which is wrong. I2New/case-studies/alex-rose · ~750 words Alex Rose, the only page carrying performance figures H1: A year of LookCheck at Alex Rose London H2: The brand Body: Alex Rose runs a bespoke tailoring house in London. Custom jackets, made to order, every piece cut for one person. The kind of business where the customer is buying something that does not exist yet. H2: The problem Body: Bespoke has a harder version of the problem every fashion retailer has online. There is no product photograph, because the product has not been made. The customer is asked to commit to a garment, a cloth and a cut on the strength of a description and their own imagination. Body: That is a great deal of friction to put in front of someone before they have spent anything. It also slows every conversation that follows, because the gap between what the customer pictured and what the tailor understood only closes through back and forth. H2: What they did Body: Alex Rose deployed LookCheck online and has run it for over a year, which makes it our longest continuous deployment. H2: What changed Body: Revenue up 1.4x over the period. Body: A week taken out of delivery time on custom jackets. Body: Customers rating their satisfaction and experience five stars directly after the change. Body: The delivery figure is the one worth sitting with. Showing the customer the garment before it is cut removes a round of clarification that used to happen after the order was placed, which is why the time saving shows up in production rather than in marketing. H2: In his words Body: "Rendream's LookCheck has elevated the client experience for my bespoke tailoring business. The technology is precise, seamless, and reflects our premium standards, while the team's support has been outstanding. Highly recommended." Body: Alex Rose, CEO, Alex Rose London H2: Why this one is unusual Body: Bespoke tailoring is not a typical e-commerce case. Alex Rose was solving a visualisation problem sharper than most retailers face, which is part of why the result is as large as it is. Your own numbers will look different. Body: What carries across is the mechanism rather than the multiple. A customer who can see the thing on themselves commits faster and changes their mind less, and that holds whether you sell bespoke jackets or stocked shirts. H2: What changed in the process Body: The visible change is on the product page. The one that mattered to his business was further back. Body: A bespoke order used to begin with a conversation about something neither party could see. Notes, references, a length of cloth held up, and a shared assumption that turned out, sometimes, not to be shared. The corrections happened after the order, which is the expensive place for them to happen. Body: Showing the finished garment before it is cut moves that alignment to the front. The customer confirms what they are getting while it still costs nothing to change, which is where the week of delivery time came from. H2: Why bespoke made it work Body: In ready-to-wear, a try-on render competes with a photograph. The customer already has something to look at, and the render has to be better than it. Body: In bespoke there is no photograph, because the garment does not exist. The render is not competing with anything. It is the first time the customer sees the thing they are buying, which makes it the single most useful asset on the page rather than a supporting one. Body: That difference explains the size of the result and it is why the number does not transfer. But the direction does. In any category, the closer a customer gets to seeing the actual item on themselves, the less of the decision is left to imagination and the fewer of those decisions get reversed later. H2: What he uses Body: LookCheck online, on his own storefront. Visual try-on, not sizing. Link: "See what LookCheck does online" [/virtual-try-on-software] CTA: Install on Shopify CTA: See pricing How these numbers may and may not be used Always attributed. "Alex Rose saw revenue up 1.4x", never "merchants see 1.4x". Always scoped. The unusual-case paragraph travels with the figures wherever they appear, including the homepage and any sales deck. Never in a hero stat row. A number in a hero reads as a promise to whoever is reading it. Get it in writing first. Confirm with Alex Rose that the revenue multiple and the delivery figure can be public before this page ships. I3New4 studies · ~400 words each Mushq, Siiine, Breakout, Narkin's Same four-part shape. Where there are no attributable figures there are none, and a quote or a described outcome does the work instead. === /case-studies/mushq === H1: Mushq, online and on the shop floor H2: The brand Body: One of Pakistan's best-known fashion labels, selling unstitched cloth and pret, online and through physical stores. H2: The problem Body: Unstitched is the hardest thing to sell online. A three-piece is three flat rectangles in a photograph, and the customer is asked to imagine the finished garment. In store they would hold the cloth against themselves. Online they get a flat lay. H2: What they did Body: LookCheck online across the catalog including unstitched rendering, and LookCheck AI Smart Mirrors in store. One of the few deployments running both products at the same brand. H2: What changed Body: Customers see a finished shalwar kameez rendered from the actual cloth, on their own body, before ordering. In store, the mirror does the same on the floor and adds a size recommendation. Body: [Add a quote from Mushq once you have one. A named sentence from them is worth more here than any figure we could put in its place.] Link: "How unstitched rendering works" [/virtual-try-on-unstitched-fabric] Link: "The Smart Mirror" [/mirror] CTA: Talk to us about unstitched fabric === /case-studies/siiine === H1: Siiine, and the render quality question H2: The brand Body: A womenswear label in the UAE, selling pieces where the detail and the drape are the product. H2: The problem Body: For a brand like this, a poor render is worse than no render. If virtual try-on flattens the fabric or loses the fall of a piece, it actively misrepresents what the customer is buying. That is why they approached it cautiously. H2: What they did Body: LookCheck online, after testing render quality on their own pieces first. H2: What changed Body: "We are particular about how our pieces are represented, so we approached virtual try-on cautiously. LookCheck holds the detail and the drape we care about, and our customers now shop with real confidence." Body: Anastasia Vance, CEO, Siiine UAE Link: "See what LookCheck does online" [/virtual-try-on-software] CTA: Install on Shopify === /case-studies/breakout === H1: Breakout, LookCheck AI Smart Mirrors in store H2: The brand Body: A high-street fashion retailer in Pakistan, selling through physical stores. H2: The problem Body: The fitting room is the bottleneck in a busy store. A customer takes three items in, two are wrong, and they either queue again or leave with less than they came for. Staff time goes on fetching alternatives rather than selling. H2: What they did Body: LookCheck AI Smart Mirrors on the shop floor. Breakout runs the mirror only, not the online product. H2: What changed Body: Customers filter on the floor before they queue, see sizes and colours the store does not physically hold, and build complete looks from the catalog rather than judging one item at a time. Body: [Add a quote from Breakout once you have one.] Link: "Smart Mirror specifications" [/mirror/specifications] CTA: Book a mirror walkthrough === /case-studies/narkins === H1: Narkin's, virtual try-on on Shopify H2: The brand Body: A Pakistani menswear brand selling on Shopify. H2: The problem Body: Menswear online carries the same visualisation gap as womenswear and gets less attention for it. A customer judging a kurta or a shirt from a product shot on a model is guessing about fit, proportion and how it works with what they own. H2: What they did Body: Installed LookCheck on Shopify. H2: What changed Body: [Newly live. Fill this in once there is something real to report, and leave it out rather than padding it. A short honest entry on the index is better than a thin page.] Link: "Virtual try-on for Shopify" [/virtual-try-on-shopify] CTA: Install on Shopify Three of these have gaps, deliberately Mushq and Breakout need a client quote. Narkin's needs time to produce a result. Those are marked as gaps rather than filled with invented outcomes, because an anonymous percentage is exactly what this rewrite is removing from the site. Publish Alex Rose and Siiine first, which are complete, and add the others as the material arrives. J The LookCheck App (Pre-launch) J2Reframe/lookcheck-app · ~280 words The app page, as a pre-launch waitlist Confirmed as a future B2C product in the pipeline. The page stops describing an unlaunched product in the present tense and starts collecting demand. H1: The LookCheck app is coming Body: One shopper app for trying clothes on before you buy them, from any store you shop at. Body: We are building it. It is not out yet. H2: What it will do Body: Try on items from stores you already shop at, on your own photo. Keep the looks you liked in one place. Work across brands rather than only the ones running LookCheck on their site. H2: Want to know when it launches? [FORM: email address] CTA: Join the waitlist H2: If you are a retailer rather than a shopper Body: LookCheck is live today for online stores and physical shops. Link: "See what we do for retailers" [/virtual-try-on-software] Everything below must come off the current page "150+ Countries", "90% Size Accuracy", "<60s Setup Time". No basis, and they describe an unlaunched product as though it has users. The shopper testimonial about a Japanese streetwear purchase. Nobody has used this app. "Download LookCheck". There is nothing to download. Two of the three H1s. One per page. "We only store the encrypted numbers required to recommend your perfect size." This is the important one. It contradicts the zero-retention promise on every other page of the site. Whatever the app eventually does, those two statements cannot both stand, and that needs settling before the app ships rather than after. For the build: keep the route indexable, since waitlist pages rank fine and build early demand, but take it out of the main nav until launch. Footer or Resources. === /privacy-policy === H1: Privacy Policy H2: 1. Overview Body: LookCheck AI ("we") is committed to a "Privacy-First" architecture. This policy outlines how we handle data processed by our Virtual Try-On API. H2: 2. Data We Process (The "Zero-Storage" Commitment) H3: 2.1. End-User Images Body: Processing: When you send a user image to our API, it is processed in encrypted Random Access Memory (RAM). Storage: We do not save, archive, or store end-user photos on our servers (Hard Disks/SSDs). Biometrics: Our AI analyzes facial/body geometry to create a 3D mesh. This biometric processing is ephemeral. The biometric template is created, used for the try-on, and immediately destroyed. H3: 2.2. Logs Body: We retain text-only metadata for billing and debugging purposes, which includes: Timestamp, Client ID, Garment ID, Status (Success/Fail). These logs do not contain visual data. H2: 3. Data Controller vs. Processor (GDPR/UAE Law) Body: You (The Client): You are the Data Controller. You are responsible for obtaining consent from your customers to upload their photos. Rendream (LookCheck): We act as the Data Processor. We process the data strictly according to your API requests and do not use it for our own purposes. H2: 4. Security Body: Encryption: All data in transit is protected via TLS/SSL encryption. Infrastructure: Our secure processing environment is hosted on AWS (Amazon Web Services). Rendream holds ISO 27001:2022 certification. H2: 5. Contact Body: For privacy concerns: info@rendream.com === /terms-of-service === H1: Terms of Service H2: 1. The Service Body: LookCheck AI is a Virtual Try-On solution provided by Rendream. By integrating or using LookCheck AI, you ("Client") agree to these terms. H2: 2. Account & Billing H3: 2.1. Free Trial & Auto-Upgrade Body: Trial Limit: New accounts are granted 20 Free Try-Ons. Automatic Conversion: Upon exceeding the free tier, your account will upgrade to the paid volume tier selected during registration. You agree to pay all subsequent volume usage fees. Notification: We will notify you via email when you are approaching the trial limit. H3: 2.2. Fees Body: LookCheck operates on a customized volume-based pricing model plus a one-time setup fee. All fees are non-negotiable once the service agreement is active. H2: 3. License & Intellectual Property H3: 3.1. User Content License Body: You represent and warrant that you have the necessary rights and consents to upload end-user images to our API. You grant LookCheck a limited, revocable, worldwide license to process these images solely for the purpose of generating the virtual try-on output. H3: 3.2. Output Ownership Body: Rendream claims no ownership over the generated images. Your end-users or your business retain full ownership of the try-on results. H2: 4. Operational Limitations H3: 4.1. Zero-Retention Policy Body: You acknowledge that LookCheck processes images using an ephemeral, real-time method. We do not store original user photos or generated outputs on persistent disk storage. Once the API response is returned to you, the image data is discarded from our RAM. H3: 4.2. Accuracy Disclaimer Body: The Service uses Artificial Intelligence to estimate 3D meshes and garment fit. The output is a visualization tool and may not represent a 100% accurate physical fit. The Service is provided "as is" without warranties of absolute photorealism. H2: 5. Liability Body: Rendream shall not be liable for any indirect, incidental, or consequential damages arising from the use of LookCheck AI. H2: 6. Governing Law Body: Governed by the laws of Dubai, UAE. === /return-refund-policy === H1: Return & Refund Policy H2: 1. 7-Day Money-Back Guarantee (Setup Fee) Body: We offer a full refund of the One-Time Setup Fee if requested within 7 calendar days of payment, subject to the following conditions: - Technical Failure: The API fails to integrate with your system due to a verified error on our end. - Defective Output: The AI results are technically defective (e.g., severe artifacting) and cannot be rectified by our support team. H2: 2. Volume Usage (No Refunds) Body: Refunds are not available for volume credits or try-ons that have already been successfully generated. If you cancel your account, you are liable for all usage fees incurred up to the moment of cancellation. H2: 3. Cancellation Policy Body: Trial: You may cancel anytime before exceeding the free limit to avoid any charges. Active Accounts: You may cancel your account at any time via the dashboard. Cancellation stops future billing but does not refund past usage. H2: 4. How to Request a Refund Body: Please email info@rendream.com with your Account ID and the reason for the request. ## Articles Canonical listing: https://lookcheck.rendream.com/articles Individual articles use /articles/{slug}. ### Smart Mirror in a Retail Store: What an Install Involves Canonical URL: https://lookcheck.rendream.com/articles/smart-mirror-retail-store-install Description: Siting, catalogue connection, staff training and the first three weeks. What deploying a smart mirror in a retail store actually involves on the ground. Published: March 2026 Last updated: 2026-10-05 Reading time: 6 min read Category: In-Store Retail Tech Author: Arsalan Shafique Role: Head of Business & Engineering LinkedIn: https://www.linkedin.com/in/arslan-shafique-rendream/ A smart mirror installation requires connecting a digital catalogue to physical floor space, training staff, and ensuring five feet of clear standing room. Deployments succeed when retail operators prioritise strategic siting over novelty, turning the unit into a reliable sales channel rather than a bottleneck. We were standing in the middle of a shop floor at 9:00 PM, looking at a reflection that finally matched the blueprint. That was the moment we knew the deployment was solid. It is one thing to write code in a controlled environment. It is another entirely to put a smart mirror in a retail store and watch it survive contact with reality. The technology is the easy part. Whether a unit actually earns its floor space is decided by siting, catalogue connection, staff habit and the first three weeks of operation. If you are preparing for a rollout, this is what that process looks like on the ground. #### Where the mirror goes decides most of the outcome A smart mirror needs around 5 feet of clear floor space in front of it for a try-on. That single number rules out half the potential locations in any given layout before we even start talking. The unit itself is a 55 or 65 inch interactive display capturing on a top of the line 4K ultra HD camera. It demands physical presence, meaning we treat it as a piece of architectural geometry rather than just a screen. When I walk a shop floor with a store manager for the first time, we look at sightlines from the entrance. A customer needs to see the unit the moment they cross the threshold. We check the ambient lighting to ensure the camera captures accurate detail without glare. Then we look at proximity. Placing it too close to the traditional fitting rooms invites comparison. Placing it too close to the till creates a bottleneck. A bad location throttles footfall immediately. If a spot creates a queue that spills into the main aisle, the store manager will turn the mirror off to clear the floor. I always ask where the dead zones are. Activating a quiet corner is often a better strategic move than crowding the high-traffic areas. Take Breakout's new outlet at Packages Mall in Lahore, which is the first smart mirror live in Pakistan. We worked with their team to find a position that drew foot traffic naturally, balancing visibility with the operational reality of a busy retail environment. #### Connecting the catalogue, and what endless aisle means in practice The real utility of virtual fitting room technology begins when a location stops being limited by its physical square footage. Connecting a store's full catalogue means a customer can browse inventory far beyond what is hanging on the rails that day. This is what endless aisle retail looks like in practice. A shopper can take a physical garment, scan it with the built-in barcode scanner, and immediately add it to their try-on queue. If they see a paired item on the screen that they want to feel in person, they can request the physical item directly from the interface. The system pings the floor staff to bring it over, keeping the customer engaged rather than wandering. Generating a finished render takes about 20 seconds, maintaining the momentum of the sale. We built the AI smart mirror to bridge the gap between digital discovery and physical fulfillment. Once the try-on is complete, the transaction happens exactly where the customer is standing. They can complete their checkout at the integrated payment terminal on the unit itself, or take their selections to the counter if they prefer. The e-invoice and complete order history go straight to their WhatsApp. This changes the fundamental equation for store managers. Stock depth is no longer a hard cap on what a specific location can sell. Every unit on the floor suddenly has the sales potential of a flagship warehouse. Integrating this level of catalogue depth ensures the mirror functions as a true sales channel. It is the reason why the shop floor is being instrumented for live data. #### Training the floor staff Getting the hardware running is only half the job. A smart mirror installation lives or dies by the people working the floor. We scheduled to train the floor staff, and the reality of that process is always revealing. The training itself is rarely about the software. The interface is intuitive enough that anyone who owns a smartphone can navigate it. The real training focuses entirely on when to offer the mirror to a customer. Week one behaviour usually involves staff treating the unit cautiously. They point it out as a feature but step back. By week three, the dynamic shifts. The best staff use it proactively to save a sale when a physical size is missing, or to suggest a multi-category outfit build. You can always predict a successful rollout by watching who picks the habit up first. It is rarely the most technically minded employee. It is usually the floor veteran who immediately recognises a tool that keeps a frustrated customer engaged. I watched during an afternoon shift, and it was a perfect example of how human habit dictates hardware success. We spend our time teaching staff how to read a customer's hesitation and introduce the try-on as a natural solution. Uptime matters, but adoption matters more. Our deployments succeed because we sit with the managers and map out exactly how the mirror fits into their existing sales script. #### What it changes about stock planning This level of integration forces a rethink of traditional inventory distribution. A small location can now carry a massive digital catalogue, completely altering what that store is capable of achieving in a given quarter. You no longer have to guess which sizes to stock deep in a low-footfall branch, tying up capital in garments that might never move. If you run operations across a mixed portfolio of stores, how are you currently handling stock depth across your smaller locations? Usually, it means making hard compromises and accepting lost revenue when a specific item is missing. The mirror shifts that dynamic entirely. You can hold thin physical inventory for tactile evaluation, letting the customer feel the fabric, while relying on the digital catalogue to secure the actual sale for variations. We see brands running mirrors now adopting this exact model. They keep the physical space focused on the newest collections or high-margin items, using the interactive display to handle the long tail of their inventory. The impact on supply chain efficiency becomes obvious within the first month. Store managers stop requesting excessive safety stock because they know the digital backstop is reliable. It is a fundamental shift from pushing inventory out in the hope of a sale, to pulling it precisely when a customer commits. This operational reality is what try-on does to cart abandonment in a physical setting. #### What to prepare for, honestly Store managers always have practical questions about capability and privacy, and we prefer to address them directly. First, AI size recommendation on smart mirrors operates with a margin under one inch on garment categories. It is a precise tool, but we are upfront about its scope. Second, unstitched fabric renders require specific setup with our team. It is a complex visual process that demands our engineering input rather than being a self-serve feature. If unstitched garments are a significant part of your catalogue, you should plan for that conversation early in the deployment timeline. We map the rollout accordingly so expectations align with operational reality. Finally, the question I get asked most often on the floor concerns data security. Customer images are encrypted, processed to generate the render, and then immediately deleted. Nothing is stored, and no customer data is ever used to train AI models. Rendream is ISO 27001:2022 certified, which provides the necessary guarantee for retail operations handling sensitive information. A shopper must use their own photograph for the system to work. Providing that level of privacy assurance is non-negotiable for consumer trust. There is no spin here. It takes work, alignment, and a willingness to adapt floor habits, but the operational returns justify the effort. #### A Major Operational Commitment Putting a smart mirror in a store is a major operational commitment. It requires planning, realistic expectations, and a clear understanding of your physical space. If you are evaluating how this technology might fit into your physical locations, we are available to outline the logistics. I am happy to walk anyone through what a real-world install actually involves, step by step, for your specific floor plan. #### Frequently Asked Questions ##### How much floor space does a smart mirror need in a store? A smart mirror requires around 5 feet of clear floor space in front of it to capture a full try-on properly. This standing distance ensures the 4K camera can frame the customer accurately. ##### How long does it take to install a smart mirror in a retail store? The physical installation is fast, but we budget 1 to 2 working days from unboxing the unit to having a fully running system. The timeline depends heavily on store layout, internet connectivity, and staff availability for training. ##### How much training do store staff need for a smart mirror? We budget dedicated hands-on sessions for staff training. The software interface is highly intuitive, so training focuses almost entirely on operational habits, like when to introduce the mirror to save a sale and how to build multi-category outfits. ##### What happens to customer photos taken at a smart mirror? Customer images are encrypted, processed for the try-on render, and immediately deleted. Nothing is stored, and no images are ever used to train AI models. Rendream operates under ISO 27001:2022 certification. #### About the Author I am an Experience Architect dedicated to designing memorable journeys that turn concepts into lived realities. My job is to remove the cognitive load of complex information and replace it with a clean, intuitive, and empowering visual workspace. I use the principles of "Learn-by-Doing" to ensure that your audience grasps the true value of your vision from the very first interaction. By focusing on "Moments of Delight" and reducing technical friction, I help you build a brand that people actually love to use. Topics: Smart Mirror, Retail Tech, In-Store AI, Endless Aisle, Omnichannel