EPOS Training & Knowledge Platform
A structured online knowledge base for tills, payments, stock, kiosks, kitchen systems and troubleshooting — written for people who have to run the estate, not only configure it.
Overview
Large EPOS estates fail operationally when only a few people know how they are supposed to work. This platform exists so tills, payments, stock, kiosks and kitchen systems can be run from documented procedures rather than from whoever is nearest with a radio.
The Problem
During major events, questions arrive faster than informal answers: how a tender should be taken, what to do when a printer fails, how a kiosk is recovered, where a stock location should deplete. If that lives in one person's head, the estate is fragile.
Requirements
- Structured coverage of tills, payments, stock, kiosks and kitchen systems
- Troubleshooting that matches devices actually on the estate
- Usable by operational staff, not only systems people
- Maintainable as configuration and hardware change
- Aligned with SOPs used by management teams
My Role
Created and maintain the platform: structure, content, operational procedures and troubleshooting. This is internal operational documentation, not a public product — internals and access details are not published here.
Approach
- Organise by the job someone is trying to do, not by the vendor menu tree
- Cover the full path: till, payment device, printer/KDS, stock, kiosk
- Write for raceday pressure: short, specific, recoverable
- Keep it next to SOPs and training rather than as a separate wiki nobody opens
System / Architecture
Content is grouped around operational domains — tills, payments, stock, kiosks/kitchen, troubleshooting — so a person can enter from the problem in front of them. It is a knowledge system sitting beside the live KAPPTURE estate, not a replacement for it.
Implementation
- Central online knowledge base
- SOP and training materials for operational and management teams
- Device and workflow coverage for payments, stock, kiosks and kitchen systems
- Troubleshooting paths for common estate failures
Challenges
- Keeping documentation current when hardware and configuration move
- Writing for mixed audiences: finance, cellar, hospitality and support
- Avoiding a document that is complete but unusable under time pressure
Outcome
Guidance for the estate has a home. Event staff and support can follow a procedure instead of reconstructing it from the last person who knew.
- A single place for operational guidance instead of tribal knowledge
- Faster onboarding for event staff and support
- Troubleshooting that can be followed without waiting for the same person
Technologies
What I Learned
- Training is part of systems ownership, not an afterthought
- Documentation has to match the device in someone's hand
- If it cannot be found in 30 seconds, it will not be used on raceday
Future Improvements
- Closer coupling to digital installation checklists
- Shorter recovery playbooks per device type
- Clearer ownership of which pages are canonical after a system change