Systems / Coffee Lane POS

A calmer counter. A clearer way to run the order.

A café staff workspace for ordering, checkout, customer records, receipts and operational reporting.

Client & contextCoffee Lane

My contributionWorkflow mapping, product design and frontend/backend development

Actual staff interface · design mode with sample records

Menu, sizes and basket in the retained POS design preview. All records are illustrative.

Choose a view above. Open the image to inspect the details.

Inside the workflow

From a need
to a useful next step.

Choose the order

Find the drink, size and quantity in one counter view.

Review the checkout

Apply the defined payment and customer rules.

Prepare the receipt

Give the team a record and a printing handoff.

Review the day

Bring orders and operational records into a shared view.

Built around the handoff.

Connect the counter experience to the work around it: order handling, customer records, receipts and reporting.

My process, scope and build status +

The starting point

Connect the counter order to the staff tasks and records around it.

Map ordering and payment handoffs.
Build a responsive register and order queue.
Connect receipt, customer and reporting journeys, with a sample-data review mode.

The work included

Counter interface and mobile checkout
Order queue and customer views
Receipt-printing handoff
Operational and reporting modules

Evidence & limits

The retained React POS includes an explicit design mode that intercepts requests and supplies sample records. The screenshots come from that mode. October go-live notes document a hosted counter build with sales disabled; later notes retain commissioning, payment and physical-printer checks. This case does not claim a fully commissioned payment, inventory, delivery or payroll system, and does not treat the sample report as café revenue.

Connected work