What is self-service kiosk software?
Self-service kiosk software lets customers complete tasks such as ordering, paying, getting a ticket or queue number, or registering on a touchscreen terminal without staff help. The screen app guides the user step by step, peripherals (card reader, barcode/QR reader, thermal printer, payment terminal) complete the transaction, and a central panel manages content, prices and device status remotely.
- Welcome: Language and task selection (order, payment, ticket, registration).
- Task: Few steps with large touch targets.
- Payment or confirmation: Card, QR or staff card verification.
- Output: Receipt, ticket or queue number printing.
- Reset: Timeout returns to the start and clears the previous user's data from the screen.
The most critical point of a self-service kiosk is that users finish without help and that no data is lost when the connection drops. For industry-specific flows see restaurant ordering kiosk, self-checkout software and queue management system.
What is a kiosk and what does it do in each industry?
A kiosk is a self-service terminal, usually fixed in place with a touchscreen, where users complete a transaction on their own without an attendant. The hardware alone means little; it is the kiosk software that defines the flow, the rules and the integrations. Typical uses by industry:
- Retail: self checkout software for tills and price-check points where customers scan and pay for products themselves.
- Restaurants and cafés: a self-service ordering kiosk where guests pick from the menu, pay, and the order goes straight to the kitchen.
- Transport and events: a ticket kiosk for choosing a trip, seat or session and printing the ticket.
- Healthcare: hospital kiosk software for patient check-in, appointment confirmation and queue tickets.
- Hotels: a hotel self check-in kiosk that takes pressure off the front desk.
- Public sector: government and municipal kiosk software for applications, payments and information; in waiting rooms, a queue management system.
The layers of kiosk software
A working kiosk project is more than a single screen app. A solid architecture treats each of these layers separately:
- Screen app: a user interface designed with large touch targets, a short flow, automatic reset on timeout, multiple languages and accessibility in mind.
- Kiosk mode and lockdown: the app opens full screen, users cannot reach the operating system, settings or other apps, it starts automatically on boot and restarts itself after a crash. For the Android side see the Android kiosk mode app page.
- Device integrations: card reader (RFID/NFC employee or membership card), barcode/QR scanner, 58/80 mm thermal receipt printer, payment terminal (a certified device from the bank or payment provider, via the provider's API/SDK), camera and, where needed, a relay/lock/motor control board.
- Central management panel: menu, product, price and content updates; online/offline status of devices, paper or stock alerts; transaction, sales and error reports; user and permission management.
- Offline operation: when the internet drops, the kiosk keeps working on local data, queues transactions and syncs with the server once the connection returns.
At Brisa these layers are concrete: the PPE kiosk reads the employee card, checks product limits per employee and department, and gets approval or rejection through the vending machine API; machines, slots, stock, staff and reports are managed in the web admin panel. The system is installed at two separate facilities. For the occupational safety side of a similar setup, see PPE vending machine software.
Off-the-shelf kiosk software or custom development?
Off-the-shelf kiosk software gives a quick start for a standard menu or information screen, a single hardware type and a flow that will not change. If your flow is not standard, the kiosk must talk to your existing ERP/stock/POS system, or special hardware (locked compartments, motorised slots, card readers) has to be controlled, custom software development delivers a better result.
- Off-the-shelf fits when: the flow is an industry standard, no integration is needed, and an annual licence fee and vendor lock-in are acceptable.
- Custom software fits when: you have your own business rules (limits, approvals, promotions, permissions), you need API integration with existing systems, you want to choose the hardware yourself, and you want to own the source code and the data.
Project process and hardware selection
- Discovery: the user flow, transaction steps, systems to integrate and peripherals to use are clarified. If the kiosk will sell, local fiscal receipt requirements (in Türkiye: e-Arşiv invoice or new-generation cash register integration) are defined at this stage together with your accountant or tax advisor.
- Hardware and platform: operating system, screen size and orientation (portrait/landscape) and the connection type of each peripheral (USB, serial port, Bluetooth, network) are decided.
- Interface prototype: the screen flow is tried on a full-size screen; touch targets and step count are simplified.
- Development and integration: the screen app, device drivers and management panel are built together.
- Field test and installation: trials with real users and testing of scenarios such as paper running out, network loss and power cuts.
- Maintenance: ongoing support with remote updates, monitoring and error logs.
- Windows: broad driver support; preferred when serial ports, legacy printers and payment devices are involved, and for .NET desktop apps. Can be locked to a single app with Assigned Access.
- Android: suited to low-cost tablets and ready-made touch panels that boot fast and can be managed remotely with MDM.
- Linux: stands out with Raspberry Pi or industrial boards for embedded control, driving relays/motors and long uninterrupted operation; see embedded software and IoT.
Installation in Türkiye and abroad, remote support
Hakan Sevimoğlu is based in İzmir, but kiosk projects are not tied to one city. The software is prepared in a test environment before installation; on-site setup is done in person or by guiding the installation team remotely. The Brisa PPE kiosk running at two separate facilities, and a Turkish/German self-service ordering kiosk for a döner restaurant chain in Germany (at demo/development stage), are examples of this way of working.
- Remote version updates and configuration changes.
- Device status, error logs and transaction tracking from the management panel.
- Menus, prices and content updated without a site visit.
- For installations abroad, multiple languages and local payment/receipt requirements built into the project from the start.
What I offer
Full-screen kiosk mode
Users cannot reach the system or settings
Card and QR reader
Employee card, membership and ticket checks
Thermal receipt printer
Order numbers, receipts and tickets
Payment terminal
Certified device via provider API/SDK
Central management
Content, prices, device status, reports
Offline operation
Local queue during outages, then sync
Technologies I use
Example projects
A selection of live projects serving real users.
ISG Virtual Warehouse Dispatch Assistant
Occupational safety ERP with REST API and BI dashboard.
View
Vending Machine Software
Embedded control, touchscreen sales UI, payments and remote management.
View
Restaurant POS & Order Management
Tables, kitchen and checkout in one system.
ViewHow we work
Free intro call
We clarify needs, existing systems and goals together.
Quote & roadmap
Scope, technology, timeline and budget within 24 hours.
Staged development
Weekly demos and a live test environment.
Launch & support
Go-live, training and ongoing maintenance.
Free pre-analysisThe first meeting and roadmap are completely free, with no obligation.
Staged delivery and approvalYou review each module on a test environment before we move on.
Written scope and rightsScope, delivery and source code rights are defined in the contract.
Frequently asked questions
What is a self-service kiosk?
A touchscreen terminal where customers complete orders, payments, tickets, queue numbers or registrations themselves, without staff. The kiosk software controls the hardware and defines the flow.
Which businesses is self-service kiosk software suitable for?
Restaurants and cafés, supermarkets and stores, hospitals and clinics, hotels, transport and event venues, municipalities and in-house dispensing points (e.g. PPE dispensing kiosks opened with a staff card).
How long does kiosk software take to build?
It depends on the number of steps in the screen flow, the peripherals to integrate (card reader, printer, payment terminal), integration with existing systems, the scope of the management panel and field testing. Once these items are clarified in discovery, a work plan is drawn up.
Which operating system should a kiosk use?
Windows stands out when serial ports and legacy peripherals are used, Android when you want low-cost tablets or panels with remote MDM management, and Linux when relay/motor control and embedded operation are needed. The choice follows the driver support of the hardware to be connected.
Can custom software run on off-the-shelf kiosk hardware?
Yes. Touchscreen kiosk enclosures on the market usually consist of a standard PC or Android board, a screen and USB/serial peripherals. Once the driver or SDK support of these units is checked, custom software can run on the same hardware.
What is needed to take card payments at a kiosk?
A certified payment terminal from the bank or payment provider is used, and integration is done through the provider's API/SDK. Card data is not stored in the kiosk software; it only sends the amount and receives the approval or decline. If the kiosk sells, fiscal receipt requirements are clarified with your accountant.
Does the kiosk keep working if the internet goes down?
Yes, if offline operation is designed in. Menus, prices and rules are kept locally on the device, transactions are queued and synced with the server when the connection returns. For steps that must be online, such as payment or live stock approval, the outage scenario is defined at the start of the project.
Can kiosks be managed remotely?
Yes. A central web panel updates menus, prices and content; it monitors device status, error logs and transaction reports; and software updates are rolled out without a site visit.