Orders and stops
Routisserie plans stops, not orders. An order is what the customer bought; a stop is a visit a driver makes. Most orders have one stop; some have two.
Orders
An order comes from NetSuite, from a CSV file, or from someone typing it in (a phone order). It holds the customer, the address, the contact, the number of guests, what to bring and any notes. Its order number (for example SO261117002) is the same one NetSuite uses. Orders typed in without a number get one like M-00901.
Each order has one service date, the day it is delivered. To deliver on another day, change the order's date: its stops leave their trips on the old day.
Stops: deliveries and pickups
A delivery stop brings the food. A pickup stop goes back later the same day to collect equipment (chafing dishes, hot boxes). A pickup is a second stop on the same order, with its own time window, and it can be on a different trip or a different driver. On the board a pickup has a small box icon.
Time windows
Every stop has a window: the earliest and latest time the driver should arrive, for example 11:30 AM–12:00 PM. If an order gives only a start time, the window is 30 minutes long (an admin can change that; see Planning defaults).
Routisserie plans each arrival inside the window, and a little before its end when it can. A stop is:
- on time when the planned arrival is inside the window with more than 10 minutes to spare;
- at risk when it arrives in the last 10 minutes of the window;
- late when it arrives after the window ends.
Time on site
Each stop also has a time on site: how long the driver stays to unload and set up. It starts at 10 minutes for a delivery and 8 for a pickup. Routisserie learns from what drivers actually do: once an address has been visited, the average time spent there is used instead. You can type a different value on the order or in the stop panel.
Units: how much a vehicle can carry
Vehicles carry units. A unit is whatever the kitchen counts by, for example one hot box. Each vehicle has a capacity in units, and each stop has a load in units.
If an order does not say how many units it needs, Routisserie works it out from the number of guests: guests × 0.05, rounded up, at least 1 (so 40 guests is 2 units). An admin can change the 0.05.
The trip card shows the load against the vehicle's capacity, and Over capacity is flagged when a trip carries more than fits.
Skills: special requirements
A skill is a requirement a stop has that not every driver or vehicle meets, for example liftgate, forklift, setup or badge_access. Drivers have skills (they can do setup) and vehicles have skills (it has a liftgate). A trip can take a stop only if its driver and vehicle together have every skill the stop needs.
Skills are just words you choose. Use the same spelling everywhere; the boxes suggest the ones already in use.
Priority
Each stop has a priority from Normal to 10. It matters only when not everything fits: Optimize leaves out lower-priority stops first. Most stops stay at Normal.
Locations and pins
Routisserie needs to know where each address is on the map. When an order arrives it looks the address up. The result shows on the order:
| Status | Means | What to do |
|---|---|---|
| Located | Found. | Nothing. |
| Approximate | Found, but not exactly (for example only the street). | Check the pin before planning. |
| Not found | No match. The stop cannot be planned. | Fix the address or set the pin by hand. |
| Pin set by hand | Someone placed it. | Nothing; it is remembered for that building. |
Routisserie remembers each building: once you fix a pin, the next order to the same address uses it. See Fixing a pin.