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. 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
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.
EasyRoutes functions like other public Shopify apps: one app install per store. If you operate multiple stores, you can plan centrally by importing stops from other stores (CSV, API, webhooks/Zapier) into the EasyRoutes workspace you use for routing. This approach lets you manage a combined delivery day while preserving each store’s native Shopify workflows.
The cutoff, lead-time, and blackout-date rules you configure live inside your date picker app and control what customers can select at checkout — EasyRoutes doesn't import those rules. What it does read is the resulting delivery date and time window the app writes onto each order, which it then uses for filtering and routing. So the customer-facing scheduling limits stay with your picker, while EasyRoutes plans around the dates and windows they produce. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: How EasyRoutes works with your Shopify setup and third-party apps · Time Windows
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.
SMS usage fees and monthly pricing tiers are identical for both EasyRoutes for Shopify and EasyRoutes for Web, with the exception of our Free monthly pricing tier, which is currently only available on EasyRoutes for Shopify. EasyRoutes for both platforms continues to offer a free 14-day trial of any pricing tier for new users to give a advanced features a test drive. Both platforms function on the same driver seat model, where you only pay for the number of drivers that are active in your account at any time.
EasyRoutes for Shopify uses Shopify’s native billing tools for all subscription and SMS usage top-ups and monthly invoicing. EasyRoutes for Web functions on the same principles, but uses an independent billing provider offering industry-standard security and encryption for all transactions.
See: SMS pricing · Pricing · Proration
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.
EasyRoutes Workflows support a wide variety of actions that cover the full delivery process, from order intake to customer communication. You can automatically generate new routes based on incoming orders, apply filters (such as only including orders tagged with “Priority” or due on a specific date), and dispatch routes directly to the correct driver. This level of automation means you can build a Workflow that matches your exact delivery process, no matter how simple or complex.
See: Workflow Actions
EasyRoutes automatically builds an inventory (packing checklist) for every route so drivers know exactly what to load before heading out. In the Delivery Driver app, tap Inventory below the map to switch between Summary view (all items and quantities for the route), Items view (each item with its stop), and Orders view (items per stop in route order). Drivers can check items off as they load. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
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.
Yes. EasyRoutes processes order and customer information to plan routes, power tracking/notifications, and provide proof‑of‑delivery records. We protect this data with modern security practices and retain it according to your account activity and legal requirements. We do not sell personal information; limited sharing may occur with subprocessors strictly to operate EasyRoutes, as described in our privacy policy.
For data removal requests, contact support and we’ll guide you through available options.
See: Privacy Policy
Yes. EasyRoutes keeps your order list synchronized with Shopify so recent orders, edits, and fulfillment changes are available for routing without manual imports. If an expected order isn’t visible, confirm the Show orders from the last… window, and other filters on the Orders page, then refresh. You can also import non‑Shopify orders alongside synced Shopify orders when needed.
EasyRoutes helps protect perishable and temperature-sensitive goods by keeping product moving and time on the road to a minimum. Cap each route with Max route duration and Max stops per route so no run exceeds your safe window, assign delivery time windows to fragile stops, and let optimization sequence and split orders across drivers for faster dispatch. This works the same in EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Time Windows
Workflows in EasyRoutes are powerful automation tools that let you design and run delivery management processes without needing to handle every step manually. Think of them as “if-this-then-that” rules that connect your orders, routes, and driver dispatching into a seamless flow. Instead of relying on a dispatcher to constantly create routes, select orders, or assign drivers, Workflows can do these repetitive tasks for you automatically.
For example, you could create a Workflow that listens for new Shopify orders tagged as “Local Delivery” and automatically builds a route every morning at 9 AM, adds matching orders to the route, optimizes route stops, and assigns it to a specific driver. By reducing manual intervention, Workflows make your operations more consistent, scalable, and error-proof.
See: Workflows Overview
Capping how many orders a customer can book into a given slot is handled by your date picker app at checkout (for example, Pickeasy's order limits), not by EasyRoutes. On the planning side, EasyRoutes helps you balance the resulting workload: filter orders by delivery date and time window, then split them across multiple routes or drivers, and the optimizer sequences each route to respect its windows. Together they keep slots controlled and routes balanced. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
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
No coding is required if you use Zapier, which allows you to set up automations like sending new Wix orders into EasyRoutes with just a few clicks. For businesses needing deeper control, the EasyRoutes API allows developers to build integrations for syncing fulfillments, handling custom workflows, or connecting to other back-office systems.
See: EasyRoutes API Guide
EasyRoutes functions like other public Shopify apps: one app install per store. If you operate multiple stores, you can plan centrally by importing stops from other stores (CSV, API, webhooks/Zapier) into the EasyRoutes workspace you use for routing. This approach lets you manage a combined delivery day while preserving each store’s native Shopify workflows.
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. In Settings > Delivery Zones, tick the zones you no longer need and click Archive to remove them from your active list. Archived zones aren’t gone for good — use the Add filter control below the map to show Archived or All, then select and Unarchive any you want back. This keeps your active zone list tidy without losing past boundaries. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
Yes. You can reshape a zone after creating it — open Settings > Delivery Zones, select the zone, adjust its points on the map, then save your changes. You can also rename it or change its route colour at any time. Updated boundaries apply the next time you use that zone to select orders for a route. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
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. 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. One of EasyRoutes’ strengths is its ability to centralize delivery management. You can import WooCommerce orders via CSV or Zapier while also syncing Shopify, BigCommerce, or other platform orders into the same account. EasyRoutes will display all of them together so you can generate optimized routes across multiple sales channels.
See: WooCommerce Overview
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?