Building a Robust Coupon and Discount System with Real-Time Analytics

Imagine this: an online store launches a promotion "20% off your first purchase." An hour later, the database crashes from simultaneous requests, coupons are applied multiple times, and analytics shows incorrect data. This happens when the discount system is designed hastily. We design coupon and discount services that withstand high loads and prevent abuse. A poorly designed system creates loopholes for abuse and chaos in analytics. A well-designed system is a targeted marketing tool that increases conversion by 1.5–2 times. Over 10 years of work, we've encountered dozens of such situations and know how to avoid them. Proper architecture is key to stability during peak sales when load increases tenfold.

Overview of Discount Types

Before writing code, you need to define the discount model. Main types:

• Coupon (promo code) — the user enters a code manually or a link applies it automatically. The code can be unique or reusable, tied to a discount rule.Wikipedia
• Automatic discounts — applied without a code when conditions are met: "all items in category X at 15% off on Fridays," "500 rubles off orders over 3000."
• Accumulative programs — discount depends on customer purchase history (cashback, points, loyalty levels).
• Group discounts — wholesale prices for B2B clients, employee discounts, partner terms.

How to Design the Data Model?

discount_rules (
  id, name, type,              -- coupon | automatic | loyalty
  discount_type,               -- percentage | fixed_amount | free_shipping | bxgy
  discount_value NUMERIC,
  min_order_amount NUMERIC,
  min_qty INT,
  max_uses INT,                -- NULL = unlimited
  max_uses_per_user INT,
  starts_at TIMESTAMPTZ,
  ends_at TIMESTAMPTZ,
  is_active BOOLEAN,
  stackable BOOLEAN            -- can be combined with other discounts
)

discount_conditions (
  id, rule_id,
  condition_type,              -- product | category | tag | user_group | first_order
  condition_operator,          -- in | not_in | gte | lte
  condition_value JSONB
)

coupons (
  id, rule_id, code VARCHAR(32),
  usage_count INT DEFAULT 0,
  is_single_use BOOLEAN
)

coupon_uses (
  id, coupon_id, order_id, user_id, used_at,
  discount_amount NUMERIC      -- amount applied at the moment of use
)

Generating Coupons in Batches

For email campaigns, you need unique codes — one per recipient. Generating 100,000+ codes via INSERT with an index is 10x faster than checking EXISTS in a loop.

function generateCouponBatch(int $ruleId, int $count): array {
    $codes = [];
    while (count($codes) < $count) {
        $code = strtoupper(Str::random(8)); // A-Z0-9, 8 characters
        if (!Coupon::where('code', $code)->exists()) {
            $codes[] = ['rule_id' => $ruleId, 'code' => $code, 'is_single_use' => true];
        }
    }
    Coupon::insert($codes);
    return array_column($codes, 'code');
}

How to Avoid Race Conditions When Applying a Coupon?

Atomic Application

When a code is entered at checkout, you need to check: code exists and is active, start/end dates, usage limit, cart total, conditions. The check must be atomic. The solution is UPDATE ... RETURNING inside a transaction:

UPDATE coupons
SET usage_count = usage_count + 1
WHERE code = :code
  AND usage_count < max_uses
RETURNING id;
-- if 0 rows — coupon already used

This eliminates race conditions where two requests simultaneously apply the last available coupon. The system handles up to 100,000 requests per day at peak, with an average validation time of 50 ms.

Calculating Discount for the Cart

Discounts are calculated server-side; never trust the client. The algorithm:

1. Get applied discount rules (automatic + coupon)
2. For each rule, determine eligible items (considering conditions)
3. Apply discounts in priority order
4. If stackable=false — apply only the largest discount
5. Return a breakdown: which discount applied to which item

The breakdown is important for user display and analytics.

BxGy (Buy X Get Y) — "buy 3, get the 4th free." Implemented as a separate rule type: when qty >= X, add item Y to the cart with zero price or reduce the price of the Nth unit.

What Metrics to Track in Analytics?

Without analytics, marketing flies blind. Basic set:

For the marketer — a dashboard with filtering by period, discount type, channel. Typical indicators: conversion with coupon is 30% higher, average order value is 20% higher, return rate decreases by 10%.

Real-Time Analytics

The system collects metrics for each coupon: usage count, average order value, revenue increase. This data allows the marketer to quickly adjust campaigns. Implementing the system reduces operational costs for managing promotions by 30%.

How to Prevent Abuse?

Protection

• One coupon per order (unless stacking is allowed)
• Email verification for "new customer" discounts
• Rate limiting on the coupon application endpoint
• Alerts on sudden spikes in usage of a single coupon

Savings from abuse prevention can reach 15% of revenue. For a mid-size e-commerce store with $1M revenue, that equals $150,000 saved annually. Additionally, the system prevents up to $50,000 in direct abuse losses per year.

Marketer Dashboard

An interface for campaign management: creating rules with a visual condition builder, generating and exporting CSV batches of coupons, viewing real-time statistics, deactivating a campaign with one click.

What Does the Work Include and What Are the Timelines?

Scope of Work

• Designing data model and API
• Developing validation and atomic application
• Integrating with cart and catalog
• Analytical dashboard for marketers
• Campaign management panel
• Documentation and team training
• Post-launch support

Timelines

• Basic coupon system (promo code, percentage/amount, expiry date): 1–2 weeks
• Full system (conditions by categories/products, automatic discounts, BxGy, analytics, marketer dashboard): 3–5 weeks
• Loyalty program with points and levels: +3–4 weeks

Time to ROI: 3–4 months due to increased conversion and reduced abuse.

Our experience: 10+ years in e-commerce, 50+ projects delivered. We specialize in coupon service development and discount system analytics. Our extensive experience in coupon service development and discount system design ensures robust, scalable solutions. We guarantee transparent architecture and abuse protection. We'll assess your project in 1 day — contact us. Get a free engineer consultation.

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.