CASE 04 / 04POS SYSTEM   /   FIELD NOTESCLOSE [ESC] ×
// 01   SUMMARY READOUT

POS System

A cashier and inventory system with live sales dashboards.

ROLEFrontend Engineer
DATES / ENGAGEMENTPRODUCT BUILD · 2024
STACKReact · TypeScript · ECharts · Swiper
// 02  THE PROBLEM

A cashier and inventory system needed an interface that kept day-to-day transactions and stock information easy to navigate. Sales and inventory data also needed to be readable in dashboard form.

// 03  WHAT I BUILT
01 / TECHNICAL DECISION

Type the interface

Built the cashier and inventory interface with React and TypeScript, making the application data shapes explicit.

typed data → React views → cashier workflow
02 / TECHNICAL DECISION

Make operational data legible

Used ECharts for sales and inventory dashboards, giving the system dedicated views for its operational data.

sales + inventory → ECharts → dashboards
03 / TECHNICAL DECISION

Connect the workflows

Used Swiper navigation to move between the system's views while keeping the cashier and inventory experience cohesive.

cashier ↔ inventory ↔ sales dashboard
// 04  RESULTS / KNOWN NUMBERS
TSTYPED INTERFACE
LIVESALES DASHBOARDS
02CORE WORKFLOWS
// 05  SYSTEM ARCHITECTURE
FIG. 04 — SYSTEM MAPARCHITECTURE / NOT A PRODUCT SCREEN
01CASHIER
02TRANSACTIONS
03INVENTORY
04DASHBOARDS
Interfaces are only one part of the system.
// 06  WHAT I’D DO NEXT

I would validate the interface with cashiers during a busy shift, then address the highest-friction steps. I would also define offline and recovery behavior explicitly, so a temporary connection problem has a predictable path back to a consistent state.

DISCUSS A PROJECT ↗