Frequently Asked Questions

Yes. Both EasyRoutes for Shopify and EasyRoutes for Web support webhooks that notify your apps when key delivery events occur—such as routes created/dispatched/updated and stops started/completed/attempted. Use them to sync delivery status into ERPs/CRMs, trigger customer communications, or update internal dashboards in real time. You can consume webhooks directly at your API endpoint or use Zapier to route events into thousands of tools (Sheets, Slack, email, etc.). Webhooks require a Premium (or higher) plan.

See: Integrate EasyRoutes Webhooks with Zapier

The EasyRoutes API lets you automate your delivery workflow end‑to‑end: import orders/stops from external systems, create routes with your preferred options, assign drivers or vehicles, dispatch routes, and update stop or route status as deliveries progress. You can also read back route/stops for reporting and pair the API with webhooks to keep other systems synchronized in real time. Capabilities are consistent across EasyRoutes for Shopify and EasyRoutes for Web.

See: EasyRoutes Routes API · Webhooks & Zapier

Yes. You can integrate EasyRoutes with ERPs, CRMs, WMS, and custom apps using our API and webhooks. Typical use cases include importing stops from non‑Shopify channels, syncing delivery status and proof‑of‑delivery back to your system of record, and powering external analytics collection. The same platform supports both EasyRoutes for Shopify and EasyRoutes for Web.

See: API Getting Started Guide · Routes API

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. If a driver’s phone was offline or a photo needs to be re‑added, open the stop in EasyRoutes and upload PoD from your browser. The new items join the stop’s timeline with timestamps and appear in exports and tracking (subject to your visibility settings). This works across both EasyRoutes for Shopify and EasyRoutes for Web.

See: Manually upload PoD

When a driver captures an e‑signature, customers see an indicator and timestamp on the tracking page confirming that the order was signed for. The signature image is stored with the stop for internal use (support, audits) and can be accessed by admins; it is not shown directly to customers to protect privacy.

See: Proof of Delivery

Yes. If you use Shopify’s native notifications, you can insert proof image URLs into the Delivered or Missed Delivery templates so customers see photo links in those emails. This is optional — EasyRoutes notifications can also include tracking links that show PoD on the hosted tracking page. Choose the path that best matches your communication setup.

See: Integrating PoD with Shopify Emails · Delivery Notifications

Yes. While the PoD gallery itself isn’t a single file download, route/stop exports include links to each proof item plus completion timestamps and driver details — suitable for audits, customer service, or further analysis with external tools. Use Analytics for high‑level performance metrics and the Activity Feed to review the exact sequence of events.

See: Exporting proof of delivery · How do I export routes/stops?

Yes. In addition to taking photos in‑app, drivers can attach images from the phone’s gallery when you allow this option. It’s especially useful when a photo was captured by the camera app while offline; the driver adds it later, and EasyRoutes syncs the proof and timestamps once connectivity returns.

See: Upload from device gallery

Each stop supports multiple PoD elements: up to four photos, an e‑signature with timestamp, and any driver notes. Use photos for placement/context and the signature for hand‑off confirmation. These items appear in admin views, can be shown on tracking pages (per your settings), and are included via links in route/stop exports for record‑keeping.

See: Proof of Delivery