Yes. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
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
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web let you re‑optimize a route whenever plans change. Use this feature after you add or remove stops, change stop priorities, edit time windows or service times, or adjust limits like max route duration and stop limits. You can also balance stops across multiple routes first, then re‑optimize each route to tighten the sequence. If permitted in your Driver Settings, drivers may manually re‑order stops from the driver app or re‑optimize the remaining stops in their route to recalculate ETAs after mid‑route changes. For API‑driven workflows, use the Routes API to programmatically update routes and trigger re‑optimization.
See: How do I re‑optimize a route? · How do I allow drivers to re‑order stops?
Yes. Integrate EasyRoutes with your existing stack in two ways: (1) programmatically via the Routes API to import stops, create/dispatch routes, and update status; and (2) event‑driven with webhooks and Zapier to push delivery events into Sheets, Slack, email, ERPs/CRMs, or custom endpoints. These options are available for both EasyRoutes for Shopify and EasyRoutes for Web.
See: API Getting Started Guide · Integrate webhooks with Zapier
EasyRoutes offers webhook-based triggers in Zapier, such as “Route Updated” and “Stop Status Updated.” These let you automatically take action in other apps when a route changes or a driver marks a stop as delivered. For example, you can update a customer record in your CRM or notify your warehouse team when a stop is completed.
See: Zapier Setup Guide
EasyRoutes builds efficient routes by combining your inputs (orders/stops and addresses) with constraints and preferences. It accounts for start and end locations, optional time windows, per‑stop service times, speed factors, and limits such as maximum duration, stops, items, or weight. You can create multiple routes at once, balance stops evenly, or optimize for the fewest routes that still meet your limits. After reviewing the map and stop list, drag‑and‑drop stops to make manual adjustments, then re‑optimize to apply changes.
See: Route Options · EasyRoutes 101: Route Optimization & Route Options
Yes. EasyRoutes maintains a route history so you can review previous runs, proof of delivery, and timing information on either EasyRoutes product (Shopify and Web). Use the Routes page to filter by status (unstarted/in progress/completed/archived) and date. Open any route to view stop details and the Activity Feed particulars for that route. You can also export route/stop data for period‑end reporting or audits.
If you don’t see older orders on the Orders page, adjust the Show orders from the last window in Settings; this does not affect existing route history.
No technical background is needed if you use Zapier to connect Xero with EasyRoutes. Zapier provides a no-code way to set up automations like sending invoices into EasyRoutes for route creation. For advanced teams, the EasyRoutes API allows for custom integrations, syncing invoice updates, or linking to ERP/CRM systems.
See: API Getting Started
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.
EasyRoutes for Shopify is seamlessly integrated into merchants’ Shopify Admin, and can be accessed directly from the navigation menu or search bar after logging into Shopify. Permissions to create, edit, and dispatch delivery routes are limited to the same individuals who have a Shopify user account with full login access to a store’s Shopify Admin.
EasyRoutes for Web uses a standalone web browser-based login, with no Shopify account required to sign up, import your orders, and access route planning tools. With EasyRoutes for Web, route planning administrators can invite additional users to their organization’s account who can then access select EasyRoutes functionality.
See: Getting started · Add collaborators
Yes. Once your Wix orders are inside EasyRoutes, you can use them in Workflows to automate common delivery tasks. For example, you could create a Workflow that builds a new delivery route every afternoon using all Wix orders tagged as “Local Delivery” and automatically dispatches them to drivers. This helps you scale delivery operations with minimal manual effort.
See: EasyRoutes Workflows
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
EasyRoutes focuses on structured stop data rather than storing arbitrary files at a stop. To share extra information (e.g., gate codes, loading dock instructions, external document links), use the stop notes fields. Notes appear on the route, in the driver app, and on printed manifests if enabled, keeping critical context with the stop.
See: Driver/Stop Notes
EasyRoutes doesn't have a setting that hard-locks a stop to one named person, but you can require and document the hand-off. Add a required Driver Task — a text field for the recipient's name, or a checkbox confirming "handed to named recipient" — that must be completed to mark the stop delivered, and note the required recipient in a stop note so the driver knows who to look for.
Pair it with a required e-signature so the signer is captured too. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Proof of Delivery
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web let you re‑optimize a route whenever plans change. Use this feature after you add or remove stops, change stop priorities, edit time windows or service times, or adjust limits like max route duration and stop limits. You can also balance stops across multiple routes first, then re‑optimize each route to tighten the sequence. If permitted in your Driver Settings, drivers may manually re‑order stops from the driver app or re‑optimize the remaining stops in their route to recalculate ETAs after mid‑route changes. For API‑driven workflows, use the Routes API to programmatically update routes and trigger re‑optimization.
See: How do I re‑optimize a route? · How do I allow drivers to re‑order stops?
Yes. You can try any plan — including Premium features like real‑time driver tracking and notifications — for 14 days at no cost. Trials are available on both products (Shopify and Web). During the trial you can invite drivers, dispatch routes, and send tracking/PoD to validate the full workflow before choosing a tier and seat count.
EasyRoutes-native barcodes are QR codes generated by EasyRoutes and printed on your packing slips and labels; each is tied to a specific stop, so a scan can be validated as a match. Existing product or order barcodes (like a supplier’s UPC) aren’t tied to a stop that way — drivers can still scan and record them as proof, but match validation is strongest with EasyRoutes-native codes. Both work in EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
Yes. In Settings > Delivery Zones, click the dropdown arrow on the Create zone button and choose Import KML, then drag in your .KML file. Zone names from the file apply automatically, and you can rename them or set a route colour before saving. Boundaries drawn in tools like Google Earth work well; KMZ or GeoJSON files should be converted to .KML first. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
Analytics reports are viewed in the dashboard and exported on demand — open any breakdown and use Export to copy the data or download a CSV. There isn’t a built-in scheduler that emails recurring reports automatically. If you need that, you can export on a cadence yourself, or use the EasyRoutes API and webhooks (with a tool like Zapier) to pull delivery data into your own reporting. Applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: Analytics
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.
Yes. On Premium/Enterprise plans, you can send SMS notifications for key delivery events (e.g., Ready for Delivery, Out for Delivery, Driver is X stops away, Delivered, Missed Delivery, and optionally Scheduled/Rescheduled). Messages are billed per segment based on the recipient’s country. Customize content and variables in the template editor, and preview with example data before enabling. Pair SMS with email and customer tracking links for full visibility.
Yes. Integrate EasyRoutes with your existing stack in two ways: (1) programmatically via the Routes API to import stops, create/dispatch routes, and update status; and (2) event‑driven with webhooks and Zapier to push delivery events into Sheets, Slack, email, ERPs/CRMs, or custom endpoints. These options are available for both EasyRoutes for Shopify and EasyRoutes for Web.
See: API Getting Started Guide · Integrate webhooks with Zapier
EasyRoutes builds efficient routes by combining your inputs (orders/stops and addresses) with constraints and preferences. It accounts for start and end locations, optional time windows, per‑stop service times, speed factors, and limits such as maximum duration, stops, items, or weight. You can create multiple routes at once, balance stops evenly, or optimize for the fewest routes that still meet your limits. After reviewing the map and stop list, drag‑and‑drop stops to make manual adjustments, then re‑optimize to apply changes.
See: Route Options · EasyRoutes 101: Route Optimization & Route Options
Yes. EasyRoutes lets you add pickups — including returns and reusable-packaging collections — as stops on a delivery route, so drivers retrieve containers on the same run. Add them as custom/manual stops or via CSV/API, set the pickup location, and use stop notes to tell drivers what to collect. Collections appear in sequence with deliveries, on printed manifests, and in the driver app. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Pickup orders · Adding custom stops · Driver Tasks
Yes. Aggregate missed vs. completed counts appear in Analytics, and when a stop cannot be completed, the driver can select or enter a reason in the mobile app. Those reasons are recorded on the stop and visible to admins for follow‑up. Reviewing these notes helps you spot patterns — like frequent access issues at certain buildings — and take corrective action.
Use Analytics to quantify the impact over time, then drill into routes and stops to see the exact explanations and any attached proof (photos/notes). This behaviour is consistent across EasyRoutes for Shopify and EasyRoutes for Web.