Programme rules

Card length, what a full card earns, which outlets share it, the features you can switch on, and the fine print behind every stamp.

Programme rules is where the loyalty card is defined: how long it is, what it earns, where it works and under what conditions a stamp is given.

The header says it plainly: changes go live on every guest card instantly. The screen holds your edits as a draft until you press Publish changes, and the line beside that button reads Unpublished changes until you do, then Live on every card · saved ….

Everything on this screen needs programme access to change. Without it you can still read the whole thing, and a line says so.

The first card

A tenant that has never set the card up sees No loyalty card yet, with one button: Create the loyalty card. It starts you on the standard card, eight stamps with the ninth on the house, and drops you straight into the editor to change any rule from there.

Base card

Linked outlets is a row of chips, one per outlet, each with a dot beside the name so the state is not carried by colour alone. An outlet that is not open yet is labelled as such. The header counts them: 3 OF 5 LINKED.

A guest holds one card per brand, not one per outlet. Stamps earned at any linked outlet land on the same card and a reward can be redeemed at any of them. There is no per-outlet balance to reconcile.

Outlets are not created here. The Add outlet chip explains why: new outlets appear on this list once they are added in Maska, because an outlet is shared with POS and Procurement rather than owned by loyalty.

Features

Four switches, each with the consequence written under it:

• Card is earning. Switch it off to stop new stamps. Banked rewards stay redeemable, so nobody loses a coffee they already earned.
• Welcome stamp. The first stamp lands the moment a guest joins, so a new card is never empty.
• Birthday reward. A treat you choose, during the member’s birthday month. Switching it on reveals a Birthday treat field for the wording. Switching it off keeps what you wrote, so turning it back on next year restores your own words rather than a default.
• Referrals. Both sides earn a stamp on the friend’s first visit. Switching it on reveals a Referral cap: how many stamps one member can earn from referrals in a month. Set the cap to zero and referrers earn nothing while the friend still gets their stamp.

Fine print

The rules that decide whether a visit earns anything at all.

The reminder is set as a lead, not a date, so moving the expiry moves the reminder with it and the two can never cross.

Terms

The last row takes paragraphs rather than a number. Whatever you write here is shown to guests when they join and in their wallet.

Above the box, and not editable, sits the one condition Maska always states on your behalf: rewards and stamps are issued and honoured by the venue, and Maska facilitates the programme without being responsible for a venue’s failure to honour or redeem a reward. It is always shown first, above whatever you write, and it is there whether you write anything or not.

Your own clauses go in the box, one rule per line.

Boosters

Under the settings cards sits Boosters: extra promos layered on the base card, for a weekend, a quiet hour or one drink that should earn faster. The counter reads 2 OF 5 LIVE.

With none running the section says No boosters running, and explains that the base card earns on its own: add one when you want a weekend, a quiet hour or one drink to earn faster.

Adding one

A row of dashed chips under the cards offers the presets:

A preset disappears from the rail once you have one of its kind. Custom booster never does.

Adding is immediate, because a booster is a row rather than a field: the card appears at once with a toast reading … added, live on publish. The two presets that need you to say what they fire on arrive paused, with the instruction to set the target and then switch it on. Removing is immediate too.

Everything else about a booster, its name, its rules and its on/off, is a draft and rides the same Publish changes button as the rest of the screen.

What a booster card holds

A name you can type over, a one-line mono summary of the whole rule (COLD BREW · SAT–SUN · 3–6 PM · 2× STAMPS · ONCE / DAY), an on/off switch, and rows of chips:

• On or Pair: the dish, the menu section, or the two sections a combo needs.
• Window or Days: 3–6 PM, 7–10 AM, 8–11 PM and a custom pair of times, or SAT–SUN, FRI–SUN, MON–FRI, ALL WEEK.
• Bonus: +1 STAMP, +2 STAMPS, 2× STAMPS, 3× STAMPS. The multiplying ones are not offered on a booster that fires on a specific dish or section.
• Cap: NO CAP, ONCE / DAY, ONCE / VISIT.

Pressing a chip replaces the whole rule rather than editing part of it, because you are choosing an outcome, not filling a form. A custom window cannot run past midnight.

Boosters sit outside the base stamp and carry their own caps, so the daily base cap does not hold them back.

A booster that is not finished blocks the publish, and the status line says A booster still needs finishing rather than letting you push a half-written rule to every card. The card itself names what is missing, for example “Pick the item this booster fires on.”

Boosters a campaign made

A double-stamps campaign creates a real booster while it runs. It appears here badged From campaign, read only, with the line Stop it from Campaigns. There is no name field, no chips and no Remove: it belongs to the campaign that made it. See Campaigns.