Coupon Management (New Engine)
In the new engine, a Discount and a Coupon are separate entities. The Coupon is the code mechanism — it does not define the offer itself, only how access to it is gated.
Three delivery mechanisms
| Mechanism | Code required | Who gets it | Use case |
|---|---|---|---|
| Automatic (no code) | No | All eligible customers silently | Mass promotions, club prices, automatic cart thresholds |
| Coupon (shared code) | Yes — one code for all | Any eligible customer who knows the code | Broadcast promotions, leaflet codes, publicly shared campaigns |
| Voucher (unique code per customer) | Yes — one code per person | A specific identified customer | Re-engagement offers, birthday rewards, targeted win-back |
When is a Coupon mandatory?
Whether a coupon is required depends on the audience selected when creating the discount:
| Discount audience | Coupon required? | Why |
|---|---|---|
| All customers (mass) | No | The discount fires automatically for every qualifying cart |
| Loyalty members (club) | No | The discount fires automatically for enrolled members' carts |
| Targeted (specific audience) | Yes | Targeted discounts have no automatic delivery — the Coupon or Voucher is the mechanism that restricts the offer to the right customers |
:::info Targeted = always needs a code A discount configured for a targeted audience will never apply on its own. It requires either a shared Coupon code (sent via a campaign) or individual Vouchers (distributed per customer via Targeted Delivery). Without a code, the discount cannot reach the customer. :::
Coupon vs Voucher
Both are code-based mechanisms, but they differ in scope:
| Coupon | Voucher | |
|---|---|---|
| Uniqueness | One code shared by all eligible customers | Unique code per customer |
| Verification | Any eligible customer who presents it | Validated against that specific customer's identity |
| Generation | You define the code (e.g. SUMMER20) or the system generates one | System generates unique codes per customer |
| Distribution | Broadcast publicly, shared via campaign | Distributed via Targeted Delivery campaign |
| Typical use | Promotional leaflet, broadcast offer, semi-open campaign | Personalized win-back, re-engagement, birthday reward |
Static Code Rules
A static code is a shared coupon code linked to one campaign/coupon. It is useful when many Customers should use the same visible code, for example a leaflet code, email code, or app banner code.
| Rule | What it means |
|---|---|
| Unique across campaigns | The same static code cannot be used by another campaign/coupon. Creating a second one with the same static code returns an error. |
| Shared inside the campaign | Multiple Customer assignments or Vouchers can exist behind the same static code when they belong to that campaign/coupon. |
| Not a per-Customer code | The visible code is shared. Customer-specific ownership and redemption state are tracked by the generated Voucher/assignment behind it when applicable. |
| Redemption resolution | If several Vouchers match the same static code, the system redeems the eligible Voucher with the earliest expiration date. |
To run a similar campaign again with a static code, create or reuse the campaign setup but choose a new static code if a new campaign/coupon is created.
How It Works
The delivery mechanism is selected in Step 3: Effect → Redemption of the discount creation flow:
| Option | Description |
|---|---|
| Automatic | No code required; discount fires silently when conditions match |
| Coupon code | Define the code string (e.g. SUMMER20) or let the system generate one. Any eligible customer who presents it at checkout receives the benefit |
| Voucher | System generates unique codes per customer; distributed via a Targeted Delivery campaign |
After a Targeted Delivery Send
When a targeted Discount is sent, Targeted Delivery creates the Customer-specific Voucher or coupon relationship and records the execution in Campaign History. The campaign send date only controls when Customers receive the benefit; it does not define the redemption window.
| Area | What to expect |
|---|---|
| Discount validity | Controlled by the Discount active dates, Coupon/Voucher configuration, limits, and redemption method |
| Campaign History | Preserves the send context: Audience snapshot, channel, status, sent date, and selected Discount or Coupon |
| Editing the Discount | Affects future evaluations and future sends. It does not rewrite past Campaign History records |
| Already issued Vouchers | Keep their ownership and operational status. Use Targeted Delivery history tools to cancel or reprint when permissions allow |
| Customer-facing changes | Avoid changing discount value, product scope, validity, limits, or redemption behavior after Customers have received the offer unless the business explicitly wants future redemptions to follow the new configuration |
For substantial customer-facing changes, create or reuse a new Targeted Delivery campaign instead of trying to reinterpret a past send.
Configuration
Go to Loyalty and Promotional engine → Discounts and open or create a discount. The redemption method is set in Step 3 → Effect → Redemption.
For the full creation flow, see Create a Discount Campaign.
:::note Legacy engine If your company uses the legacy engine, see Legacy Engine → Create a Coupon. In the legacy engine, the Coupon contains the offer definition — the concept is different. :::