🐙

OctoPOS — early prototypes

A dive-centre management system, migrated from an old Microsoft Access database. These are clickable UI mockups for feedback — not the finished app.

PROTOTYPES · FEEDBACK WELCOME

👤 Customer record

A diver across every visit, and one booking in detail. Start with “+ New customer / booking” to see how a customer is created — search first, then create. Live discount control on the account.

Open →

✅ Check-in

Moving a booking to “checked in”. It’s a gate: passport, medical, waiver and certification must be uploaded and verified before the button unlocks. Two demo divers — one clears, one is blocked.

Open →

🤿 Daily dive planner

The day’s dives on a board. Drag divers onto a dive, tanks onto people, gas blends onto tanks. Copy a dive to another day, cancel a dive. Page between days.

Open →

📖 Dive log / roster

After a dive: enter each diver’s tank pressures, max depth and times, set the outcome (completed / aborted / cancelled), and complete the dive. Also a per-diver logbook of past dives.

Open →

🧾 Check-out

Settling up at the end of a stay: review the account (dives, supplements, equipment), issue the invoice, take the balance, and close the booking. Volume pricing and the customer discount flow through to the total.

Open →

⚙️ Admin / settings

The dials behind everything else: customer discounts, the dive rate card, gas and cylinder supplements, check-in document rules, cert requirements, staff pay, dive sites. Change a value here and the whole system follows.

Open →
Everything here runs in your browser with made-up data (the customers are pets) — nothing is saved, and a refresh resets it. The black “data operations” panels show the database writes the real app would make. Feedback of any kind is useful at this stage.