A discount code that's just a flat mapping from a string to a percentage off has an obvious problem: nothing stops it from being reused indefinitely, applied to an order it was never meant for, or stacked past whatever margin it was actually designed to protect. A promotion that's supposed to run for one week and cap at 100 uses needs to actually enforce that, not rely on someone remembering to disable it manually.
What real discount validation needs to check
A valid date window (not live before it starts, not usable after it ends), a usage cap -- both overall and per customer, since "100 uses" and "any one customer can use it 100 times" are very different promotions -- a minimum order amount where relevant, and a maximum discount cap so a percentage-off code doesn't produce an unintentionally enormous discount on a large cart. And critically: the discount calculation itself needs to be based on server-side prices, not whatever subtotal the client claims, or the validation is trivially bypassable.
How Vedron handles this
Vedron's discount codes support both percentage and fixed-amount discounts, scoped storefront-wide, per shop, or restricted to specific products (including resolving down to child product variants automatically, not just the parent listing). Validation covers valid-from/valid-until dates, overall usage caps, per-customer usage caps (checked against actual completed orders, not just attempted redemptions), minimum order amount, and a maximum discount amount ceiling. The cart subtotal used for the calculation is recomputed from actual database prices at redemption time, not trusted from whatever the client sends -- so the discount that's actually applied matches the rules you configured, not something that can be manipulated client-side.
Frequently asked questions
Can a discount code apply to only some products in my catalog?
Yes -- codes can be scoped to specific products, and that scoping resolves through to child variants automatically rather than requiring you to list every variant separately.
What stops a customer from using the same code repeatedly?
Per-customer usage limits are checked against real completed orders, so a cap of one use per customer is actually enforced, not just a suggestion.
Is the discount amount trusted from the checkout page, or recalculated?
Recalculated server-side from actual prices at the time of redemption -- the checkout page's own number is never the final authority.
Have a question specific to your setup?
Every seller's marketplace mix and stock setup is a little different -- if you're weighing this against your own, book a short call and we'll walk through it with you directly rather than leaving you to figure it out from a blog post alone.
Beta offer: if you join as a beta client, custom integration setup -- configured for your actual marketplace and inventory mix -- is free for your first 2 months.
Still evaluating and need more time than the standard trial window? Just ask us for an extension -- we're happy to give you the room to actually test it properly before deciding.