Promotion codes that apply before the processor ever sees a number.

Codes that behave

Create percentage or fixed-amount promotion codes and put the limits on them you’d expect:

• start and end dates,
• a total usage limit, and a per-customer limit (one by default),
• a minimum subtotal,
• an on/off switch that pauses a code without losing its history.

Scoped to products — without a product catalog

Limit a code to specific products by the ids you already use: line item id, reference id, SKU, product id, or variant id. Matching ignores case and spacing, so SKU-001 and sku 001 are the same thing.

The buyer hears the real reason

When a code doesn’t apply, Throttle says why — expired, not started yet, used up, below the minimum — so the buyer isn’t left guessing and support isn’t left explaining.

Preview, then apply

Check a code and show the reduced total without using it up; a code’s usage is counted only when the order is placed. Shoppers enter codes in the hosted checkout’s promotion box, and the dashboard lets your team create, edit, pause, and test them.

Tax on the right number

Tax is calculated on the discounted price, and the figure agrees everywhere — Throttle’s own tax, the Avalara estimate, and the document Avalara files.

Test and live never share a counter

Codes belong to an environment: the same code in test and in production are separate, with separate usage counts, so testing never burns a live redemption.

See what’s working

The dashboard’s performance panel shows orders, revenue, and discount given per code over the last 7, 30, or 90 days, and an AI assistant can answer “which codes drove revenue last month?” directly.

Good to know

• One code per cart; applying another replaces it.
• On a subscription, a discount applies to the first charge.
• Codes are entered by the buyer — automatic discounts and bulk code generation aren’t available.