Café in Sliema

The shape of the day

A typical Maltese coffee-and-pastry shop opens at 06:30 for early commuters and closes after lunch at 15:00. One iPad on the counter, one printer, one card terminal, two staff members at peak. No KDS — coffee orders go directly to the barista; lunch orders go to the small kitchen at the back via printed kitchen ticket.

The business case for a POS upgrade was straightforward: the existing till was a Windows-based register from 2017, the receipt printer threw a paper-jam error a few times a week, and the owner had no way to see daily takings without physically being in the shop.

What the workflow needed

Three constraints emerged from the conversations:

1. No downtime tolerance during lunch service. A 20-minute outage at 12:30 means three or four covers walking out the door, irrecoverable. Whatever replaced the old till had to be fully usable when the broadband dropped.
2. MTCA-correct numbering, every receipt, every time. The owner had been catching scattered numbering issues during her own quarterly review — the kind of issue she didn’t want to take to MTCA for explanation.
3. A way to see daily takings from her phone. She lives in San Ġwann and the shop is in Sliema. The drive at end-of-day to print a Z-reading was an unwelcome ritual.

What the VIND-shape workflow looks like

• Single-terminal POS running on an iPad mounted on the counter. The app caches the full menu locally on clock-in. Receipt-number range is allocated at clock-in too.
• Bluetooth-paired Viva terminal for card payments. When the broadband drops, the Viva still authorises via 4G fallback in the terminal itself.
• Cloud-backed backoffice showing daily takings, broken down by VAT rate, viewable from anywhere. Z-readings auto-close at 16:00 (configurable) so the owner doesn’t have to be present.
• Printer over local Wi-Fi, so a broken cloud link doesn’t break printing.

The outage that made the case

Mid-pilot, the broadband cabinet at the end of the street went down for 90 minutes during lunch. 31 transactions were processed in the offline window. Card payments kept authorising via the terminal’s mobile fallback. Receipts kept printing. When the link came back, the queue drained in under two minutes and the backoffice showed the day’s takings as if nothing had happened.

This is the workflow that motivated VIND’s offline-first architecture and the reason we pre-allocate receipt-number ranges instead of asking the server for a number per receipt.

Honest caveats

This is a composite profile, drawn from conversations with multiple café operators in the Sliema / Gżira / St Julian’s area during 2026 H1. The 90-minute outage scenario is a real event that occurred during pilot testing; the specific operator details (staff count, opening hours) are common to many venues in this archetype.

When we publish a named case study with explicit operator consent, this page will link to it from the top of the post.