Changelog
What is live, what is next, and how we ship.
Fizzy sits between your customers' money and your tax return, so we do not ship the way a consumer app ships. This page is the public record: what is in the product today, what we are building, and the rules we hold ourselves to when we change something.
Live in production today.
Running in Finland, on real counters, every day.
August 2026
Live
The sealed spine, end to end
Everything below is in production and in daily use. It is listed here as the baseline that future entries build on.
- ▪Sealed ledger. Append-only, hash-chained journal of every sale, void and refund, with timestamp and staff identity on each entry.
- ▪Worldline-certified payments. Card, contactless and MobilePay, reconciled to the sale that they settled.
- ▪Offline-first operation. Selling continues without a connection, and everything syncs sealed when it returns.
- ▪Line-level VAT and the tax engine. Sector-aware rates per line, with Z-report and SAF-T export.
- ▪Onni. Multilingual, deterministic answers from the live ledger on web, WhatsApp and Telegram.
- ▪Anomaly Guard. Flags void and refund patterns that deserve a second look.
- ▪Omnichannel stock. One inventory across shop and webshop.
- ▪Open spine. REST API, webhooks and file exports into accounting, ERP or Baslic.
From here on
Dated entries
Release notes start here
From this point every change that customers can see gets its own dated entry on this page: what changed, who it affects, and whether anything is required of you. Nothing that touches the ledger, VAT classification or exports will ever arrive unannounced.
On the bench
What we are building next.
Plans, not promises. Dates come when the work is close enough to be honest about.
ViDA readiness
Structured, real-time-ready sales data ahead of the EU's 2030 regime, so our customers meet the deadline without a migration.
More accounting routes
We add connectors in the order customers actually ask for them. Tell us what you use and it moves up the list.
Deeper multi-outlet views
Comparisons across outlets and periods, built on the same sealed rows, so the headline number and the audit agree.
Missing something you need? Small teams can move fast on a good request. Write to help@fizzy.fi.
How we ship
Rules for changing a system your books depend on.
A point of sale cannot have an exciting release night. These are the constraints we work under, and you should hold us to them.
- ▪History is never rewritten. New behaviour applies forward, and past entries keep their original seal.
- ▪Changes to VAT logic, exports or the ledger are announced before they land.
- ▪API changes that break integrations get a new version. Existing versions keep working.
- ▪We do not deploy to a counter during its trading hours if we can avoid it.
- ▪Incidents are posted on the status page while they are happening, not summarised afterwards.
Want the updates as they land?
Customers get release notes by email. Ask and we will add you.