Beyond order-taking apps, FuelBuddy's UAE operations needed a tool for managing customer and partner accounts and approving financial corrections. I built this admin panel's frontend.
What I built
- Account administration: Built customer and partner account management, including linked physical assets, credit, and per-customer configuration.
- Approval workflows: Built approval flows for discounts, order cancellations, invoice-item corrections, task-value corrections, and Local Purchase Order (LPO) changes, each its own reviewed action rather than a direct edit.
- Device calibration: Built a calibration interface for physical metering devices tied to customer accounts.
Why it mattered
Routing financial corrections and account changes through explicit approval steps gave FuelBuddy an auditable process for changes that directly affect billing, instead of ad hoc edits.
Not Generic CRUD
The device-calibration feature is the clearest sign this isn't a generic admin-CRUD tool: it manages calibration parameters on a physical metering/dispensing device attached to a customer account, a real hardware-adjacent operation, not just editing a database row. The approval flows (discount, cancellation, invoice correction, task-value correction, purchase-order changes) exist as their own reviewed steps rather than direct edits, on purpose, for anything that touches billing.
Data Model & Scale
- Structured exports run through
papaparseandvue-json-excel3for CSV and Excel output, built for financial and account reporting, not just on-screen tables. - Form validation runs through
vee-validateandyup, so a malformed account edit or financial correction is caught client-side before it ever reaches Hasura. - Configured as an installable PWA, consistent with FuelBuddy's other UAE frontends.
Stack
Vue 3, Vite, Pinia, graphql-request with GraphQL Code Generator against Hasura, Firebase.