POS systems and tills

Usually not because of the software, but because of what surrounds it. The till shares the same Wi-Fi as the guests, the receipt printer gets a new IP address after a router reset so the till can no longer find it, and the fiscalisation certificate expired without anyone noticing. Any one of these stops payments at the worst possible moment.

In hospitality there are also the kitchen and bar printers. If an order never reaches the kitchen, the waiter only finds out when the guest asks where the food is.

• tills and printers on cable, on a network separate from guests, with fixed IP addresses
• a UPS for the router and the till, so a short power cut does not stop payments
• a backup connection through a 4G or 5G router
• the certificate expiry date recorded and a reminder set well ahead
• a spare printer configured and tested

When the connection drops, the till keeps issuing receipts with the issuer's protective code (ZKI), and the unique invoice identifier (JIR) arrives later, once the receipt is delivered to the Tax Administration. We check that the software really does this and that the backlog is sent as soon as the connection is back.

Payments that do not depend on how many guests are on the Wi-Fi, a list of devices with their addresses and the certificate expiry date, and staff who know how to change the paper roll, restart the printer and spot a receipt that was not fiscalised. For venues with several tills we also set up a shared view of takings per shift, if the software supports it.

The card terminal usually belongs to the bank or the payment processor, so we leave it alone, but we check that it has a connection and does not depend on the same Wi-Fi as the guests.