A kiosk is not a shrunken website
The person using a kiosk is standing, has a queue behind them and is seeing the screen for the first time. So the measure of success isn’t the number of features but how many seconds and taps a transaction takes. Large touch targets, a single main action and a way back at every step are the foundation of the design.
Scope tiers and timelines
| Kiosk type | What it includes | Time |
|---|---|---|
| Single-flow kiosk | Queue ticket, application or check-in screen | 3-5 weeks |
| Ordering kiosk | Catalogue or menu, basket, orders routed to the kitchen or warehouse | 5-8 weeks |
| Kiosk with payment | Payment terminal integration, receipts and invoices | 6-10 weeks |
| Remote management panel | Content, prices and status across several kiosks | 2-4 weeks |
Devices in the field fail in the field
A kiosk is a device standing on its own: the connection drops, the printer runs out of paper, someone walks away halfway through. We plan how each of these is handled from the start, and provide a panel where you can monitor every kiosk remotely, so you see that a device has a problem before a customer complains.
How a self-service order moves through the kiosk
On paper these five steps look simple. The work is in the small cases between them. What happens if a customer fills the basket and walks off? Where does the order go if the payment is declined? How does the customer get an order number if the printer fails? We write each of these down during design.
- After a set time with no touch, the screen resets and the basket is cleared, so one customer’s choices never carry over to the next.
- If a payment fails, the basket is kept and the customer can try another method or is sent to the till.
- If the receipt can’t print, the order number is shown in large type on screen and an alert opens in the management panel.
- Each screen has one main button, and "Back" and "Start again" sit in the same place on every screen.
Choosing hardware for a kiosk project
Software and hardware limit each other, so we suggest choosing the device once the flow is clear. If you already have devices, we build the software around them. If you don’t, these are the points to go through with your supplier.
Screen
Size and orientation (portrait or landscape) shape the interface from the start. At sunny entrances, brightness matters too.
Receipt printer
Decide what the kiosk does when paper runs out, and who changes the roll.
Payment terminal
The integration method your bank or payment provider offers sets the scope and the timeline.
Scanner
If you need a barcode, QR or card reader, we test how it talks to the device before building on it.
Connection
Wired, wireless or a mobile line. What the kiosk does when the connection drops is defined in the software.
Enclosure and mounting
Cable routing, ventilation and a service hatch. Someone should be named to open the unit when it fails.
Ask your supplier how long spare parts take to arrive, whether there is on-site service for faults, and whether they provide developer documentation for the connected hardware. That last answer has a direct effect on how long the software takes.
How a kiosk project runs, step by step
- 01
Discovery call
30 minWe talk through where the kiosk will stand, who will use it and what they need to do on it. It’s free.
- 02
Flow and screen design
We map every screen and every failure case, and cut the number of taps at this stage.
- 03
A working version on the device
WeeklyEach week you get a version you can try on the real screen. The task list stays open to you.
- 04
Pilot at one site
The kiosk runs first at one branch or entrance with real customers. This is where the sticking points show up.
- 05
Roll-out and support
30 daysThe other sites are connected to the remote management panel. Bug fixes are free for 30 days after launch.
The tier you choose sets the overall timeline: a single-flow kiosk takes 3-5 weeks and a kiosk with payment takes 6-10 weeks. If the scope changes along the way, we send you the effect on time and budget in writing within 24 hours.
Is a kiosk the right answer for you?
A kiosk makes sense when
- The same short transaction repeats many times a day
- The till or front desk becomes a bottleneck at peak times
- The choices are limited and can be explained on screen
- You offer the same service at several sites
Something else may suit you better when
- The transaction needs a long explanation or advice
- Customers could do the same thing on their own phone via a QR code, which is usually cheaper
- There are only a few transactions a day and no queue
- A member of staff has to check ID or documents
Frequently asked questions
Will it work with our existing kiosk hardware?
In most cases, yes. The first step is reviewing the device’s operating system, screen and connected hardware (printer, payment terminal, scanner); the software is designed around that review.
Can the kiosk take payments?
Yes. Payment terminal integration is its own scope tier and is planned around the integration method your bank or payment provider offers.
How do we manage kiosks across several branches?
Through the remote management panel: menu, price and content changes go out to every kiosk from one place, and you can see whether each device is online and when it last completed a transaction.
Does the kiosk work without an internet connection?
The kiosk is set up to keep taking transactions when the connection drops. Records are held on the device and sent to the centre once the connection is back. Steps that need online approval, such as card payments, depend on the payment terminal’s own connection, so we agree up front what the screen shows in that situation.
What drives the cost of kiosk software?
The tier is the biggest factor: a single-flow queue screen and an ordering kiosk that takes payments are very different jobs. Connecting to your existing till, stock or booking system and the number of kiosks also affect the scope. Our rates are US$25-60 per person-hour, depending on the role, and projects start from US$1,000. The firm figure comes once the scope is clear in the discovery call.
Who owns the kiosk software’s source code?
The source code and IP transfer to you on final payment. Delivery includes the source code, documentation and setup instructions, so you can develop the kiosks further with another team later if you choose.