Codes & usage limits

Attach a code to a discount and it stops applying automatically — it waits to be typed. Codes are unique across your business, and the builder checks as you type.

The two usage limits#

The Stacking and limits section caps redemptions two ways — as its own copy says: "Cap how many times this discount can be redeemed, and how much it can take off. Leave a field empty for no limit."

• Maximum total uses — a global counter across all customers. The count is exact even under load: two checkouts racing for the last redemption cannot both win it.
• Maximum uses per customer — how many times one customer may redeem it. Guest checkouts are exempt, as the builder's tooltip notes — "There is no customer to count against" — so a strictly one-per-customer promotion should require a customer at checkout.

A customer over their limit is told exactly that: "you have already used this discount the maximum number of times."

How the counters move#

• A redemption is counted only when the order is saved — an abandoned or failed checkout never consumes a use.
• Cancelling the order gives the redemption back.
• A return does not — the promotion did its job of making the sale; refunding the goods doesn't refund the coupon.

Deleting vs deactivating#

A discount that has never been redeemed can be deleted. One that has been used cannot — the refusal is explicit: "this discount has been redeemed N times and cannot be deleted; deactivate it instead." That is deliberate: orders that used it still point at it, and deleting it would orphan their history. Deactivating removes it from every checkout just as thoroughly, and keeps the books whole.

Related pages#

How discounts work · Rules & scheduling · Combining discounts