discounts · promo codes · margins

Promo Code Abuse: How to Cap the Damage Before a Sale

Limit promo code abuse before your next sale. Set a discount budget, test coupon restrictions, protect first-order offers, and handle leaked codes carefully.

By cartt.io Team · November 13, 2026 · 11 min read

Promo Code Abuse: How to Cap the Damage Before a Sale

You push a spring code the night before a weekend, then wake up to orders from shoppers you never sent it to. Promo code abuse becomes expensive when the checkout accepts more than you intended. Before sharing a code, cap the discount budget, restrict eligible purchases, and test how you'll switch it off. Treat the string as public from the moment you create it, even if you only send it to your email list.

How does promo code abuse happen?

A subscriber forwards your email. The code lands in a deal group, or someone tries a predictable seasonal name at checkout. Another buyer discovers it works on an already reduced item. None of these paths requires access to your admin.

You can also create the problem yourself. Copy a campaign into another store and leave its code active, or assume the same offer is affordable across markets with different fulfillment costs. The checkout follows the saved settings, including the ones you forgot to change.

Discount code abuse also includes existing buyers claiming a first-order offer or returning under new emails. A rule attached to an email or customer record has gaps when those details change.

Trying to stop discount code leaks entirely is a poor operating assumption. Make the offer survivable if it spreads, and use eligibility restrictions to keep it close to its intended audience.

How do you set a loss cap before you launch a code?

Start with contribution per order: the selling price minus product costs, fulfillment, payment costs and other costs that rise with each sale. Then subtract the proposed discount. Keep advertising and overhead visible too.

Here's a hypothetical example, with rounded costs for illustration. You sell a $60 item with $38 in variable costs. That leaves $22 before advertising and overhead. A $9 discount leaves $13 on the discounted order under those assumptions. An order can remain worthwhile while still giving away money to someone who would have paid full price.

For a fixed discount applied once per order:

Maximum discount spend = maximum redemptions × discount per order.

A cap of 60 redemptions at $9 off means up to $540 in discounts. Suppose you can allocate $720 to the campaign. Reserving $180 for mistakes, support and fulfillment problems leaves that $540 discount budget. These are example amounts, not targets for your store.

Percentage offers need another bound. A redemption cap alone doesn't limit the value of the eligible cart. Multiple quantities can make the discount much larger than your usual order. Calculate using the largest permitted purchase, or choose a fixed amount applied once per order when you need a predictable budget.

This calculation caps discount spend under the stated conditions. Overselling, refunds and cancellation work can add costs. For subscriptions, include future discounted invoices too. An expiry for new redemptions doesn't necessarily end discounts already applied.

Which code settings limit the damage?

Coupon code limits solve different problems. Choose them together, then verify what your checkout actually enforces.

ControlWhat to setWhat it doesn't stop
Store and market scopeEnable only where the offer is affordableAccidental activation in another store
Eligible productsInclude items with enough contributionExcess quantities of an eligible item
Minimum orderRequire a basket that supports the offerAn expensive percentage discount on a large basket
Total redemption capDerive it from the discount budgetUnintended shoppers consuming the allocation
ExpirySet an end time and check the time zoneA rush of redemptions before the deadline
Customer restrictionsLimit repeat use and intended recipientsThe same person appearing under new details
Combination settingsDisable unwanted combinationsA lower product price already saved in the catalog

What can you enforce in Stripe?

Stripe's coupon defines the discount and can restrict eligible products. Promotion codes wrap that coupon with customer-facing strings and restrictions such as max_redemptions, expires_at, a minimum transaction amount and a specific customer. Use a shared coupon's redemption cap when several codes must share one allocation.

For customer-entered codes in Stripe Checkout, your integration enables allow_promotion_codes. Creating a code in the Dashboard doesn't enable that field in every checkout built on Stripe. The Checkout Session API currently accepts at most one coupon or promotion code in its discounts parameter. A reduced underlying price can still compound the saving.

Check access before choosing this route: Stripe's support page lists promotion codes as a paid Billing feature. Confirm the requirement and applicable cost for your account rather than assuming every coupon feature comes with payment processing.

What can you enforce in Shopify?

Shopify includes discount codes in its standard store plans. Its code settings support dates, usage limits, minimums and product selection. Set both total usage and one-use-per-customer limits when your offer needs them. Customer eligibility can target specific customers, segments or markets. Those eligibility choices aren't automatically a combined rule; verify any required intersection before launch.

Shopify codes work across markets by default. Assign market eligibility deliberately. A market label in the code's name doesn't restrict redemption.

Combination settings let you control stacking discounts by class. Combining multiple product discounts on the same item requires Shopify Plus; other combinations have their own eligibility conditions. You don't need that feature to decide your offer shouldn't combine. Manually added custom discounts can bypass combination settings, so include staff-created orders in your review if you use them.

Coupons are also built into cartt.io checkout pages. Check the controls exposed by your checkout before promising any restriction to customers.

How do you launch a code safely?

Keep one campaign record for prices and discounts across your stores. Record the intended store, market, currency, products, dates, budget and person responsible for stopping the offer. A shared document is enough if everyone uses it. Separate tabs nobody reconciles won't help.

