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.
By integrating Xero with EasyRoutes, you unlock a complete last-mile delivery toolkit: multi-stop route optimization, real-time driver tracking, branded notifications, proof of delivery (photos, signatures, notes), and analytics. This makes it easy to turn Xero invoices into efficient deliveries while providing customers with professional updates and proof of completion.
See: Xero Integration
Yes. Programmatically modify routes and stops using the Routes API — update stop status (delivered/attempted), change assignments, dispatch routes to drivers, or edit route options, then re‑optimize as needed. When your store uses EasyRoutes notifications, status changes made through the API follow the same rules and can send customer updates and refresh ETAs. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
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
Access the Drivers & Vehicles tab from the EasyRoutes navigation menu, click Add driver, and enter the driver’s name and phone number. EasyRoutes sends the invite; the driver installs the Delivery Driver app and signs in with an SMS code. Assign a seat to activate them and dispatch their first route.
Yes. You can operate from several depots in both EasyRoutes for Shopify and EasyRoutes for Web. For each route, define the start and end locations (a store, local warehouse, or driver’s home base). Filter orders by zone or location tags, build multiple routes, and monitor all drivers together via Route Groups. Printed documents and ETAs reflect different depot travel times automatically.
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 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
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.
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.
CSV imports are manual, but Zapier and the EasyRoutes API let you automate the process. With Zapier, new Xero invoices can be sent directly to EasyRoutes as soon as they’re created. With the API, developers can build real-time integrations that sync orders and updates automatically, keeping your delivery pipeline fully up to date.
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
When a delivery can't be completed, the driver marks the stop Attempted and selects a reason (customer unavailable, access denied, refused, and more), capturing proof of the attempt. To redeliver, use Send to another route to move the stop onto a new or later route — as a fresh stop, or as a copy that preserves the original's history.
This keeps failed stops from getting lost and lets you batch redeliveries into the next run. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Mark an order as Attempted · Send orders to another route
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
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. Configure a start location (e.g., your store, a local warehouse, or a driver's home base) and an end location (e.g., a depot, final stop, or loop back to the route's start location) on each route. These points are included in optimization and time estimates, so drivers see realistic drive times and customers receive accurate ETAs. You can set defaults in Route Options, then override per route as needed. For multi‑warehouse operations, create routes that begin near each inventory location to reduce deadhead driving. In both EasyRoutes for Shopify and EasyRoutes for Web, you can adjust these locations after route creation and re‑optimize to update the sequence and times.
See: Start/End Locations
Yes. Even though WooCommerce doesn’t have the same native integration as Shopify, once orders are imported into EasyRoutes they behave the same as any other order. This means customers can receive branded email or SMS notifications, along with live tracking links. This reduces “Where’s my order?” calls and improves the customer experience.
Yes. Delivery Ratings allow recipients to provide quick feedback from the tracking page right after their order is delivered. You can collect a star rating and an optional comment, then export results or segment by driver to monitor individual performance and service quality. Ratings help highlight coaching opportunities and verify customer satisfaction trends over time.
See: Delivery Ratings
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
SMS delivery notifications use usage-based pricing by recipient country and message length. Costs are per segment (e.g., a U.S. segment is $0.043 USD). Longer messages or those with emojis/Unicode may use multiple segments. You fund a prepaid SMS balance and can enable auto-top-ups so notifications continue without interruption.
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.
For extended-handling stops, increase the Time per stop or the individual stop's service time so ETAs and Max route duration account for the extra work. For two-person deliveries, note that a route is assigned to a single driver account, so you'd staff that route's vehicle with a crew operationally rather than assigning two driver logins to one route.
Driver Tasks can capture crew-specific steps at the stop. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Driver Tasks
Yes. EasyRoutes supports Squarespace orders through multiple integration methods. The simplest way is exporting orders from your Squarespace dashboard to CSV and importing them into EasyRoutes. For automation, you can connect Squarespace with Zapier to send orders directly into EasyRoutes, or build custom workflows with the EasyRoutes API. This ensures Squarespace merchants can take advantage of the same delivery optimization and tracking tools available to other platforms.
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?
Zapier makes it easy to send internal notifications whenever a stop status changes in EasyRoutes. For example, you can set up a Zap that listens for the STOP_STATUS_UPDATED webhook and then sends a Slack alert or email to your team with details like the order number and driver notes. This keeps staff informed in real time without needing to manually monitor dashboards.