Engineering note · TapDine · 1 min read
A fiscal step that never blocks service
Every TapDine sale is recorded with a certified fiscal provider. The provider is a network dependency, so the fiscal step is a queue with retries, not a gate in front of the guest.
In Albania, every sale a restaurant makes has to be fiscalized: the invoice is recorded with a certified fiscal provider, in line with Albanian legislation. TapDine is integrated with such a provider. For France, where the NF525 requirements apply, the integration with a certified provider is running in the provider's test environment.
A fiscal provider is a network dependency. If it is slow or down at nine on a Saturday night, the venue still has a full room to serve. So the rule we built in is simple: payments are never blocked by the fiscal step. If the provider fails, the payment goes through, the failure is stored, and the fiscal document is retried later. Everything that had to be retried is visible in reporting, so the owner can see what happened and show it.
The rest of the order path is built the same way, around the hardware and habits a venue already has. Orders reach the kitchen display in real time over WebSockets, organised by work station. Tickets print on standard ESC/POS receipt printers, one per station: kitchen, bar, counter. Waiter calls reach staff phones immediately.
A venue is set up from a standard Excel template: zones, tables, menu categories and items. Menus, prices and languages change instantly, with no reprinting. Venues with several zones, each with its own menu and team, and groups with several locations, are managed from one panel.