Skip to content
← All projects
/ Case study · Web terminal · cashier & restaurant operations

Valid POS

Build the order. Take payment. Run the shift.

A restaurant POS for the counter: product search, item choices, bills, cash and EDC payments, kitchen tickets, and cash shifts in one workspace.

Live at validpos.id

Valid POSBuild the orderBuild the order01 / 06
For developers
Web
ReactTypeScriptC#Next.jsDrizzleTursoESC-POS
What I did & the proof ↓
Web
Valid POSProduct tour

Follow the real POS 0.2.7 cashier flow, from an order to payment, kitchen tickets, and the cash shift. The outlet is a sample.

Valid POS: Build the order
Screen by screen

Build the order

Two nasi goreng and one iced latte make a Rp98,000 order. Quantity controls, item notes, saved bills, promotions, and the payment total sit together at the register.

POS 0.2.7 · real cashier screens · sample outlet

3 / 6
Valid POS · Build the order
Real product screenshots. Everything you click stays inside this portfolio.
The problem
The counter, kitchen, and cash shift need to agree on the same order.
What I built
A cashier terminal with item choices, bills, payment records, kitchen tickets, and shift reports.
What it enables
Staff can follow an order from the counter to the kitchen and reconcile the shift’s cash.
Feature highlights
  • Cashier catalog, item choices & saved bills
  • Cash change calculation & EDC payment records
  • Kitchen tickets, cash movements & shift reports
Built with

React / TypeScript / C# / Next.js / Drizzle / Turso / ESC-POS

Designed and built by Alexanders Schwartzmann · start to finish

  • Cashier UX & React terminal
  • Order & payment backend
  • Kitchen & cash shifts
  • C# printing integration
See what I did and the proof ↗
Want something like Valid POS?

I can build one around how your business works.

Talk about a similar project
What I did

I designed and built this project from start to finish.

Project creator

Alexanders Schwartzmann

From the product idea and design to the code behind the features below.

My implementation scope
  • Cashier UX & React terminal
  • Order & payment backend
  • Kitchen & cash shifts
  • C# printing integration

How the main flow works

  1. 01

    Cashier catalog & item choices

  2. 02

    Backend bills & payment records

  3. 03

    Order queue & kitchen tickets

  4. 04

    Shift records & printed receipts

Proof of the work

What was built, how it works, and why it was built that way.

01 / Real screen & code

One order, from catalog to payment

Item quantities and choices feed the bill. The cash workspace calculates the remaining balance and change; EDC approvals are recorded by the cashier.

Technical decision

Payment recording and receipt printing are separate: a printer failure must not undo a recorded sale.

02 / Real screen & code

A traceable cash shift

The shift workspace connects the opening float, cash sales, cash movements, and drawer count.

Technical decision

Shift figures come from the backend; the open-shift drawer expectation stays hidden for a blind count.

About these screens

Screens from the real POS 0.2.7 with a sample outlet. No real sale or payment was sent, and no printer was tested.

POS 0.2.7 · real cashier screens · sample outlet ·

The problem

A busy counter needs a clear path from selecting a dish to collecting payment. Kitchen staff need the right quantities and notes, while the shift supervisor needs a traceable record of cash movements. Valid POS brings those jobs into one restaurant terminal.

Feature highlights

  • Search or scan products, select item choices, adjust quantities, and save bills.
  • Take cash with automatic change calculation; record QR, debit, and credit payments made through an EDC.
  • Track kitchen tickets by status, quantity, notes, and elapsed time.
  • Manage opening floats, cash movements, X reports, and drawer counts when closing a shift.
  • Print receipts and kitchen checkers through the local C# printing agent and ESC-POS.

Current implementation

The current 0.2.7 terminal uses React and TypeScript, with a C# local printing agent. Next.js, Drizzle, and Turso power the backend. Cashier catalog data, saved bills, kitchen tickets, and shift records come from that backend. EDC payments are recorded by the cashier after payment on the bank terminal.

Explore the real product

The walkthrough opens on the cashier’s populated order, then covers the catalog, item configuration, payment breakdown, kitchen, and shift workspace. All six screens were freshly captured from the original POS 0.2.7 components on 14 October 2026. “Outlet Contoh” uses isolated sample data; no sale or payment was submitted to the production system.