Overview: venue
One period, one picture. Each block below is one of the things this venue runs, and each separates what is true RIGHT NOW from what MOVED during the period.
Guests of the reservation system across every venue of this group, grouped into people by e-mail or phone. A match with one of your customers is a suggestion, never a merge.
Everyone the reservation system knows, across every venue of this group, grouped into people by e-mail or phone. How many of them you can actually write to, and how many already have an account.
A segment is the question, not the answer: the people in it are worked out again every time you open it. Someone who starts visiting a second venue joins on their own, and someone who asks not to be contacted leaves on their own.
Campaigns and templates have their own tabs now.
Pick a segment and a template, prepare the campaign and send yourself a test. Nobody receives anything until you press Send or schedule it.
The e-mails your campaigns send. A new template opens guided: choose a kind of e-mail and fill in the blocks; the venue's footer and the unsubscribe link are added for you.
Whoever is on this list disappears from every guest list and every export, across the whole group. It is kept by e-mail and phone rather than by record, so a resync or an erasure cannot bring someone back.
Search customers
New customer
Customer
Find a card
All cards: venue
Card detail
Issue a card
Batches
Activate at sale
Create a pre-printed batch
Invoices
New invoice
Discount profiles
Named discounts the till offers on its discount screen: the waiter picks "Company B (15%)" instead of typing the percentage. A change here reaches every till of this venue. A customer's account can carry one, so the till proposes it when it opens that account.
On the floor
Everyone whose last badge left them working or on a break, right now.
Register
Shifts belong to the day they started, so a night that crosses midnight stays one shift. Anomalies are reported, never corrected on their own.
Hours
Worked against expected, per week or per month. Lateness and absence need an expected week: set one under Staff, or those columns stay empty.
Staff
The people who badge in at this venue. They are not app users: badging needs no password.
Add an employee
Time-clock settings
Times are stored in UTC everywhere; the zone below only decides where the working day is cut. Coordinates are used to record how far a punch happened from here, and never to refuse one.
Expected week:
Leave a day empty to mean a day off. An end before the start reads as crossing midnight, so 22:00 to 02:00 is a six-hour night.
| Day | Start | End |
|---|
The addresses this venue uses
Every page the service serves, besides this one. Open one to check it, or send the address to the device that needs it.
My second factor
Modules
What this venue has. Only Pindot staff can change it: a merchant cannot switch on what they have not bought.
Users: venue
Active sessions
Create user
Integration keys
Generate integration API key (POS / machines)
Orders
Online gift-card shop: venue
Customers buy a card on your page and pay with YOUR payment contract. Nothing is issued until the payment is verified. Public page: /shop/…
Payment provider
Your own Saferpay contract: the money never passes through us. Credentials are write-only: they are never shown again. Status: —
Loyalty program: venue
Sign-up QR code
Put it on the tables or at the till. Guests scan it with their phone, create their account and become members of this venue: they collect points from their first order and carry the member card on their phone.
Rewards catalogue
Give points a goal with a name: this is what makes a programme feel worth joining.
Stamp cards
"The 10th coffee is free": one stamp per qualifying order.
Redeem a reward code
The guest shows the code from their wallet. Type it in to see what to apply: a code works only once.
A group is which venues belong to the same company. Inside one, a customer can open an account at any venue, the marketing module sees the guests of all of them, and, with a shared pool, a gift card issued by one is spent at any. Putting two venues together lets them see each other's customers, so only Pindot staff can change this.
Buyers on a venue's online shop pay a service fee on top of the voucher. That fee is Pindot's: the venue's payment contract collects it with the voucher, and Pindot invoices it to the venue once a month.
Before the first invoice, choose which Pindot site issues them and the VAT rate, under Settings at the bottom of this page.
1 · Invoice a month
The fees of the shop orders paid in that month (Zurich time), venue by venue. One invoice per venue and month.
2 · Send them and record the payments
Send each invoice to the venue by e-mail, and mark it paid when the money reaches Pindot.
Settings: who issues the invoices, VAT
Tenant settings: venue
Webhooks: tell your systems what happened
Instead of polling us, your POS or kiosk receives an HTTPS call the moment something happens. Every call is signed, retried if your endpoint is down, and carries a delivery id you can use to ignore duplicates.
Recent deliveries
Pindot registry: —
·
Group: — ·
guests' page: /wallet