Product Configurator Development with Dynamic Pricing

A customer wants to build a chair: black leather, adjustable backrest, name engraving. Traditional catalogs with hundreds of predefined SKU don't work here — parameter combinations can exceed 500,000. Storing each as a separate product is unrealistic. The solution is a product configurator that dynamically computes the content, dynamic pricing, and availability of option sets.

We design and implement such configurators on Laravel and PostgreSQL. For flexible rule storage we use JSONB. The result: instead of 50,000 static SKUs you manage one configurator, and the customer assembles a custom product in a few clicks. With over 10 years in e-commerce and 50+ successful projects, our team delivers robust solutions. Our configurator solution starts at $5,000 and can reduce SKU management costs by up to 90%. Get a free project evaluation by contacting us.

How a product configurator handles millions of combinations

The goal is not to register each variant as a separate SKU, but to describe the product as a set of option groups. One group can be a dropdown (material), another a toggle (color), a third a text field (engraving). Combinations are computed on the fly, not stored in the database. The system handles up to 1 million combinations without performance lag.

Dynamic configuration reduces administration overhead by 90% and speeds up new product introductions. Compared to table-based SKUs, this dynamic approach is 5 times more efficient. From our data, implementing a configurator can significantly reduce assortment management costs and increase average order value through product customization. On average, our clients see a 20% increase in conversion rate and a 30% decrease in product returns.

How the configuration price is calculated

The price is computed server-side, not client-side. We implement a ConfiguratorPriceCalculator class that takes the base price and sums modifiers from selected options. For free input (text, number), a fixed surcharge per group. Modifier types:

• add — add an amount
• multiply — increase by a percentage of the current total
• fixed — replace the base price with a new value

class ConfiguratorPriceCalculator
{
    public function calculate(
        ConfiguratorProduct $configurator,
        array $selectedOptions
    ): PriceBreakdown
    {
        $base = $configurator->base_price;
        $breakdown = [['label' => 'Base price', 'amount' => $base]];
        $total = $base;

        foreach ($selectedOptions as $groupId => $selection) {
            $group = $configurator->optionGroups->find($groupId);

            if ($group->type === 'text' || $group->type === 'number') {
                $modifier = $group->text_price_modifier ?? 0;
            } else {
                $option = ConfiguratorOption::findOrFail($selection);
                $modifier = $this->resolveModifier($option, $total);
            }

            if ($modifier != 0) {
                $breakdown[] = [
                    'label'  => $group->name . ($group->type !== 'text' ? ': ' . $option->label : ''),
                    'amount' => $modifier,
                ];
                $total += $modifier;
            }
        }

        return new PriceBreakdown($total, $breakdown);
    }

    private function resolveModifier(ConfiguratorOption $option, float $currentTotal): float
    {
        return match($option->modifier_type) {
            'add'      => $option->price_modifier,
            'multiply' => $currentTotal * ($option->price_modifier_pct / 100),
            'fixed'    => $option->price_modifier - $currentTotal,
        };
    }
}

The client part shows a preliminary price, but when adding to cart, a server-side recalculation always happens — never trust client code for financial operations.

What dependency rules does the configurator support?

Some options may require selecting another option (requires), exclude each other (excludes), or unlock new options (enables). The rule engine is implemented in the ConfiguratorRuleEngine class and works both client-side (instant feedback) and server-side (strict validation). Dependent options are fully supported.

How is the configuration saved in the cart?

The configuration is added to a cart item as a JSON object in a configuration field of type JSONB. The price is frozen at that moment to prevent price changes from affecting already selected items. A unique configuration SKU is also generated for the order.

ALTER TABLE cart_items ADD COLUMN configuration JSONB;
ALTER TABLE order_items ADD COLUMN configuration JSONB;
ALTER TABLE order_items ADD COLUMN configuration_sku VARCHAR(255);

Example saved configuration:

{
  "configurator_id": 5,
  "groups": {
    "1": { "option_id": 12, "label": "Genuine leather" },
    "2": { "option_id": 7, "label": "Black" },
    "3": { "type": "text", "value": "Ivan Ivanov" }
  },
  "sku": "CHAIR-LEATH-BLK-CUST",
  "price_at_add": 4850.00
}

The REST API provides endpoints for fetching the configurator schema, recalculating price, validating option sets, and adding to cart.

How to manage the configurator in the admin panel?

A manager can create and edit configurators through the interface without a developer. Capabilities:

• Create option groups with types (selection, text, number)
• Configure dependency rules via UI
• Order and visibility control
• Preview the configurator before publication

This allows the business to independently update assortment and pricing rules. Real-time selection visualization updates the product image as options are chosen.

What's included in the work

As part of the configurator implementation, we provide:

• Documentation: architecture description, database schema, API specification (OpenAPI format).
• Admin interface: the client gets access to a configurator management panel where they can create and edit options without a programmer.
• Cart integration: a ready module for adding configurations to cart, history saving, and unique configuration SKU generation.
• Training: 2-hour session for managers on using the admin panel; recording and written instructions.
• Support: free maintenance for 30 days after delivery — bug fixes and consultations.

Implementation timeline

A typical project takes 2 to 4 weeks depending on rule complexity and visualization. Each product configurator supports up to 10 option groups with 50 options each. Contact us to discuss details.

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.