Sep 2025 — present · Frontend developer · admin dashboard and customer ordering apps

Food Base

Kitchen and meal-service management for a Japanese food-service operator

confidential — built at wesionaryTEAM, described without screenshots or client data

A kitchen operator whose orders, billing and dietary rules all have to stay consistent across an internal admin dashboard and a customer-facing ordering app.

fig. 01 — billing as versioned snapshotsdrawn to no scale

Billing as versioned snapshots, not mutable rows
Orders are captured as snapshots with draft and issued versions, so a bill can be compared against any earlier one and a diff view shows exactly what moved. Invoices that change after issue are a support problem; versioning makes the change visible instead of silent.
Dietary conflicts resolved across loaders, not in a component
Restriction conflicts and substitute-dish coverage are computed across five React Router data loaders, so a conflict surfaces before the order is placed rather than at the kitchen.

React Router 7Turboreposhadcn/uiAWS CognitoAWS S3