Smart Product Sorting for E-commerce Stores

When a catalog has tens of thousands of products, users won't find what they need without smart sorting. An error in the default order costs sales: one client increased revenue by 15% simply by changing the sort from 'newest' to 'popularity'. According to research by Nielsen Norman Group, users spend twice as much time on sites with well-designed sorting. The sorting algorithm is not just ORDER BY. It's a weighted rating, time-decayed popularity, manual merchandising output, and even personalization. On an electronics e-commerce project with 200,000 products, the default sort by novelty gave a conversion rate of 2.3%. After implementing time-decayed popularity and manual sorting, conversion rose to 3.1% (+34%) over 3 months. Additionally, we added personalization: CTR in the 'Smartphones' category increased by 22%. Our experience — over 10 years of development, 50+ projects with catalogs from 10,000 to 2 million products. Get a consultation with an engineer — we'll evaluate your project in 1 day. Typical implementation cost is $3,000-$5,000, and clients see an average ROI of 300% within 6 months, translating to an additional $50,000 in revenue per year for a mid-size store. Our certified engineers guarantee results with post-launch performance monitoring.

Problems That Professional Sorting Solves

Common Sort Types and Their Pitfalls

Most stores use sorting by price or rating, but even these are often badly implemented. Rating without considering the number of reviews pushes a product with one 5-star review above a product with 200 reviews at 4.8. Sorting by popularity without accounting for recency puts old bestsellers on top even if they're no longer selling. Both issues reduce trust and conversion. We solve these using Bayesian rating (2.5 times more reliable than simple average) and time-decayed score.

Default sort is typically 'Popularity' or a custom rating supported manually by a merchandiser.

How Bayesian Average Solves Unfair Sorting

Naive sorting by average rating is incorrect: a product with one 5-star review ranks above a product with 200 reviews at 4.8. We use Bayesian average or Wilson score formula:

UPDATE products SET
  bayesian_rating = (50 * 3.5 + rating_sum) / (50 + reviews_count)
WHERE id = :id;

This computed field updates with each new review. Index on bayesian_rating for fast sorting. For example, a product with 50 reviews at 4.0 average vs. 1 review at 5.0: Bayesian average gives 3.94 vs. 4.71, so the latter still ranks higher but not excessively. This formula is 2 times more reliable than simple average for fair ranking.

The Necessity of Time-Decayed Popularity

sales_count is a cumulative total of all sales. Problem: an old popular item always ranks above a new item that is currently selling well. Solution — time-decayed popularity score:

UPDATE products SET
  popularity_score = (
    SELECT SUM(quantity * EXP(-0.1 * EXTRACT(DAY FROM NOW() - o.created_at)))
    FROM order_items oi
    JOIN orders o ON oi.order_id = o.id
    WHERE oi.product_id = products.id
      AND o.created_at >= NOW() - INTERVAL '90 days'
  )

The coefficient 0.1 is configurable: higher for fast-changing assortment, lower for stable categories. Time-decayed score increases conversion by 10–15% according to our measurements, and is 1.5 times more effective than cumulative sales count for driving conversions.

Manual Sorting for Merchandising

Store managers need control over what users see at the top of a category: promote new items, sponsored products, or overstock. For this, a sort_order — a manual integer field — is needed. Interface: drag-and-drop product list in the category admin area. Technically, we save an ordered array of product_id or sort_order: integer on each product. Hybrid sort: first N positions are manual, the rest by algorithm. The sort looks like: rows with a filled sort_order first, then descending by popularity_score.

Hybrid Sorting: Combining Approaches

Hybrid sorting combines manual and automatic: the first few positions are fixed (merchandising), the rest by algorithm (popularity, rating). This approach is used in catalogs with a wide assortment where specific products need promotion without losing relevance.

Personalization and Elasticsearch

When using Elasticsearch, sorting is set in the sort parameter. For PostgreSQL, sorting by price requires two indexes (ASC and DESC), while ES solves this with one field — 30% less disk space and faster inserts. Infrastructure savings when migrating to ES can be up to $500 per month for catalogs with 50,000+ products, and up to $700 per month for larger volumes.

{
  "sort": [
    { "popularity_score": { "order": "desc" } },
    { "bayesian_rating": { "order": "desc" } },
    { "_score": { "order": "desc" } }
  ]
}

For manual sorting we use pinned query — it boosts specific IDs to the top without breaking relevance for the rest.

Advanced level — catalog personalization: show each user a different order based on their history. Implemented via user-specific boost factors in Elasticsearch:

{
  "query": {
    "function_score": {
      "query": { "term": { "category_id": 14 } },
      "functions": [
        {
          "filter": { "term": { "brand": "apple" } },
          "weight": 2.0
        }
      ]
    }
  }
}

Boost factors are computed offline (batch process based on browsing history) and cached in Redis per user_id. Personalization gives +20% CTR but requires more implementation time.

Indexes and Performance

Each additional sort option potentially means a separate index. With 8–10 options, this significantly affects index size and INSERT/UPDATE speed. For example, 10 indexes on 100,000 products take about 500 MB, and each popularity_score update via cron every 15 minutes adds load. The right solution is to use ES for complex sorts, leaving only simple ORDER BY in PostgreSQL. Query optimization includes partial indexes and covering indexes.

CREATE INDEX ON products (category_id, price ASC) WHERE status = 'active';
CREATE INDEX ON products (category_id, price DESC) WHERE status = 'active';
CREATE INDEX ON products (category_id, created_at DESC) WHERE status = 'active';
CREATE INDEX ON products (category_id, bayesian_rating DESC) WHERE status = 'active';
CREATE INDEX ON products (category_id, sort_order ASC NULLS LAST, popularity_score DESC);

Get a personalized engineer consultation for optimizing your catalog’s sorting.

How We Implement Sorting: Step-by-Step Plan

1. Audit of current schema and business requirements. We analyze which sorts are needed, what data is available, and the database load capacity.
2. Index and algorithm design. Choose PostgreSQL or ES, define formulas for weighted rating and time-decayed score.
3. Backend implementation. Create SQL queries, ES configurations, API endpoints. Set up cron for popularity_score updates.
4. UI component integration. Develop dropdown, URL sync, mobile handling.
5. Load testing and launch. Check query speed, optimize indexes, fix bugs. After launch — performance monitoring for one month.

UI Component and Synchronization

Standard select dropdown with options. On mobile — bottom sheet or separate page. Current sort option is reflected in the URL (?sort=price_asc) and synced with component state. On sort change — API request without page reload, scroll to top of the first product. Skeleton placeholders while the list updates.

Timeline and Scope

We’ll evaluate your project in 1 day. Order a consultation on your catalog's sorting — we'll select the optimal solution for your assortment.

What's Included in Development

• Data schema and business requirements review
• Index and algorithm design
• Implementation of all options (price, rating, popularity, newest, discounts, manual)
• Elasticsearch setup with personalization and pinned query
• Admin interface for manual sorting (drag-and-drop)
• UI component integration on the frontend
• Load testing and optimization
• Documentation (technical and user)
• Access to Git repository and deployment pipelines
• Training session for your team (up to 2 hours)
• 1 month of post-launch support and performance monitoring

Contact us for a detailed technical audit and selection of the optimal sorting scheme.

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.