Each program inside a tenant is its own pass: separate branding, separate audience, separate enrollment policy. You can run as many as you need — Dýrabær launches with two (Breeder Club and Food Club).
Click + New program on the loyalty home page. The fields:
breeder-club). Used in public form URLs.The pass designer is the source of truth for the card. When you change the logo, colors, or fields and save, the update reaches cards that are already on customers' phones — you don't re-issue anything. Google Wallet cards refresh automatically within a short window; Apple Wallet cards update on their next refresh.
Live updates to Google cards only happen once a tenant's Google Wallet class is configured under wallet credentials. Until then the design still saves, but there are no Google cards to update.
In a program's Settings you can set an optional Welcome message — a custom note shown in the "your card is ready" email, above the Add-my-card button. Use it to greet new members or explain what the card gets them. Leave it blank for the default wording.
On a program's page, Notify Google Wallet holders pushes a short message (title + body) to everyone who has saved that card to Google Wallet — it shows as a notification on their card. The count next to it tells you how many holders can be reached. Use it for relevant, occasional updates (a sale, a reward); for regular marketing, use your email/SMS list instead, since overusing wallet notifications gets cards muted. Apple Wallet messaging arrives with Apple support.
In Settings → Enrollment fieldsyou can add extra questions to a program's public signup form (e.g. a breeder name). Each answer is saved on the member and becomes a {customer.attr.<key>} token you can place on the card in the designer. You can also fill or edit these on a member directly in CRM → the customer → Custom fields.
Two toggles per program:
/enroll/{tenant-slug}/{program-slug}. Customers can sign themselves up on a kiosk iPad or any device. Disabled by default.Public forms are rate-limited per IP and have a hidden honeypot field, but a determined bot can still flood the queue. Watch the applications queue after enabling public enrollment — if abuse appears, ask Stokk to wire up captcha (planned for v1.1).
Toggle Active off to hide a program from the operator UI and 404 the public form. Existing pass holders are unaffected — the cards on their phones keep working until you revoke them.