veydex

Integrations

Which till you run decides what Veydex can do.

Veydex Connect links existing till systems to the Hub. How well that works and which data comes across depends on the individual system — so we check it individually rather than keeping a list nobody redeems.

There is no list here yet. On purpose.

A directory of system names would take an hour to build. The damage would come later: a business reads its provider there, stops looking, plans around it — and only learns in conversation that the route does not exist that way. A name goes here once the connection actually runs.

What there is instead: five connection routes over which a link comes about at all, and an answer about your system — in writing, within one working day. Tell us below which one you run.

Compatibility

Does Veydex work with your till?

Tell us which till system runs at your place today. We will show you how Veydex can link it, which data is available and where the limits are.

Regardless of your till: Reservations · Shift plan · Phone AI · Documents · Hygiene & HACCP · Payments. They read no till data and work even if the system you run today cannot be linked.

Five routes over which a till gets connected

Which of them works for your system depends on manufacturer, version and contract. That is exactly the question we settle before you book — not after.

Cloud API

Your provider offers an interface and Veydex collects the data there.

OAuth

You grant access once inside your provider's account. We will not ask you for your till password.

Local connector

A small program on site reads the till when the till itself does not speak outwards.

Direct push

The till reports every closed transaction to Veydex itself.

DSFinV-K import

The legally required till export — which exists even on systems never built for a connection.