Food Trailer / Online Ordering
Flavor on 51
Flavor on 51 (Food Trailer): A website with online ordering, where the menu and prices come from the system that charges the customer.
Overview
Flavor on 51 is a food trailer. We built its website and online ordering: a menu that reads from the payment system, an on-site checkout, customer accounts with rewards, and a site that installs on a phone.
The brief
The rule for the build: the menu and prices come from the system that charges the customer, so there is no second copy to keep up to date.
What we built
Website
flavoron51.com replaced the older WordPress site. All 65 of its old addresses answered with a live page after redirects.
Web Development →Menu
The menu is the live Square catalog. When checked, the site menu and Square differed by zero items.
API & Third-Party Integration →Checkout
Customers pay on the site. A test order was paid end to end, the confirmation email arrived, and eight Square payment events were verified and stored.
API & Third-Party Integration →Accounts and rewards
Customers can check out as a guest or create an account. Accounts track orders and rewards, with points added on a paid order and taken back on a refund.
Custom Systems Architecture →Pickup or delivery
The order screen asks first. Pickup goes through the site's own checkout. Delivery goes to the Square Online order page, where Square dispatches the courier.
Front-End Development & Experience →Phone app feel
The site can be added to a phone's home screen, and an offline page keeps the phone number and hours available.
Front-End Development & Experience →How it helps
- One menu and one set of prices, so nothing has to be changed in a second place.
- Guests are not forced to create an account.
- In testing, a refund reconciled back to the order through Square's own events.
Every figure on this page is a count from a build record or a test run. A business result goes on this site only when it traces to a source we can open on a call: Results.
What it runs on
Next.js on Cloudflare Workers, a separate ordering service on Cloudflare, Postgres on Supabase, Square for the catalog and payments, and Resend for email. The ordering flow was tested across five device profiles in the browser and as an installed app.
How the work ran
This is how we run every engagement. It describes the process, not a timeline for this project.
The audit
We map what you already run and show you where it leaks. You keep the map either way.
The plan
What we would change, in what order, what it costs, and what number we will judge it on. You approve before anything is built.
The build
Each piece goes live on its own, so you see progress weekly instead of waiting for a big reveal.
The run
Managed, measured, month to month. Every channel judged on what a booked job costs you.
Builds are quoted once and built once; retainers you can stop any month. The full process and the published prices: How we work.
Questions
Is there a long-term agreement?
What does a build like this cost?
Do you use AI on this kind of work?
Read the full charter: The AI Charter.