A point of sale a chain can actually grow into
A hospitality chain outgrows its tills faster than anything else it owns. Wezly runs every store and outlet on one TSE-compliant point of sale — and has kept HPC GmbH trading on it for six years.
The register a server actually rings a sale up on: modifiers, discounts, a running total, charged in one tap. Every sale, refund and cash movement in one ledger — the record a signed transaction has to leave behind. The Kassensichv export the Kassensicherungsverordnung requires on demand, generated from the live trading record rather than assembled after the fact. Revenue, sales count and profit read back as a business, month over month, from the same data the till writes.
- Sector
- Retail & hospitality
- Market
Germany - Delivered
- 2020
Wezly is the point of sale we built for HPC GmbH. It went live in 2020 and it is still running.
It is also the system behind a claim this site makes elsewhere: the point of sale that met Germany's fiscal requirement from its first release rather than after an audit.
The structure most tills get wrong
A single shop needs a till. A business that intends to become several shops needs a hierarchy, and retrofitting one later is the migration nobody budgets for.
Wezly was built with three levels from the start. A business has stores, a store has outlets, and an outlet has registers. Products carry variants, and their properties resolve per outlet, set either by a rule or by hand, because the same product genuinely is a different thing in two locations: a different price, a different tax treatment, a different availability on a Sunday.
That last part is the one that decides whether head office can actually run the estate, or whether every branch quietly becomes its own island of spreadsheets.
Why the German part is the hard part
Everywhere else a point of sale is a screen, a printer and a card reader. In Germany it is a regulated object. Under the Kassensicherungsverordnung every transaction must be signed by a certified technical security element, and the tax authority can ask for a structured export of the trading record going back years.
That is not a feature added once the ordering flow works. It decides how a sale is stored on the day the first line is written, because a signed sale cannot be quietly amended afterwards. Systems that treat it as a late requirement get rewritten.
Built against the market leaders, not against a template
The reference points were the products a retailer would otherwise be buying, Vend among them. The question through the build was not "what is the minimum a till needs", it was "what would make someone leave the incumbent", which is a harder specification and produces a different piece of software.
The stack, where it matters
Angular with NgRx on the front, Nest.js and Node on the back, PostgreSQL through TypeORM for the trading record, Firestore where the shop floor needs something to react immediately, Docker and Google Cloud underneath. One person carried it end to end.
That is the same arrangement this site describes generally: the engineer in your first meeting is the one who writes the code, and the team is small on purpose.
Six years is the result worth quoting
Not a launch number. A regulated system built in 2020 is still in service, through the rule changes and platform updates that happened in between. The measure is whether a system is still maintainable in five years by someone who was not there when it was written, and this one has now passed that mark.
On this page
What would yours have to do?
Thirty minutes with the engineer who would build it, not a salesperson. Straight answers on scope, on cost, and on where the real risk sits.