Five device classes
SmartPOS, desktop, tablet, mobile, and browser — the same operation, with no parallel version.
Platform · Operations layer
PDV Multi-OS
Standardized operation across different devices, on a single technology base.
The challenge
A chain rarely has the same equipment across every location. A street-front store, a mall kiosk, and an events operation each call for different hardware, and every new purchase joins a fleet that's already heterogeneous. When the system requires a specific device, the chain ends up deciding its operation based on what the software accepts — not on what the venue needs.
What this costs
The cost shows up in three places. In capital, because standardizing hardware to match the software means replacing equipment that still works. In training, because every parallel POS version is one more manual, one more script, and one more refresher cycle. And in expansion, because opening a location stops being a repeatable process and becomes an infrastructure project.
EPOC's POS runs the same operation on SmartPOS, desktop, tablet, mobile, and browser, from a single codebase. Service is standardized because the interface and the rules are the same; hardware stays flexible because none of them depend on the device. A team trained on one terminal can operate any other.
5
device classes
Product specification
Layer 01
Operation
This is where the order originates. Everything the POS records flows up to the Multi-store ERP, which applies the chain's rule, and ends in the Data Lake, from where the data feeds the customer's BI.
What this delivers
Offline operation
The terminal keeps entering orders and closing tabs without internet; synchronization happens when the connection returns.
Entry by seat position
Order tied to the seat at the table, for dining room service that needs to know who ordered what.
Tab and table
Opening, transferring, merging, and splitting tabs without leaving the service flow.
Multiple points of sale
Multiple terminals and mobile registers in the same venue, sharing the same tab.
Single codebase
Fixes and new features reach every device at the same time.
Split checks and partial payments
One check takes several payments in different methods, with the amount already paid and the amount still due always in sight — the table closes with no calculator and no queue at the register.
Conversation with
- Certified acquirers
- Multi-store ERP
- KDS
- Self-service
- Data Lake
In operation
Large-format bar
Tatu Bola
Technology ready for the hour when everything happens at once.
The challenge
Order concentration at peak times, multiple simultaneous points of sale, and check closeouts under queue pressure.
40tables
Individual tab at the tabledeployed
Frequently asked questions
Do I need to replace the locations' equipment to implement it?
That's not a premise of the product. The POS runs on all five device classes, so the existing fleet is usually reusable. What determines replacement is the condition of the equipment, not a software requirement — and that's evaluated in the implementation assessment.
What happens to the operation if the internet goes down?
The terminal keeps entering orders and closing checks locally. When the connection is restored, synchronization happens without operator intervention.
Does the team need different training for each device?
No. The interface and the rules are the same across all of them, which reduces training material to a single set and allows staff to be reassigned between locations with different equipment.
How does the POS communicate with the ERP and the KDS?
Through the same architecture: the order recorded on the POS flows up to the Multi-store ERP, which centralizes menu, price, and permissions, and is dispatched to the KDS in production. There's no file-based integration or manual synchronization.
Talk to a specialist
Your operation has grown. Is your technology ready?
How many locations, what stack is already running, what needs to be integrated, and what the rollout would look like.
