Integrations
Integrations with POS systems are released per POS as partnerships are confirmed.
How the connector works
Connect puts the restaurant's own ordering site next to the POS it already runs. The POS stays the source of truth; Eetloket talks to it. Here's how it will work once an integration is in place:
POS → ordering site
The menu comes from the POS
Items, prices and what's sold out come from the POS. You change the menu once, in the POS.
ComingOrdering site → POS → status page
Orders go in, the status comes back
A paid order from the site goes into the POS, and its status comes back to the guest's status page.
ComingPOS ↔ ordering site
One gift card balance
A gift card has one balance, online and at the counter.
ComingOrdering site → the POS's payment service
Payments through the POS
Online payments run through the POS's own payment service, so the restaurant keeps its own payment setup.
Coming
What the restaurant keeps
- Its POS, and the vendor behind it
- Its payment processing
- Its reports and end-of-day, in the POS
What Eetloket adds
- An ordering site and app of its own, on the restaurant's own domain
- Measurement after consent: which visit and which campaign led to an order Coming
- Campaigns and promotions on its own site Coming
With an ordering site of its own, the restaurant decides what gets measured and which campaigns run on it.
Which POS systems?
Integrations are released one POS at a time, as each partnership is confirmed. None is confirmed today, which is why we name none here.
The demo request asks which POS you use. That shows us where the demand is, and which integration comes first.
Request a demo and tell us your POSWhat exists today
- Built
Partner API
Orders arrive exactly once, even when a partner retries a request. Webhooks are signed to the Standard Webhooks spec, and the API is described in OpenAPI.
- Built
Consent first
The ordering site uses Google Consent Mode v2: all measurement stays off until the guest chooses.
- Being built
The ordering site's measurement layer
Tags that follow that consent, and a visit's UTM values saved with the order.
- Coming
POS integrations
One POS at a time, as each partnership is confirmed.
For partner teams
What's under the hood, for anyone reviewing an integration:
- Multi-tenant from the ground up: one tenant per restaurant, with its own domain and its own data, separated row by row in the database.
- Six roles, fourteen rights per person, and two-factor sign-in.
- A journal that only grows: entries are added, never changed, and chained per register with a SHA-256 hash.
Work at a POS vendor and want to talk about an integration? Use the demo form; 'A partnership as a POS vendor' will already be selected.
Get in touch as a partner