Applies to: Saleculator POS/PDA 4.5 update 4 (4.5.4), Webin 3.7 and Waiter 1.3.0, as relevant to this guide. Download the published packages from Saleculator Downloads.
Start with Settings > Setup and connection check. Use Recovery for unconfirmed orders or printer attempts. In the local Waiter 1.4.0 preview these screens are called Connection check and Needs attention.
| Problem | What to check |
|---|---|
| Phone cannot reach Webin | Open the exact Webin address in the phone browser. Check the host, port and folder, PC/web service, firewall and Wi-Fi. Do not use localhost for a different computer. For a hosted site, use the valid HTTPS address. |
| Webin loads without styling, or pages show 404 | Check the extraction folder, configured base URL and web-server rewrite rules. Preserve the assets folder. Avoid nested webin/webin folders. |
| Database check fails | Confirm the intended Saleculator database exists and that Webin’s host, port, database name and credentials match it. Do not fix this by rerunning historical SQL on live data. |
| Webin browser login works, waiter PIN does not | They are different sign-in methods. Use an active staff account with a unique PIN and a role that allows waiter work. Ask an administrator to correct duplicate PINs or role access. |
| Button or settings page is unavailable | Check role permissions and whether an order operation is still active. Staff without bill permission cannot request bills. Sign in again after role changes. |
| Table is owned by another phone or POS | Continue on the owning device or use the authorized handover process. Do not clear reservations manually in the database. |
| Printer test fails | Check power, paper, address, TCP port, network reachability and the destination configured on this phone. Guest Wi-Fi may block local printers. |
| Layout refresh fails | Check the two exact resource names, JSON validity and supported schema. A failed refresh keeps the last valid cache; verify that a custom change actually reached the phone before service. |
| Bill request remains pending | Use its recovery/status action. The app retains the original request identity to avoid duplicates. Check whether the cashier already received/imported it before making another request. |
When a print result is uncertain #
- Inspect the printer and ask kitchen staff whether that specific slip arrived.
- Open the pending attempt in Recovery/Needs attention.
- Confirm printed or not printed according to the actual result. Do not guess.
- If it did not print, retry through the recovery flow when the connection is restored.
Unresolved print attempts block edits that could make reconciliation ambiguous. If one kitchen route succeeded and another failed, handle the failed route rather than repeating every slip. A backup failure after a successful print is not a reason to print again.
What works when Webin is unreachable? #
KOT printing can continue after a network failure for a table already reserved on that phone, provided the printer remains reachable and the app has the required local reservation information. The phone retains the changes and backs them up when Webin returns.
This does not allow opening arbitrary new tables offline. An explicit server rejection, expired session, access denial or ownership conflict blocks offline printing. Bill-summary printing and Request Bill still require Webin. There is no background printer queue.
Manager handover to another phone #
- Stop using the old phone before transferring the table.
- Reconnect it and back up its latest work where possible. Reconcile any offline changes and unconfirmed slips with staff.
- Have a manager with recovery permission perform the handover.
- Open the table on the receiving phone and verify items and kitchen status before continuing.
Do not uninstall the app, clear its storage or switch servers to resolve a pending order. Those actions can remove access to work that exists only on the phone.
Information to give support #
Record the app/Webin versions, device name, table, time, displayed error and whether the cashier/printer received the order. Use the app’s diagnostic-copy action where available. Send diagnostic details privately; do not include PINs, activation keys, database passwords or customer information in public posts.
