These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Food Truck Management
- Features
- Trucks and stops
Trucks and stops
Keep each service destination and its operating team in context.
OverviewActive Truck Stops×
Food Truck Management · Trucks and stops
New
Active Truck Stops
Truck stops
| Code | Name | Address | Contact name | Eligibility note | |
|---|---|---|---|---|---|
| CDE-747 | Stop 836 | G-6 | Contact 271 | EN-683 | |
| CDE-558 | Stop 350 | X-11 | Contact 167 | EN-618 | |
| CDE-450 | Stop 250 | M-6 | Contact 828 | EN-577 | |
| CDE-221 | Stop 765 | C-17 | Contact 613 | EN-369 | |
| CDE-492 | Stop 561 | C-20 | Contact 487 | EN-411 |
6 of 6 records
CDE-747Truck stops · TS-44256
NameStop 836
AddressG-6
Contact nameContact 271
Eligibility noteEN-683
What you can do
Know where service is planned
A food truck order needs a real place and an accountable operating team. Truck Manager maintains the organization and the destination record before Service Lead accepts work for that stop. The stop carries a code, address, contact and eligibility note. The organization supplies its time zone and currency, and the staff record links a team member to that organization. These records let the team identify where an order belongs when several stops are active.
An active destination is a candidate for service, not a promise that every requested serving time fits. The acceptance decision still checks capacity and the order’s planned serving time. For example, when a venue contact requests a lunch handover, Service Lead chooses the intended stop and checks the proposed time against the service period before accepting portions.
How the work is organized
- Operating context. Admin maintains the organization and access identities used by the team.
- Destination details. Truck Manager keeps the stop address, contact and eligibility note current.
- Assigned work. Service Lead follows orders by stop, owner, status and serving time.
The same stop can appear on several orders without becoming a second order record. The order keeps its own customer reference, serving time and owner. This separation helps Truck Manager correct a stop contact without changing what an earlier customer requested. Team members have an active flag and a linked platform user, so access setup can follow the actual person assigned to the operation.
What to agree during setup
Agree which organization owns each stop and which staff may handle its orders. Check the time zone before entering planned service times. Choose a code convention that makes venues easy to distinguish in a crowded route list. If a stop represents a dining room or delivery destination, make that meaning clear in its eligibility note and in the team’s operating practice.
Truck Manager and Service Lead should also agree who checks capacity at order acceptance and what evidence they use. A stop marked active does not replace that check. Review how inactive destinations are handled when historical orders still refer to them, and retain the old order’s stop reference for later investigation.
Check the handoff on an actual case
Take a proposed order for a known venue. Truck Manager confirms its destination record and contact. Service Lead selects the stop, assigns an owner and enters the planned serving time. The acceptance check compares that time with available service capacity. Once accepted, the order preserves its destination and responsible owner. If the venue contact later changes, the team can update the stop record while the accepted order continues to show which stop was chosen.
Use a second case with an inactive stop. The team should resolve its eligibility before taking new work there. Compare the order list with the stop record and the assigned team member so a shift lead can explain who was expected to act.
What your team sees
- Active Truck Stops — Find destinations available for new service planning, with address and contact details.
- Open Service Orders — Follow current work at those destinations by serving time and owner.
Follow the work through
See plan the stop and menu before accepting an order, then accept a service order for the capacity decision.
What it keeps track of
Data model- Organizations
- Operating organizations within the food and beverage group.
- Truck stops
- Dining rooms, outlets, venues and delivery destinations served by the operation.
- Team members
- Staff members linked to an organization and platform identity.
- Users
- Users
- Service orders
- Customer orders accepted and fulfilled by the kitchen and service team.
Who uses it
Permissions- Truck Manager
- Owns destination and staff context.
- Admin
- Maintains organization and user access.
- Service Lead
- Selects the stop and owns the order acceptance check.
Set up Food Truck Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.