A free, self-healing, offline-first point of sale for hospitality.
Built for Estonia and the EU, wider Europe and the UK. The till is free and stays free — a venue keeps its own payment processor, its own hardware and its own data.
The system repairs itself.
SwiftPOS runs its own diagnostics, matches what it sees against a machine-readable wiki of known failures, and executes repair playbooks. When a printer dies mid-service at 21:40 on a Saturday, the till either fixes it or tells the operator exactly what to do. Every incident it cannot match becomes a new wiki entry, so the fleet learns the failure before the next venue meets it.
Costing that reaches the ingredient.
AI-assisted recipe creation, ingredient-level costing, allergen tracking as EU law requires, and menu-engineering suggestions grounded in what the venue actually sold.
- Offline is the default, not a mode. Cash sales work with zero connectivity, cold start included.
- The event log is the truth. Every action is an immutable event; reports, stock, fiscal chains and integrations are folds over it. Corrections are new events, never edits.
- Compliance is data, not code. VAT tables, fiscal profiles and receipt rules are per-country configuration over one engine.
- The till is never the paywall. Front of house stays free — items, tabs, split bills, offline sales, kitchen display, shifts, multi-store.
-
ERP.CIRCONAAccounting and inventory of record. Z-report posting, stock depletion, catalogue pull.
-
My MenuQR and tablet menus, guest loyalty, pay at table and reservations. The till stays the source of items, prices and availability; what the guest orders comes back as events.
-
NOPISupplier ordering. Deliveries increment stock on hand; sales depletion powers reorder suggestions.
-
Merit APPTips and staff incentives, routed to the person who earned them rather than into turnover.
-
MixifyCocktail specifications become menu items with real ingredient depletion behind them.
-
EDI / PROOFXSigned, idempotent, provable document exchange — invoices, price catalogues, delivery notes, stock reports — verifiable from both ends.
We are looking for tools to connect, before the first venues arrive.
Every connection above is on by default for every venue, and every one of them can be switched off from the till. We want more of them — and we want them in place from day one rather than bolted on afterwards.
If you build something a hospitality venue already runs — supplier ordering, accounting, menus, reservations, loyalty, payments, kitchen or printer hardware — the event stream is open and the coupling is a conversation, not a partner programme.
ping@swiftpos.techIn development. The cloud API, the till and the back office are built and running, and the first venue has been exercised end to end. SwiftPOS is not yet generally available and is not taking signups.