Yes. Drivers can add photos and notes for attempts (e.g., no answer, inaccessible). You can make PoD mandatory for Attempted stops, so drivers document the situation before moving on. Attempt proof appears with the stop’s history for admins and, if enabled, on customer tracking pages/notifications to explain what happened.
See: Proof of Delivery
Yes. Drivers mark a stop Attempted, choose a preset reason (e.g. no answer, inaccessible, Canceled), and can add a note or proof of delivery.
Yes. Require photos, eSignature, and/or a driver note individually before a stop can be marked Delivered or Attempted in the driver app.
You can attach up to four delivery photos per stop, plus an e‑signature and driver notes, to document each delivery thoroughly.
For unattended drops, EasyRoutes drivers photograph the location and add a note; photos, timestamp, and GPS are stored as proof of delivery.
EasyRoutes has no built-in age-gating, but you can run age-restricted deliveries using required signature, photo, and Driver Task ID checks.
EasyRoutes-native barcodes are tied to a specific stop for match validation, while existing product/order barcodes can be scanned and recorded but aren’t stop-matched.
Yes. Scans are stored with the stop’s proof of delivery for live or later review, and can be included when you export stop data.
Use a CSV export template with one row per sub-item to ensure proper mapping.
Search the FAQs, browse the guides, or talk to a human.