Targeting

Targeting controls when a discount fires. By default, a published discount applies to every cart from every customer. Four sections of the rule editor narrow that down: Who is this for? (which customers), When does it apply? (which dates, days and times), Where does it apply? (which zones and currencies), and What triggers it? (spend, weight or item thresholds, a coupon code, or matching items in the cart).

Each section is independent — combine any of them and the discount only fires when every section’s conditions are satisfied. The Summary box at the top of the editor reads the whole configuration back as a sentence, so you can sanity-check the combination at a glance.

---

Who is this for? — customer targeting

The Who is this for? section restricts the discount to specific customers.

Condition	What it checks
First-time customers	The customer has not yet placed a paid order (failed and pending orders don’t count)
Customers with N+ past orders	Reward repeat shoppers (e.g. at least 3 past orders)
Lapsed customers — N days since last order	Win-back: only customers who haven’t ordered in at least N days
Customers with lifetime spend ≥ amount	The customer’s total across all past orders, including tax and shipping. On a multi-currency store only orders in the cart’s currency count
Logged-in customers or guests	Logged-in only requires a customer account; Guests only targets shoppers without one
Customers in specific user roles	Matches any of the roles you pick — Customer, Wholesale, VIP, or any role your site or membership plugin registers. The row appears once your site has at least two customer roles

The default empty state is Anyone — every customer qualifies. Tick condition rows to narrow it down. Ticked conditions combine with AND.

Wholesale pricing without a separate plugin

Create a “Wholesale” user role in WordPress, then target volume discounts to that role. You get tiered wholesale pricing without any extra plugins.

---

When does it apply? — dates, days and times

The When does it apply? section offers a date window, days of the week, and a daily time window. The default is Always. See Scheduling for the details.

---

Where does it apply? — zones and currency

The Where does it apply? section restricts the discount by location and currency. Zones are defined on the Countries & Zones tab and can be reused across any number of discounts.

Condition	What it does
Customers in specific zones	Matches if the customer’s checkout country resolves to any selected zone. Pick Auto ROW (Rest Of World) to cover every country outside the zones you have defined
Applies in currency…	Only fires when the cart’s currency is one of the currencies you pick. Use it to scope a money-amount discount to one currency on a multi-currency store

The default empty state is Anywhere — every checkout country and currency is in scope.

Common uses:

• Stronger discounts for price-sensitive markets
• Region-exclusive launch offers
• Currency-specific promotions on a multi-currency store

See Countries & Zones for setup.

---

What triggers it?

Leave What triggers it? empty and the discount is Auto-applied — it fires whenever the cart matches the other sections. Tick one or more triggers to add a cart condition:

Trigger	Behaviour
Cart reaches spend, weight, or items threshold	Set one or more of Cart subtotal at least, Cart weight at least, Total items at least (total quantity) and Distinct items at least (different products — 2 of the same counts as 1). The cart must meet every threshold you set. The subtotal is compared before any other discounts apply
Type a coupon code at checkout	The customer must enter a code from one of the coupons you pick — links the discount to a coupon. Codes match case-insensitively
Cart contains matching items	The cart must contain the item sets you define, each with its own required quantity — see Item sets below

Ticked triggers combine with AND, so you can make a code that only works above a certain order value. The When does it apply? section interacts with this too — see Scheduling for time-bounded coupon windows.

Coupon vs automatic

Without a coupon trigger, the discount applies silently when conditions are met. With one, the customer must enter the code to unlock it. You can combine coupon activation with any other targeting — for example, a code that only works for orders over £50 from new customers.

Why use Dino’s coupon-activation instead of a plain WooCommerce coupon?

A plain WooCommerce coupon can only apply a simple discount. Dino’s coupon-activated discounts can layer the full rule editor on top: customer targeting, zones, schedules, the rich reward structures (tiers, BOGO, bundles), and any other conditions. The customer experience is the same — they enter a code — but the logic behind it is far more powerful.

Allow stacking with WooCommerce coupons

Below the triggers, Allow stacking with WooCommerce coupons decides whether this discount still fires when the customer has applied a plain WooCommerce coupon. When it’s off, the discount steps aside while a WooCommerce coupon is on the cart. The store-wide setting on Global Settings overrides this when it suppresses all Dino discounts, and a WooCommerce coupon set to “Individual use only” blocks every discount while it is applied.

---

