Skip to content
Point of sale (POS)

Sell with no queues, no outages and no till shortfalls.

A dedicated till app: split payments, SIAT invoicing with contingency, kitchen orders and blind cash close with discrepancy detection. If the internet drops, sales are stored on the device and sync on their own without duplicates.

Without MKA

  • The internet drops and the till freezes with a queue waiting.
  • At close, the cashier “adjusts” the count because they already know what should be there.
  • Shortfalls are found days later and nobody knows which shift they happened on.

What you’ll measure

Time per sale
38 s−14 s
Average ticket
Bs 86,40+7 %
Close discrepancies
0,12 %−0,31 pts
of sales
Offline sales synced
100 %0 duplicadas

Sample indicators with illustrative data. In MKA they are computed live from your operation.

Try it right here

Ring up a sale, then cut the internet.

The cashier’s till and the customer display. Add two products, cut the internet and charge anyway: the invoice is issued in contingency and the till keeps selling. When the connection returns, the queue is sent by itself as a package. Press "Watch it run" to see it play by itself.

Try it right here

Do a blind cash close.

On the left, the cashier closes her till without seeing the expected amounts: she counts the drawer and declares card and QR. On the right, the supervisor: on close they see the difference per payment method and the issue lands in their queue on its own. "Watch it run" plays it by itself.

Example flow

A till shift, from opening to close

Step 1/6

The till opens

The terminal is bound to its till; the session starts with its float and its shift target.

Sales targets

Benefits

Why Point of sale (POS) in MKA

Keeps selling offline

Sales, orders and advance payments are stored on the device and synced with retries and a lock, so nothing is sent twice.

SIAT with contingency

Invoices issued offline and sent in packages, CUFD alert and the status of each e-invoice.

Blind close

The cashier counts without seeing the expected amount; the system detects the difference per payment method and sends it to the issues queue.

Split payments

Cash, card, QR (with its reference), gift card and voucher on the same sale.

Table orders

Kitchen printing, item annulment and salesperson reassignment.

Load tested

In load tests it sustained 249 sales per second with 20 branches at once, with no duplicated numbering or stock.

In detail

Everything included

Cash sessions

  • Open and close with breakdown by payment method
  • Blind count and discrepancy detection
  • Reconciliation and issues queue
  • Cash movements with reversal and transfers between tills
  • Per-session target summary and breakdown by salesperson
  • Report with 8 tabs and receipt reprint

Continuity and SIAT

  • Offline mode: sales, orders and advance payments queued locally
  • Sync with retries and an anti-duplicate lock
  • SIAT contingency with package submission
  • CUFD alert, e-invoice status and voiding with retry

Selling and payment

  • Split payments: cash, card, QR with reference, gift card and voucher
  • Variable kits and portioning
  • Supervisor authorization
  • Thermal printing and keyboard shortcuts

Restaurant and store

  • Table orders with kitchen printing
  • Item annulment and salesperson reassignment
  • Supply requests and supply-use logging
  • Stock transfers with a pending badge

All-in-One

Connects with

Data flows between modules on its own: no integrations, no exporting or importing.

FAQ

What happens if the internet drops mid-sale?

The sale is stored on the device and invoicing continues in contingency. When the connection returns it syncs with retries and a lock that prevents sending it twice.

Is QR payment dynamic?

No. The POS records the QR payment with its reference number as another payment method.

More in Omnichannel commerce

See Point of sale (POS) with your data.

In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.