Loyalty without a marketing team. Marketing without a second integration.
Issue Apple Wallet & Google Wallet passes for your members. Open enrolment or approval-required. Then segment and SMS — using the same customer, product and stock data your buyers already work with.
Sits on top of your ERP. Reads stock, writes transactions, never duplicates the source of truth.
Loyalty and marketing live in a separate world from inventory.
Most retailers run loyalty in one tool, SMS in another, and inventory in a third. The customer's segment doesn't know what's in stock. The buyer's plan doesn't know who's about to walk in. Stokk wires them together.
- Apple Wallet & Google Wallet passes signed under your tenant
- Open enrolment, approval-required, or operator-issued
- Bulk import from your legacy loyalty vendor (CSV)
- Customer auto-creation in your ERP if absent
- Segmented SMS to members, with E.164 phone normalisation
Capabilities, in plain language.
Wallet passes
Apple .pkpass + Google Wallet JWT generated under your tenant's credentials. Pass holders tracked with state (pending / active / revoked).
Branded design
Per-programme logo, colours and copy. UA-aware landing page detects iOS / Android and shows the right wallet button.
Enrolment policies
Open enrolment with a public form, approval-required for vetted programmes, or operator-only issuance. Approval queue for the gated programmes.
SMS campaigns
Queue-based sender, retries on failure, batch processing. E.164 phone normalisation handles international numbers cleanly.
Member segments
Segment by purchase history, last visit, lifetime value, tier. The same customer data Stokk already uses for forecasting.
Public unsubscribe
Hosted unsubscribe page with audit trail. GDPR-aligned, with a single source of truth for opt-out.
From members to messages.
What sending a campaign looks like, and how segments are built from the same customer data your buyers already work with.
- Gold · weekly visitors8,240
- Lapsed · 90+ days silent3,104
- Beauty · sample lovers1,822
- Furniture · high LTV612
The numbers Stokk customers report after the first cycle.
After the first full ordering cycle, lost-sale events on A-classified items roughly halve.
Buyers stop building proposals from scratch. The Brief lands; they review and approve.
Stokk's per-store sizing and lateral transfers free cash that was sitting on a pallet.
Continuous, offline-capable counts replace the once-a-year shutdown count.
Audiences that know what's in stock.
Stokk's customer-data layer is the same one used for forecasting and replenishment. When you message your members, the audience respects what's actually in stock at their nearest store — stops you advertising what you can't sell.
Member behaviour (visits, purchases, redemptions) feeds back into demand signals. The marketing team and the buying team are no longer two systems trying to get along.
How AI gets used here
Decisions stay explainable. Every recommendation has a written reason and a human approval step. Your data isn't used to train shared models. Claude's prompts are scoped per request.
Plays nicely with the systems you already pay for.
Common questions about this module.
Do we need our own Apple Developer account?
Stokk operates a tenant-level wallet credential model. We sign passes under managed credentials by default; bring-your-own-credential is supported.
Can we migrate existing loyalty members?
Yes. Bulk CSV import from any legacy vendor. Members keep their identifiers; passes reissue under your new programme automatically.
Which countries are SMS supported in?
Iceland is fully supported via Síminn. EU + UK delivery is rolling out via standard SMS providers in 2026.
Other parts of the operating system.
See Marketing on your data.
A 20-minute demo on your ERP, your SKUs, your stores. We do the work; you decide if it earns its place in your operating system.