Product
The operating system for money-in.
One immutable spine from the counter to the tax return. Every sale sealed at the source, reconciled to a certified payment, and turned into structured data, for any business that takes money, on any hardware or in the browser.
Core
Written once. Impossible to quietly change.
Every sale, void and refund is appended to a hash-chained journal, each entry linked to the one before it, sealed with a timestamp and staff ID. Nothing can be edited or deleted after the fact. It's the tamper-proof foundation Nordic cash-register rules require, and the reason an audit takes minutes instead of weeks.
- ▪Append-only, hash-chained journal
- ▪Cancel & refund logged with reason, time, staff
- ▪Daily Z-report & SAF-T export, tax-office ready
- ▪Line-level VAT, sector-aware rates
Hur mycket sålde vi i går?
8 110 EUR
124 sealed sales · VAT 25,5% · Kamppi · 4 Aug
Deterministic
Ask in your language. Get a sourced answer.
Ask on WhatsApp, Telegram or the web, in Finnish, Swedish, Danish, Turkish or English, and Onni answers from your live, sealed ledger. It runs on curated, versioned rules, not model-generated numbers, so every figure traces back to a rule and the exact sales behind it. An answer you can take to your accountant.
- ▪Natural language in, structured answer out
- ▪Deterministic & fully auditable
- ▪Anomaly Guard flags suspicious voids & refunds
Onni is included from the Scale plan upwards.
Certified by Worldline
Card, contactless and MobilePay, reconciled to the sale.
Fizzy is integrated and certified with Worldline, the infrastructure behind a large share of European card transactions. The tender, the receipt and the sealed record are one flow, so the money that came in always matches the sale that was rung up. Card data never touches your device.
About the Worldline partnership →
Hospitality
The kitchen sees the order as it is rung.
A line rung at the till reaches the kitchen screen in the same moment it is written to the ledger. The board is pushed, not fetched every few seconds, because three seconds is three seconds of a cook not cooking. Cards are edged in the colour of how long they have waited, so the next thing to make is chosen from two metres away, before anyone reads a word.
- ▪Tickets grouped by table, with the minutes they have waited
- ▪Fresh, working, late: the colour does the reading
- ▪Bumping a line on one screen clears it on every screen
- ▪Any paired terminal runs as a kitchen screen, so it is a mode on hardware you already own
QR ordering
The table orders. Your staff still decide.
Every table carries its own code. A guest scans it, reads the live menu off your catalogue and sends an order, and that order lands in an approval inbox on the register rather than in your sales. Someone accepts or rejects it, and only then is it rung, on the till that accepted it. Nothing a guest types can write itself into your ledger.
- ▪One code per table, menu and prices straight from your catalogue
- ▪A table can have five orders waiting at once, so nobody floods the pass
- ▪Accepting is atomic, so two registers cannot ring the same order twice
- ▪Guests order, they do not pay: the tender stays on your certified terminal
Kitchen display, QR ordering and table service are the hospitality module, switched on for the outlets that need them.
From the table · waiting for a person
The platform
Every capability on one sealed spine.
Core
Sealed Ledger
Hash-chained, append-only: the foundation every module writes to.
Worldline-certified
store + online, one inventory
VAT · SAF-T · ViDA 2030
multilingual, deterministic
fraud & error flags
clean data out, no lock-in
pushed to the pass, bumped once
table to approval inbox
open orders, running totals
orders and takes its own card
picked and handed over at the counter
appointments & reservations
planned hours against actual
on the tab, with a credit limit
punch cards, cards that spend
what came in, what was thrown out
a sold dish empties the fridge
eat-in and takeaway, each with its VAT
the bottle rides its drink
for who does not pay at the till
QR on the paper, or emailed once
your logo, your layout
one office, stock per shop
Read the day
Every figure is computed from the ledger, not kept beside it.
There is no second set of books to fall out of step with the first. Open tabs and voided lines are excluded and it says so, refunds and discounts are their own figures, and every number can be traced back to the sales underneath it.
- ▪Turnover, receipts and average receipt, per outlet or across all of them
- ▪Refunds, discounts and voided lines each shown on their own
- ▪Turnover by hour and weekday, on the shop's own clock
- ▪VAT by rate, payment methods, staff, products and channels
- ▪Any date range, out as PDF or spreadsheet
REST + webhooks
Your data, flowing wherever you keep your books.
Output VAT, input VAT and what is payable are derived from the same events the register wrote, one row per business day. Your bookkeeper gets their own login and reads everything without changing anything, so nobody has to send a spreadsheet or share a password. Or take it out: an open REST API, webhooks, CSV with ISO dates, straight to your ERP or to Baslic for filing. No migration, no lock-in.
