Onboarding walkthrough
A step-by-step walkthrough for a brand-new till. You'll install Kiosk Desktop, survive the one-time first launch, set up your counter, and ring up a real sale — no internet, no extra programs, no account to reach.
Part 01
Four parts: install, first launch, ready the counter, first sale. By the end you'll have a till that takes cash, tracks stock, and closes the day with a number you can trust.
This walkthrough follows the path of a brand-new install, in the order you'll actually do it. Each part tells you what should appear on the screen, what it means, and what to do if it doesn't. It's written for a single cashier on a single till — the setup most shops start with. Adding a second till later is covered at the end.
Part 02
Nothing exotic — a PC, a few minutes, and (optionally) the printer that will live on the counter.
| Item | Need it? | Why |
|---|---|---|
| A 64-bit PC — Windows 10/11 or macOS | Yes | Runs the whole system: the app, the database, and the printer bridge. |
| About 2 GB of free disk space | Yes | The installer plus the data folder that will hold your shop. |
| 4 GB of RAM (8 GB better) | Recommended | Smooth selling now, and headroom for browser tills on the LAN later. |
| Receipt printer (ESC/POS, network) | Optional | Paper receipts and the cash-drawer kick. You can start without one. |
| Barcode scanner or scale | Optional | Speed up the counter. Plug them in whenever they arrive. |
| Internet connection | No | Selling, stock, tabs, shifts, and reports are all local. Only cloud features (M-Pesa STK, SMS) need the internet — Desktop doesn't use those. |
Part 03
Grab the installer from the download page and run it. The exact clicks differ slightly between Windows and macOS.
Windows protected your PC, click More info → Run anyway. This is expected until the installer is code-signed; the file is the one you just downloaded from the site.Open → Open again in the confirmation dialog.Part 04
The only slow moment in the whole setup — and it never happens again.
The first time you launch Kiosk Desktop you'll see a splash screen with a message like Starting your till…. Behind that message the app is doing something important: building your private database from scratch. It creates the local database engine, generates a secure password for it, and applies the full schema — 220+ steps.
Part 05
A handful of fields and you're on the dashboard. Everything you enter here can be changed later.
Part 06
Five small jobs before your first real customer. Do them in order and the first sale is a formality.
| Mode | When to use it |
|---|---|
| File | Testing — receipts append to a file instead of paper. |
| Network (RAW 9100) | Real shops — point it at the printer's IP and receipts print directly. The cash-drawer kick uses the same connection. |
| Disabled | No printer attached; the POS falls back to normal browser printing. |
Part 07
A till day has a shape: open, sell, close. Follow it and the cash in the drawer always matches the ledger — that's the whole trick of a shop.
From the cashier screen, open a new shift and enter the opening float. From this moment, every sale, drawout, and refund is recorded against this shift. If your counter has several cashiers, only one shift is open at a time — handovers happen at close.
On Desktop, receipts go through the built-in device bridge to your ESC/POS printer — no browser print dialog. The same bridge fires the cash-drawer kick when a cash sale completes.
At the end of the day (or when the cashier hands over), close the shift and count the drawer. Kiosk totals the expected cash from the ledger; the difference between expected and counted is your variance — zero is a perfect day. Drawouts (cash removed mid-shift) are tracked separately so they never look like shortages.
Part 08
A desktop shop has one copy of everything, on one disk. A backup is not optional — it's the difference between “lost an afternoon” and “lost the ledger.”
backups/ folder of your data directory.Part 09
Kiosk writes a detailed log for everything it does. Most problems announce themselves there long before they reach your eyes.
On Windows, if the app doesn't come up, the launcher can show a dialog that looks like this:
You might see this dialog
Kiosk couldn't start
Backend never reported healthy: /actuator/health never returned 200 within 90s (last error: http://127.0.0.1:5050/actuator/health: Connection Failed: Connect error: No connection could be made because the target machine actively refused it. (os error 10061))
Log file: C:\Users\Fabian\AppData\Roaming\Palmart\kiosk.log
Here's what it means. The launcher starts the app's backend, then waits for a health check on port 5050 before opening the window. “Actively refused it (os error 10061)” is Windows' way of saying nothing is listening on 5050 yet — either the backend is still booting, or it stopped while booting.
C:\Users\<you>\AppData\Roaming\Palmart\kiosk.log.Kiosk Desktop uses three local ports. They belong to this PC — you shouldn't need to touch them, but they explain almost every startup error:
| Port | What runs there | Purpose |
|---|---|---|
| 5050 | The app (HTTP). Open http://127.0.0.1:5050 on this PC. | The POS itself — the UI and the API. |
| 33306 | The bundled database | Where sales, stock, and customers live. Internal — you shouldn't need to touch it. |
| 19500 | The device bridge | Receives ESC/POS print jobs and drawer kicks from the app. |
Everything — data, media, backups, logs — lives in one per-user folder:
| OS | Data folder |
|---|---|
| Windows | %APPDATA%\Palmart (C:\Users\<you>\AppData\Roaming\Palmart) |
| macOS | ~/Library/Application Support/Palmart |
kiosk.log — the launcher's diary; start here.backend.out.log / backend.err.log — the backend itself.mariadb.log — the database.backups/ — backups you create.| Symptom | Likely cause | What to do |
|---|---|---|
| App opens but shows nothing | A background component failed to start. | Open kiosk.log in the data folder — the last lines say exactly what failed. If in doubt, send the file to support. |
| First launch takes over a minute | The database is being created for the first time. | Wait — it only happens once. Don't close the window mid-setup. |
| “Port 5050 (or 33306) is already in use” | Another program holds the port. | Close the other program, or uninstall it, then launch Kiosk again. |
| Antivirus quarantines part of the app | Bundled runtimes look unfamiliar to some scanners. | Allow the Kiosk Desktop folder as a trusted app, then reinstall. The app is fully offline and makes no network calls of its own. |
| After a restore the app won't start | The restore interrupted the running database. | Restart the PC, then launch Kiosk again. If it still won't start, restore from the most recent backup before the bad one. |
To start completely fresh: uninstall Kiosk Desktop, then delete the data folder for your OS (above). This removes the database, media, and logs — keep a backup file somewhere safe first, because nothing survives a reset. Reinstall and the first launch builds a brand-new database (Part 4, again).