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. You can cap a route by Max route duration, Max stops per route, and Max items per route so optimization never exceeds your operational limits. These constraints shape ETAs, the stop sequence, and whether additional routes are required. Enable or edit these limits from the Route Options panel before creating routes, or open any route and choose Edit route options to apply changes and re‑optimize. This feature functions the same way 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.
Pick any plan to start a 14-day trial with full feature access. Cancel during the trial to avoid charges; continue and your subscription begins at the end of day 14. Trials apply to any tier, and billing starts on your first post-trial cycle through Shopify (for EasyRoutes for Shopify) or Stripe (for EasyRoutes for Web). Seat changes you make later will be prorated within your billing cycle.
No. The Activity Feed is an internal operations log available to EasyRoutes admins and dispatchers. Drivers use the EasyRoutes Delivery Driver app to view assigned routes, update stop statuses, and capture proof of delivery; these events will appear in the Activity Feed for admins, but drivers do not access the account‑wide feed. This separation keeps internal data and audit trails restricted to management.
See: Activity Feed
When exporting orders from Squarespace, ensure you only include “Pending” orders from the fulfillment filter. This ensures you’re working with unfulfilled deliveries that still need to be routed. If only certain products require delivery, you can filter by “Specific product” during export. This gives you precise control over which orders are included in your EasyRoutes import.
Yes. From the Routes page or an individual route view, export to CSV for all relevant route data points. Exports include stop details, timestamps, driver assignments, and URLs to related proof of delivery (photos/signature/notes). Use these files for accounting, customer service follow‑up, or analysis in spreadsheets or external tools. Exports are supported in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. From the Routes page or an individual route, export CSV files containing stop information (customer name, address, contact fields), timing, driver assignments, and URLs to any proof of delivery items. Use these exports for customer service, accounting reconciliation, or analysis in spreadsheets and external tools.
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.
Yes. From any route, use the checkboxes to select one or more stops, then click the bulk actions bar and choose Send to another route. You can also open a Route Group and drag stops from one route to another within the group. After moving, click Save and (optionally) Re‑optimize to update the stop order and ETAs. This workflow works the same in EasyRoutes for Shopify and EasyRoutes for Web.
Use this to balance workloads mid‑day, handle late additions, or consolidate leftovers onto a cleanup route.
Yes. From EasyRoutes Settings → Customer notifications, tailor email and SMS templates with your branding and dynamic variables, and select exactly which events trigger messages (Ready for Delivery, Out for Delivery, Driver is X Stops Away, Delivered, Missed Delivery, plus Scheduled/Rescheduled). You can maintain separate templates for Shopify orders vs. imported/manual stops, and send messages automatically with links to branded tracking pages. This customization is available in both EasyRoutes for Shopify and EasyRoutes for Web.
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.
Yes. From the EasyRoutes Customer Notifications settings you can enable/disable templates per event and edit their content. Common events include Ready for Delivery, Out for Delivery, Driver is X Stops Away (configurable), Delivered, Missed Delivery, plus Scheduled and Rescheduled notices. Templates can differ for Shopify orders vs. imported/manual stops to match your data and workflow.
Yes. Set a scheduled start date and time when creating or editing a route. EasyRoutes will use that schedule — plus stop time intervals and any delivery time windows — to calculate ETAs for every stop. Customers can receive their individual ETAs via branded tracking pages and optional email/SMS notifications. If plans change, simply edit the route's schedule, re‑optimize the route, and ETAs will update automatically.
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.
Yes. EasyRoutes allows you to build Workflows in a safe, draft environment where you can preview how they would behave without actually triggering live actions. This lets you confirm that your conditions and actions are working as expected before rolling them out to your team.
For example, you might test a Workflow that creates a route every morning at 8 AM by running it with sample orders first, so you can see how the route would look. Once you’re confident it works, you can enable it in production and have it run automatically every day. This ability to test Workflows helps prevent mistakes like dispatching routes too early or sending customers duplicate notifications. It also makes it easier to experiment with new automations before committing to them.
See: Testing Workflows
Drivers can install the EasyRoutes Delivery Driver app from the App Store (iOS) or Google Play Store (Android) using the official links provided in our Help Center. The app works with both EasyRoutes for Shopify and EasyRoutes for Web accounts; once added as a driver, sign in using the phone number on file and the SMS code sent to that device. After dispatch, routes appear automatically in the app and can also be opened from the push notification's shared route link.
See: Where can I download the EasyRoutes Delivery Driver app?
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?
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
Yes. The EasyRoutes Delivery Driver mobile app supports complete proof of delivery: capture multiple photos, obtain a customer e‑signature, and add notes (e.g., where the parcel was left). PoD is stored with the stop and visible to admins; if you enable PoD on tracking pages, customers can view it as well. PoD uploads immediately when a driver has an active internet connection, and will sync when re-connected if captured while offline.
See: Proof of Delivery
EasyRoutes for Web is best suited for merchants and service providers who do not have an existing Shopify presence. Users may currently be using spreadsheets and manual processes to track orders/stops and plan delivery routes, or may be using an alternate eCommerce platform where orders/stops can be exported into a spreadsheet. We also offer an API.
Spreadsheets containing order data can quickly be imported into EasyRoutes for Web to plan and dispatch optimized delivery routes in a fraction of the time compared to manual planning methods.
See: Import orders from CSV · API: Getting Started · Zapier webhooks
Yes. EasyRoutes opens your driver’s preferred navigation app for turn‑by‑turn directions. Drivers can choose Google Maps, Apple Maps, or Waze as their default navigation app from the mobile app's settings page. Drivers can also long tap and choose a different app on the fly if needed. Getting directions is available in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. When you assign and dispatch a route, EasyRoutes sends the driver a push notification that opens the route in the EasyRoutes Delivery Driver mobile app. If the driver doesn’t receive alerts, confirm notification permission on the device and that the driver is added with the correct phone number. Drivers can also pull‑to‑refresh their route list to fetch new assignments.
See: How do I dispatch/share routes? · Troubleshooting push notifications
By default, CSV imports are static snapshots. To achieve real-time updates, you can set up Zapier workflows or use the EasyRoutes API. For example, if an order’s address changes in WooCommerce, Zapier or a custom API connection can automatically push that update into EasyRoutes, ensuring drivers always have the latest information.
See: Zapier Guide
Drivers can install the EasyRoutes Delivery Driver app from the App Store (iOS) or Google Play Store (Android) using the official links provided in our Help Center. The app works with both EasyRoutes for Shopify and EasyRoutes for Web accounts; once added as a driver, sign in using the phone number on file and the SMS code sent to that device. After dispatch, routes appear automatically in the app and can also be opened from the push notification's shared route link.
See: Where can I download the EasyRoutes Delivery Driver app?
Yes. When location capture is enabled, EasyRoutes records the driver’s GPS location and a timestamp alongside each proof-of-delivery entry — photos, e-signature, notes, and barcode scans — so every completed stop has a location and time on record. You can review these details on the route’s stop entries and include driver location when exporting stop data for your files. Available in both EasyRoutes for Shopify and EasyRoutes for Web.