August 7, 2026
Most brands assume AR integration is the hard part. It's not. Here's the real 2–4 week breakdown - prep, platform paths and what to check once you're live.
Garima Poddar
~t.compress(q:75)~t.toFormat(f:webp)/cms_uploads/ChatGPT-Image-Aug-7-2026-12_00_27-PM.png)
You've decided your customers need virtual try-on. Maybe returns are hurting your profits, your competitors already have it, or customers keep asking, "How will this look on me?" before buying. Now you wonder: how do you get it live in your store?
Here’s the short answer: it usually takes 2- 4 weeks, mostly to build accurate 3D models of your products, not to write code. The technical embed on a custom site is just 2–3 lines of code. This guide shows what to prepare, which integration fits your platform, and what to check once you’re live.
Before starting, know what this integration is and isn’t, so you prepare your team right.
What it is: Fynd GlamAR is an SDK, a ready AR tool you add to your site or app. You’re connecting their AR engine to your product catalog not building AR from scratch.
What it isn’t: It’s not a quick plugin that needs no tech work. Shopify and Fynd Platform have easier extensions. Custom sites need a developer to add the SDK. And your products need 3D models first.
Your integration options, at a glance:
Platform | How you integrate | Effort on your side |
Shopify | GlamAR Shopify App | Low - install the app, map your products |
Fynd Platform | GlamAR Extension | Low - activate the extension, sync your catalogue |
Custom website or app | SDK embed (2–3 lines of JavaScript) | Medium - you'll need a developer |
iOS native app | GlamAR iOS SDK (Swift) | Medium to high - developer required |
Android native app | GlamAR Android SDK | Medium to high - developer required |
If rollout is delayed beyond 2-4 weeks, it’s usually missing key assets. Prepare these four things before contacting GlamAR or coding:
Start with your top 20–50 SKUs - best sellers or most returned. Each SKU needs its own 3D model, which sets your timeline.
GlamAR covers many categories: makeup, eyewear, jewelry, accessories, hair color, watches, furniture, clothing and footwear.
If you lack 3D models, GlamAR builds them. They’ll ask for:
Clear product images from multiple angles
Exact specs: size, materials and colors (Pantone or hex codes)
For jewelry and watches: CAD files or drawings, if available
Better references speed up and improve results.
If you have them, confirm file format. GlamAR prefers GLB and GLTF; OBJ and FBX often convert. Send what you have early- you may skip making some models.
GlamAR gives you
An App ID, which identifies your account
An Access Key, which authenticates your integration
Keep them secure and don’t expose them in client-side code without controls.
Install the GlamAR app from the Shopify App Store; it links directly to your product catalog.
Configure GlamAR in the Pixelbin Console using your API Token, SDK CSS/UI code, and metadata provided by your account manager.
Map your products: Publish List (live), Unpublish Category (mapped but not live), No Data (no 3D model yet). Upload via CSV or individually.
Add products and link 3D models; GlamAR uploads models they create directly.
Preview and adjust try-on settings, then publish. The "Try On" button appears on product pages automatically.
To disable, go to Settings in the extension and deactivate your account.
Add the GlamAR SDK script to your site’s <head> or load it asynchronously; find code at glamar.io/docs.
Embed the GlamAR viewer on product pages with 2–3 lines of code using your SKU ID to load the right 3D model.
Upload your catalog via the console individually or by CSV, linking each product to its 3D model.
Test in staging on various browsers and devices before going live.
Place the "Try On" button prominently near the main product image or Add to Cart button for better engagement.
Use GlamAR’s Swift SDK designed for native iOS apps.
Swift Package Manager (SPM) - recommended for most projects
CocoaPods - add pod 'GlamAR' to your Podfile
Carthage - add binary "https://raw.githubusercontent.com/pixelbin-io/glamar-swift/main/GlamAR.json" to your Cartfile
Manual - download the latest release and drag GlamAR.framework into your Xcode project
Initialize GlamAR in your AppDelegate:
swift import GlamAR func application( _ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? ) -> Bool { GlamAR.initialize( accessKey: "YOUR_ACCESS_KEY", development: false // Set to true for testing, false for production ) return true } |
Add the AR view. Set GlamArView as an IBOutlet in your view controller, then start the camera preview and apply SKUs:
swift import GlamAR class ViewController: UIViewController { @IBOutlet weak var glamArView: GlamArView! override func viewDidLoad() { super.viewDidLoad() glamArView.startPreview(previewMode: .camera) } // Apply a product try-on by SKU ID func applyProduct(skuId: String) { glamArView.applySku(skuId: skuId, category: "beauty") } } |
Camera permissions. Add the camera usage description to your Info.plist, required for App Store approval:
xml <key>NSCameraUsageDescription</key> <string>Camera access is required for virtual try-on</string> |
In Fynd Platform, go to Extensions → Available Extensions, find GlamAR and install it.
Configure GlamAR in Pixelbin with your API token and SDK setup.
Use FeedSync to map your Fynd catalog to GlamAR’s console, with products moving through Publish List, Unpublish Category, or No Data states.
Add products and link 3D assets individually or via CSV.
Preview and activate; the "Try On" button appears automatically on your product pages.
If under 10%, improve visibility by moving the button above the fold and making it clearer.
Test on mid-range Androids, older iPhones and tablets. GlamAR can help optimize lagging devices.
Check if products look right (e.g., watch size, lipstick shade). Fix issues before they cause returns.
Use GA4 to track views, try-on clicks, add to cart and purchases. Compare users who try on vs. those who don’t.
GlamAR’s SDK is optimized, but check product pages load within 2–3 seconds on mid-range mobile connections.
Not for Shopify or Fynd Platform apps. Yes for custom sites and native apps.
Usually 2-4 weeks: 1-2 for 3D models, 1-2 for integration and testing. Faster if 3D assets exist.
Shopify, WooCommerce, Magento, Fynd Platform, custom sites (Web SDK) and native iOS/Android SDKs.
Web SDK works on mobile browsers with no download. Native SDKs offer more customization.
GlamAR switches rendering modes to keep try-on working, though frame rates may be lower.
The tech side is simpler than expected: a 2–3 line embed, Shopify app install or Swift SDK. The real time goes into preparation - choosing products, gathering 3D references and setting up tracking.
Remember: the 3D models are your most valuable asset. Once in the GlamAR Console, they power try-on, 360° views, 3D configuration and AR ads. You’re investing in your full 3D commerce foundation, not just one feature.
Ready to start? Contact the GlamAR team, read the full docs or check pricing to find a plan that fits your catalog and platform.
It's a software development kit, a set of pre-built AR tools you integrate into your website or app to add virtual try-on, 360° product viewing and AI skin analysis, without building the underlying AR technology yourself.
GlamAR issues both once you sign up and your plan is active. You'll find them in your GlamAR Console account. To start, reach out to sales@glamar.io.
Yes. GlamAR's team builds 3D models from your product images and specifications as part of onboarding. Existing assets speed things up, but they're not a requirement.
Yes, through a dedicated app that connects directly to your Shopify catalogue and handles most of the setup, so developer effort stays minimal.
GLB and GLTF for web-based AR. OBJ and FBX can typically be converted. If you already have 3D assets, share them with the GlamAR team early to confirm compatibility.
Yes. GlamAR is SOC2, GDPR, and ISO certified, and all customer data, including skin scan and try-on session data, is handled in line with GDPR requirements. Full details are on the security page.
Discover how Instaghar partnered with Fynd to build a hyperlocal grocery platform with unified ecommerce, multi-store fulfillment, intelligent order routing and Transport Management System.
AI shopping assistants improve product discovery, build baskets and handle post-purchase support. See where they add value, how to measure ROI and what to look for.
AI assistants already compare price and stock before a customer visits a website. See what agentic commerce means for retailers, and what to prepare for.
Fill out the form
Share your contact information to get started
Speak to an expert
A member of our sales team will get in touch with you