Message Token Reference

Dino Discounts lets you write shopper-facing copy with tokens — short [bracketed] placeholders the storefront swaps for live values at render time. A single string like [ccy][amount_discount] off when you spend [ccy][threshold_reached] renders as “£5 off when you spend £50” for one shopper and “€5 off when you spend €50” for another, with no per-currency re-save.

Each surface has its own token vocabulary — a token that works on one surface does not necessarily work on another, because each is substituted by its own engine code. On top of those, a set of rule-level tokens works the same on every per-discount surface. The checkout notice takes no tokens at all.

Surface	Where it shows	Edited in
Cart label	The discount line in the cart and at checkout	Messaging → Cart label
Spend-more nudge	”Add more to save” prompts in the mini-cart, cart, and checkout	Messaging → Spend-more nudge
Product-page custom message	A custom line on the product page (Custom Message display mode)	Messaging → Product page
Doesn’t-qualify message	The notice when a shopper types this rule’s coupon code but the cart doesn’t qualify	Messaging → Doesn’t-qualify message
Message Settings wording	Removed-reward row, coupon rejections, express-pay decline	Message Settings tab

Tokens are honest by design

A token only renders a value when the rule actually supplies one. If a token doesn’t apply to the current rule, the storefront strips it rather than showing a literal [token] to the shopper — and the editor’s chip toolbar only offers the tokens that will resolve for the rule you’re editing. The one exception is a hand-typed token the engine doesn’t recognise (a typo like [amount]) on the cart label: it renders literally so you can spot and fix it, and the editor warns you about it.

Cart label tokens

The cart label is substituted by the engine (AbstractStrategy::replace_placeholders) at the moment the cart line renders. There are two value slots plus the currency token. Each slot has several interchangeable spellings — a generic name, and descriptive names chosen per discount type by the chip toolbar. The chip toolbar also appends the rule-level tokens the rule supports.

The two value slots

Slot	Spellings (all interchangeable)	Resolves to
Currency	[ccy]	The shopper’s checkout-currency symbol (£ / € / $)
Primary value	[discount_value], [percentage_discount], [amount_discount]	The rule’s primary number — percent value or fixed amount
Secondary value	[second_value], [threshold_reached], [quantity_reached]	The rule’s secondary number — the spend / item-count threshold crossed

The descriptive spellings ([percentage_discount], [threshold_reached], …) are pure aliases of the same two slots — they exist so the chip toolbar can name the value for what it actually represents. The engine treats every primary spelling identically and every secondary spelling identically; there is no data migration when a rule is saved with one spelling or another.

What each spelling renders

Token	Renders	Example
[ccy]	Checkout currency symbol	[ccy]10 off → “£10 off”
[percentage_discount]	The percent number (no %)	[percentage_discount]% off → “15% off”
[amount_discount]	The fixed-amount number (no symbol)	[ccy][amount_discount] off → “£5 off”
[threshold_reached]	The spend threshold crossed (money)	spend [ccy][threshold_reached] → “spend £50”
[quantity_reached]	The item-count threshold crossed	[quantity_reached]+ items → “5+ items”
[discount_value]	Generic primary value (used in the recipe seeds)	[discount_value]% Discount → “15% Discount”
[second_value]	Generic secondary value	[discount_value]% off over [ccy][second_value] → “10% off over £50”

Which tokens the toolbar offers per discount type

The chip toolbar offers only the tokens that resolve for the rule’s shape, so you never insert a placeholder that the engine will strip. (You can still hand-type any spelling, but a cross-type token resolves to this rule’s slot value, so prefer the chips.)

Discount type	Tokens offered
% off cart (no threshold)	[percentage_discount]
Fixed $ off cart (no threshold)	[ccy], [amount_discount]
Spend & Save — % off at a spend threshold	[ccy], [percentage_discount], [threshold_reached]
Spend & Save — fixed $ off at a spend threshold	[ccy], [amount_discount], [threshold_reached]
Volume / bulk — % off at a quantity threshold	[percentage_discount], [quantity_reached]
Volume / bulk — fixed $ off at a quantity threshold	[ccy], [amount_discount], [quantity_reached]
Free shipping / free gift	none
Bundle (Buy X Get Y, Mix & Match) — money reward (bundle price / amount off)	[ccy]
Bundle — non-money reward (%, free items, free gift, free shipping)	none — the label needs no token

Why some types offer no [ccy]

The currency symbol is only offered when a money value actually renders — a fixed-amount reward, or a spend threshold. A percentage-only or quantity-only rule renders no currency, so [ccy] is withheld. A bundle’s cart label binds no value tokens at all, so only [ccy] is offered, and only for a money reward.

If you leave the cart label blank, Dino builds a default label from the reward (e.g. “10% Discount”, “Bundle deal”), falling back to “Discount” — never the internal coupon code. See Cart Labels for the editor walkthrough.

Rule-level tokens

These tokens read the rule’s own settings rather than the cart, so they render the same on the cart label, the spend-more nudge, the product-page custom message and the doesn’t-qualify message. Each surface’s chip toolbar offers one only when the rule carries the setting it reads; a hand-typed one the rule can’t fill is stripped.

Token	Renders	Offered when
[items]	A short description of the items the rule matches — each item group’s label if you set one, otherwise its category, tag, attribute or SKU names (or “items” for any item). Up to four, comma-separated	The rule is scoped to items
[start_date]	The scheduled start date, in your site’s date format and timezone	The rule has a scheduled start
[end_date]	The scheduled end date, in your site’s date format and timezone	The rule has a scheduled end
[end_time]	The scheduled end time, in your site’s time format	The rule has a scheduled end
[min_items]	The minimum item count the rule requires	The rule has an item-count threshold
[min_spend]	The minimum spend the rule requires, formatted as money	The rule has a spend threshold

