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 POS & Route Planner
- Features
- Route stops and teams
Route stops and teams
Keep each serving destination and responsible team member attached to the order.
OverviewActive Route Stops×
Food Truck POS & Route Planner · Route stops and teams
New
Active Route Stops
Route stops
| Code | Name | Address | Contact name | Eligibility note | Organization | |
|---|---|---|---|---|---|---|
| CDE-589 | Stop 355 | Y-20 | Contact 957 | EN-687 | ORG-5340 | |
| CDE-910 | Stop 812 | Z-23 | Contact 226 | EN-906 | ORG-2917 | |
| CDE-860 | Stop 565 | J-13 | Contact 467 | EN-256 | ORG-1495 | |
| CDE-685 | Stop 724 | X-19 | Contact 305 | EN-483 | ORG-8136 | |
| CDE-314 | Stop 117 | H-19 | Contact 925 | EN-883 | ORG-2958 |
6 of 6 records
CDE-589Route stops · RS-49236
NameStop 355
AddressY-20
Contact nameContact 957
Eligibility noteEN-687
OrganizationORG-5340
What you can do
Start with a named destination
A stop order points to a route stop within the operating organization. The stop carries its name, code, address, contact and eligibility note. An order owner can check that context before accepting a serving commitment. That matters when two venues have similar names or when the stop’s eligibility needs a human check. The service team can use the same destination record later, instead of retyping a location on each order.
A route stop can be active or inactive. Operations Manager should review the active list before a shift and confirm which stops the truck will serve. The address and contact give staff the practical details they need when an order is prepared for a venue. The eligibility note is where local operating constraints belong; the person accepting the order still checks the actual serving time and capacity.
How the work is organized
- Organization. Keep the operation’s code, name, time zone and currency with the staff and stops it owns.
- Destination. Use the active stop list to choose the intended serving location and check its contact and address.
- Owner. Assign the order to a team member so open work has a named person responsible for the next step.
What to agree during setup
Agree who maintains stop codes and when a stop becomes inactive. Decide how staff handle a venue whose address or contact changes after an order is accepted. The order should retain the correct serving destination while the current stop record stays accurate for the next shift. Check the organization and team member associations before moving records in from an existing list.
An example is a lunch stop at a recurring venue. Operations Manager confirms the active stop and the serving team. Order Taker selects that stop, assigns an owner and sets the serving time on the order. Service Lead later checks the same destination while recording actual service. The stop is a shared destination record; the order is the commitment for a particular serving time.
Check the handoff on an actual case
Rehearse a stop with a valid contact and address, then an inactive stop that should not be selected for new work. Check that a staff member from the intended organization owns the order. If the venue changes, verify that the new order uses the current destination and that prior orders still explain where they were served. Check the time zone used for the serving time with the shift team.
What your team sees
- Active Route Stops — Find the destinations available to the shift, with their address and contact.
- My Team Member Record — Check the signed-in team member’s organization and shift context.
- Open Stop Orders — See accepted work, owners and serving times for those destinations.
Follow the work through
What it keeps track of
Data model- Organizations
- Operating organizations within the food and beverage group.
- Route 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
- Stop orders
- Customer orders accepted and fulfilled by the kitchen and service team.
Who uses it
Permissions- Operations Manager
- , Order Taker, Service Lead and Admin.
Set up Food Truck POS & Route Planner your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.