Customer tracking pages can display an anonymized, live driver pin so recipients can see the driver’s progress as delivery approaches. Enable the option in EasyRoutes Settings → Order tracking, and use delivery notifications (email/SMS) to send tracking links automatically. When live location is unavailable (e.g., permissions off), the page still shows status updates and ETAs based on route progress.
See: Real-Time Driver Location Tracking · Customizable Order Tracking Pages
Yes. Use Delivery Analytics to review outcomes by driver — completed vs. missed stops, average delivery time, and overall success rate — over a selected period. Filter to focus on a single driver or compare across the team. For detailed investigations, open routes to see timestamps and proof of delivery, or export results for use in external tools.
See: Delivery Analytics
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web can display proof of delivery (PoD) on the customer’s tracking page right after a stop is marked Delivered or Attempted. PoD can include delivery photos, e‑signature confirmation, and optional driver notes. Turn this on from EasyRoutes Settings → Order tracking, and use notifications (email/SMS) to send tracking links automatically. For internal auditing, PoD is also visible on the route and stop records for your team.
You don’t need to be technical to connect Squarespace with EasyRoutes. Using Zapier, you can build “if-this-then-that” workflows to automatically send Squarespace orders to EasyRoutes for route planning. For businesses that want more advanced automation, the EasyRoutes API lets developers build custom integrations and connect with other business systems. This gives you both a no-code and pro-code path to integration. See: API Getting Started
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.
If a Shopify order arrives without a valid shipping address, EasyRoutes highlights it so you can fix the address before planning. Edit the order in Shopify (preferred for data accuracy) or add the correct address details to the stop in EasyRoutes, then refresh and route. For pickup orders, set the address to your store or pickup point so drivers and staff can see the correct location on the route map and in documents. Address completeness ensures accurate ETAs, navigation, and proof‑of‑delivery records.
See: My order does not have a shipping address—how do I add one?
Yes. If a driver is seasonal or temporarily inactive, they can be temporarily deactivated until required again. The driver’s profile, history, and assignments remain in your account, but they cannot receive routes or sign in until re‑activated. This helps control costs without losing configuration.
Manage seats from the Drivers & Vehicles tab of the EasyRoutes navigation menu. Works in EasyRoutes for Shopify and EasyRoutes for Web.
Delivery Analytics provides a consolidated view of your operations across both EasyRoutes for Shopify and EasyRoutes for Web. Key metrics include total stops and routes, completion rate, attempted/missed deliveries, average delivery time, and per‑driver performance summaries. Use it to compare activity over time, spot bottlenecks, and validate operational changes.
You can filter by time period and specific drivers to focus on a team or individual, then export results to CSV for reporting. For event‑level detail (e.g., when a stop changed status), open the route’s Activity Feed. Analytics refreshes as new delivery events are recorded, so the dashboard stays current throughout the day.
EasyRoutes protects order and customer information with modern security practices. Traffic between your browser, the driver app, and our services is encrypted in transit; stored data is encrypted at rest. Access to accounts and APIs is token‑based and limited to the minimum required to operate features like routing, tracking, and notifications. Payments are handled by Shopify or other PCI‑compliant providers — EasyRoutes does not store card data.
We do not sell personal information. Limited sharing with subprocessors may occur solely to operate EasyRoutes as described in our Privacy Policy. Contact support if you have questions about data retention or deletion requests.
See: Privacy Policy
No — routes are single‑driver to keep tracking, ETAs, and proof‑of‑delivery accurate. If two or more drivers are needed, split the stops into multiple routes (or create a new route for leftovers) and dispatch each separately. You can also publish a route without assigning a driver, and share a self‑assign link so someone from your pool can claim it when ready.
Yes. Use the driver filter on the Analytics page to view metrics for a single driver or compare across drivers by switching the filter. This helps you evaluate utilization, completion rates, average stop times, and trends over time. It’s supported in both EasyRoutes for Shopify and EasyRoutes for Web and respects any date range you’ve selected.
If a driver worked on multiple routes per day, those results roll up in the selected period. For route‑by‑route detail, open the route list and drill into specific days.
See: Filtering by Driver
Yes. Once invoices are imported into EasyRoutes, customers linked to those invoices can receive branded notifications via email or SMS, complete with live tracking links. This improves delivery transparency and reduces customer inquiries. See: EasyRoutes for Xero
Yes. EasyRoutes Delivery Driver supports low‑connectivity scenarios. Have drivers open or refresh the route while connected to preload stops and attachments. If signal drops, they can continue navigating (via their chosen maps app), mark stops delivered/attempted, and capture photos/signatures. The app queues events locally and syncs them back to EasyRoutes as soon as the device reconnects, updating ETAs and tracking automatically.
See: Can I use EasyRoutes Delivery Driver without a connection?
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web can display proof of delivery (PoD) on the customer’s tracking page right after a stop is marked Delivered or Attempted. PoD can include delivery photos, e‑signature confirmation, and optional driver notes. Turn this on from EasyRoutes Settings → Order tracking, and use notifications (email/SMS) to send tracking links automatically. For internal auditing, PoD is also visible on the route and stop records for your team.
Yes. You can add breaks before optimization (by setting the planned break time) or after creating a route (by inserting a break and positioning it between stops). Breaks appear to drivers as a stop in the sequence, and when a break is included in a route, EasyRoutes will recalculate remaining ETAs and the overall route duration. This is useful for lunch windows, mandatory rest periods, or overnight pauses. For multi‑day itineraries, consider splitting different days into separate routes, or using an overnight strategy so customer ETAs align with actual delivery periods.
Drivers should enable: (1) Location set to Always/Allow all the time with Precise on for accurate tracking and ETAs; (2) Camera/Photos to capture proof of delivery; (3) Notifications for new route alerts; and (4) on Android, allow Storage/Media so photos save correctly. Battery optimization should not restrict the app so background location continues during a route.
See: What app permissions does EasyRoutes Delivery Driver use?
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. Enable automatic dispatch so newly created routes with a scheduled start time are assigned and sent to the chosen driver immediately — no extra clicks. Use this for recurring daily runs or integrations that create routes programmatically. You can still edit or un-dispatch a route before start time if plans change.
Drivers can capture multiple photos, obtain a customer e‑signature, and add notes at the stop. These items are stored with timestamps and the completion context, and they’re visible to admins on the route and stop record. When enabled in EasyRoutes Settings, customers can see PoD on tracking pages and in notifications.
See: Proof of Delivery
EasyRoutes maintains a persistent log of account activity so admins have an authoritative record of delivery events over time. The Activity Feed retains entries for the lifetime of your account unless data is explicitly deleted (e.g., via route removal or a data‑deletion request). When you need a file for records or audits, pair the feed with route/stop CSV exports that include timestamps and proof‑of‑delivery links. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: Activity Feed · Export routes/stops
Yes. From Proof of Delivery settings, you can force one or more PoD elements to be collected before drivers can complete a stop. Choose the combinations that fit your workflow — e.g., require a photo for attempted stops, or require e‑signatures for only completed stops. These rules apply in EasyRoutes for Shopify and EasyRoutes for Web, and can include Attempted stops.
See: Make PoD Required
Yes. Use the Delivery Zones tool to outline one or more areas on the map, then filter/select orders within those zones to build your route quickly. Zones help planners batch by neighbourhood or service area and pair well with other filters like tags or dates. Once configured, zones are stored permanently to standardize your daily workflow when planning for the same areas.
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.
Manual CSV imports work well for smaller batches, but to achieve automatic syncing, you can use Zapier or the EasyRoutes API. For example, create a Zap that triggers whenever a new BigCommerce order is placed and sends it directly to EasyRoutes. Or, for more advanced use cases, use the API to integrate real-time order creation and updates.
See: Zapier Integration
Yes. Drivers can start their route — triggering Out for Delivery notifications, if enabled — mark individual stops as Delivered or Attempted, and add proof (photos, signature, notes). These updates appear instantly on the route and — if enabled — update customer tracking and notifications. Admins can review all events in the route timeline and export later for records.
See: How do I mark an order as Delivered? · How do I mark an order as Attempted Delivery?
Yes. From any route you can dispatch to a specific driver, or share a route link that allows self‑assignment by your driver pool. Assigned drivers receive the route in the EasyRoutes Delivery Driver app (iOS/Android) with turn‑by‑turn directions via their preferred navigation app. For busy days, combine dispatch with Route Groups to release multiple routes at once and monitor progress on a single screen. This behaviour is consistent across EasyRoutes for Shopify and EasyRoutes for Web.
See: How do I dispatch / share routes? · Route Dispatch Links / Driver Self‑Assign