Example: Ends [end_date] at [end_time] → “Ends October 31, 2026 at 11:59 pm”.

Spend-more nudge tokens

The nudge is substituted by SpendMoreNudge::resolve_placeholders. It only fires on rules with a threshold the shopper can move toward — Spend & Save (tiered), volume (bulk), any discount gated by a Cart subtotal at least spend threshold, and a BOGO or bundle deal with a single set (BOGOF, Bundle), which counts down to a full set. A discount with no threshold has no gap to nudge toward, and a deal with two or more sets (Mix BOGOF, Meal deal) doesn’t nudge, so no nudge renders for either. See Which discounts can nudge. The chip toolbar also appends the rule-level tokens the rule supports.

Token	Renders	Example
[amount_left]	How much more is needed to reach the next tier. Formatted as money on a spend (cart_subtotal) rule, as an integer on a quantity rule	Spend [amount_left] more → “Spend £15.00 more”
[qty_left]	Items still needed to reach the next tier, or to complete the set on a BOGO or bundle deal — always an integer	Add [qty_left] more → “Add 2 more”
[next_tier]	The next threshold value the shopper is heading toward — the target spend (money) or item count, not a reward description	Reach [next_tier] → “Reach £50.00”
[discount_label]	The complete, kind-agnostic reward label	for [discount_label] → “for 10% off” / “for Free Shipping”
[discount]	The bare reward number — no % or currency unit, so you supply your own	for [discount]% off → “for 10% off”
[discount_value]	Synonym of [discount] — same bare number, descriptive spelling	[discount_value]% off → “10% off”

[amount_left] vs [qty_left]

On a spend rule, [amount_left] is the money gap (“£15.00”), while [qty_left] would print that gap as a bare whole number (“15”) — so use [amount_left]. On a quantity rule, use [qty_left]. The editor greys out the chip that won’t resolve for the rule’s tier kind and shows an inline warning if you type it anyway.

[discount] is a bare number on purpose

[discount] and [discount_value] render the number only (“10”), so you can write the unit yourself: [discount]% off → “10% off”. If you want the whole label without writing the unit, use [discount_label] instead — that’s what the default templates use.

Defaults (the exact copy rendered when an input is left blank):

• Mini-cart: Spend [amount_left] more for [discount_label]
• Cart & checkout: You're [amount_left] away from [discount_label]. Add a few more items to your cart.

See Upsell Messages for the editor.

Product-page custom message tokens

When the Product page block’s display mode is Custom Message, the message is substituted by StorefrontDisplay::replace_placeholders. The block’s chip toolbar offers the same descriptive vocabulary as the cart label, named per discount type, plus [price] and the supported rule-level tokens. Tokens are case-insensitive — [price] and [PRICE] resolve identically.

Token	Renders	Example
[buy_quantity]	Bundle size — the total units one bundle needs (Buy X Get Y, Mix & Match)	Buy [buy_quantity] to save → “Buy 3 to save”
[percentage_discount] / [amount_discount]	The first tier’s reward value (Volume / Tiered)	Save [percentage_discount]% → “Save 15%“
[price]	This product’s price, formatted in the store’s currency	Just [price] each → “Just £20.00 each”

What the primary value token resolves to depends on the discount type (the chip toolbar offers the spelling that matches — [buy_quantity] for a bundle size, [percentage_discount] / [amount_discount] for a reward value):

Discount type	Primary value resolves to
Bundle (Buy X Get Y, Mix & Match)	The total units one bundle needs (sum of the item groups’ quantities, via [buy_quantity])
Volume / bulk, Tiered / Spend & Save	The first tier’s reward value ([percentage_discount] / [amount_discount])

The product page has no secondary value: [threshold_reached], [quantity_reached] and [ccy] are not offered and render blank if typed.

See Product Page Pricing for the display-mode and position controls.

Doesn’t-qualify message tokens

The Doesn’t-qualify message (shown when a shopper types this rule’s coupon code but the cart doesn’t qualify) takes only the rule-level tokens — e.g. Spend [min_spend] or more to use this code → “Spend £50.00 or more to use this code”. Leave it blank to use the store-wide default set on the Message Settings tab.

Message Settings tokens

A few store-wide messages on the Message Settings tab take one token each:

Token	Where	Renders
[label]	Removed-reward wording (Removal & restore)	The removed discount’s cart label — default [label] - removed
[name]	Express-pay decline (Apple Pay / Google Pay)	The declined discount’s name
[code]	The Coupon rejection messages (type it — there’s no chip)	The code the shopper typed, in capitals

A note on multi-currency and language

Every money token ([ccy], [amount_discount], [threshold_reached], [amount_left], [next_tier], [min_spend], [price]) resolves against the shopper’s checkout currency, not the store’s base currency — so one rule’s copy reads correctly in every currency without a separate rule per region.

Tokens are locale-neutral: they substitute the same way regardless of the language you type the surrounding copy in. For multilingual stores, model each language as a separate rule scoped with Zone targeting — see Cart Labels → Multilingual stores for the pattern.

What’s next

• Cart Labels — the cart-line label editor
• Upsell Messages — the spend-more nudge editor
• Product Page Pricing — the product-page display block
• Testing with Cart Preview — confirm your tokens resolve before publishing