Item sets — which items count

Product scoping is built from item sets. On the trigger side, tick Cart contains matching items and define the sets under Which items qualify the rule?. Each set has:

Field	Options
Eligible set	Category, Tag, Attribute, List of SKUs, or Any item
Qty required	How many matching items the cart needs

Add more sets with + Add another set. All sets must match — they combine with AND.

The set editors on the reward side — in BOGOF, Mix BOGOF, Bundle and Meal deal discounts, and under A specific set of items — also have a Matching choice: Any mix from the set, or All the same item (either Same product, any variation or Same exact variation (SKU)).

On the reward side, the Rewards section’s What the discount applies to picks between The items that triggered the rule and A specific set of items, so you can trigger on one set and discount another.

Targeting by category or tag

Targeting a category automatically includes any products you add to that category later — you don’t need to update the discount when your catalogue changes.

Why some discount types behave differently

The answer comes down to where the discount is applied:

Order-level discounts (% off the cart, amount off the cart) reduce the cart total as a whole. Item sets on the trigger control eligibility — whether the discount fires — but the reward itself lands on the order, not individual items. For example, you can make “10% off orders” require that the cart contains at least one item from a specific category, but the 10% applies to the entire order total.

Item-level discounts (% off matching items, amount off matching items, volume pricing, BOGO, bundles) operate directly on line items. The discount only applies to the qualifying items, leaving other cart items untouched.

---

Usage limits — how many times it can be redeemed

Inside What triggers it?, Limit Uses caps how many times a discount is redeemed:

Limit	What it caps
Total uses	The number of redemptions across your whole store. Once it’s reached, the discount stops firing for everyone. If an order is cancelled, fully refunded or fails, its use is given back. A partly refunded order keeps its use.
Per customer	The number of redemptions per customer. Once a customer hits it, the discount stops firing for them. Counting starts when you enable the limit — orders placed before you set it are not counted.

The limit applies to each discount separately — a customer who uses up one discount can still qualify for others. If the discount is triggered by coupon codes, each code’s own redemption limit is set on the coupon. Reset usage for this discount clears both counters, which is handy after testing a small cap.

How “per customer” identifies a customer

A signed-in shopper is always identified by their account. Guests have no account, so under For guests, match by → Match by email address a guest is identified by the billing email they enter at checkout (lower-cased and trimmed; otherwise treated exactly as typed). A signed-in customer and a guest who use the same billing email are counted as one customer — so someone can’t reset a one-per-customer limit just by checking out as a guest with the same email they used while logged in (it works in both directions).

The default, Treat every guest as first-time, does the opposite: every guest checkout is treated as a brand-new customer, so the per-customer limit only ever constrains signed-in accounts.

Guest matching is best-effort — and what to do about it

Matching guests by billing email is a deterrent, not a guarantee. A guest can enter a different email address and claim the discount again — there is no reliable way to tell that two guest checkouts are the same person. If you need a limit that cannot be worked around, use the Total uses cap: it counts every redemption store-wide and always holds.

A customer said they were wrongly refused a “one per customer” discount

Billing email is not unique — two genuinely different people can use the same billing email (for example, a shared household address, or one person ordering on another’s behalf). Under Match by email address, once that email has claimed a per-customer-limited discount, the next order on the same billing email is refused — even if it’s a different person. This is expected behaviour of matching by email, not a bug.

If a customer contacts you about this, you have two options: switch that discount’s guest handling to Treat every guest as first-time (which stops matching guests by email at all), or keep the email matching and rely on the Total uses cap for the hard ceiling. There’s no way to both match guests by a shared email and tell the two people apart.

---

How sections combine

A discount fires only when every section’s conditions are satisfied. Conditions inside a section combine with AND — e.g. “Logged-in only AND lifetime spend ≥ £100” — so each tick narrows the audience further.

Where a single condition takes several values — user roles, zones, currencies, days of the week — any one of the picked values qualifies:

User role is Wholesale OR User role is VIP

For more complex combinations — “(Role is Wholesale OR Role is VIP) AND lifetime spend ≥ £100” — file a request.

The Summary box at the top of the editor renders the combined logic as one sentence — useful for catching mistakes before you publish.

---

How targeting interacts with stacking

When multiple discounts target overlapping product sets, each discount applies to its qualifying items independently. The stacking mode controls what happens when a single item qualifies for more than one discount.