easyPOS, a register and back office for shops and restaurants

easyPOS has two parts. The register runs on a touch screen at the counter, in barcode mode for groceries and pharmacies or in touch mode for cafes and restaurants. Cashiers open a shift, ring up sales, take payments, handle refunds and close the shift. The back office runs in a browser, where supervisors check shifts and readings, and owners see sales, items and stock across branches.

I built it on the easyFS and easyHR system: the same shell, components and patterns, with pink as the brand colour, so the three apps read as one family. The register is a different place to design for. A cashier has a line in front of them, so the total and the next action are always the biggest things on screen and every target is at least 48 px. Anything that takes money out of the drawer asks for a reason, and voids and refunds use an orange-red, never the brand pink. The stores, people and amounts shown here are made up.

A typical task for each kind of user, step by step. The line follows how each step feels, where it dips and where it recovers. The feelings are my assumptions and still need testing at a real counter.

In barcode mode the scan field sits on top and every scan confirms with an Added line and Undo. The cart and the total stay on the right with Pay pinned at the bottom. Hold, Recall, Discount, Price, Customer and Void sit in a bar under the items, so Void is far from Pay.

Payments stack in a list, so a customer can pay part by GCash and part in cash. Non-cash defaults to the exact balance and only cash gives change. Finish sale stays off until the sale is fully paid, and the reason is shown as Still to pay.

In touch mode the register opens on the floor plan. Each table shows its state with an icon and a label (open, no order yet, eating, bill out, to clean) plus the time and amount. The menu groups the order into what was already sent to the kitchen and what is new, so nothing is sent twice.

The cashier counts the drawer by bill and coin before seeing the expected amount, so the count is their own. Short or over needs a note. In the back office, the supervisor sees every shift of the day in one table, with how expected was worked out next to the cashier’s note.

Home starts with today so far against the same time last week, then the things that need someone: approvals, low stock, expiring items, a short shift and a missing Z reading. Sales by hour and by branch, top sellers and how customers paid sit below.

An item lists its price per order type and the stock it uses. Each sale takes those components out of stock, so the item page can say how many more can be made today and which component runs out first.

Z readings for every register sit in one table for the day. When a register did not close, a notice names it and says how to fix it, instead of the accountant finding out weeks later. X readings, the eJournal and eSales are in the same place.