Tap Command — The PintPod Platform
Tap Command is the platform behind every PintPod. Sales as they happen, keg levels that keep themselves current, licence hours the machine actually obeys — across one bar or thirty, from wherever you are.
See Tap Command in Action »Know what you need? Get a tailored quote Rather see one pouring first? Book a demo
Running a Bar Blind
Most bars run on what someone noticed at the time. That works for one bar on a quiet night. It stops working the moment there are three of them, or one busy one.
The Keg Blows Mid-Rush
Nobody knows a barrel is nearly out until it starts pouring foam, in the middle of the busiest twenty minutes of the night. The cellar is a guess until it becomes an emergency.
Licence Hours Rely on Memory
Last orders happen because somebody remembers, walks over, and stops serving. On a good night that is fine. On a chaotic one it is the thing a licensing officer asks about.
One Barrel, Counted Three Times
Run one keg to taps on three different units and most systems count three kegs. An 88-pint barrel reads as 264, every alert fires three times, and the stock figure is fiction.
Multi-Site Means Multi-Spreadsheet
Every extra bar adds another set of numbers that only reconcile on a Monday, and only if someone does it. Comparing two sites honestly becomes a job rather than a glance.
10 Sec
Kiosk Sync Interval
3
Payment Gateways Supported
7 Days
Rolling KPIs, With Trends
Included
With Every PintPod
What It Does
Tap Command comes with every PintPod. No platform fee, no per-user charge, no separate contract.
How It Is Organised
Tap Command is built as Client, then Location, then Kiosks. Configuration lives at the location — and that one decision is what makes everything else behave sensibly.
A location is whatever you decide it is. North Concourse and South Concourse can be two locations in the same building. A festival can carve a site into a zone per stage. It is not tied to a postcode or a building; it is the unit you want to manage as one thing.
Serving Controls
Operating hours, licence hours, drink limits, prices, product assignments and open or closed state are all real configuration, set per location and mirrored by every kiosk there. Matching a licence condition is something the software does, not something a member of staff has to remember at the end of a long night.
Stock
A keg is its own record in Tap Command, tied to a location and a product, with taps pointing at it. Pour from two kiosks on the same barrel and one number moves, twice. Level alerts fire once for the barrel, not once for every tap attached to it.
Levels are derived from the sales ledger rather than measured by a sensor in the barrel, which is what makes them consistent with the money taken.
When Things Go Wrong
Every kiosk is designed to stand on its own. Connectivity is a convenience for you, not a dependency for the customer in front of it.
Optional Add-Ons
A PintPod pours for a few seconds per customer. The rest of the night it is a bright screen at eye level, in a queue, in front of people who are already spending money. Two optional add-ons turn that into something useful.
Idle Screen accepts JPG, PNG, GIF and MP4 up to 10 MB per file, with the idle delay configurable and set to five minutes by default. Content goes live at the next kiosk sync, and is cleaned off the same way when you remove it. Both add-ons are separate from each other — take either, both or neither.
Access
Four roles — admin, manager, viewer and client. A client account is genuinely walled to its own data: their units, their sales, their support thread, and nothing belonging to anybody else. That is what makes handing a venue a login safe rather than nerve-racking, and it is what lets one operator run many customers from one platform.
Common Questions
It is included with every PintPod, whether the unit is hired or purchased. There is no separate platform fee and no per-user charge. Idle Screen and Screen Branding are optional paid add-ons on top; everything else described on this page comes as standard.
Yes. Tap Command is built around Client, then Location, then Kiosks. A location is whatever you decide it is — two concourses in one stadium can be two locations, and a festival can carve a site into zones. Configuration lives at the location, so moving a unit between locations is a physical job rather than a setup job.
Each kiosk checks for changes every 10 seconds, so a price, a schedule or a closed tap takes effect within seconds. Uploaded media goes live at the next sync once the file has transferred. Kiosk software updates overnight on its own.
Every sale is written to local disk before any network call is attempted, so a dropped connection delays the upload rather than losing the transaction. Card readers fall back to offline authorisation, and safety actions like closing a tap or closing the kiosk still work at the unit. What you lose during an outage is visibility, not sales.
The admin screen locks itself and returns the kiosk to customer mode after a set idle period. The default is five seconds, configurable per unit up to five minutes. It is deliberately unforgiving, because an admin screen left open in a busy venue is a screen the public can reach.
Yes. There are four roles — admin, manager, viewer and client — and a client account is walled to that client's own data: their units, their sales, their support thread, and nothing else. Two-factor authentication is available, and sessions time out after 10 minutes idle.
Get In Touch
Tell us how many bars you run and what you are trying to see. We will walk you through Tap Command on a call and show you the same screens your team would use.
We will be in touch to arrange a walkthrough of Tap Command against how your bars actually run.