Interactive 3D Product Viewer for E-commerce

The customer sees a product photo but cannot rotate it, zoom in, or assess the texture. The result is returns due to mismatched expectations, lost sales. 3D viewing solves this problem: the user independently explores the object by rotating, scaling, and enabling augmented reality. Studies show: conversion on product cards with 3D is up to 40% higher than without (per Shopify data for furniture — up to 65%).

Our experience in furniture, jewelry, footwear, and electronics niches confirms this statistic. We have delivered over 15 projects, each requiring an individual approach to modeling, lighting, and integration. Content production costs can be reduced by up to 70% through photogrammetry, and the ROI from implementing 3D viewing can exceed 300%. Contact us to discuss a 3D strategy for your catalog.

Which 3D model formats are best for the web?

GLB is the de facto standard for 3D on the web glTF 2.0 specification. Everything is packed into one file: geometry, materials, textures, animations. It supports PBR materials (metalness/roughness workflow), providing physically correct rendering.

Three.js — basic stack

Minimal 3D widget using Three.js:

import * as THREE from 'three';
import { GLTFLoader } from 'three/examples/jsm/loaders/GLTFLoader.js';
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls.js';
import { DRACOLoader } from 'three/examples/jsm/loaders/DRACOLoader.js';
import { RGBELoader } from 'three/examples/jsm/loaders/RGBELoader.js';

const scene = new THREE.Scene();
const camera = new THREE.PerspectiveCamera(45, container.width / container.height, 0.1, 100);
const renderer = new THREE.WebGLRenderer({ antialias: true, alpha: true });
renderer.setPixelRatio(Math.min(window.devicePixelRatio, 2));
renderer.toneMapping = THREE.ACESFilmicToneMapping;
renderer.outputColorSpace = THREE.SRGBColorSpace;

// OrbitControls — rotation, zoom, pan via mouse/touch
const controls = new OrbitControls(camera, renderer.domElement);
controls.enableDamping = true;
controls.dampingFactor = 0.05;
controls.minDistance = 1;
controls.maxDistance = 10;

// DRACO decompression for compressed models
const dracoLoader = new DRACOLoader();
dracoLoader.setDecoderPath('/draco/');

const loader = new GLTFLoader();
loader.setDRACOLoader(dracoLoader);
loader.load('/models/product.glb', gltf => {
  scene.add(gltf.scene);
  fitCameraToObject(camera, controls, gltf.scene);
});

// HDR environment for PBR lighting
new RGBELoader().load('/env/studio.hdr', texture => {
  texture.mapping = THREE.EquirectangularReflectionMapping;
  scene.environment = texture;
});

What does Draco compression give?

Draco is a 3D geometry compression algorithm from Google. Typical compression: geometry reduces by 5–10 times with no visible quality loss. An 8MB chair model becomes 800KB after Draco.

Conversion in the pipeline (offline, when an administrator uploads a model):

# gltf-pipeline by Khronos
npx gltf-pipeline -i input.glb -o output.glb --draco.compressionLevel 7

# or via blender CLI
blender --background --python export_with_draco.py

The Draco decoder in the browser is a WASM module (~200KB). It must be placed on the server and the path specified in DRACOLoader.setDecoderPath().

<model-viewer> as a ready-made component

If deep customization is not needed, Google's <model-viewer> covers 90% of use cases. The open-source project model-viewer is actively maintained.

<model-viewer
  src="/models/chair.glb"
  ios-src="/models/chair.usdz"
  alt="Herman Miller office chair"
  camera-controls
  auto-rotate
  auto-rotate-delay="3000"
  rotation-per-second="30deg"
  shadow-intensity="1"
  exposure="0.8"
  environment-image="/env/neutral.hdr"
  ar
  ar-modes="webxr scene-viewer quick-look"
  loading="lazy"
  style="width: 100%; aspect-ratio: 1; background: #f5f5f5;"
>
  <div slot="progress-bar">
    <div class="progress-bar" style="..."></div>
  </div>
  <button slot="ar-button" class="ar-button">
    View in your interior
  </button>
</model-viewer>

Built-in: OrbitControls, touch support, AR (WebXR + Quick Look), shadow, lazy loading, progress indicator.

Lighting and PBR materials

The quality of browser rendering is determined by lighting. Without a proper environment, even a good model looks flat.

An HDR environment map is a spherical HDR panorama of studio or neutral lighting. It creates correct reflections on metallic and glossy surfaces. Size: 2MB–8MB, loaded once and cached.

For products: a neutral studio HDRI (gray background, even light) — neutral.hdr from the model-viewer repository. For jewelry, an HDRI with pronounced highlights.

Animated materials: switching variants (color, material) — change material.color, material.roughness, material.metalnessMap. Without reloading the model:

const materials = model.querySelector('model-viewer').model.materials;
const chairMaterial = materials.find(m => m.name === 'Fabric');
chairMaterial.pbrMetallicRoughness.setBaseColorFactor([0.8, 0.2, 0.2, 1]); // red

How to optimize performance?

Model size: target GLB size for a product card is up to 2MB. Larger — the user waits, conversion drops. Optimization methods:

• Draco compression of geometry (5–10x)
• KTX2 / Basis Universal texture compression (3–5x, with GPU decoding)
• Retopology: remove hidden faces, simplify invisible parts
• Bake high-poly details into a normal map on a low-poly model

Lazy loading: Three.js/WebGL initializes only when the widget enters the viewport using IntersectionObserver. When the widget is off-screen, rendering is paused.

Pixel ratio: on mobile, limit devicePixelRatio to 1.5 max — saves GPU on Retina displays.

Use <model-viewer> with built-in lazy loading if custom logic is not required.

Annotations and hotspots

Annotations are points on the 3D model with explanations. The user hovers/clicks — a tooltip appears with information about the detail.

In <model-viewer>, annotations use slots:

<model-viewer src="headphones.glb" camera-controls>
  <button
    slot="hotspot-ear-cup"
    data-position="-0.3 0.1 0.2"
    data-normal="-1 0 0"
    data-visibility-attribute="visible"
  >
    <div class="hotspot-label">
      <strong>Ear pads</strong>
      Memory foam, 40mm
    </div>
  </button>
</model-viewer>

Coordinates data-position — world coordinates in the model's coordinate system. Determined in Blender or via built-in picking in Three.js.

Content preparation pipeline

Widget development and model preparation are parallel tasks. Typical pipeline:

1. 3D modeling (Blender, Cinema 4D) or photogrammetry (RealityCapture, Meshroom)
2. Optimization (Blender: retopology, LOD), Draco compression
3. PBR texturing (Substance Painter) + texture conversion to KTX2
4. QA in browser: test in model-viewer, test on mobile
5. Convert to USDZ for iOS AR (Reality Converter, online converters)
6. Upload to CDN with correct headers (Content-Type: model/gltf-binary)

Development timeline

3D model preparation (if not available): from 4 hours to 2 days per SKU. For large catalogs, photogrammetry reduces content production costs by 5–10 times compared to manual modeling.

What is included in our work package

• Analysis of existing models and recommendations for optimization
• Selection and setup of environment (HDR, lighting)
• Widget integration into your CMS or frontend
• Lazy loading and caching configuration
• Documentation on model management
• Training administrators on uploading and replacing models
• Warranty support for one month after delivery

Order 3D viewer development — write to us to evaluate your project. Get a consultation for your catalog. We will offer the optimal solution for your budget and assortment.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.