Use this launch checklist:

  • Review the saved settings. Have another person check them against the campaign record. If you work alone, save the draft and reread it the next morning before activation.
  • Test accepted and rejected purchases. Try the intended cart, an ineligible item, mixed items, extra quantities, another discount and an existing customer. Check the final amount and confirmation email.
  • Start in one market. Verify the local price, currency and eligibility before copying the setup. Use a generated, non-obvious code rather than a predictable word; that reduces guessing but can't prevent forwarding.
  • Stay available after launch. Watch the first hours and agree who can stop the campaign. Don't schedule an unattended midnight launch before a weekend.

Test the kill switch before distribution. In Shopify, open Discounts, select the code, then choose Deactivate and confirm. Stripe promotion codes can be inactivated with active: false. Verify that a fresh checkout rejects the stopped code; review already-open checkouts separately.

Use your platform's supported test-order process. Shopify's payment test mode prevents live customer purchases while enabled, so schedule testing carefully. A test on a quiet store is useful; disabling real checkout during a campaign creates another problem.

For the wider purchase flow, use the checkout optimization guide. Here, the critical check is whether the final charge matches your campaign record.

How do you protect a first-order discount?

Preventing first order discount abuse starts with separating “one use per customer” from “new customers only.” An existing buyer who has never used a particular code may still qualify under a one-use restriction. Deleting a Shopify discount and creating a duplicate also gives previous users another opportunity to redeem that new discount.

Stripe offers a first-time transaction restriction. Its documented check can reject customers who initiated a PaymentIntent even without completing payment, or who started a trial. Test eligibility with realistic customer histories. Checkout Sessions without a Customer record also have documented restrictions on first-time codes; don't assume anonymous checkout will work unchanged.

A new customer record can undermine assumptions about a unique buyer. Reuse the known customer record where your integration supports it. Even a customer-restricted code identifies a record, not a verified person.

On Shopify, don't assume a segment of customers without orders catches every new visitor. Shopify warns that segment-restricted discounts can exclude first-time shoppers without an existing customer profile. Test an entirely new shopper before advertising the offer.

You can reduce repeat exposure separately. If you already use Klaviyo, its form targeting can hide an offer from recognized existing profiles. Cleared cookies, a new device or private browsing can make that visitor anonymous again. Hiding a popup doesn't enforce checkout eligibility.

For popup timing, my preference is to test an engagement trigger against immediate display. Klaviyo supports delays, scrolling and page-count triggers. That establishes what's possible, not which timing will improve your results. Compare contribution per visitor and purchases, not just email signups; a delayed offer might reduce interruptions while missing shoppers who leave quickly.

Skipping welcome discounts is reasonable when contribution is thin or your product sells at its stated price. You can invite email signup at checkout without promising a discount. A bounded welcome offer fits when you can fund a test and check whether it brings additional worthwhile orders. Some recipients would have bought anyway.

Frequent offers may also teach buyers to wait. The broader pricing trade-off belongs in fake discounts versus honest pricing. If your regular price doesn't cover costs, review how to raise prices before funding another promotion.

What do you do when a code has leaked?

Deactivate it first. Then remove it from scheduled messages and any other stores where it was enabled. If you issue a replacement, fix the eligibility and budget before sending it. Changing the string alone leaves the same exposure.

Export the affected orders and separate paid, unfulfilled, fulfilled and oversold purchases. Count the actual discounts and remaining contribution. Check outstanding checkouts and inventory commitments too. Order count alone won't tell you the cost.

Before cancelling paid orders, check local consumer rules, the terms shown at purchase and your platform's terms. A code reaching an unintended audience doesn't establish that every buyer violated a condition. A clear cancellation policy matters, but don't assume it overrides consumer protections. Get local advice if the decision is material.

For US physical-goods orders, the FTC's guidance addresses missed shipping promises through delay notices, cancellation options and refunds. EU guidance also sets out contract-information and purchase-confirmation duties. Neither gives you a universal answer about cancelling a particular pricing error. Check the applicable national or state rules.

Where you can honor accepted orders, weigh that cost against cancelling a purchase the buyer believed was valid. If cancellation is permitted and necessary, explain the specific issue and refund arrangements promptly. Don't accuse every buyer of abuse. Clear records and communication also matter for preventing chargebacks.

Handle overselling separately. Establish what's available before promising replacement stock or a revised shipping date. After the immediate work, compare the saved campaign settings with your record: wrong store, missing restriction, predictable name or forwarded email. Fix that cause before the next launch.

FAQ

Can I cancel orders placed with a leaked code?

Don't assume so. Check local rules, the offer's conditions, your cancellation policy and platform terms before reversing a confirmed purchase. An unexpected discount cost alone doesn't tell you whether cancellation is permitted.

Are single-use codes better than one public code?

They limit the reach of each leaked string. They can still be forwarded before use. Customer restrictions add another boundary, while a campaign-wide budget prevents a large batch of individual codes creating excessive total exposure.

Does a redemption cap stop abuse?

It limits accepted redemptions, including legitimate ones. Unintended buyers can exhaust the allocation. Combine the cap with eligibility rules and a bounded discount per order to control spending.

Should I discount at all?

Use a discount when the remaining contribution and campaign budget make the experiment worthwhile. If you can't fund the worst case, shrink the offer or skip it. Higher order volume alone doesn't establish that it worked.

How do I stop customers stacking a code with a sale price?

Exclude sale items from the code's eligible products or collections, then test a mixed cart. Shopify treats a sale price and compare-at price separately from discounts. Turning off discount combinations alone doesn't exclude those reduced-price products.