Driver requirements are the tasks a driver has to complete for a delivery — capture a signature, take a photo, check photo ID, keep it refrigerated, collect a copay. You set defaults per location, they carry onto every ticket from that location, and they can be adjusted on an individual ticket when it is created.
Turning the feature on
Go to Settings → Drivers App and switch on Driver Requirements. With it on you get a Driver Requirements tab in the Locations Manager and a requirements section on the new ticket form. Switch it off and both are hidden.
The switch defaults to off for accounts that have never configured requirements, and to on for accounts that already have some, so it cannot silently switch off a requirement somebody is already relying on.
Setting the defaults for a location
Open Locations → All Locations, edit a location and go to its Driver Requirements tab. The requirements you switch on there apply to every delivery from that location.
The requirements, and which ones are enforced
This is the distinction that matters most, because it decides whether a requirement can actually stop a bad delivery:
- Signature required — enforced. The driver app will not let the driver mark the delivery successful until a signature has been captured.
- Photo required — enforced. Same rule: no photo, no successful.
- Photo ID required — advisory. The platform cannot verify that a driver looked at an ID, so this prints on the packaging slip as a checklist item for the driver.
- Refrigerate — advisory. Prints on the packaging slip.
- Collect Copay — advisory. Prints on the packaging slip, together with the Copay Amount you enter next to it, so the driver knows exactly what to collect.
Every enabled requirement prints as a checkbox at the bottom of the packaging slip, including the two enforced ones.
Printing the packaging slip
Open Tickets, press Actions on the ticket and choose Print Packaging Slip. The slip carries the requirement checklist for that ticket. Print Label and Print Packaging Slip are part of the scanning feature, so they appear on accounts that have it.
Changing requirements on one ticket
The location's requirements are defaults, not a cage. When a ticket is created, the requirements section on the new ticket form is pre-filled from the location and can be adjusted for that delivery — so a location that normally needs a signature can have one ticket that does not, without changing the location.
When a driver cannot complete a delivery
If a driver reports they are stuck on "cannot mark successful", the first question is which enforced requirement is outstanding — a signature or a photo. If the signature cannot be collected in person, an operator can send a contactless signature request from the ticket's Actions menu, unless that location has contactless signature excluded.