Usage Scenarios
DiKAS adapts to any hospitality business — from a small kiosk with a single tablet to a club with 20 POS terminals and an NFC card system. This page shows typical usage scenarios with specific hardware recommendations and the appropriate DiKAS modules.
Scenario 1: Small Kiosk / Takeaway
Business: Kebab shop "Yildiz" with one counter, 2 employees, direct sale only.
Hardware
| Device |
Type |
Description |
| POS |
1x Android tablet (10") |
DiKAS MAUI app, wall-mounted behind the counter |
| Printer |
1x receipt printer (ESC/POS) |
Epson TM-T20III or Star TSP143 |
| TSE |
1x TSE module |
Swissbit or Epson TSE (USB or microSD) |
| Card terminal |
Tap-to-Pay (SoftPOS) |
Built right into the tablet (NFC) — no extra hardware needed |
DiKAS Configuration
| Setting |
Value |
| Table service |
Off (direct sale only) |
| Kitchen display |
Off |
| Delivery service |
Off |
| Time tracking |
Optional |
| Article groups |
3–5 (Kebab, Beverages, Sides, Extras) |
| Employees |
2 (PIN switch) |
| DATEV export |
Mode "End-of-day report" |
Workflow
Customer arrives → Staff selects articles → "Pay" → Cash/Card → Receipt printed → done
Cost: Minimal — one tablet + printer + TSE. No server, no PC, no router needed (tablet operates standalone with SQLite).
Scenario 2: Cafe with Counter and Seating
Business: Cafe "Bohne & Blatt" with counter (direct sale) and 12 seats (table service), 4 employees.
Hardware
| Device |
Type |
Description |
| POS 1 |
1x touch PC (15") |
Main POS at the counter |
| POS 2 |
1x Android tablet (10") |
For table orders (mobile) |
| Printer |
1x receipt printer |
At the counter |
| TSE |
1x TSE module |
On the touch PC |
| Card terminal |
1x ZVT terminal |
Hardwired at the counter |
DiKAS Configuration
| Setting |
Value |
| Table service |
On (12 tables in 2 groups: Indoor + Window) |
| Direct sale |
On (for counter) |
| Kitchen display |
Off (small menu, no kitchen operation) |
| Customer credit |
On (loyalty program) |
| Points |
On (10th coffee free) |
| Time tracking |
On |
| Articles |
~30 (Coffee, cake, breakfast, beverages) |
Workflow
Counter sale:
Customer orders at the counter → Direct sale → Cash/Card → Receipt
Table service:
Guest sits down → Waiter takes order on tablet
→ Items are assigned to the table → Waiter checks out at the table
Regular customers:
Mrs. Weber comes every morning → Scan NFC card → Customer credit
→ 10th visit: Free coffee via points system
Scenario 3: Restaurant with Table Service
Business: Restaurant "Bella Vista" with 60 seats, kitchen, bar, 8 employees.
Hardware
| Device |
Type |
Description |
| Main POS |
1x touch PC (15") |
At reception/counter |
| Waiter tablets |
3x Android tablets (8") |
Order taking at the table |
| Kitchen display |
1x monitor (22") + mini PC |
In the kitchen |
| Bar display |
1x monitor (15") + mini PC |
At the bar |
| Kitchen printer |
1x ESC/POS printer |
Backup for kitchen display |
| Bar printer |
1x ESC/POS printer |
Beverage receipts |
| POS printer |
1x ESC/POS printer |
POS receipts |
| TSE |
1x TSE module |
On the main PC |
| Card terminal |
1x ZVT terminal |
At the counter |
| Router |
1x Wi-Fi router |
For tablet connection |
DiKAS Configuration
| Setting |
Value |
| Table service |
On (15 tables in 3 groups: Dining room, Niche, Window) |
| Kitchen display |
On (separate: Kitchen = food, Bar = beverages) |
| Course control |
On (Starter, Main course, Dessert) |
| Cleaning requirement |
On |
| Reservations |
On |
| Waiter permissions |
Differentiated (Waiter, Head waiter, Shift leader) |
| Time tracking |
On |
| DATEV export |
Mode "Per Receipt" or "Article Group" |
| Articles |
~80 (Food menu + beverage menu) |
Workflow
Guests arrive → Reception assigns table → Table turns red (occupied)
→ Waiter takes order on tablet → Course 1 goes to kitchen
→ Kitchen display shows order → Chef marks "Ready"
→ Waiter serves → Course change → Course 2 goes to kitchen
→ Guests want to pay → Waiter checks out at the table
→ Table turns purple (cleaning) → Employee cleans → Table green
Scenario 4: Beer Garden with Tables and Direct Sale
Business: Beer garden "Zum Kastanienbaum" with 120 seats (30 tables), self-service counter, seasonal (April–October), 12 employees.
Hardware
| Device |
Type |
Description |
| Main POS |
1x touch PC (15") |
At the tap |
| Counter POS |
1x touch PC (15") |
Food counter |
| Waiter phones |
4x Android smartphones (6") |
Order taking in the garden |
| Kitchen printer |
1x ESC/POS printer |
In the kitchen |
| Receipt printers |
2x ESC/POS printers |
One per POS |
| TSE |
1x TSE module |
On the main PC |
| Card terminals |
2x ZVT terminal |
One per POS |
| Outdoor router |
1x outdoor Wi-Fi AP |
Coverage in the garden |
DiKAS Configuration
| Setting |
Value |
| Table service |
On (30 tables in 4 groups: Chestnut tree, Lawn, Pavilion, Playground) |
| Direct sale |
On (self-service counter) |
| Kitchen printer |
On (food only, beverages directly at the tap) |
| Price rules |
Happy hour 15:00–17:00 (beverages −20%) |
| Customer groups |
Regulars' club (custom prices) |
| Time tracking |
On (many temporary staff) |
| DATEV export |
Mode "End-of-day report" |
Highlights
- Smartphones instead of tablets: Waiters walk through the garden — phones fit in the apron
- Hybrid operation: Self-service at the counter (direct sale) + table service in the garden
- Seasonal business: Employees are created in spring, deactivated in autumn
- Outdoor Wi-Fi: Stable Wi-Fi throughout the garden is essential
Scenario 5: Pizzeria with Delivery Service
Business: Pizzeria "Napoli" with 8 tables, 3 delivery drivers, GloriaFood integration, 6 employees.
Hardware
| Device |
Type |
Description |
| Main POS |
1x touch PC (15") |
At the counter (order intake + POS) |
| Kitchen display |
1x monitor (22") + mini PC |
In the kitchen |
| Delivery printer |
1x ESC/POS printer |
For delivery slips |
| Receipt printer |
1x ESC/POS printer |
POS receipts |
| TSE |
1x TSE module |
On the main PC |
| Card terminal |
1x ZVT terminal |
At the counter |
| Driver phones |
3x smartphones |
Personal phones, route via WhatsApp |
DiKAS Configuration
| Setting |
Value |
| Table service |
On (8 tables) |
| Delivery service |
On |
| Delivery zones |
3 zones (City center 2 EUR, City 4 EUR, Suburb 6 EUR) |
| Free delivery |
From 25 EUR |
| GloriaFood |
Connected (auto-confirmation on) |
| Route optimization |
On (Valhalla) |
| WhatsApp routes |
On |
| Kitchen display |
On |
| Default delivery time |
40 min. |
Workflow (Delivery)
Online order comes in (GloriaFood)
→ Automatically confirmed → Kitchen receipts printed
→ Kitchen prepares → Marked "Ready"
→ Delivery service tab: Order "Ready"
→ 3 orders collected → Route optimized
→ Driver Tom assigned → Route sent via WhatsApp
→ Dispatch → Receipts created → Tom heads out
→ All delivered → "Completed"
Scenario 6: Nightclub / Club
Business: Club "Neon" with 3 bars, 800 guest capacity, NFC card system, 15 employees.
Hardware
| Device |
Type |
Description |
| Entrance POS |
1x touch PC (15") |
Admission + card distribution |
| Bar POS |
3x touch PC (15") |
One per bar |
| NFC readers |
4x USB NFC readers |
At each POS |
| Receipt printers |
4x ESC/POS printers |
One per POS |
| TSE |
1x TSE module |
On the server |
| Card terminal |
1x ZVT terminal |
At the entrance (card top-up) |
| Server |
1x mini PC |
Central, all POS terminals connected |
| Router |
1x gigabit switch + Wi-Fi |
Network for all devices |
DiKAS Configuration
| Setting |
Value |
| Disco module |
On |
| NFC card system |
On (guest tables via cards) |
| Customer credit |
On (prepaid cards) |
| Table service |
NFC guest tables only (no fixed tables) |
| Direct sale |
On (bar sales) |
| Price rules |
Happy hour 22:00–23:00 |
| Time tracking |
On (night shift over midnight) |
| Disco admission |
Configured (admission, minimum spend, free money) |
Workflow
Guest arrives → Entrance POS: collect admission fee + issue NFC card
→ Optional: top up card with credit (e.g. 50 EUR)
→ Guest goes to bar → Scan NFC card → Book beverage
→ Credit is deducted (or credit)
→ At the end: Guest pays remaining balance → Card collected
→ Night shift: End-of-day report at 06:00 (business day logic)
Highlights
- Night operation: DiKAS calculates correctly over midnight (business day 06:00–05:59)
- NFC prepaid: Fast transactions at the bar (no searching for cash in the dark)
- Multiple POS terminals: All connected via a central server
- Disco statistics: Guest count, admission revenue, beverage statistics
Scenario 7: Food Truck / Street Food Stand
Business: Food truck "Curry Corner" at weekly markets and events, 1–2 employees.
Hardware
| Device |
Type |
Description |
| POS |
1x Android smartphone (6") |
DiKAS MAUI app, in the apron |
| Printer |
1x mobile Bluetooth printer |
Star SM-L200 or similar |
| TSE |
1x microSD TSE |
In the smartphone (or USB TSE on the printer) |
| Card terminal |
Tap-to-Pay (SoftPOS) |
The smartphone itself as card terminal |
DiKAS Configuration
| Setting |
Value |
| Table service |
Off |
| Direct sale |
On |
| Articles |
8–12 (Currywurst, fries, beverages) |
| Price rules |
Event prices vs. market prices (via customer groups) |
| Tap-to-Pay (SoftPOS) |
On |
Highlights
- Fully mobile: Smartphone + Bluetooth printer — fits in a backpack
- Offline-capable: DiKAS MAUI app with SQLite works without internet
- Tap-to-Pay: No separate card terminal needed — the smartphone is the terminal
- Changing locations: No fixed installation, everything portable
Scenario 8: Workshop with Cafe
Business: Bicycle workshop "Speiche" with attached cafe, 3 employees.
Hardware
| Device |
Type |
Description |
| Workshop POS |
1x touch PC (15") |
Order intake + POS |
| Cafe tablet |
1x Android tablet (10") |
Cafe sales |
| Label printer |
1x ESC/POS printer |
Work order labels (Code128) |
| Receipt printer |
1x ESC/POS printer |
POS receipts |
| TSE |
1x TSE module |
On the touch PC |
| Card terminal |
1x ZVT terminal |
For both areas |
DiKAS Configuration
| Setting |
Value |
| Workshop module |
On |
| Direct sale |
On (cafe + spare parts) |
| Workshop status |
New → In Progress → Paused → Completed → Invoiced |
| Label printing |
On (Code128 barcode per work order) |
| Time tracking |
On |
| Customer management |
On (master data, bicycle history) |
Workflow
Customer brings bicycle → Create work order
→ Print label with barcode → Attach to bicycle
→ Mechanic works → Log working time + materials
→ Completed → Notify customer
→ Customer picks up → Invoice (working time + materials + cafe)
→ Payment → Work order completed
Scenario 9: Catering Company
Business: Catering "Festtafel" for events and corporate clients, 5 employees.
Hardware
| Device |
Type |
Description |
| Office |
1x PC with browser |
Admin, quotes, invoices |
| Event POS |
1x Android tablet (10") |
Mobile POS on-site |
| Printer |
1x mobile Bluetooth printer |
For receipts on-site |
| TSE |
1x microSD TSE |
In the tablet |
| Card terminal |
Tap-to-Pay (SoftPOS) |
Mobile, right on the tablet |
DiKAS Configuration
| Setting |
Value |
| Table service |
Off (or: 1 "table" per event) |
| Customer management |
On (corporate clients with addresses) |
| Invoices |
On (combined invoices, net mode) |
| Subscriptions |
On (regular deliveries, e.g. lunch) |
| Dunning |
On (delinquent corporate clients) |
| DATEV export |
On (mode "Per Invoice") |
| Credit |
On (corporate clients on account) |
| Expenses |
On (purchases for events) |
Workflow
Corporate client orders catering for 50 people
→ Create quote → Client confirms
→ Purchasing: Record expenses (groceries, decoration)
→ Event day: Mobile POS on-site
→ Charges posted to customer account (credit)
→ After event: Create combined invoice → Send via email
→ Payment by bank transfer → Mark invoice as paid
Hardware Overview
POS Devices
| Device Type |
Price Range |
Advantages |
Disadvantages |
Recommended For |
| Android tablet (8–10") |
150–400 EUR |
Affordable, mobile, camera |
Small screen |
Waiters, food trucks, small businesses |
| Android smartphone (6") |
200–500 EUR |
Fits in pocket |
Very small screen |
Beer garden waiters, food trucks |
| Touch PC (15") |
400–800 EUR |
Large screen, robust |
Stationary |
Main POS, counter, bar |
| Mini PC + monitor |
300–600 EUR |
Flexible, monitor size selectable |
Two devices |
Kitchen display, office |
Printers
| Type |
Price Range |
Connection |
Recommended For |
| ESC/POS network |
200–400 EUR |
LAN/Wi-Fi |
Stationary POS, kitchen |
| ESC/POS USB |
150–300 EUR |
USB |
Single station |
| Bluetooth mobile |
200–350 EUR |
Bluetooth |
Food truck, beer garden |
| Label printer |
150–250 EUR |
LAN/USB |
Workshop (barcode labels) |
Card Terminals
| Type |
Price Range |
Connection |
Recommended For |
| ZVT terminal |
300–500 EUR + fees |
LAN/Wi-Fi |
Stationary POS (highest reliability) |
| Tap-to-Pay (SoftPOS) |
0 EUR extra hardware + fees |
Android device (NFC) |
Minimal setup — the POS device itself is the terminal |
TSE (Technical Security Device)
| Type |
Price Range |
Connection |
Recommended For |
| USB TSE |
100–200 EUR |
USB |
Touch PC, mini PC |
| microSD TSE |
100–200 EUR |
microSD |
Android tablet/smartphone |
| Network TSE |
300–500 EUR |
LAN |
Multiple POS terminals (1 TSE for all) |
Decision Guide: What Do I Need?
By Business Size
| Business Size |
POS Terminals |
Server |
Recommended Setup |
| 1–2 employees |
1 tablet |
None (standalone) |
Android tablet + Bluetooth printer |
| 3–5 employees |
1–2 devices |
Optional |
Touch PC + tablet + LAN printer |
| 6–15 employees |
2–5 devices |
Yes (mini PC) |
Touch PCs + tablets + kitchen display |
| 15+ employees |
5+ devices |
Yes (server) |
Full setup with network TSE |
By Feature
| Feature |
Minimum Hardware |
| Direct sale |
1 tablet + 1 printer |
| Table service |
1 tablet/PC + Wi-Fi router |
| Kitchen display |
+ 1 monitor + mini PC |
| Delivery service |
+ smartphones for drivers |
| NFC cards (disco) |
+ NFC reader per POS |
| Workshop |
+ label printer |
| Debit card |
+ card terminal (ZVT) or Tap-to-Pay (SoftPOS) on the Android device |
| Multiple POS terminals |
+ server + network |
Frequently Asked Questions
Do I need a server?
Only with multiple POS terminals. A single Android tablet operates standalone with SQLite — no server, no internet needed.
Does DiKAS work without internet?
Yes. The MAUI app on Android works completely offline. Internet is only needed for: GloriaFood orders, route optimization, DATEV email delivery, FinTS banking.
Can I upgrade later?
Yes. DiKAS is modular — start with one tablet and expand as needed with kitchen display, delivery service, additional POS terminals, etc.
What Android version do I need?
Android 10 or newer. Recommended: Android 12+.
Can I use existing hardware?
Yes. DiKAS runs on any Android device (tablet/smartphone) or in the browser (touch PC with Chrome/Edge). Existing ESC/POS printers and ZVT terminals are supported.
How much does the DiKAS software cost?
DiKAS offers various license models — from single station to enterprise licenses. Contact us for a personalized quote.