u.POS Contact

Retail POS · iPad · iPhone · Stripe S710 · Desktop

Sell anywhere,
keep sales in one place.

u.POS is a retail POS that sells the same products, stock and sales across iPad, iPhone, Stripe payment readers and PC. The server confirms every payment, and one admin console runs the rest.

Card · CashReceipts · Formal receiptsStock reservationQR refundsJapanese · Korean
4sales platforms
1admin console · 1 API
2payment methods (card · cash)
2app languages (Japanese · Korean)

Platforms

The right device for every counter.

Every app uses the same API and the same design system. iPad at the counter, an iPhone or a single reader at a pop-up, a PC in the back office — mix them freely and sales and stock still add up in one place.

All in one reader

Stripe S710 POS

A POS that runs directly on the Stripe payment reader. From picking products to card payment and receipt, it all happens in one hand.

  • Pick products → card payment → Bluetooth receipt
  • Cash payments and register (float, paid in/out, expected balance)
  • Charge a typed-in amount
  • Formal receipts with numbered reissue copies
  • Refund lookup by receipt QR (managers)
  • Battery level display · admin PIN lock

Kotlin · Jetpack Compose · Stripe Terminal

iPadOS

iPad POS

Landscape for the counter. Catalog and cart at a glance.

  • 4-column catalog + cart column
  • Card (S700/S710 readers) · cash
  • Automatic recovery of unfinished orders
  • Order history · handover · reprint
iOS

iPhone POS

For pop-ups and mobile sales. The iPad features in portrait.

  • Bottom tabs: sell · orders · printers · settings
  • 2-column catalog + cart bar
  • Same payment and printing engine as iPad
macOS · Windows

Desktop POS

For PC checkouts. Fast with a barcode scanner and keyboard.

  • USB barcode scanner · keyboard cash entry
  • LAN and OS-driver printers
  • Refunds · register · cached catalog when offline
Web

Admin console

Run the whole operation in the browser.

  • Products · SKUs · per-location prices · images
  • Stock receiving · counts · transfers · ledger
  • Orders · refunds · returns · print history
  • Sales reports · CSV · share links
  • Staff roles · devices · readers · audit log

Payment flow

The server confirms every payment.

Receipts print only after the server — not the app screen — confirms the payment through Stripe's signed notification. If the app closes midway, the order picks up where it left off.

  1. Pick products

    The catalog, prices and available stock for the location come from the server.

    POS
  2. Order · reserve stock

    The server recalculates with its own prices and reserves every SKU at once.

    Server
  3. Pay

    Take a card on the Stripe reader, or cash with the amount tendered and change.

    POS · Reader
  4. Server confirms

    The webhook signature is verified, the order is marked paid and reserved stock becomes a sale.

    Server
  5. Print receipt

    The confirmed receipt goes to the store printer — Japanese, Korean and QR intact.

    POS · Printer
  6. Handover · reconcile

    After handover, sales, reconciliation and reports live in the admin console.

    Admin

Idempotent A repeated request is applied to payments and stock only once. An app timeout is never treated as a failure.

Features

Everything a store needs.

Card payments

Stripe Terminal S700, S710 and WisePOS E. After a decline or cancel, the same payment is collected again.

Cash · register

Tendered amount and change, float and paid in/out records, expected balance.

Automatic receipts

Bluetooth, LAN and OS printers. Printed as images, so Japanese and Korean work on any model.

Formal receipts

Addressee and description, reissues numbered and kept in the history.

QR refunds

Scan the receipt QR, choose items, refund in full or in part. Managers only.

Per-location stock

Reserved on order, sold on payment. Receiving, counts and transfers all stay in the ledger.

Sales reports

Sales by location and period, CSV, and read-only share links for partners.

Roles · security

Admin, manager and staff roles, registered devices only, two-factor for admins, audit log.

Architecture

Built so selling never stops.

  • ✓
    An API at the edge

    Cloudflare Workers answers from close to wherever you are.

  • ✓
    Payment events are never lost

    Webhooks are stored first; queues and scheduled jobs handle retries and reconciliation with Stripe.

  • ✓
    One contract

    A single OpenAPI contract keeps every app and the admin console on the same data.

FAQ

Frequently asked questions.

Which devices does u.POS run on?

You can sell on iPad (landscape), iPhone (portrait), Stripe Reader S700/S710 payment terminals (running directly on the reader) and macOS or Windows desktops, and manage everything in the browser-based admin console. Every device shares the same products, stock and sales data.

Which payment methods are supported?

Card payments through Stripe Terminal readers (S700, S710, WisePOS E) and cash. For cash, the POS calculates the amount tendered and change, and the register screen tracks the float, paid-in and paid-out amounts and the expected balance.

What happens if a payment is interrupted?

Payments are confirmed by the server after it verifies Stripe's signed notification, not by the app. If the app closes or the network drops, the order stays on the server and resumes when the device reconnects, and a repeated request is applied to payments and stock only once. Card payments themselves require a connection.

Which receipt printers can I use?

ESC/POS thermal receipt printers over Bluetooth, LAN (port 9100) or the PC's OS printer driver. Receipts are rendered as images, so Japanese, Korean and QR codes print correctly on any model.

Can it issue Japanese formal receipts (領収証)?

Yes. On the payment-complete screen, enter the addressee and description to issue a formal receipt; reissues carry a copy number and are kept in the history. Issued receipts and cancellations are visible in the admin console.

Can each store have its own stock and prices?

Yes. Stock and prices are kept per location and SKU. Stock is reserved when an order is created and turned into a sale once payment is confirmed, and every receipt, count and transfer is recorded in the stock ledger.

How are staff permissions organized?

There are three roles: admin, manager and staff, and only managers and above can refund. Only devices registered in the admin console can sign in to the POS, admin accounts can use two-factor authentication with an authenticator app, and key actions are written to the audit log.

Tech stack

Built on proven technology.

Swift · SwiftUIKotlin · Jetpack ComposeElectron · ReactReact · Vite · TailwindTypeScript · Cloudflare WorkersPostgreSQLCloudflare R2 · QueuesStripe TerminalESC/POSOpenAPI

Get started

Start selling
in your store today.

Register devices and set up products and prices in the admin console. For a consultation, get in touch below.