Time & attendance systems
The gatehouse verifies that the arriving person is an employee and logs their arrival. No more double record-keeping or disputes over who arrived when.
Connectivity
Integration with your systems
A gatehouse that can't tell who's an employee is just a more expensive barrier. The real value appears once the system connects to what already runs in your company.
What we connect to
The most common integrations
Transport planning (TMS)
A registered carrier is passed to the time-slot system and receives a gate and a position in the queue. An unregistered one is processed at the kiosk. Dock scheduling itself is handled by the the logistics module.
ERP and WMS
Passing on delivery, delivery-note and reference-number data so the driver doesn't have to retype anything by hand.
Weighbridges
Linking each weighing to a specific passage and delivery note — the weight ticket is generated automatically.
Access control (ACS)
Passing the rights of an issued card to your existing access control system, if it offers a usable interface.
Outlook and calendars
A visit invitation as a calendar event that the host accepts the usual way.
How we do it
Verify first, promise second
Integration is where projects most often fall behind — usually because it was taken for granted in the quote, and only during delivery did it turn out that the other side has no usable interface.
We do it the other way round. Before we offer an integration, we want to see the other side's interface documentation and know who is responsible for it on your side. If the interface doesn't exist, we say so straight away and propose another route — for example a regular file import instead of a live connection.
We handle custom interface development as a separate line item, not hidden in the licence price. That way you can see what the integration costs and decide whether you want it now or in a second phase.
What we need to know
- Which system and which version you run
- Whether it has a documented interface
- Who is responsible for it on your side
- What data should flow in which direction
- How often they should synchronise
For integrators
An open machine interface, not a closed box
The system has machine interfaces (APIs) secured by both an API key and a token: an external gate, kiosk or barrier can report a vehicle entering, query authorisation by licence plate or control passage. Thanks to this we can also connect to gates, barriers and kiosks that are already on site — there's no need to replace the whole infrastructure because of us.
We take the same approach to a third-party access control system: through the interface we exchange identities, cards and permissions in both directions — we don't replace the system, we complement it. Where it makes sense, we also pass on the safety briefing status, so that someone without a valid briefing can't even reach the gate.
The rule stays the same as with any other integration: check the other side's interface first, promise second. The open API is our side of the bridge — the counterpart has to have the other side too.
What the API makes possible
- Reporting an entry from a third-party gate or kiosk
- Querying authorisation by licence plate
- Two-way exchange of cards and permissions
- Complementing, not replacing, your existing ACS
- Secured by an API key and a token (JWT)
Frequently asked questions
What people ask most often
Can you connect to our ERP or WMS?
Yes, integrations with enterprise systems are a standard part of the delivery — orders and dispatch advices from your ERP/WMS can drive who the gatehouse expects. We build the interface to fit your system, not the other way round.
Can you integrate with a time & attendance system?
Yes, passing through a turnstile is written straight into attendance. We have several time & attendance integrations in operation and the API is our own, so you don't wait on a third party.
Do you have a public API for our developers?
The system has an M2M interface — reporting a vehicle, querying the schedule, granting site access — secured by an API key. We provide the documentation with the project; the scope of the interface grows with every integration.
Interested in integration with your systems?
Describe how things work at your site today. We'll come back with a proposed scope and a price — or start by building your specification in the configurator.