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 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. EasyRoutes is designed to unify multi-platform delivery operations. You can import Wix orders and combine them with orders from Shopify, WooCommerce, BigCommerce, or other sources. All orders appear in one dashboard, so you can generate optimized multi-stop routes across platforms. See: EasyRoutes for Wix
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.
Zapier is designed to be used without coding. To integrate EasyRoutes, you typically select “Webhooks by Zapier” as a trigger, paste a webhook URL into EasyRoutes, and then connect it to actions like sending an email or updating a spreadsheet. All steps are handled through a simple, click-based interface. This makes automation accessible to any team member, not just developers. See: EasyRoutes Zapier
Importing Wix orders is easy. From your Wix dashboard, export orders as a CSV file, then log into EasyRoutes and upload the file via the “Import new CSV” option. EasyRoutes automatically maps order fields like name, address, and quantity to ensure your orders are routed correctly. Once imported, your orders appear as pins on the EasyRoutes map for route planning. See: Importing Orders from Wix
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.
Workflows are closely integrated with EasyRoutes’ existing notification and dispatch systems. This means you can set up a Workflow that not only creates a route but also automatically assigns it to a driver and triggers delivery notifications to customers at the right moments. For example, you could design a Workflow that dispatches a route to a driver as soon as it’s created, ensuring they receive a push notification in the EasyRoutes Delivery Driver app. As soon as the driver starts their route, EasyRoutes can send customers an email or SMS letting them know their delivery is on the way. This seamless integration ensures your team doesn’t need to remember to click multiple buttons — communication and route management just happen automatically.
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web can surface proof of delivery (PoD) to customers. Enable PoD display on tracking pages and decide which delivery events should send links via email/SMS. When a driver completes a stop, PoD is attached to that stop and becomes available to customers according to your settings. Admins always see PoD in route and stop details for auditing or future reference.
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.
Yes. If you need to drive the same set of stops in the opposite direction (e.g., afternoon run), open the route, choose the actions menu (three dots), and click Reverse route. The stop list flips order and ETAs update based on your scheduled start time and stop service times. This tool is available in both EasyRoutes for Shopify and EasyRoutes for Web. You can still drag‑and‑drop to fine‑tune any exceptions or stops that require particular attention.
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.
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
Yes. To repeat a regular run, open the route and use the actions menu to duplicate/copy it, then set a new date/time, driver, and any updated options. Re‑optimize to account for traffic windows or new constraints. You can also copy only a subset of stops by selecting them and sending them to a new route. This approach works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: How to Edit Routes
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
EasyRoutes combines route planning, driver dispatch, live tracking, and proof of delivery in one system. Teams select orders (from Shopify or external sources), create optimized routes with start/end locations and options (time windows, service times), then dispatch to the EasyRoutes Delivery Driver app.
Admins monitor routes in the browser, view ETAs and driver location (Premium/Enterprise), and share branded tracking pages and notifications with customers. Proof of delivery items — photos, eSignature, notes — are captured in the field and visible on the stop record. EasyRoutes is designed for SMBs and delivery fleets of any size across industries.
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
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. Workflows can include multiple steps and conditions, such as only dispatching routes to certain drivers if the route exceeds a number of stops, or only adding particular stops if the corresponding order includes certain tags. There are no limits to how many Workflows route planners can create, offering maximum flexibility for businesses with varying delivery schedules.
Workflows also respects conditions that are applied via EasyRoutes' order automation rules, giving route planners additional tools and controls for automatically applying time windows, delivery dates, driver tasks, or stop priority status based on matching order tags or attributes.
See: Conditional Workflows · Order Automation Rules
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
By default, CSV imports are static snapshots of your Squarespace orders. For real-time updates, you can set up Zapier workflows that push new or updated Squarespace orders into EasyRoutes automatically. Alternatively, you can use the EasyRoutes API to sync changes like address updates or cancellations. This ensures your delivery routes always have the latest order information. See: Zapier Integration
Yes. Use EasyRoutes Order Filters to build the batch you want to route. Common filters include delivery date ranges, order/fulfillment status, tags, and geography (postal/ZIP code, city, country, or your own delivery zones). Filters apply to Shopify orders and any imported/manual stops so a single route can cover precisely the area and schedule you intend.
See: Order Filters
Yes. With Premium or Enterprise plans, turn on live tracking from EasyRoutes Settings → Driver settings. You’ll see a live GPS pin, breadcrumb path, current/next stop, and real‑time status updates on each route’s Tracking tab. Ensure drivers grant Always/Precise location permissions in the Delivery Driver app. Route Groups let you monitor multiple drivers at once.
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. EasyRoutes allows you to centralize deliveries across multiple platforms. You can import invoices from Xero alongside Shopify, WooCommerce, BigCommerce, or Squarespace orders, then optimize routes across all of them in one place. See: EasyRoutes for Xero
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?