The most mobile trade has the most scattered tracking
A food truck or market trader permanently juggles: which markets this week, which permit expires, which pitch fee to pay to whom, how Wednesday at the market hall compares with Saturday in the village. Add private-event requests — weddings, corporate, festivals — arriving by DM and getting lost between two services.
There is no dominant software for this trade: what you find are Excel templates to download, or booking marketplaces that manage THEIR requests, not your operation. The documented result: bookings run on “spreadsheets, texts, and DMs” — and route decisions run on gut feeling.
Your round, described then generated
Describe your business: “I run a burger truck. I have recurring locations (two markets, a business park) each with its permit, expiry and pitch fee, plus one-off events. Each service session has a date, a location and a revenue figure. Private-event requests have a status: received, quote sent, confirmed, done. I want the week ahead, expiring permits and average revenue per location.”
The generated application structures the operation: locations with their administrative deadlines, sessions linked to locations, private bookings with statuses — and a dashboard that answers the trade's real question: where is it worth going?
- Locations: place, day, pitch fee, permit and expiry
- Service sessions: date, location, revenue
- Private bookings: request, quote, status, deposit
- Week ahead: where to be, which day
- Dashboard: revenue per location, deadlines, seasonality
Revenue per location, finally comparable
A mobile trader's profitability hinges on location choices — and those deserve better than memory. With each session entered in seconds at closing, the dashboard computes average revenue per location, weekday and season: the market that “does well” gets verified in numbers, and the one no longer worth its pitch fee shows.
The application ships with realistic demo data (varied locations, seasons, private bookings) to evaluate immediately, and three generation levels (Sketch, Craft, Masterpiece).
An owned tool, at a mobile trade's pace
It's a responsive web application: the day's revenue is entered from the phone, in the truck, at the end of service. And the tool belongs to you — code ZIP export, GitHub push, free hosting or the included dedicated URL: your location and season history is a company asset.
Free Discovery plan for the first application; Pro (€25/month) and Max (€149/month) to iterate, with the cost shown before each generation.
Typical generated entities
- Location
- Service session
- Permit
- Private booking
- Client
Generated screens
- Week ahead by location
- Location record: permits, revenue history
- Today's session entry
- Private-booking queue by status
- Round dashboard
Dashboard indicators
- Average revenue per location
- Permits expiring within 60 days
- Confirmed private bookings this month
- This month's revenue vs last month
Frequently asked questions — food trucks
Does the application handle the till (payments, receipts)?
No — payment and till obligations remain the business of certified POS solutions. The application keeps the operating register: the session's revenue is reported in seconds at the end of service, and that's what feeds the per-location comparisons.
Can we track permits and their deadlines per municipality?
Yes: each location carries its permit (organiser, expiry date, pitch fee) and the dashboard surfaces those expiring — no more permit found expired on market morning.
Can private-event requests follow my quoting flow?
Yes: describe your steps (received, quote sent, deposit, confirmed, done) and they become the application's statuses, with the pending queue visible at a glance.
What about ingredient or supply stock?
If your description mentions it, simple stock tracking (items, thresholds, movements) joins the structure — see also the inventory use case for that side.
Can I enter data from the truck, with patchy signal?
It's a web application: you need a connection at entry time (4G is enough). The typical entry — one revenue figure, one date — takes seconds once service ends.