TURKISH PLATFORMS

3D/AR integration for Ticimax, İdeasoft and İkas stores

TicimaxİdeasoftİkasTemplate embed
SUMMARY

GlareAR builds 3D product viewer and WebAR integrations for Ticimax, İdeasoft and İkas, the e-commerce platforms widely used in Turkey. The integration consists of a viewer embedded into the platform's product page template plus a selection layer wired to the platform's own variant structure. Because these platforms do not offer native 3D model support the way Shopify does, the embedding layer is built specifically.

Why do Ticimax and İdeasoft need a different integration approach?

Shopify natively supports uploading a 3D model as product media and rendering an AR button. Ticimax, İdeasoft and İkas model product media as images and video, with no dedicated media type for 3D. GlareAR therefore installs the model not as product media but as a standalone viewer embedded into the product page template.

In practice this means the model is hosted externally and matched to the product page by product code. Variant selection is wired to the platform's own variant fields so the colour a shopper picks points to the same product in both the 3D view and the cart.

115,43 milyar USD

Turkey's e-commerce volume, up roughly fourfold in six years from 23.94 billion USD in 2019

Source: Ticimax e-ticaret verileri (2025)

How do the platforms differ for integration?

PlatformNative 3D supportGlareAR integration method
ShopifyYes — 3D model as product media plus AR buttonNative media field or custom viewer
TicimaxNoViewer embedded in product page template, matched by product code
İdeasoftNoViewer embedded in product page template, matched by product code
İkasNoViewer embedded in theme template
WooCommerceNo — via pluginEmbedding at plugin or theme level

The table shows whether each platform treats a 3D model as a first-class media type. Lacking that support is not a blocker; it means the embedding layer has to be built separately.

What are the integration steps?

  1. Product and variant inventory: Decide which products get 3D and map each product's variant structure. Variant codes are the key to the integration.
  2. Model production: Web-optimized glTF/GLB and USDZ are produced from CAD or reference imagery.
  3. Viewer embedding: The viewer is added to the product page template and the model is matched by product code.
  4. Variant binding: The platform's variant selector is wired to the material channels in the 3D view.
  5. AR trigger: AR Quick Look is linked for iOS and Scene Viewer for Android; the button is hidden on desktop.
  6. Measurement: Viewer interaction and AR launches are tagged as analytics events; conversion comparison rests on those events.

Does it break the existing theme or template?

The GlareAR integration works as a block added to the theme template and does not remove the existing product gallery. The viewer can sit next to the gallery or as an additional tab inside it. The change is reversible: removing the block restores the page.

FAQ

Common questions on this topic

Can a 3D configurator be integrated into Ticimax?

Yes. Since Ticimax has no dedicated native media type for 3D models, GlareAR installs the viewer as a standalone block embedded in the product page template and matches the model by product code. Variant selection is wired to Ticimax's own variant fields so the colour selected in the 3D view goes to the cart as the same product.

Is İdeasoft integration different from Ticimax?

The approach is the same: in both cases the viewer is embedded into the product page template and the model is matched by product code. The differences lie in the template editing interfaces and how variant fields are named, which affects setup effort rather than how the integration works.

Does the integration need permission from the platform vendor?

If you have rights to edit the theme or product page template, no additional permission is needed; the integration runs on standard HTML embedding. On plans where template editing is restricted, the step of adding the block needs to be coordinated with the platform vendor's support team.

Where are the model files hosted?

Models can be hosted by GlareAR and served over a CDN, or handed over to the brand's own server. CDN hosting loads faster on mobile because files come from a geographically closer server, while self-hosting gives full control over the files.

For all questions see the FAQ page.

Let us scope this for your product range

GlareAR scopes timeline and deliverables against your product and file inventory.

Start a project