Connect Commercetools with Luna.io to power virtual try-on, fit guidance, and prescription-ready product configuration, so shoppers pick the right frames and lenses and complete checkout with confidence.
• Product data is pulled from commercetools using the Composable Commerce APIs, with scheduled or event-driven syncs for new and updated products.
• Variant attributes (size, color, frame material, rim type, and other eyewear-specific fields) are mapped to Luna.io configuration inputs used for guided selection and try-on.
• Prescription-related options (lens types, coatings, and constraints) are represented as structured option sets, with validation rules passed to the Luna.io flow.
• Media assets (images and, when available, 3D/try-on assets) are linked per SKU or variant, with fallbacks handled when an asset is missing.
• Delta sync logic sends only changed records, while full catalog syncs reconcile mismatches and reindex affected items in Luna.io.
• IDs and references are preserved across systems, and sync errors are logged with payload context to support retries and auditing.
.png)
We map Commercetools product types, attributes, and variants to Luna.io so frame geometry, colorways, and fit metadata stay consistent across try-on and configuration.
Typically you need frame SKUs, lens option rules, Rx input constraints, pricing, and eligibility attributes so Luna.io can validate choices and build the correct cart payload.
Yes; we implement rule-based configuration that translates shopper selections into sellable Commercetools variants or line items, with validation to prevent misconfigured orders.
It can; we align store views, currencies, languages, and region-specific lens rules so Luna.io experiences reflect each Commercetools market correctly.
Timelines depend on catalog complexity and Rx rules, but scandiweb has delivered 2,100+ eCommerce projects since 2003 and can own the integration end to end.




