TUKO/Features/Point of Sale
TUKO Point of sale

A POS terminal that already knows your business.

Open the register, tap products, take payment — cash, card, wallet, or split. Every sale posts to your inventory, customers, and reports. No second system to reconcile.

Open register. Tap. Take payment. Done.

The cashier flow is three taps of training — a new hire can run the counter on day one.

Open the register

Sign in on your terminal and start a session with an opening float. Terminals are registered per location — each with its own code, optional device binding, and a default receipt printer.

Ring it up

Tap products on the grid, or search by name, SKU, or barcode — results appear as you type. Categories keep the grid short; stock awareness keeps you from selling what's gone.

Take payment

Cash with tendered amount and change — quick-tender buttons for the common bills — plus card, bank transfer, digital wallet, check, or other. Split a sale across methods in the same checkout.

Done — receipt and all

The sale commits first, then the receipt prints through the device's print dialog or shares as a PDF. A printer hiccup never loses a sale — reprint anytime from the record.

Built for the counter, wired to the back office

Everything a register should do — and none of the re-entering after close.

Speed at the till

A product grid, cart, and checkout panel laid out for landscape tablets — adapting to portrait and phones. Fast debounced search, large touch targets, dark mode, and screen-reader labels.

Every payment method

Cash with change computed, card, bank transfer, digital wallet, check, other — and split payments on one sale. Each payment is individually recorded, auditable, and idempotent: a double-tap or retry can never charge twice.

Cash sessions that reconcile

Opening float, cash payouts with a reason, and a close-out that compares expected cash — computed server-side — against what you counted. Variance shows clearly on the session summary.

Customers, optional

Walk-in is the default — no friction for a quick sale. Attach an existing customer when it matters and the sale lands on their record with everything else.

Multi-location aware

Terminals belong to your locations, so inventory resolves against the right branch. Run one register or a dozen across a multi-location workspace.

Into one system of record

POS sales flow into orders, inventory, payments, and Business Pulse — a counter sale and a phone order live in the same reports.

Keeps selling when the internet drops

On the native apps, a dead connection doesn't close the register — it just delays the paperwork.

What happens offline

  • Sales taken without a connection are queued durably on the terminal — closing the app doesn't drop them.
  • When connectivity returns, queued sales replay automatically under the same cashier and workspace.
  • Replays are deduplicated — the queue can't post the same sale twice, no matter how the connection flaps.

What never happens

  • No silent loss — a sale that can't post cleanly (a different cashier signed in, a product removed, insufficient stock) is parked for manager review, not dropped.
  • No double-charges — payments are idempotent, so a retry is safe even when the network isn't.
  • No end-of-day surprise — queued and parked sales are visible, so you always know what's still in flight.

Offline capture is available on the iOS and Android apps; the web app needs a connection to sell.

Locked down like the rest of TUKO

The register is where cash moves — so every sensitive action is gated and logged.

Permission-gated actions

  • Sell, cash payout, refund, void, reconcile, and manage terminals/printers are separate permissions, granted per staff member.
  • Discounts apply only for authorized staff — a cashier can't discount their own drawer.
  • Every gated action lands in the audit trail: who, what, when, and on which terminal.

Workspace isolation

  • Terminal codes are unique per organization, with optional device binding and a default receipt printer per terminal.
  • Data is isolated per organization in the database — one workspace can never see another's sales.
  • Currency and timezone come from your organization settings — never hard-coded.

Not a bolt-on — the same workspace

TUKO POS isn't a separate product with its own analytics. A sale at the register deducts stock, records payment, updates the customer, and feeds Business Pulse — so a slow-moving item on the shelf or a best-seller at the counter shows up in the same morning brief.

New to the terminology? POS vs ERP: what's the difference explains how a point of sale and a business system fit together — TUKO is both.

POS questions, answered

How does a sale work in TUKO POS?

Open a register session with a starting float, tap products to build the cart, take payment — cash, card, bank transfer, digital wallet, check, other, or a split across methods — then print or share the receipt. The sale posts to inventory, payments, and reports automatically.

Does TUKO POS work offline?

Yes, on the iOS and Android apps. Sales taken without a connection are queued durably on the terminal and replay automatically when you're back online — deduplicated, so a retry never posts twice. Sales that need attention are parked for manager review, never silently lost.

Can TUKO POS take split payments?

Yes. A customer can pay part cash and part digital wallet — or any mix of methods — on one sale. Each payment is recorded individually and auditable on its own.

Does TUKO POS process card payments?

TUKO records card payments on the sale but does not run a card terminal — take the card on your own terminal or payment app, then record the payment in TUKO so the sale, receipt, and reports stay complete.

How do cash sessions and end-of-day work?

Each session starts with an opening float. TUKO computes expected cash as you sell, cash payouts are recorded with a reason, and at close you enter the counted cash to see the variance — an X/Z-style session summary, fully audited.

Can cashiers apply discounts or void sales?

Only with permission. Discounts, cash payouts, refunds, voids, and terminal settings are permission-gated actions — granted per staff member and written to the audit trail.

Every sale. Counted.

Create your workspace and open your first register today.

Get started free

Free to start · No credit card required · Works on web, iOS, and Android