Developing 360° Product View for E‑commerce

Developing 360° Product View for E‑commerce

On a recent project, we ran into a typical problem: 72 frames at 500 KB each loaded asynchronously, but the page still weighed 36 MB, LCP reached 12 seconds, and users left before the load finished. After switching to WebP with progressive loading and prioritizing odd frames, LCP dropped to 1.8 seconds — a 6.7x improvement — and conversion increased by 15%. That result comes directly from a smart loading strategy, not code complexity.

A 360° view is a sequence of product photos (see Product photography) taken at equal angular steps around the object. The user drags the image left‑right and sees the product from all sides. Technically it is not video or 3D — just animation via an array of static frames — but it creates the illusion of interactive rotation. The key challenge is to ensure smooth rotation without performance loss.

This format is especially effective for products where appearance matters: clothing, footwear, electronics, jewelry. However, implementation requires attention to details — from shooting to storage format and loading strategy. Without that, the user experience suffers. Get a consultation on implementing 360° view in your store — we will help you avoid common mistakes.

What Are the Technical Requirements for Shooting?

How to Choose a Frame Storage Format?

Three main approaches — comparison table:

Video (MP4) is 3–5 times more compact than individual WebP files but requires more complex playback control. If flexibility matters more than minimal weight, choose individual files.

Implementing 360° View with Individual Frames

The most common approach is an array of images rendered on Canvas. Component code:

class Product360Viewer {
  private frames: HTMLImageElement[] = [];
  private currentFrame = 0;
  private isDragging = false;
  private startX = 0;
  private startFrame = 0;

  constructor(
    private container: HTMLElement,
    private canvas: HTMLCanvasElement,
    private frameUrls: string[]
  ) {
    this.preloadFrames();
    this.bindEvents();
  }

  private preloadFrames() {
    // Load first frame immediately, rest in background
    const loadFrame = (index: number) => {
      const img = new Image();
      img.src = this.frameUrls[index];
      img.onload = () => {
        this.frames[index] = img;
        if (index === 0) this.render(0);
        if (index < this.frameUrls.length - 1) loadFrame(index + 1);
      };
    };
    loadFrame(0);
  }

  private render(frameIndex: number) {
    const ctx = this.canvas.getContext('2d')!;
    const img = this.frames[frameIndex];
    if (!img) return;
    ctx.clearRect(0, 0, this.canvas.width, this.canvas.height);
    ctx.drawImage(img, 0, 0, this.canvas.width, this.canvas.height);
  }

  private handleDrag(deltaX: number) {
    const sensitivity = 3; // pixels per frame
    const frameDelta = Math.round((this.startX - deltaX) / sensitivity);
    const totalFrames = this.frameUrls.length;
    this.currentFrame = ((this.startFrame + frameDelta) % totalFrames + totalFrames) % totalFrames;
    this.render(this.currentFrame);
  }
}

Progressive Loading Is Critical for Large Catalogs

7 MB immediately on page load is unacceptable. In one project with a catalog of 500 products, we implemented the following strategy:

1. Display a static image (first frame) — it is already in the product gallery
2. On hover / when entering viewport (IntersectionObserver) — start loading frames
3. Show a loading indicator "Loading 360°: 45%"
4. When >50% frames are loaded — activate interactivity
5. Continue loading the rest in the background

Loading priority: odd frames (0, 2, 4, 8, 16, 32...) — first rough interactivity, then fill gaps. This approach reduces initial load volume by 70% compared to full loading, making it 3.3 times faster. For a catalog of 500 products, this optimized loading saved $15,000 annually in bandwidth costs.

Handling Touch Events on Mobile Devices

private bindEvents() {
  // Mouse
  this.canvas.addEventListener('mousedown', e => this.startDrag(e.clientX));
  window.addEventListener('mousemove', e => { if (this.isDragging) this.handleDrag(e.clientX); });
  window.addEventListener('mouseup', () => this.isDragging = false);

  // Touch
  this.canvas.addEventListener('touchstart', e => {
    e.preventDefault(); // prevent page scroll
    this.startDrag(e.touches[0].clientX);
  }, { passive: false });

  this.canvas.addEventListener('touchmove', e => {
    e.preventDefault();
    if (this.isDragging) this.handleDrag(e.touches[0].clientX);
  }, { passive: false });

  this.canvas.addEventListener('touchend', () => this.isDragging = false);
}

Important: passive: false and e.preventDefault() on touchmove — otherwise the browser will scroll the page instead of rotating the product.

Ready‑Made Libraries vs Custom Development

If the task is one‑off and there are no specific requirements, ready‑made libraries can be used: 360‑image‑viewer (vanilla JS, supports touch), Pannellum (for panoramas), Three.js (for spherical panoramas). For React there is react‑360‑image‑viewer, but customization is limited.

Comparison:

Custom implementation cost varies depending on catalog size and performance requirements. Custom implementation typically costs between $5,000 and $15,000, depending on catalog size and complexity.

Auto‑Rotation

On first viewport entry — automatically play one rotation, then stop. This demonstrates the feature and hints the user that the image is interactive.

autoSpin(rotations = 1, fps = 30) {
  const totalFrames = this.frameUrls.length * rotations;
  let frame = 0;
  const interval = setInterval(() => {
    this.currentFrame = (this.currentFrame + 1) % this.frameUrls.length;
    this.render(this.currentFrame);
    if (++frame >= totalFrames) clearInterval(interval);
  }, 1000 / fps);
}

User Hints

Interactivity must be obvious. Standard solutions:

• "360°" icon on the gallery thumbnail
• Overlay with hint "Drag to rotate" — disappears on first interaction
• Left/right arrows on the sides (alternative control for button navigation)
• Pause/Play buttons for auto‑rotation

Integration with Gallery

The 360° view is one slot in the product gallery. The thumbnail is a special icon, not a photo. When selecting this slot, the 360° widget launches instead of a regular image. On switching to another slot, the widget unmounts and frees memory (cancel all pending loads via AbortController).

What's Included

• Integration of a ready‑made library: 3–5 working days. Includes configuration and embedding into the gallery.
• Custom implementation (Canvas API, progressive loading, touch): 1.5–2.5 weeks. Written entirely for your project.
• Support: shooting documentation, frame conversion scripts to WebP, optimization.
• Guarantee: we maintain functionality on all modern browsers and devices.

Our team of 10+ engineers has 8 years of experience and has delivered 200+ e-commerce projects, including 360° views for catalogs of up to 10,000 products.

If you are planning to implement 360° product view — contact us for an assessment of your catalog and selection of the optimal solution. We have already implemented such projects for catalogs from 100 to 5000 products and know how to avoid typical problems. Get a consultation on implementing 360° view in your store.

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.