Glossary — POS System Terminology¶
All technical terms related to DiKAS, POS systems, and hospitality IT.
A¶
ACK / NACK¶
Acknowledgment and error signals in communication with draught systems. ACK (Acknowledge) confirms the receipt of a command. NACK (Negative Acknowledge) signals an error — the command is automatically retried.
Addimat¶
Manufacturer of draught systems. DiKAS supports the Addimat protocol (STX/ETX framing with XOR CRC checksum) for automatic beverage dispensing.
Allergens (EU-14)¶
The 14 allergens subject to mandatory labeling under EU Regulation No. 1169/2011. DiKAS stores allergens per article and prints them on receipts.
API (Application Programming Interface)¶
Programming interface. DiKAS offers over 120 REST API endpoints for integration with external systems. Authentication via JWT tokens.
Article Group¶
Organizational structure for articles. Groups are hierarchically organized (up to 3 levels) and determine printer assignment, POS sorting, and article group reporting. Printer settings are automatically inherited from the parent group.
Article Option¶
Additional selection when placing an order (e.g. extra topping, side dish, preparation method). Options can have a surcharge and can be configured as mandatory or optional.
Audit Log¶
Tamper-proof log of all fiscally relevant transactions. Maintained automatically and can be downloaded as a file. Relevant for tax audits (Betriebsprüfungen).
B¶
Backup¶
Complete backup of all DiKAS data as a ZIP file. Contains all documents (JSONL compressed with Brotli) and file attachments. Can be selectively restored (e.g. only articles or only customers).
Area-dependent Print Option (Bereichsabhängige Druckoption)¶
Printer control that uses different printers depending on the table group (service area). Example: beer orders in the beer garden go to the garden printer, while orders in the dining room go to the bar printer.
Hospitality Receipt (Bewirtungsbeleg)¶
A tax-relevant receipt for business entertainment expenses. DiKAS automatically prints a hospitality receipt with occasion, participants, and tip.
Receipt (Bon)¶
POS receipt. DiKAS distinguishes four receipt types: Invoice (for the guest), Consolidated order ticket (Sammelbon — kitchen overview), Station ticket (ExtraBon — individual station), and Void receipt (StornoBon — void).
BYOD (Bring Your Own Device)¶
Concept where any end device can be used as a POS terminal — PC, tablet, smartphone. DiKAS runs in the browser and does not require specialized hardware.
C¶
Clean Architecture¶
Software architecture pattern. DiKAS is built in four layers: Domain (business logic), Application (use cases), Infrastructure (database, printers), Web (API endpoints).
CouchDB¶
NoSQL database used by DiKAS as the default data store. Advantages: offline capability through replication, document-based data model, real-time change notifications.
CQRS (Command Query Responsibility Segregation)¶
Architecture pattern that separates read and write operations. DiKAS uses commands for changes (place order, process payment) and queries for reads (load articles, display reports).
D¶
DATEV¶
Standard accounting software in Germany. DiKAS exports POS data in DATEV format (EXTF v13) with 7 different export modes. Supports encrypted ZIP archives and email delivery to the tax advisor.
Direct Sale (Direktverkauf)¶
POS transaction without table assignment. Ideal for takeaway, bakery, kiosk, or counter service. Select articles, choose payment method, done.
Docker¶
Container technology for server deployment. DiKAS is delivered as a single Docker image (API + frontend in one container).
DSFinV-K¶
Digitale Schnittstelle der Finanzverwaltung für Kassensysteme (Digital Interface of the Tax Administration for POS Systems). Standardized export format for tax audits. DiKAS creates DSFinV-K-compliant exports.
E¶
ESC/POS¶
Print protocol for thermal printers (receipt printers). Developed by Epson, supported by almost all receipt printers (Epson, Star, Bixolon, etc.). DiKAS communicates with ESC/POS printers via TCP/IP.
Station Ticket (ExtraBon)¶
Additional receipt that is automatically printed at a specific station when an order is placed (e.g. kitchen, bar, salad station). Each article can have up to two station ticket printers.
F¶
FinTS (Financial Transaction Services)¶
Protocol for online banking in Germany (successor to HBCI). DiKAS uses FinTS for automatic bank statement retrieval to match incoming payments.
FlexCel¶
Library for generating Excel files. DiKAS uses FlexCel for Excel exports (time tracking, reports, DATEV templates).
FreeCount¶
Option group setting. Defines how many of the cheapest selected options are free. Example: "one sauce included" → FreeCount = 1.
G¶
Course (Gang)¶
Course sequence in a multi-course meal. DiKAS supports course control: the waiter changes the course, and the kitchen receives a course ticket indicating which dishes should be prepared next.
Course Ticket (Gang-Bon)¶
Automatically printed receipt when changing courses. Informs the kitchen that the next course should be prepared. Only printed on printers with the course ticket option enabled.
GDPdU (GoBD)¶
Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form (Principles for the Proper Management and Storage of Books, Records, and Documents in Electronic Form). DiKAS meets GoBD requirements and creates GDPdU-compliant exports.
Gruber¶
Manufacturer of draught systems. DiKAS supports the Gruber protocol (STX/ETX framing with ENQ handshake and optional XOR checksum).
Voucher (Gutschein — Value voucher / Single-item voucher)¶
DiKAS distinguishes two voucher types: Value vouchers (any amount, 0% VAT on sale, VAT on redemption) and Single-item vouchers (for a specific article, normal VAT on sale, 0% on redemption).
H¶
House Account (Hausbon)¶
Payment method "on account." The amount is posted to the customer account and can later be issued as an invoice. No cash effect (no cash flows).
Hogatron¶
Manufacturer of draught systems (also WMF). DiKAS supports the Hogatron protocol with configurable field lengths.
J¶
JWT (JSON Web Token)¶
Authentication mechanism. DiKAS uses JWT tokens for API authentication. Tokens are issued at login and sent with every API call.
K¶
KassenSichV¶
Kassensicherungsverordnung (Cash Register Security Ordinance). Mandatory in Germany since January 1, 2020. Every electronic POS system must use a TSE (Technische Sicherheitseinrichtung — Technical Security Device) that signs transactions in a tamper-proof manner.
KDS (Kitchen Display System)¶
Kitchen display. Shows orders on a screen instead of on paper. DiKAS uses SignalR for real-time updates — new orders appear instantly.
Customer Credit (Kundenguthaben)¶
Prepaid credit on the customer account. DiKAS distinguishes AccountBalance (topped-up cash credit) and BonusBalance (top-up bonus as percentage/amount). Top-up = 0% VAT, redemption = normal VAT.
M¶
MediatR¶
.NET library for the CQRS pattern. All DiKAS commands and queries are dispatched via MediatR.
Minimum Spend (Mindestverzehr)¶
Minimum order value per guest (e.g. in clubs). Calculated as a surcharge when paying if the guest has not reached the minimum spend.
N¶
NFC (Near Field Communication)¶
Contactless communication over short distances. DiKAS uses NFC for staff login (employee holds chip to reader) and disco guest accounts (card ID).
NgRx Signal Store¶
Angular library for global state management. DiKAS uses the Signal Store (AppStore) for the application state in the frontend.
O¶
OpenBon¶
Open order item. Every ordered article on a table is stored as an individual OpenBon document. All OpenBons with the same BonId belong to one order session. Becomes a ReceiptItem upon payment.
Option Template (Optionsvorlage)¶
Reusable collection of article options. Created once and can be assigned to multiple articles. Changes to the template take effect immediately for all assigned articles.
P¶
PLU (Price Look-Up)¶
Article number for draught systems. Each tap has a PLU number. The article in DiKAS is linked to the tap via the "Draught system PLU" field.
POS (Point of Sale)¶
POS system / point of sale. In DiKAS, the area where checkout takes place (as opposed to the admin area for management).
Price Rule (Preisregel)¶
Automatic price change based on conditions such as day of the week, time, table group, customer group, or delivery mode. Article rules take priority over group rules.
PrintPool¶
Background print service in DiKAS. Manages a queue of print jobs, sends them via TCP to printers, and handles errors with automatic retries and backup printers.
Q¶
QR Code (TSE)¶
DiKAS prints a QR code on receipts that contains the TSE signature. Format per DSFinV-K Appendix I: serial number, signature counter, start time, end time, signature.
R¶
Receipt¶
POS receipt after a payment. Contains all items, tax breakdown, payment method(s), and TSE signature. Permanently stored in the database.
REST API¶
Programming interface via HTTP. DiKAS offers 120+ endpoints under /api/v1/... for all functions: articles, orders, payments, customers, reports, settings.
S¶
Consolidated Order Ticket (Sammelbon)¶
Summary receipt that groups all articles of an order for a specific station. Unlike the station ticket (ExtraBon — one receipt per article), the consolidated order ticket shows all items at a glance.
Draught System (Schankanlage)¶
Automatic beverage dispensing system. DiKAS supports Gruber, Addimat, and Hogatron/WMF via serial, TCP, or UDP. Orders automatically trigger dispensing.
SEPA Direct Debit¶
European direct debit scheme. DiKAS creates SEPA XML files for automatic bank collection of open invoices and subscriptions.
SignalR¶
Real-time communication technology. DiKAS uses SignalR for live updates in the kitchen display, for table changes, and configuration changes. All connected devices see changes instantly.
Soft Delete¶
Deletion mechanism where records are not physically deleted but marked as "deleted." This ensures they remain in reports and historical data.
Split Payment¶
Separate payment of a bill. DiKAS supports both splitting by items (each guest pays for their articles) and by amount (equal splitting).
SQLite¶
Local database engine. DiKAS can alternatively be operated with SQLite instead of CouchDB — ideal for single-station installations and the Android app.
System Article¶
Predefined articles in DiKAS that are required for internal functions (e.g. credit top-up, voucher redemption, deposit). Cannot be deleted.
T¶
End-of-Day Report (Tagesabschluss / Z-Report)¶
Close of a business shift. Summarizes all revenue, payment methods, taxes, and discrepancies. TSE-signed and printed as PDF or receipt. Resets the draught system (if configured).
Table Group (Tischgruppe)¶
Service area within the establishment (e.g. indoor, terrace, beer garden, VIP). Table groups control printer resolution (area-dependent print options) and can have their own price rules.
TSE (Technische Sicherheitseinrichtung — Technical Security Device)¶
Tamper-proof signature mechanism for POS systems. Mandatory in Germany since January 1, 2020. DiKAS supports hardware TSE (Swissbit USB) and TSE proxy (network). Every receipt, every order, and every end-of-day report is signed.
V¶
Virtual Printer¶
Placeholder printer in DiKAS: Waiter printer (__kellner__) = the printer of the current device. Default printer (__standard__) = the printer specified in the settings.
Voucher¶
→ see Voucher (Gutschein)
Z¶
Time-based Article (Zeitartikel)¶
Article with time-based billing (e.g. pool table, bowling lane per hour). The price is automatically calculated based on duration.
ZVT (Zahlungsverkehrstechnik)¶
Standard protocol for communication between POS systems and debit card terminals in Germany. DiKAS communicates via ZVT with any compatible terminal (Ingenico, Verifone, CCV, etc.) — without being tied to a specific payment provider.
Next Step¶
→ Frequently Asked Questions (FAQ) — The most important questions and answers
→ Troubleshooting — When something is not working