Invite drivers from the Drivers & Vehicles tab, then assign a driver seat to activate them. Deactivate drivers anytime to free a seat without deleting their profile or history. You can switch which people occupy seats as staffing changes — ideal for seasonal or on-call drivers. These controls are available in both EasyRoutes for Shopify and EasyRoutes for Web.
Zapier’s app directory includes thousands of CRMs, ERPs, and productivity tools. With EasyRoutes as the trigger, you can automatically update customer records in HubSpot when a delivery is completed, or sync invoice statuses in NetSuite when routes are dispatched. This ensures delivery data flows into the rest of your business systems seamlessly.
See: Zapier App Directory
Yes. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
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.
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. 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. 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. Both EasyRoutes for Shopify and EasyRoutes for Web can display proof of delivery (PoD) on the customer’s tracking page right after a stop is marked Delivered or Attempted. PoD can include delivery photos, e‑signature confirmation, and optional driver notes. Turn this on from EasyRoutes Settings → Order tracking, and use notifications (email/SMS) to send tracking links automatically. For internal auditing, PoD is also visible on the route and stop records for your team.
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. 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 protects order and customer information with modern security practices. Traffic between your browser, the driver app, and our services is encrypted in transit; stored data is encrypted at rest. Access to accounts and APIs is token‑based and limited to the minimum required to operate features like routing, tracking, and notifications. Payments are handled by Shopify or other PCI‑compliant providers — EasyRoutes does not store card data.
We do not sell personal information. Limited sharing with subprocessors may occur solely to operate EasyRoutes as described in our Privacy Policy. Contact support if you have questions about data retention or deletion requests.
See: Privacy Policy
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
Yes. Manual and imported stops can send the same email/SMS notifications as Shopify orders once configured. In EasyRoutes Settings → Customer notifications, enable templates under the Imported Orders sections and ensure each stop includes an email address and or phone number. Use tracking links to provide status and proof of delivery even when the source isn’t Shopify.
Delivery Analytics provides a consolidated view of your operations across both EasyRoutes for Shopify and EasyRoutes for Web. Key metrics include total stops and routes, completion rate, attempted/missed deliveries, average delivery time, and per‑driver performance summaries. Use it to compare activity over time, spot bottlenecks, and validate operational changes.
You can filter by time period and specific drivers to focus on a team or individual, then export results to CSV for reporting. For event‑level detail (e.g., when a stop changed status), open the route’s Activity Feed. Analytics refreshes as new delivery events are recorded, so the dashboard stays current throughout the day.
Yes. From EasyRoutes Settings → Driver settings, enable the options to let drivers reorder stops and re‑optimize the remaining sequence when plans change (traffic, customer requests). Re‑optimization recalculates the fastest order for what’s left, while respecting your route constraints (time windows, priorities). Admins can still edit routes from the web at any time.
See: How do I re‑optimize remaining stops? · Re‑ordering stops
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
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.
You don’t need to be a developer to connect WooCommerce with EasyRoutes. Zapier provides no-code automation tools that let you push WooCommerce orders directly into EasyRoutes with just a few clicks. For businesses that want more control, the EasyRoutes API is available to build deeper integrations, such as syncing fulfillment statuses or creating custom routing rules. This gives you both no-code and pro-code options.
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?
When no one is available, the driver documents the drop instead of collecting a signature: up to four photos of where the order was left, an optional note (e.g., "left behind the side gate"), and the GPS location and timestamp captured automatically. All of it is saved to the stop's proof-of-delivery record.
You can make a photo and/or note mandatory to mark the stop delivered, and display these items on the customer's tracking page for confidence. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
EasyRoutes doesn't include a dedicated age-verification or age-gating feature, so it won't automatically confirm a recipient's age. You can still operate alcohol, CBD, or other age-restricted delivery routes and enforce the check at the door: require an e-signature and/or photo to mark the stop delivered, and add a required Driver Task (e.g., "ID checked, recipient 21+") the driver must complete first.
Note that age-gated content isn't supported for SMS notifications. These options work in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks
CSV exports are static, but Zapier or API integrations let you sync real-time updates. For example, if an invoice’s payment status or address changes in Xero, the update can flow directly into EasyRoutes, keeping your drivers informed with the most accurate data.
See: Zapier Guide
Yes. The EasyRoutes Delivery Driver app runs on both phones and tablets — it’s available for iOS (including iPad) and Android devices. The interface is optimized for a phone in the vehicle, but it works on larger tablet screens too. Just install it from the App Store or Google Play and sign in with the driver’s phone number. The same app serves drivers on both EasyRoutes for Shopify and EasyRoutes for Web.
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. 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
Absolutely. EasyRoutes supports mixed sources across both products (Shopify and Web). Bring in non‑Shopify orders by uploading a CSV, sending stops through the Routes API, connecting via webhooks/Zapier, or adding custom stops manually. Once imported, they appear alongside Shopify orders on the Orders page, can be filtered like any other stop, and can be optimized together on the same route.
See: Adding custom stops from outside Shopify · Routes API · Webhooks & Zapier