Yes. When you configure a Scanner-input Driver Task, tick the Delivered and/or Attempted checkboxes to make a successful scan mandatory before that status can be applied. You can also require a Barcode Scan as proof of delivery from Settings > Driver Settings. Either way, drivers can’t mark the stop complete until the scan is captured. Available on Premium and Enterprise plans, in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver tasks · Driver settings
Yes. Require photos, eSignature, and/or a driver note individually before a stop can be marked Delivered or Attempted in the driver app.
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.
Yes. Require photos, an eSignature, and/or a driver note individually before a stop can be marked Delivered or Attempted in the driver app.
Enable Driver tasks in Add/edit options, add a Scanner-input task, name it, and optionally require it before a stop can be marked Delivered or Attempted.
Absolutely. Drivers can add photos, collect an e‑signature, and record notes at each stop; these appear in the route and customer tracking (if enabled).
Yes. Admins can upload photos and notes directly to a stop from the browser if something couldn’t be captured from a mobile device.
Yes. You can show proof of delivery (photos, eSignature confirmation, and driver notes) on customer tracking pages for delivered or attempted stops. Enable this from EasyRoutes' Order Tracking settings.
Yes. You can show proof of delivery (photos, e‑signature confirmation, and driver notes) on customer tracking pages for delivered or attempted stops. Enable this from EasyRoutes' Order Tracking settings.
Search the FAQs, browse the guides, or talk to a human.