Offline-first
Sells without a signal
Orders, auths, and the menu live on the device. When the signal returns, everything reconciles. No dropped payments.
Food truck POSOne reader,
no fixed rig.
TablePort runs on a phone behind the hatch. Offline-first: payments queue when the signal drops and settle when it returns. Nothing waits for 4G.
Works offline. UK rails. Month-to-month, cancel any time.
Lunch window12:40 · 9 in queue
- #41 · brisket boxReady
- #42 · loaded friesCooking
- #43 · two tacosPaid
Offline-first: the queue survives a dead hotspot
What changes on the road
The gig that doesn't need a signal.
The signal drops and you keep selling.
Orders and card auths queue locally. The customer leaves with their burrito; the settlement clears when you're back on a bar.
One tap from order to receipt.
Tap card, tap done. No tip prompt rabbit hole, no second screen. The line behind you moves on actual prep time.
Event-by-event reporting.
Every gig is its own report. Where you parked, what you sold, what you ran out of by 8pm. The post-event email writes itself.
Built for the truck
The toolkit, tuned for food trucks.
Light rig
Runs on a phone or one iPad
Bring what you already have. The card reader pairs over Bluetooth. No fixed terminal, no power-hungry till.
Tap to pay
Settlement in one tap
Contactless on the reader or directly on the phone (Tap to Pay). Apple Pay, Google Pay, card: the queue keeps moving.
Events
Per-event reporting
Tag every gig: market stall, carnival, private booking. End-of-day report is filed against the event, not lumped into the week.
Menu
86'd in one tap
Sold out of the brisket? Tap once on the phone, it's hidden from QR ordering and the till at the same time.
QR queue
Order-ahead from the line
Customers scan a QR, order on their phone, pay there. A name pops on the screen when it's ready. The hatch isn't a bottleneck.
Saturday, 19:20
“The signal dropped. The line never noticed.”
TablePortIn service
Saturday, 19:20
4G drops. Burritos
keep going out.
Three cards in the queue tap, get an auth, and the customer walks away. The reader holds the captures locally. Twenty minutes later the bar comes back, everything settles, no one notices.
Yes. Card auths, orders, and the menu live on the device. Captures queue offline and settle when signal returns, the same offline-first design used across every till.
No. A phone behind the hatch and one card reader is the rig. Tap to Pay on the phone works too, if you don't want a separate reader.
Customers scan a QR on the truck, order on their phone, pay there. Their name shows on your screen when the order's ready. Cuts the queue without cutting the experience.
Yes. Tag every gig, and it gets its own report at end-of-event with sales, top items, what ran out, and average ticket time. Filed for tax later, ready for the WhatsApp recap now.
UK acquirer, UK VAT, UK receipts. Set the VAT rate per menu line if you mix food and ancillaries.
Ready to take TablePort
for a spin?
30 days free. No card required. White-glove migration in a weekend.