ESB Viewer

When the Order System Hangs

A server connection drops mid-order. The kitchen printer sits silent. A waiter stands at the tablet, tapping refresh, while the table waits. This is the moment ESB Viewer exists to prevent. The app connects directly to the ESB POS server — the brain of many Indonesian restaurants and cafes — and gives staff a window into the system from a handheld device. It is not a full POS system itself. It is a viewer, a monitor, a remote pair of eyes on the order flow.

PT Esensi Solusi Buana, the developer behind this tool, builds restaurant technology for the Indonesian F&B market. The company's ecosystem includes POS software for Windows and Linux, a lighter POSLite version for Android and iOS, and an Order Management System that ties kiosks, kitchen displays, and queue screens together. ESB Viewer fits into this ecosystem as the mobile window. It lets a manager check what is happening on the POS without standing at the register. It lets a server confirm an order went through. It gives visibility when the main terminal is out of reach.

The app weighs in at just over three megabytes on Android. That small footprint matters. Restaurant tablets and phones often run on older hardware, and storage is precious when the device also holds menu photos, payment logs, and staff schedules. ESB Viewer asks for little. It asks for a connection to the POS server — nothing more on the surface. The core job is simple: display what the POS sees.

Printer Pathways and the Scale That Changed

Connectivity is where ESB Viewer shows its real shape. The iOS version, listed as ESB OMS, allows printer connections through three paths: LAN, Bluetooth, and Star Micronics printers. This is not a generic "supports printing" claim. Each path serves a different kitchen setup. LAN printers sit on the same network as the POS, hardwired and stable. Bluetooth printers cut the cables, useful in pop-up stalls or outdoor seating. Star Micronics is a specific hardware brand common in Indonesian hospitality — the app acknowledges that kitchens have preferences, and it adapts.

The most recent change, logged in the version 1.32 changelog, added support for the Imin D1w scale POS. This is a weighing scale that integrates with the POS system. In a restaurant that sells seafood or meat by weight, the scale sends the weight directly into the order. Before this update, that process may have required manual entry. Now the viewer reflects that weight data in real time. A cashier can see the scaled item appear on the order, confirm it, and send it to the kitchen without typing a number. This is the kind of detail that separates a generic viewer from a tool built for a specific operational flow.

But the connection is not always seamless. One user reported that the app does not appear on their iPad at all. Another noted that using Chrome causes the order input to disappear mid-process. These are not catastrophic failures, but they point to a pattern: the app works best when used exactly as intended, on supported hardware, with the correct browser. Deviate from that path, and the viewer stops viewing.

What Happens When Two Features Meet

Here is where the app reveals its true behavior. The printer connection and the POS server connection are not separate features. They interact. When a waiter enters an order on the POS, the viewer shows that order on the mobile screen. But the viewer does more than display — it also confirms that the order reached the printer. If the printer is connected via Bluetooth and the connection drops, the viewer may show the order as sent, but the kitchen never receives it. The staff member must then check the printer status, not the viewer. The viewer shows the POS state, not the printer state. This is a critical distinction. The app displays what the POS thinks happened. It does not independently verify that the hardware executed the instruction.

This interaction creates a practical workflow. A manager using ESB Viewer during a busy dinner service can spot an order that appears stuck. They see the order on the viewer, but the kitchen has not started cooking it. The manager then knows to check the printer connection rather than re-entering the order. Re-entering would create a duplicate. Checking the printer solves the real problem. The viewer acts as an early warning system, not a fix. It tells you something is wrong, but it does not tell you what or how to fix it. That knowledge comes from experience with the hardware.

The Imin D1w scale integration adds another layer. When a weighed item is added to an order, the viewer reflects that weight. But the viewer does not control the scale. It only shows what the POS received from the scale. If the scale sends the wrong weight, the viewer shows the wrong weight. The staff member must catch that error before sending the order to the kitchen. The viewer is a mirror, not a filter. It reflects the data. It does not correct it.

What the Changelog Actually Changed

The version 1.32 update, dated July 2024, added one line: "Penambahan dukungan untuk POS Timbangan Imin D1w." That is it. No performance improvements. No bug fixes. No stability updates. Just the scale support. This is honest. The developer did not pad the changelog with generic filler. They added one specific feature and documented it. For a restaurant that already uses Imin D1w scales, this update is essential. For everyone else, nothing changed. The app remains what it was: a viewer for the ESB POS server.

The iOS version, version 1.0.5, added printer connection support for LAN, Bluetooth, and Star Micronics printers. That update came earlier, and it established the connectivity foundation. The Android version followed a different path, focusing on the scale integration. The two platforms are not identical. Android users get the scale support. iOS users get the broader printer options. A restaurant using both platforms may need to manage expectations carefully.

Permission Realities and Device Constraints

The legacy version of ESB Viewer, designed for Android 4.4 and earlier, requested four permissions: INTERNET, BLUETOOTH, BLUETOOTH_ADMIN, and CAMERA. The current version does not list permissions on the Play Store page, which means they are either not requested or not displayed in the scraped data. The Bluetooth permissions make sense for printer connections. The camera permission is less obvious — possibly for scanning barcodes or QR codes on orders or inventory items. The absence of a permission list on the current page is unusual. Most apps list their permissions prominently. ESB Viewer does not, at least not in the visible snippet.

Android 4.4 is the minimum supported version. That is an old baseline. Many restaurant tablets run older Android versions because upgrading the hardware is expensive and the POS software is stable on the current setup. ESB Viewer accommodates that reality. It does not force restaurants to buy new tablets to use the viewer. It runs on what they already have. The file size stays small. The permissions stay minimal. The trade-off is that the app cannot use newer Android features, but for a viewer, that trade-off is acceptable.

Support for the app appears limited. The developer contact is listed as [email protected], and the physical address is in Tangerang, Banten, Indonesia. There is no visible FAQ, no user forum, no dedicated support page for the viewer itself. The ESB website focuses on the broader POS ecosystem, not on this specific viewer app. If the viewer stops working, the user must contact the developer directly or rely on the restaurant's internal IT support. This is not unusual for B2B software, but it is worth noting for anyone installing the app independently.