Many retailers and POS software vendors ask us:
“Can we pay a fixed monthly fee per POS instead of per transaction?”
I understand the request. Fixed fees feel predictable.
But for fiscalization, pricing “per POS” is like paying highway tolls “per car” instead of “per kilometer”. It sounds simpler, but it breaks fairness, it breaks incentives, and it breaks economics.
Here’s the core truth: fiscalization happens per transaction.
Every sale (and often every return, void, correction, e-receipt, invoice) creates a legal event that must be validated, signed, stored, reported, monitored, and sometimes re-sent if connectivity fails. The workload, the infrastructure cost, and the compliance risk are driven by the number of fiscal events, not by the number of devices.
A per-POS model misprices reality in both directions.
Imagine two stores.
Store A has 2 lanes and runs 8,000 transactions per day.
Store B has 10 lanes but runs 500 transactions per day.
If both pay “per POS”, Store A pays less although it creates massively more fiscal workload and risk.
Store B pays more although it barely uses the service.
That’s not just “unfair pricing”, it’s an unstable business model that either underfunds compliance or overcharges low-volume stores.
Now let’s add the part nobody wants to say out loud: the POS is no longer a stable concept.
In the classic world, “POS” meant a physical cash register or lane. Then we added self-checkout. Then kiosks. Then mobile POS. Then endless-aisle tablets. Then apps on phones. Then assisted selling devices.
In many retailers today, the store has more “points of sale” than it has employees, and some of them are not even fixed devices.
So if we price “per POS”, what exactly are we counting?
Is a handheld used only during peak hours a POS? Is a tablet used for assisted selling a POS? Is an in-app checkout a POS? Is a kiosk with access to your e-commerce a POS? Is your website with online store, which receives thousands of visitors per hour, a POS? Is it one POS in total, or one POS per country?
What about concepts like cashierless stores – physical locations with no physical point-of-sale terminals at all?
And if you think this is already messy, here comes the real disruption: social commerce, shoppable content and agentic commerce.
If a customer buys directly from your live video on YouTube, where is the POS? If a purchase happens through Instagram or TikTok checkout, what device should be “licensed”?
If an AI agent places an order on behalf of a customer, negotiating options, delivery, and payment — where is the POS then?
In those models, there may be no “device” at all, and the buying moment is distributed across platforms, APIs, and automated workflows. A monthly per-device cost doesn’t just become unfair, it becomes IMPOSSIBLE.
That’s why the most logical and future-proof unit is the only unit that remains true across every sales concept: THE TRANSACTION.
And this is also why a serious fiscalization solution must be designed to cover the full spectrum: from traditional lanes, to self-checkout, to mobile selling, to e-commerce, to social commerce, and yes — to agentic commerce. And who knows what else the future will bring.
You should never be forced to change your fiscalization solution just because your sales concept evolves.
Compliance should be the stable layer underneath innovation, not the thing that slows it down.
At this point, let me add one uncomfortable truth. Many VCs and investors don’t like transaction-based pricing because it doesn’t look like “safe” recurring revenue on paper. It’s harder to package as predictable ARR, which is often the basis for their decisions. I’m sorry to be that direct, but solutions should be developed for users, not for investors.
There’s another important point that both retailers and POS vendors feel every day: peak time.
Fiscal systems don’t struggle at 6am. They struggle when you run promotions, holiday traffic, end-of-day rush, or nationwide campaigns.
The capacity you need, the monitoring you need, and the operational effort you need scale with transaction volume. A per-transaction model naturally funds the exact moments that create the most load and the most risk.
If you want a well-known comparison, look at payments.
Payment providers don’t charge “per card terminal per month” and ignore volume. They charge per transaction because their cost and exposure are per transaction. Fiscalization is closer to payments than it is to “software seats”.
The biggest objection I hear is predictability: “We need a monthly number.”
That’s a budgeting problem, not a pricing truth.
You can make per-transaction pricing predictable with volume tiers, committed minimums, or caps, but the logic should still stay tied to the thing that creates the legal event: the transaction.
The moment you move to per-POS, you disconnect price from usage and from compliance risk, and you create the wrong incentives for everyone.
So when someone says “per transaction feels expensive”, my answer is: it’s not expensive — it’s accurate.
It charges more when you sell more, and less when you sell less. That’s exactly how compliance services should behave in retail, especially in low-margin businesses.