Fault tolerance at the point of sale
POS and kiosks are designed to keep working during a connection loss and resync when it returns.
Solution layerBAMIAPP · Multi-site F&B case study
One system connecting 28 stores from point of sale to management.
ZiniSoft connects the web back office, mobile app, POS, kiosks, and LED order displays from counter to kitchen for an F&B business serving the Vietnamese community in Australia.
- 28+
- operating stores
- 2 states
- South Australia and Victoria
- 5+
- new stores opened in the past year
- 120+
- regular staff users
01
Delivery context
Many touchpoints. One operating data flow.
The project's value does not sit in one screen. The point of sale, fulfilment area, mobile channel, and back office must reflect the same transaction and status.
Operating requirements
A multi-site model sets three requirements from day one.
- 01The point of sale cannot stop
Counters, kiosks, and the app must keep taking orders even when the connection is unstable.
- 02The kitchen sees the order the moment it is placed
Orders from every channel must appear on counter and kitchen screens with the right status.
- 03The owner sees 28 stores on one screen
Revenue, stores, and operating data flow into one back office with role-based access.
System map
One transaction across four operating layers.
01Order intake
POS · Kiosk · Mobile app
→02Fulfilment display
Counter · Kitchen · LED displays
→03Administration
Web back office · Permissions
→04Management
Revenue · Stores · Data
The system is treated as one operating chain, not a collection of disconnected applications.
Engineering decisions
Four choices that shaped the system.
Multi-site sync to a central back office
Transactions and inventory from 28 stores flow into one back office with no manual consolidation.
Solution layerCounter and kitchen screens update in realtime
Orders from POS, kiosks, and the app appear on LED displays by status as soon as they are placed.
Solution layerAccess by store and role
The owner, store managers, cashiers, and kitchen staff each see exactly their part of the work.
Solution layerWho uses what
More than 120 staff, one touchpoint per role.
CashierPOS
Take orders, process payment, send to kitchen
Self-ordering customerKiosk · Mobile app
Choose items, pay, track the order
Kitchen and counterLED display
See orders by status, mark complete
Store managerWeb back office
Products, shifts, and inventory for their store
Chain ownerWeb back office
Revenue and operating data across 28 stores
System in pictures
From the counter to the back office.
Brand and store images from Bami's public channels
Delivery timeline
Put it into use first. Expand with real operating data.
Instead of waiting for the full scope, the project prioritized an operable release and continued evolving with real operations.
- 01Delivery began
Defined the architecture and connected operating touchpoints.
- 02First release went live
Put one complete operational slice into real use.
- 03Continued operation and expansion
Evolved around feedback and the needs of a multi-site model.
What this case demonstrates
The ability to support a multi-site F&B system with multiple user roles.
- Connect software and devices across multiple touchpoints.
- Design data for both store operations and central management.
- Continue support and development after the first release.
ZiniSoft publishes only facts approved and verified by the client. Transaction volume and direct testimonials will be added only when official data is available.
Your project does not need to resemble BAMIAPP
The shared principle is a slice clear enough to put into operation.
ZiniSoft will clarify the bottleneck, data, roles, and first scope before proposing an architecture or delivery plan.