Frequently Asked Questions

Yes. From any route, choose Assign driver (or select from the header), then click Dispatch. The driver gets a push notification and can start the route from their phone. For busy days, dispatch multiple routes from a Route Group to release them all at once.

See: How do I dispatch / share routes?

Driver seats control who can receive routes and use the EasyRoutes Delivery Driver app. Assign a seat to any driver in your roster to activate them; deactivate a seat when a driver is seasonal or temporarily off the road. You’re billed only for the number of seats included at your plan at any time. Deactivating preserves the driver’s details and history so you can re‑activate them later without re‑inviting.

Seat management is available in both EasyRoutes for Shopify and EasyRoutes for Web from the Drivers & Vehicles tab of the EasyRoutes navigation menu, or the Billing tab of EasyRoutes Settings for plan upgrades/downgrades.

See: How do I manage my driver seats?

Access the Drivers & Vehicles tab from the EasyRoutes navigation menu, click Add driver, and enter the driver’s name and phone number. EasyRoutes sends the invite; the driver installs the Delivery Driver app and signs in with an SMS code. Assign a seat to activate them and dispatch their first route.

See: How do I add a driver?

Yes. The EasyRoutes API enforces rate limits to ensure consistent performance for all users. Most workflows run comfortably within default limits when you batch requests, avoid unnecessary polling, and rely on webhooks to trigger updates rather than frequent reads. If you expect sustained high throughput (e.g., large imports or rapid status updates), our team can help you design an efficient approach and advise on limits for your use case.

See: API Getting Started Guide

While there isn’t a separate public sandbox, you can safely test in a non‑production environment. Create a test shop (Shopify) or an EasyRoutes for Web workspace with sample data, generate a dedicated API token, and point webhooks to staging URLs. Use draft orders or manual stops that contain your own contact info so notifications and tracking tests go only to your team. When your flows are validated, switch credentials and endpoints to production.

See: EasyRoutes API Getting Started Guide

Yes. Programmatically modify routes and stops using the Routes API — update stop status (delivered/attempted), change assignments, dispatch routes to drivers, or edit route options, then re‑optimize as needed. When your store uses EasyRoutes notifications, status changes made through the API follow the same rules and can send customer updates and refresh ETAs. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.

See: API Getting Started Guide · EasyRoutes Routes API

API access uses tokens you create in your EasyRoutes account. Follow the Getting Started guide to generate a token, store it securely, and add it to requests from your server or integration platform. Tokens work the same way for both EasyRoutes for Shopify and EasyRoutes for Web. Rotate credentials periodically and avoid embedding them in client‑side code.

See: EasyRoutes API Getting Started Guide

Yes. The EasyRoutes Routes API accepts imported stops (customer details, address, items, notes) so you can bring orders from non‑Shopify sources into EasyRoutes. After importing, you can create new routes, add the stops to existing routes, assign drivers, and dispatch. This works for both EasyRoutes for Shopify and EasyRoutes for Web and complements CSV import when you need automation.

See: EasyRoutes Routes API – Import Stops

Yes. Access to the EasyRoutes API and webhooks requires a Premium (or higher) subscription across both products (Shopify and Web). If you’re evaluating, you can prototype with CSV import or the driver app while you finalize your integration plan, then enable API once you upgrade.

See: API Getting Started Guide · Pricing & Plans FAQ

Yes. Use EasyRoutes webhooks as Zap triggers to connect delivery events to apps like Google Sheets, Slack, Gmail, Twilio, HubSpot, and more. Common automations include updating a shared delivery log, notifying customer service when an attempt fails, or sending a custom message when proof of delivery posts. Zapier is supported for both EasyRoutes for Shopify and EasyRoutes for Web.

See: Integrate EasyRoutes Webhooks with Zapier

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