Product Catalog Development: EAV, SEO, Variants & Caching

When clients come to us with a slow catalog, filters taking minutes to load, and SEO traffic dropping due to duplicate pages, the root cause is often poor architecture: wrong category model, inefficient pagination, or lack of caching. Developing a product catalog is the central task for an e-commerce store, and getting it right can save up to 40% of support budget (infrastructure cost reduction up to 300,000 RUB per year). Statistics show 70% of users leave a site if the catalog takes longer than 3 seconds to load, and a well-designed catalog can boost conversion by 20%. With 8 years in catalog development and over 50 projects for stores with 10,000+ daily visitors, we know what works.

The catalog is the core module of an e-commerce site. Its architecture determines search speed, navigation ease, and SEO traffic. Mistakes here are the most costly, requiring data migration and reworking dependent modules. A properly designed product catalog handles up to 500,000 items without performance loss.

Which Category Model to Choose?

The category tree is stored in the database. Two common approaches:

Adjacency List – each record stores parent_id. Simple writes, but reading the full tree requires a recursive CTE:

WITH RECURSIVE category_tree AS (
  SELECT id, name, parent_id, 0 AS depth
  FROM categories WHERE parent_id IS NULL
  UNION ALL
  SELECT c.id, c.name, c.parent_id, ct.depth + 1
  FROM categories c
  JOIN category_tree ct ON c.parent_id = ct.id
)
SELECT * FROM category_tree ORDER BY depth, name;

Nested Sets (MPTT) – each record stores lft and rgt values. Subtree query: WHERE lft BETWEEN :parent_lft AND :parent_rgt – one query, no recursion. Writes are more complex: adding a node updates all right siblings.

Closure Table – a separate table with all ancestor–descendant pairs. Most flexible, more storage. Optimal for complex tree operations (moving subtrees).

Our recommendation: for catalogs up to 10,000 categories, Adjacency List with Redis tree caching is sufficient. MPTT when subtree queries are frequent and no cache is used.

How to Implement Product Attributes Correctly?

Products of different categories have different attribute sets. Three approaches:

• Fixed columns table: products.color, products.size, products.weight. Works only with homogeneous assortment. Adding a new attribute requires ALTER TABLE, migration, deploy.
• EAV (Entity-Attribute-Value): flexible but slow with JOINs. For filtering, you need Elasticsearch or a denormalized index.
• JSONB column in PostgreSQL:

ALTER TABLE products ADD COLUMN attributes JSONB;
CREATE INDEX ON products USING GIN (attributes);

A compromise: flexibility of EAV without excessive JOINs. As documented in PostgreSQL documentation, JSONB columns provide EAV flexibility without extra tables. Suitable for catalogs up to 500,000 products.

Product Variants: Parent-Child

Products with variants (color × size) are common. Two patterns:

• Simple SKU: each combination is a separate record in products. Simple but hard to manage parent card.
• Parent-Child: parent product type 'variable' and child 'variant' with specific attribute combinations.

products (id, type, parent_id, sku, name, price, stock)
-- type: 'simple' | 'variable' | 'variant'
-- variant: parent_id → variable product

When displaying the product card, load parent + all variants. User selects attribute combination → find corresponding variant → update price, photo, stock. For the variant matrix, use an object indexed by attribute ID.

URL Structure and SEO

Category URLs are critical for SEO. Three options:

• Flat: /catalog/noutbuki – simple, loses hierarchy context.
• Hierarchical: /catalog/elektronika/kompyutery/noutbuki – better for SEO, harder when category is moved.
• Hybrid: /noutbuki-c142 – readable slug + unique ID (resilient to renames).

For filtered pages: /noutbuki?brand=apple&ram=16 with canonical to /noutbuki or separate SEO pages for popular combinations (/noutbuki-apple-16gb as static aggregator). Schema.org: ItemList on category pages with ListItem for each product in listing.

Pagination and Infinite Scroll

Offset pagination: LIMIT 48 OFFSET 144. Works, but on deep pages (OFFSET 10000) PostgreSQL still reads 10048 rows. Solution – keyset pagination:

SELECT * FROM products
WHERE (sort_value, id) > (:last_sort_value, :last_id)
ORDER BY sort_value, id
LIMIT 48;

Keyset pagination is instant at any depth, but doesn't support arbitrary page jumps.

For mobile – infinite scroll with IntersectionObserver, for desktop with SEO priority – classic pagination (search engines better index pages with explicit numbers).

Catalog Management in CMS

Admin interface for the catalog:

• Bulk editing: select 50 products → change category/status/price.
• Import from CSV/XLSX: column mapping, preview with errors, background loading via queue.
• Drag-and-drop sorting: visual tree with reorder ability.
• Attribute management: add attribute to category – it appears on edit forms of all category products.

For bulk import: Laravel Jobs + Horizon. File uploaded to S3, job picks from queue, parses line-by-line (via league/csv or PhpSpreadsheet), products inserted in batches of 100.

How to Speed Up the Catalog with Caching?

Catalog pages are the main DB load. Caching strategy:

When a product changes, flush cache only on pages where it appears. Cache tags in Laravel: Cache::tags(['category:electronics'])->flush(). Optimal caching configuration can reduce page load time from 3 to 0.5 seconds. Caching can cut server costs up to 200,000 RUB per year.

For catalogs with high dynamics (frequent price or stock changes), reduce listing TTL to 1-2 minutes and use tag-based invalidation. For static catalogs, increase TTL to an hour.

Timelines

• Basic catalog (categories, product list, card, pagination): 2–3 weeks.
• With variants, EAV attributes, import, and caching: 4–7 weeks.
• Integration with Elasticsearch for search and filters adds 2–3 weeks.

What's Included

1. Preparation of technical specification with detailed data model.
2. Design and implementation of category hierarchy, attributes, and variants.
3. Development of SEO-optimized URL structure and Schema.org markup.
4. Configuration of pagination and caching.
5. Integration with admin panel for assortment management.
6. Code and API documentation, team training, access handover.
7. 30-day warranty support after delivery.

If you want to estimate the scope for your project, contact us – we will analyze your current catalog and propose a solution. Get a free catalog audit: request an engineer consultation. Our specialist will contact you within a day.

Common Mistakes in Catalog Design

• Using offset pagination for catalogs >10,000 products – leads to slowdowns on deep pages.
• EAV without indexing and caching – kills performance during filtering.
• Missing canonical on filtered pages – creates duplicates and lowers ranking.
• Flat URL without rename protection – loses SEO weight.

These mistakes increase load time by 40% and reduce conversion. Avoid them with proper design using modern practices.

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.