Skip to content

List · reads coupon

Coupons

Discount codes.

One row per item, the plainest possible view.

The trade code used three times in a season is a partnership that needs a phone call.
  • AUTUMN2020% off
  • BELLEVUE€15 off, trade
  • WELCOME1010% first order
  • SUMMER2525% off

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Redemptions against the limit, so a code doing nothing and a code being abused stop looking identical.

An expired code stays visible with its final count instead of vanishing, which is what makes the next promotion easier to price.

The agent applies a code when it is mentioned, and says why one does not apply rather than ignoring it.

Per-partner codes turn a discount into a measurement of which partnership is working.

How it works

  1. 1

    A code is created with a discount, a limit and an expiry.

  2. 2

    Redemptions are counted as the agent applies it.

  3. 3

    An expired code stays visible with its final count, which is what makes the next promotion easier to price.

  4. 4

    The agent explains why a code does not apply rather than ignoring it.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
CoderequiredtextThe string a customer types at checkout, stated when the promotion is set up.
DiscountrequiredtextWhat it takes off, as a percentage or an amount.
UsedrequiredtextRedemptions against the limit. Doing nothing and being abused look identical without it.
ExpiresrequiredtextWhen it stops, or No limit. Both are real and one is riskier.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • No per-customer restriction, so a code can be shared publicly whatever the intent.
  • No stacking rules — behaviour with two codes is undefined.
  • No automatic expiry enforcement beyond the date.
  • Nothing attributes revenue to a code beyond the redemption count.

Before it works

What you have to provide, if anything.

  • Set a limit even on an internal code. An unlimited code is one screenshot away from being public.
  • Pair with Segments if the discount is meant for a particular group.

In practice

A roaster running a seasonal discount and a separate code for stockists.

Twenty percent off until the end of October, two hundred uses.
What was said to the agent

What the agent built

A code with a limit and an expiry, and a count that rose as it was used.

What changed

The seasonal code reached 84 of 200. The trade code, live all season, had been used three times — by one stockist who turned out to be the only one who knew it existed.

Questions

What data does the Coupons page use?

It reads coupon records the agent has collected. Discount codes. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