Where mPOS is today. mPOS is in active development, with early-access rollouts starting with a small number of businesses. We're deliberately taking on few enough of them to be on site for the first shifts. If that's a fit for how you'd want a till replaced, we'd like to talk.
Why it's built this way

Built around the floor, not the back office

Offline-first

A connectivity drop mid-service doesn't stop a sale.

Fast on cheap hardware

Runs well on inexpensive Android devices — no premium tablet required.

Trained in a shift

Not a week. Staff are working in it the same day.

What it connects to

Integrations, honestly labelled

mPOS is early. Rather than imply an integration is finished when it isn't, we mark anything not yet built as planned — an integration a buyer discovers isn't real does more damage than a shorter list.

  • Payments and card terminals (planned)
  • Delivery aggregators, for F&B (planned)
  • Tally and Zoho (planned)
  • E-commerce and marketplace stock, for retail/fashion (planned)
  • WhatsApp Business (planned)
How a rollout works

Assess, plan, roll out, support — for a till

01

Assess

Your menu or catalogue, your hardware, and how the floor actually runs today.

02

Plan

Menu or catalogue migration mapped out, hardware sorted, a switch-over sequence agreed.

03

Roll out

Staff trained on their own devices, with someone on site for the first shifts.

04

Support

Direct access to the team that built it while the product is this young.

Early access

What early access means

What it means

Reduced pricing, a direct line to the people building it, and your feedback shaping the roadmap.

What we ask

Patience with a young product, and honest feedback when something doesn't work.

FixedScope and price per engagement
Advisory · Build · RunEngage at any depth
Senior onlyBuilt by people who've shipped it before

Want to see mPOS on your own floor?

Request early access or book a walkthrough — we'll tell you honestly whether it's ready for what you need.

Request early access