LOOOK and custom integrations
LOOOK is the case missing from every list of ready connectors: the chain wrote its own POS for its own processes, and we connected to it. If you run custom software or a till nobody supports, an integration is still possible — it is simply built for you.
When a custom integration is needed
Three situations come up most often. First, in-house development — a chain outgrew boxed solutions and wrote its own accounting, as LOOOK did. Second, a rare or local till missing from integrator lists. Third, not a till at all but an ERP or warehouse system that needs the orders.
In all three the question is the same: does the system expose an API.
What is transferred either way
The data set does not depend on whether the till is boxed or bespoke. Your system receives the complete order; menu, prices and stop-lists come back so you do not maintain two catalogues.
How the timeline works
A boxed integration connects in a working day. A custom one takes longer, depending on what exists on your side: a documented API, an undocumented one, or nothing at all.
The first step is free either way: show us the system and its exchange interface, and we will say what is technically possible.
FAQ
We have our own POS. What does integration cost?
It depends on the work required on your side, so we quote after looking at your exchange interface. The assessment is free.
What if our system has no API?
Then we look at what does exist: direct database access, file exchange, an intermediate service. A way is not always there, but more often than you would expect.
Who maintains a custom integration afterwards?
We do. Once live, a custom integration is maintained like a boxed one and covered by the same 24/7 support.