:~
integration :: mpluskassa

MplusKASSA,
connected to the rest.

We have a developer account with MplusKASSA and tested the API and webhooks end to end on our own test till: items, buttons, stock, receipts, the daily journal and webhooks at checkout. At a drinks wholesaler with a shop, till sales already go to the shop warehouse in Exact every week.

✓ tested on our test till · weekly export to Exact live
#// what we build

What an integration with MplusKASSA does for you

Each part shows how far along it is: running at a client, built and in testing, or proven on our own test setup.

running at a client

Till sales to your stock

What goes over the counter comes off the warehouse in your accounting. Weekly from the till export to Exact today; per receipt via a webhook is the next step.

tested on our test till

Listening to the till live

After every completed receipt a webhook, within a second, with item, Exact code, quantity, price, VAT and revenue group per line. Signed, so you know it came from the till.

tested on our test till

Daily journal to your cash book

Per day and branch the revenue per revenue group, payments per method and VAT per rate, with ledger account. Enough to fill a cash book or daily entry.

tested on our test till

Managing items and buttons

Create and update items from your own system, including the button layout on the till screen with price and stock visible.

tested on our test till

Setting stock after a count

Read and set stock per branch. The till keeps its own stock and a sale takes it off.

we build this for you

One stock level with your web shop

A web shop sale comes off the till stock and a shop sale off the web shop stock. We build this on the same building blocks; no web shop integration is running at a client yet.

388
operations in the till API
< 1 s
from checkout to webhook
HMAC
signature on every call
weekly
till sales to Exact, live
#// what the docs don't say

Lessons from real work

With an integration you mostly pay for what isn't in the manual. This is what we ran into, so you don't have to.

A blocking webhook can stop checkout

If a blocking webhook points at an address that doesn't respond, checkout fails. Our receiver always responds, and we only make a webhook blocking when it has to be.

Saving replaces the whole list

Revenue groups and the button layout are sent back in full. Whatever you leave out disappears. Read first, then send everything back.

Deposits don't link by themselves

A linked deposit item is accepted by the API but not saved. It didn't show up on the receipt; deposits need their own solution.

The till has to go online once first

As long as the till software has never connected to the database, the API gives no access. Allow a day for that when setting up.

#// how we build

Look first, then book

// copy

A copy, not live queries

We fetch the data into our own database once and after that only the changes. Fast for you, and well within the package's limits.

// writes

Named write actions

Writing is only possible through actions agreed up front. A test in the code fails as soon as one is added that wasn't agreed.

// approval

Look first, then book

Every booking shows up front what will happen. Only after a 'checked' tick and a check on the totals does anything go to your books.

// errors

Errors aside, work goes on

An unknown item or a timeout doesn't hold up the rest. It becomes an alert for whoever picks it up, and an interrupted run resumes where it stopped.

#// rates

Start small, a fixed price per phase

hourly rate
€90
for small jobs and extensions
day rate
€600
for build days
kickoff
€600
one day, with a plan and a price per phase

All amounts excl. VAT. A fixed price per phase, and the code is yours. Management and monitoring are available for a fixed monthly fee.

#// frequently asked questions

What do I need to connect MplusKASSA?

Access to your own administration through the API. You usually arrange that through your Mplus dealer, who gives our developer code access to your database. Webhooks are set up in the back office under Beheer > Instellingen > Webhooks.

Can an integration slow down or block my till?

A webhook is either blocking or non-blocking. A blocking webhook to an address that doesn't respond makes checkout fail. We set webhooks to non-blocking by default and our receiver always responds, even when something goes wrong.

Does it work with Exact Online?

Yes. Every till item carries the Exact item code. That's how we link till sales to items and stock in Exact, weekly or per receipt.

Can I connect my web shop to the till?

Yes, we build that for you: one stock level for shop and web shop, with the till as the source. We've tested the building blocks (reading and setting stock, items, webhooks at checkout); no web shop integration is running at a client yet.

Can the till fill my cash book?

The till's daily journal holds revenue per revenue group, payments per method and VAT per rate, with ledger account. That lets you pre-fill a cash book or daily entry, so only the check is manual work.

What does an MplusKASSA integration cost?

€90 per hour or €600 per day, excl. VAT. We start with a one-day kickoff and then agree a fixed price per phase. Any Mplus fees for API or webhook access go through your dealer.

$contact --reason="new client"

Can we help
your business?

Digital agency in Groningen for Claude hosting, websites, automation and AI agents that simply do what they should. We handle the tech, you handle the growth.

stats.json
  • Experience
    // years online
    20y
  • Projects
    // live & running
    100+
  • Tool lock-in
    // always the best solution
    0