DiKAS on Android¶

DiKAS offers two Android apps for different use cases:

App	Use case	Server required?
DiKAS Standalone	Self-contained POS on the tablet	No — everything runs locally
DiKAS Client	Tablet connects to a DiKAS server	Yes — server on the network

DiKAS Standalone (Self-Contained App)¶

The Standalone app runs entirely on the tablet — without a separate server, without a permanent internet connection.

Requirements¶

Requirement	Minimum
Android version	Android 10 or newer
Storage	At least 2 GB free
Device type	Tablet or smartphone
NFC	Optional, for contactless payment (SumUp Tap-to-Pay)

First Start¶

Open the DiKAS app
The app starts the integrated server automatically (a few seconds)
The login screen appears
Log in with admin / admin
Change the password immediately (Admin → Personal → Admin user)

The app runs in full-screen mode — no Android navigation bar, no status bar. DiKAS uses the entire screen.

DiKAS Client (Server Connection)¶

The Client app is designed for tablets that connect to an existing DiKAS server — e.g., as an additional waiter POS in the service area.

Requirements¶

DiKAS server reachable on the network
Tablet and server on the same WLAN/network
Android 10 or newer

Setup¶

Open the DiKAS Client app
Enter the server address (e.g., https://192.168.1.100)
Confirm the SSL warning with "Weiter" (Continue) (self-signed certificate)
Log in with your credentials

The Client app shows the same interface as the browser but additionally offers:

Full-screen mode without Android navigation bar
SumUp Tap-to-Pay directly on the tablet (NFC)
More stable connection than the browser (no accidental tab closing)

Tip

The Client app is ideal as a waiter terminal: take orders, manage tables, and accept Tap-to-Pay payments — all on one tablet.

Feature Set (Standalone)¶

The Standalone app contains the complete DiKAS POS system:

All Core Functions¶

Function	Available
Point of Sale (direct sale + tables)	Yes
Articles, groups, options	Yes
Customers, credit, vouchers	Yes
Table plan with table shapes	Yes
Staff & staff switch	Yes
Orders & kitchen/bar printing	Yes
End-of-day report (Z-report)	Yes
Void	Yes
Hospitality receipt	Yes
Time tracking (clock in/out)	Yes
Reports & analytics	Yes
Admin area	Yes

Printing via WLAN¶

The app prints via network printers (WLAN/LAN):

Receipt printer (Epson, Star, Bixolon) via ESC/POS
Kitchen printer for consolidated order tickets
Bar printer for beverage orders

No printer available? Receipts are displayed as PDFs in the browser.

Card Payment with SumUp Tap-to-Pay¶

On NFC-capable Android devices, you can accept payments directly via Tap-to-Pay — without a separate card terminal:

Select "SumUp" as the payment method
Customer holds their card or smartphone to the tablet
Payment is processed via SumUp
Receipt is created

Setup: Admin → Einstellungen → Terminals → Enable SumUp Tap-to-Pay. You need a SumUp merchant account (API key and Merchant Code).

ℹ️ Note: Tap-to-Pay requires an internet connection to the SumUp server.

ZVT Terminal via WLAN¶

Classic card terminals (Ingenico, Verifone, CCV) can be connected via WLAN when the terminal and tablet are on the same network.

Step-by-step setup:

Prepare the terminal:
- Turn on the card terminal and connect it to the WLAN
- Note the terminal's IP address (found in the terminal menu under Network/WLAN, e.g., 192.168.1.50)
- Check the ZVT port (default: 20007)
Add the terminal in DiKAS:
- Admin → Einstellungen → Terminals
- Tap "Neu" (New)
- Enter a name (e.g., "EC-Terminal Theke")
- Type: ZVT
- Enter the terminal's IP address (e.g., 192.168.1.50)
- Port: 20007
- Click "Speichern" (Save)
Test the connection:
- In the terminal settings, tap "Status"
- On successful connection, "Verbunden" (Connected) appears
- Optional: Perform a "Kassenschnitt" (batch close) on the terminal
Paying by card:
- When checking out, select "EC-Karte" (Debit card) as the payment method
- The amount is automatically sent to the terminal
- Customer pays at the terminal (insert card or contactless)
- After successful payment, the receipt is finalized

Tip

Assign a static IP address to the card terminal in the router so the connection doesn't change with every restart.

📡 Offline Operation¶

The Android app works completely offline:

Property	Details
Database	SQLite — stored locally on the device
Internet connection	Only required for card payment (SumUp)
Cash payment	Always works, without internet
Data	All articles, customers, receipts stored locally

Data remains on the device even when the app is closed. A regular backup is recommended.

Differences Between Variants¶

Function	Server (PC)	Standalone App	Client App
Own server required	—	No	Yes
Database	CouchDB / SQLite / SQL Server	SQLite (local)	Server
Multiple devices	Yes (unlimited)	Single device	Yes (via server)
Card terminal (ZVT)	Serial + Network	WLAN only	WLAN only
SumUp Tap-to-Pay	No	Yes (NFC)	Yes (NFC)
DATEV export	Yes	No	Yes (via server)
Disco module	Yes	No	Yes (via server)
Draught system (serial)	Yes	No	No

All other functions are identical — the same interface, the same workflows.

💡 Tips for Tablet Operation¶

Disable screen lock: So the tablet doesn't lock during operation. Android Settings → Display → Screen timeout → "Never" (or very long).

Disable battery optimization: Android Settings → Apps → DiKAS → Battery → "Unrestricted". This prevents the app from being terminated in the background.

Adjust brightness: Increase brightness for terrace operation. Reduce brightness for night operation (disco, bar).

Charge during operation: Connect the tablet to a power source when it is permanently stationed at the counter. The battery lasts for a normal service day, but charging is safer for continuous operation.

Backup: Create regular backups via Admin → Datenimport → Backup. You can transfer the backup file to a PC.

Next Step¶

→ First Login — Get to know the interface