Home / Supported POS

Ten POS systems, read the same way.

Numal connects to the point of sale your client already runs. Every connection is read-only, approved by the business owner, and limited to the amount and time of settled sales. Where a POS gives us less than the others, it says so on its tile.

Square

Live

The default for cafés, salons and small retail in the US, UK and Australia.

Connection · OAuth, read-only History read at setup · 24 months New vs returning · Yes, via customer directory

Toast

Live

Restaurants, bars and anywhere with table service. US only.

Tips arrive separately from the sale, so attributed revenue excludes them.

Connection · Partner API, read-only History read at setup · 18 months New vs returning · Yes, on loyalty accounts

Clover

Live

Barbers, studios, convenience and quick service. Common where the merchant bank sold the terminal.

Connection · OAuth, read-only History read at setup · 24 months New vs returning · Yes

Shopify POS

Live

Shops that also sell online. In-store and online sales are read separately.

Online orders are matched on a longer window than walk-ins.

Connection · Private app, read-only History read at setup · 24 months New vs returning · Yes

Lightspeed

Live

Hospitality and multi-location retail, strong across Europe and Canada.

K-Series and O-Series both work; X-Series is on the list.

Connection · OAuth, read-only History read at setup · 18 months New vs returning · Yes, on Retail and Restaurant

Stripe Terminal

Live

Businesses running a custom checkout on Stripe hardware.

Card-present charges only. Online Stripe payments are a separate connection.

Connection · Restricted API key History read at setup · 24 months New vs returning · Yes, where Customers is used

SumUp

Live

Market stands, mobile vendors and very small shops across Europe.

No customer record, so new-versus-returning is unavailable on this POS.

Connection · OAuth, read-only History read at setup · 12 months New vs returning · No

Zettle

Live

PayPal's card reader. Widespread with UK and Nordic independents.

Connection · OAuth, read-only History read at setup · 12 months New vs returning · Partial

Epos Now

Beta

Pubs, salons and retail in the UK and Ireland.

In beta: timestamps can lag settlement by a few minutes, which we correct for.

Connection · API key, read-only History read at setup · 12 months New vs returning · Yes

Revel

Beta

Multi-location quick service and franchise groups.

In beta: location rollups are supported, per-station splits are not yet.

Connection · Partner API, read-only History read at setup · 18 months New vs returning · Yes

What we read from every one of them

	Read	Never
Money	Amount of each settled sale	Card numbers, cardholder data
Time	Timestamp of the sale	—
People	Whether a sale was a first visit or a repeat, where the POS tracks it	Names, emails, phone numbers, loyalty identities
Items	Nothing	Itemized baskets — we see $14.20, not two flat whites
Refunds	Deducted from the attributed total	—

Settled means settled. Authorizations that never clear, voided tickets and open tabs are excluded, which is why a Numal figure matches the client's own month-end rather than a live dashboard.

How a connection happens

1. You pick the POS	From the list above, on the business you're adding.
2. The owner approves it	They get an email, grant read-only access themselves, and can revoke it at any time without going through you.
3. We read the history	Between twelve and twenty-four months, depending on the POS. This is what makes the first baseline possible.
4. Two quiet weeks	Nothing is credited to a post before the baseline is built. The first report follows.

Beta means the connection works but the edges aren't finished. We'll tell you which parts before you connect a client to one, and a beta POS never costs less accuracy without being labeled in the report itself.

Not on the list?

Tell us which POS and which business, and we'll give you a straight answer about whether it's coming — including “not this year”, which is the honest answer for POS systems without a usable API.

Two things worth knowing while you wait:

A CSV export can stand in. If the POS exports settled sales with timestamps, we can read a monthly upload. It's clumsier and the baseline takes the same fourteen days, but the numbers are the client's own.
Never on the roadmap: screen-scraping a POS dashboard or asking a business owner for their login. Both are the sort of shortcut that ends with someone's card data somewhere it shouldn't be.

Ask about a POS → Get early access