Unified POS Platform
Everything Works Together.
Restaurant integration is the automatic exchange of POS data with systems such as accounting, ERP, payment, e-invoicing and ordering platforms. Kerzz connects food ordering channels, fiscal devices, e-invoicing processes and external systems to the restaurant operation through APIs and ready-built integrations.
A POS never works alone. Sales go to accounting, takings reconcile against bank statements, online orders enter the operation, e-invoicing runs, and in some setups data flows both ways with an ERP. Without those links, the work becomes someone manually matching two systems every evening.
Kerzz does not treat integration as an add-on bolted on afterwards. What matters is not that two systems exchange data, but that the exchange happens at the right point in the operation with clear ownership.
ERP · Accounting · FiscalYemeksepeti · Getir · Trendyol · MigrosRESTful API
ERP, accounting, payment, fiscal devices and ordering platforms in one operation.
How it works
Orders from supported channels such as Yemeksepeti, Getir, Trendyol Yemek and Migros Yemek are passed into the Kerzz operation and handled in the existing order flow. Instead of watching a tablet per channel, the order lands directly in the POS and kitchen flow. Supported channels and functions are confirmed per project.
See the platform pagesSupported fiscal devices and PIN pads work alongside Kerzz POS so the sale and the fiscal transaction move in one flow. Device compatibility is assessed against your existing hardware.
Card, meal card and online collection scenarios run on supported payment infrastructures. Integration scope depends on the bank or payment provider in use.
Your e-transformation processes connect to the restaurant operation through integration, with document creation and submission fed by sales data. Scope is settled according to the integrator service in use.
Sales, stock and purchasing data integrate with the ERP in use. Which data moves in which direction, how often and at what granularity is defined at the start of the project.
The sales and collection data accounting needs is passed to the relevant system, so period close does not wait on manual entry. Scope is assessed against the accounting platform in use.
Peripherals such as barcode scales, self-service kiosks, handheld terminals, barcode scanners and label printers join the operation. Compatibility is confirmed per device model.
Kerzz exchanges data with external systems over a RESTful API and provides API documentation. The data reached, the transaction scenario and the permission model are set by the technical requirement.
Who it is for
Buying guide
"Which system are we connecting?" is not enough on its own. Settle up front which system is the source, when data moves, which one wins on conflict or error, where the user action happens and who owns reconciliation. Kerzz plans integration projects in that order.
Frequently asked questions
Orders from supported channels such as Yemeksepeti, Getir, Trendyol Yemek and Migros Yemek are passed into the Kerzz operation; the current channel list is confirmed during the project discussion.
Yes. Sales, stock and collection data integrate with the ERP or accounting system in use; scope depends on the system and the workflow.
Yes. A RESTful API and documentation are available, and external systems can reach Kerzz data with defined permissions.
Not for supported models. Device compatibility is assessed against your existing hardware.
Let us plan the right setup for your business — you do not have to wait to start using it.