Your till
Checking…Programme figures
Computed from your own ledger and receipts. These are the numbers the assistant is allowed to talk about, and the only ones it ever sees.
| Measure | Value |
|---|
Earn rules
Live. No release, no downtime, and members see the change the next time their app refreshes.
A voucher with no end date never leaves your books, so you can never tell what the programme actually owes. 90 days is long enough not to feel mean. Set it to 0 if you would rather make no such promise, and members are told the date either way.
Two kinds of deadline, one setting. A reward they could claim that is about to stop being offered, and a voucher they already hold that is about to run out. Reminders go once each, and one notification however many things are closing. A voucher already earned is also flagged in the app itself, so a member who never allowed notifications still sees it. Set the days to 0 to send none: a programme nobody mutes is worth more than one that interrupts.
Points per £1 multiplied by what a point is worth gives what your programme costs you. Ten points per £1 at 1p a point is 10% back, which is generous for most shops. One point per £1 at 1p is 1%.
Bring a friend
Every member gets a code to share. Both sides are paid the moment the friend joins, so your staff can point at it working while somebody is at the counter. Set either figure to 0 to switch that side off, or both to 0 to switch the whole thing off.
Paying on a join means paying for an email address rather than for a customer, so the limit matters. Somebody who can produce sign-ups will produce them. If you would rather pay for custom, keep the friend's bonus small and the limit low: the code still gets shared, because the person sharing it is doing it to help a friend.
The visitor reward rewards frequency rather than basket size. A visit is a distinct day with a purchase, so several sales in one day count once. Set visits to 0 to switch it off.
Rewards
What your points can be exchanged for. Money off is the obvious one and the most expensive: the rewards members value most often cost you very little, like something only members can do.
Promotions
Customers see changes instantly. A boost is never stacked with a standing category bonus: the better of the two applies.
Assistant
Checking…
It drafts wording from your figures and your brand voice. It never sees member names, emails or card numbers, it cannot change points or prices, and nothing it writes goes live until you save it.
Appearance and sign-up
App look
Change how your member app looks. Your colours and name stay the same; this changes the layout and feel. Members see it the next time their app refreshes.
Sign-up QR code
Print this and put it where people pay. Customers scan it with their phone camera and join in under a minute, with no app to download.
What you ask members for
Signup stays fast on purpose. Anything set to "in the app" is asked later, where a member has time and a reason to answer. Fields set to "at signup" are required on the join form and will cost you some completions.
| Field | Where |
|---|
Preference chips (what members can pick in the app)
Chips drive offer personalisation and push-notification targeting. Removing a chip doesn't delete it from members who already picked it, it just stops being offered.
Messages to members
Checking provider…
| When | Type | To | Channel | Status |
|---|
Login codes, welcome messages, receipts and reward alerts are transactional and always sent. Marketing goes only to members who opted in.
Demo tools
Demo tools
Seed creates three members with purchase history, a return and an activated offer. Reset wipes every member, point and receipt in this programme, and cannot be undone.
Members
How sales reach your programme. Either your till system sends them, or Square sends them for you. Nothing here changes what members see.
If you use Square
Square
Connect your Square account and every sale earns points on its own. Your staff carry on as they do now: they add the customer to the sale in Square, which is the same button they already use. Nothing else changes and there is nothing to install on the till.
You will need four things from your Square developer console at developer.squareup.com. This takes about ten minutes and you only do it once.
- Sign in with the same Square account your till uses.
- Create an application, then open it and copy the access token and the merchant id.
- Add a webhook subscription. Paste the address below as the notification URL, and subscribe to payment.updated, refund.updated and oauth.authorization.revoked.
- Copy the signature key Square shows for that subscription.
Your token and signature key are stored for your programme only and are never shown again, not even to you. If either is ever exposed, replace it in Square and connect again.
If you sell online too
Shopify
Online orders earn points on the same balance as your shop, and a refund takes them back. There is nothing to install, no app to approve and no access token to hand over: Shopify's order message already contains everything we need.
In Shopify, go to Settings, then Notifications, then Webhooks. Add two webhooks, both format JSON, both pointing at the address below: one for Order payment and one for Refund create. Shopify then shows a signing secret once. Paste it here with your shop address.
Use the address ending in myshopify.com rather than your own domain: that is the one Shopify sends with every message.
If you use any other till
Letting members spend rewards on your website
Optional, and separate from the above. Earning needs nothing from you beyond the two fields. Spending needs one permission, because only Shopify can create a discount.
Checking…
What your supplier needs
Your programme has an open contract that any till system can use. Hand your supplier these two values and the guide, and they can build it without involving us or you. This is the same whichever of the two ways below you use.
Then choose one of the two below. The difference is who holds the credential: one for each till, or one for the whole programme.
A credential for each till
Every till gets its own credential, so you can switch one off without touching the others. You do not set them up one by one: you send the same file to all of them and each one sets itself up the first time it runs.
Or one credential for everything
One credential for the whole programme, which you hand to your supplier yourself. Use it if a single back office system sends all your sales, or if your supplier has already built against it. Sales only say which branch they came from if the sender names one, and replacing this credential stops every till at once.
Checking…
This is the secret a till signs its calls with. It is shown once and never readable again, by you or by us, so replace it rather than hunting for it. Replace it whenever an integrator leaves, a device is lost, or it has been sent somewhere it should not have been.
Your admin key
This key opens your console and shows your member list, so treat it like a password. Replace it whenever someone who had it leaves, or if you think it has been shared too widely. The old key stops working the instant you do.
People who only need to look
Your admin key can change everything, so handing it to a manager hands over the earn rate, your member list and your tills. Give them their own key instead: they see every screen and can change nothing. Looking a member up at the counter still works. Downloading the whole member list does not.
One key each, so when somebody leaves you withdraw theirs and nobody else notices. Each one stops working after 90 days whether you remember or not, and you can renew the ones still needed in a click.
Change history
Every change anyone makes to your programme, including changes we make as your platform provider. Kept permanently and cannot be edited, so you can always answer the question "who changed the earn rate".
| When | Change | What changed | By |
|---|