Run discounts and promo codes

A home décor seller wants to run a genuine end-of-season clearance — twenty percent off, minimum order value, expires in a week — but a version they tried before through informal WhatsApp promises turned into an argument with a customer who insisted the discount still applied after it had technically expired, with no clean record of what was actually promised or when, exactly.

The discount and coupon engine turns that promise into a rule the system enforces consistently for every customer, rather than a verbal offer that depends on someone remembering the details correctly weeks later. The owner sets the discount type, the minimum order value, and an expiry date once, and Kuber applies it automatically at checkout for any customer who enters the code, tracking exactly how many times it's been redeemed against whatever limit was originally set for it.

A coupon rule set is only as airtight as the combinations it was designed to prevent, and the most common way a promotion loses more margin than intended is stacking — a customer applying more than one discount to the same order when the rules weren't built to be mutually exclusive. A seller running a seasonal code alongside a first-time-buyer code needs to decide upfront whether the two can combine on one order or are meant to be either-or, because leaving that ambiguous is how a discount ends up larger than intended, discovered only once the margin on a batch of orders looks thin.

Redemption limits carry a timing risk easy to underestimate: if a coupon is capped at, say, a hundred uses and it's popular enough that many customers redeem it in a short window — during a flash sale announcement — near-simultaneous checkouts can create a race condition around who counts as the hundredth redemption. A seller running a tightly capped, high-demand promotion should expect this kind of edge case around the limit boundary rather than assuming the count will always land perfectly clean.

Measuring whether a promotion actually worked also depends on data the coupon engine alone doesn't fully provide. Redemption count shows how many times a code was used, but understanding whether a sale genuinely drove incremental revenue — orders that wouldn't have happened without the discount — versus simply discounting purchases that would have happened anyway requires comparing sales before and after, a judgement made using the broader analytics dashboard alongside the redemption numbers.