Custom MplusKASSA integration development
MplusKASSA is a Dutch point-of-sale system for hospitality and retail, with a large number of standard integrations and an API for partners. Via that API, you can retrieve products with stock levels, request sales figures and place orders in the till. Appfront builds the integration with the systems that are not on the standard list, such as your own app, ERP, purchasing or reporting.
What is a MplusKASSA integration?
MplusKASSA is a Dutch point-of-sale system widely used in hospitality and retail, from restaurants and cafés to shops with multiple locations. It has a long list of standard integrations, for example with staff scheduling tools, accounting packages and ordering platforms. For anything not on that list, MplusKASSA offers an API for partners, with its own developer portal.
Whatever is not covered by the standard integrations is often done by hand. Sales figures per location are exported and placed in a spreadsheet next to purchasing. Orders from your own app or website are retyped into the till. And stock in the shop and in the warehouse drift apart, because the ERP only sees sales later.
We build it custom because every business is different: one location or a group, which systems sit alongside, and which data needs to go where. Via the API, products with stock levels can be retrieved, sales figures can be requested and orders can be placed in the till, and with webhooks an integration can respond to what happens at the till. Access to the API runs through a partnership with MplusKASSA; we arrange that in the first step.
Revenue in one place
Sales figures per location in your systems.
Orders in the till
From your own app or website, without retyping.
Via the API
With partner access at MplusKASSA.
How we build your MplusKASSA integration
We start with your business: which systems you use alongside MplusKASSA, which data is currently handled by hand, who needs to see what, and whether your system might already be on the standard list. Then we arrange access to the API and define which data flows in each direction. We often start with sales figures per location going to the ERP or reporting, because that immediately saves manual work and carries little risk. Orders from your own app and two-way stock follow once the first integration is running well. After that, we maintain the integration when the API or your own systems change.
Systems, data and who needs to see what.
Partner access to the API.
Revenue, orders and stock, with checks.
Go-live, monitoring, and maintenance when things change.
What a MplusKASSA integration actually does
The components below appear in almost every MplusKASSA integration. Which ones you need depends on your business and systems.
Sales figures
Per location and day.
Notes
To the accounting system.
Orders
From app or website.
Stock
Till and warehouse.
Webhooks
Responding to the till.
Log
Every message recorded.
Who we build a MplusKASSA integration for
The integration is intended for businesses that use MplusKASSA alongside systems that are not on the standard list. The more locations and systems you have, the more time it saves.
Hospitality groups
Multiple locations. Comparing figures side by side matters.
Restaurants with an app
Your own orders. Getting orders into the till matters.
Retail chains
Your own ERP. Accurate stock is the core.
Software suppliers
A product for hospitality or retail.
Technology and integrations
This page covers integrations with MplusKASSA. For a custom point-of-sale system, see our page on POS software; for staff scheduling alongside the till, see our page on the Eitje integration; and for your own hospitality app, see our page on hospitality apps. You can read about our approach on building software.
Why Appfront for your MplusKASSA integration?
Revenue exported per location, and orders retyped into the till, cost a hospitality business or shop time and errors every week. That's what we build around: revenue in one place, orders that arrive in the till automatically, and an integration through the official API.
No exports
Revenue flows in automatically.
No retyping
Orders straight into the till.
Official route
Via the partner API.
Security and privacy in a MplusKASSA integration
The integration processes sales data and sometimes data about guests or customers, such as names on an order. We only use the data that is needed, API credentials are stored encrypted, and every message is logged. Payment data stays with the payment provider.
The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement.
Frequently asked questions about a MplusKASSA integration
Questions that hospitality owners and retailers ask before getting started.
MplusKASSA is a Dutch point-of-sale system for hospitality and retail. It is used in restaurants, cafés and shops, and has a large number of standard integrations with staff scheduling tools, accounting packages and ordering platforms, among others.
Yes, a great many. If your system is on the list and the integration does what you need, custom work isn't necessary, and we'll tell you so. A custom integration is for your own app, an ERP, a report or a process that isn't in the standard list.
Through the API that MplusKASSA offers to partners and, where needed, through webhooks. This lets you retrieve products with stock levels, request sales figures and place orders in the till. Access is arranged through a partnership with MplusKASSA, and we look at which parts you need in the first step.
Yes. An order from your app or website can be placed in the till as an order, so the kitchen or the shop sees it without anyone retyping it. We tailor exactly how this works to your business and your app.
Yes. Sales figures per location, per day and per product group come together in a single overview or in your own reporting, without anyone having to export them location by location.
The integration reports it and records what went wrong. The message is retried or queued for review, so no order or receipt is lost or arrives twice.
For hospitality groups with multiple venues, for restaurants with their own app or website, for retail chains with their own ERP or warehouse, and for software vendors who want to connect their product to MplusKASSA. If your system is in the standard list, a custom integration is often not needed.
MplusKASSA connected to your own systems?
Tell us which systems you use alongside MplusKASSA and which data is currently transferred by hand. We'll show you what the integration looks like.