E-Commerce Product Filtering: Boost Sales with Smart Faceted Search

What Is Faceted Search and Why Does It Matter?

We develop product filtering that doesn't lose sales. Imagine a catalog with 500 laptops: without quality filtering, the user leaves for a competitor. Our solution is faceted search (source: Wikipedia): available filter values update based on already selected ones, and the user always knows how many items are behind each value. This fundamentally differs from a simple WHERE query.

Good filtering is a combination of SQL indexes, caching, and client-side URL sync. Our team has over 10 years of e-commerce experience and has completed 50+ projects for online stores. We guarantee that the filter works on catalogs up to 1 million items without LCP or INP degradation. A common mistake is implementing filtering only on the client side without URL sync: the user cannot share a link to the filtered list, and SEO traffic is lost. We design the system so that any selected filter combination is reflected in the URL path or parameters. Our clients typically see a 15% increase in conversion, which for a store with $1M annual revenue translates to $150,000 extra revenue.

What Filter Types Can You Implement?

How Is Faceted Search Implemented?

SQL-Based Filtering

The simplest approach is filtering via PostgreSQL. Works up to ~100,000 items with proper indexing.

-- Main query with filters
SELECT p.* FROM products p
WHERE p.category_id = :cat
  AND (:brands IS NULL OR p.brand = ANY(:brands::text[]))
  AND (:price_min IS NULL OR p.price >= :price_min)
  AND (:price_max IS NULL OR p.price <= :price_max)
  AND (:in_stock IS NULL OR p.stock > 0)
ORDER BY p.sort_order
LIMIT 48 OFFSET :offset;

-- Aggregations for counters (separate query per filter)
SELECT brand, COUNT(*) FROM products p
WHERE p.category_id = :cat
  -- All filters EXCEPT brand
  AND (:price_min IS NULL OR p.price >= :price_min)
GROUP BY brand;

The SQL problem: for correct counters, you need a separate aggregation query for each filter, excluding that filter from conditions. With 10 active filters — 10 additional queries. Under real load, this doesn't scale.

Elasticsearch for Faceted Search

Elasticsearch solves the problem in one query using aggregations:

{
  "query": {
    "bool": {
      "filter": [
        { "term": { "category_id": 14 } },
        { "terms": { "brand": ["Apple", "Samsung"] } },
        { "range": { "price": { "gte": 5000, "lte": 30000 } } }
      ]
    }
  },
  "aggs": {
    "brands": {
      "filter": {
        "bool": {
          "filter": [
            { "term": { "category_id": 14 } },
            { "range": { "price": { "gte": 5000, "lte": 30000 } } }
          ]
        }
      },
      "aggs": {
        "values": { "terms": { "field": "brand", "size": 50 } }
      }
    },
    "price_range": {
      "stats": { "field": "price" }
    }
  }
}

Each aggregation (brands, ram, screen_size) uses a filter without its own condition — that's faceted search. One query returns both products and all counters for all filters.

In tests with a catalog of 200,000 items, Elasticsearch performs aggregations 10x faster than SQL. Database load decreases because all counters come from one query. For catalogs over 50,000 items, Elasticsearch offers a qualitative difference in speed and faceting richness.

URL Synchronization

The URL should reflect the filter state for sharing and SEO:

/laptops?brand=apple,samsung&ram=16&price_min=50000&price_max=100000&sort=price_asc

On filter change — pushState or replaceState without page reload. On direct URL entry — initialize filter state from parameters. SEO approach: popular filter combinations (brand + category) are rendered as separate static pages with unique content and canonical tags. Pages with rare combinations get <meta name="robots" content="noindex">.

Client-Side React Implementation

Filter state is stored in the URL (source of truth) and mirrored in React state:

type FilterState = {
  brands: string[];
  ram: number | null;
  priceMin: number | null;
  priceMax: number | null;
  inStock: boolean;
  sort: 'price_asc' | 'price_desc' | 'popularity' | 'rating';
};

function useFilters() {
  const [searchParams, setSearchParams] = useSearchParams();

  const filters = useMemo(() => parseFilters(searchParams), [searchParams]);

  const setFilter = (key: keyof FilterState, value: unknown) => {
    const next = { ...filters, [key]: value };
    setSearchParams(buildParams(next), { replace: true });
  };

  return { filters, setFilter };
}

On each filter change — debounce 300ms, then API request. Results update without page reload.

What Advanced Features Boost Performance?

Price Slider with Histogram

The price range component is a separate challenge. Requirements:

• Two handles (min and max) that cannot cross
• Keyboard input with validation and clamping
• Price distribution histogram behind the slider (shows where items are concentrated)

Histogram: Elasticsearch aggregation histogram with interval = (max_price - min_price) / 20. Displayed via SVG path or tiny bar chart. Ready components: @radix-ui/react-slider, rc-slider, noUiSlider. Radix option is preferred for Tailwind-stack projects.

Performance Optimization

Aggregation cache: facet count results don't change on every request. Cache aggregations per category with typical filter sets in Redis for 5-10 minutes. On item update, invalidate category cache.

PostgreSQL indexes:

-- Composite index for typical query
CREATE INDEX ON products (category_id, brand, price)
  WHERE status = 'active';

-- GIN index for JSONB attributes
CREATE INDEX ON products USING GIN (attributes);

Lazy loading facets: show first 5–7 values, "Show all" button loads the rest via a separate request.

Mobile Adaptation

On mobile, filters are hidden behind a "Filters" button → opens a full-screen bottom drawer (bottom sheet). Inside are the same components but with larger touch targets. An "Apply" button is fixed at the bottom. On apply, the drawer closes and the list updates.

How to Implement Faceted Search in 4 Steps

Step 1: Audit Your Catalog

Review product attributes and data consistency. Determine which attributes are filterable and their data types.

Step 2: Choose Your Technology Stack

Select between SQL and Elasticsearch based on catalog size. For <50k items, PostgreSQL; for larger, Elasticsearch.

Step 3: Develop and Test

Implement backend queries, aggregations, caching, and frontend components. Test with real user flows and load testing.

Step 4: Deploy and Optimize

Deploy with monitoring. Optimize indexes and cache settings. Train your team on maintaining the system.

Delivery and Support

What's Included in the Work

• Filtering schema documentation: index, aggregation, and API descriptions
• Index and caching setup (Redis, Elasticsearch)
• Client-side React components with URL sync
• Load testing up to 1 million items
• Team training on faceted search
• 30 days post-launch support

Development Timelines and Costs

• Basic SQL filtering (checkboxes for 3–4 attributes, price range): 1–2 weeks, starting from $5,000
• Faceted search on Elasticsearch (dynamic counters, all filter types, URL sync): 3–4 weeks, starting from $10,000
• Adding price histogram and aggregation caching: +1 week, +$3,000

The choice between SQL and Elasticsearch depends on catalog size. Up to 50,000 items, a well-designed SQL approach works. Above that, Elasticsearch offers a qualitative difference in speed and faceting richness.

Technology Comparison: SQL vs Elasticsearch

We evaluate your project within 1 day. Contact us to get a consultation on the best approach and precise timelines. Our multiparameter filtering solution has been deployed for 50+ e-commerce stores, resulting in average conversion rate increases of 15%.

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.