V0LTOPERATIONSHandle what needs attention.Your work, at a glance.
The dashboard prioritises the next operational decisions. Revenue cards and generic analytics are deliberately secondary.
Action queue
Most urgent customer or bench decisions first.
Weekly capacity
Controlled Tuesday + Saturday intake.
Free Repair Challenge
Operational proof, not invented public marketing.
Every repair. One next action.Repairs
Status, customer approval, parts, payment and custody stay attached to the same canonical Ticket ID.
One customer ID across every system.Customers
Repair tickets, devices, invoices and future POS activity attach to the same customer record.
The device history survives the repair.Devices
Device ID is the POS object. Device Passport is the customer-facing ownership/history layer.
Know what can be sold.Inventory
Manage the actual online-store catalogue, supplier availability and audited Home Lab stock from one screen.
Products
Store availability, supplier observation and local stock.
Recent stock movements
Audited receiving, sale and adjustment activity.
Inventory controls
Advanced workflows stay available without cluttering daily work.
POS-ready before the POS arrives.System & POS
Canonical IDs and data contracts are already defined so the future Tauri + SQLite + PostgreSQL POS does not require rebuilding repair records.
Never key the business by a name or phone number.
Every durable business object receives its own permanent identifier.
Production gates remain explicit.
Preview flows can be tested now without pretending backend integrations are already live.
Public SKU outside. Private supplier mapping inside.
Parts workflow stores the V0LT public Supplier SKU on the ticket. Private supplier SKU and supplier cost remain server-only.
Local first. Cloud acknowledged.
Future terminal records use SyncVersion and event IDs so reconnecting does not duplicate customers, invoices, repairs or payments.