Skip to content

Commerce & Food Operations System

CommerceMobileOperations
2014–2026
Production operating system
Commerce & Food Operations System
My role CTO · Product & Operations Systems Lead

Overview

This work grew from operating the business itself. I owned the customer journey and the systems behind it: subscription logic, meal planning, ordering, payments, kitchen production, delivery operations, support, retention, and reporting.

The result is not one isolated app. It is a connected operating model across web, mobile, kiosk, staff, and backend surfaces, shaped by the realities of running food and commerce businesses in production.

Key decisions

  1. Modelled product logic around real kitchen and delivery constraints instead of forcing operations into a generic commerce template.
  2. Connected customer acquisition, ordering, fulfilment, support, and retention data into one accountable operating flow.
  3. Moved critical customer and staff journeys toward monitored, supportable production systems with clearer recovery paths.

Evidence

  • Customer web, Flutter mobile and kiosk ordering surfaces
  • Subscriptions, payments, kitchen, delivery and lifecycle workflows
  • Operational reporting, support automation and production monitoring

Technologies Used

  • Flutter
  • Vue
  • Laravel
  • Payments
  • Subscriptions
  • Operations
  • CRM
  • Automation