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.
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?
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
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.
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.
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.
Yes. When you create multiple routes together, EasyRoutes groups them so you can monitor all active drivers in a single view. The Route Group page shows color‑coded pins, per‑route progress, and live stop updates. Use this view to coordinate dispatch, answer customer inquiries, and rebalance work if needed by moving stops between routes.
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
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 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
EasyRoutes calculates ETAs from drive times and your configured service time per stop, adjusting for start/end locations, stop priorities, and time windows. As drivers complete stops, ETAs refresh automatically based on actual timing. The best results come from accurate addresses, realistic service times, and consistent driver start times.
Customers see ETAs on tracking pages and (optionally) receive updates via email/SMS.
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. See: Zapier Integration Guide
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
Yes. If you don’t use Shopify, EasyRoutes for Web provides the same core workflow — order intake, route planning, dispatch, tracking, proof of delivery, and analytics. Bring orders in via CSV uploads, the Routes API, or webhooks/Zapier. You can also mix non‑Shopify orders with Shopify orders if you operate via multiple e-commerce channels.
Customer tracking pages and notifications work the same, and drivers use the same EasyRoutes Delivery Driver app.
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.
While CSV imports are manual, you can automate order import with Zapier or the EasyRoutes API. For example, you can use a Zap to trigger whenever a new WooCommerce order is placed, automatically sending it to EasyRoutes for routing. With the API, developers can build custom real-time integrations for order imports and updates. This ensures your delivery operations stay in sync without requiring manual exports.
Yes. Creating a fulfillment from EasyRoutes writes the EasyRoutes tracking number and URL to the Shopify order, so customers and support teams can track delivery progress. The link also appears in Shopify’s order status page and, when enabled, in Shopify or EasyRoutes notification emails/SMS. Tracking remains accessible even after routes are archived.
Yes. Upload a CSV to create stops with customer, address, and item details — even if the orders weren’t placed in Shopify. The importer supports line‑item fields such as quantity and weight so you can use vehicle capacity limits accurately. Once imported, these stops can be filtered, optimized into routes, and dispatched to drivers like any other order source.
Dispatchers manage routes from the browser interface. On Shopify, open the Shopify mobile app and launch EasyRoutes to view routes, assign drivers, and monitor progress from supported mobile devices. For EasyRoutes for Web, sign in from your phone’s browser for a responsive experience. Drivers should use the dedicated EasyRoutes Delivery Driver app for turn‑by‑turn and proof of delivery.
EasyRoutes integrates with Shopify fulfillments so your order system stays in sync. Marking stops Ready for Delivery, Out for Delivery, Delivered, or Attempted updates the Shopify fulfillment accordingly and adds the EasyRoutes tracking number/URL. Depending on your configuration, Shopify or EasyRoutes sends the customer emails/SMS. Partial items and multi‑item orders are supported; admins can review fulfillment history on the Shopify order and in EasyRoutes route/stop details.
Yes. Packing slips are configurable so teams can show the fields drivers or packers need. In EasyRoutes Settings → Packing Slips & Labels you can: include a logo, select variables (customer details, order items, notes), set text sizes, and tweak headers and helper text. Print slips directly from any route.
Note: Some variables are only available when printing one slip per stop vs. one per item. Adjust your preference in the Print Preview if you need item-level detail.
Yes. Use EasyRoutes webhooks as Zap triggers to connect delivery events to apps like Google Sheets, Slack, Gmail, Twilio, HubSpot, and more. Common automations include updating a shared delivery log, notifying customer service when an attempt fails, or sending a custom message when proof of delivery posts. Zapier is supported for both EasyRoutes for Shopify and EasyRoutes for Web.
We offer a self‑serve Help Center with step‑by‑step guides and videos, plus email support from our team during business hours (ET). Most questions are resolved the same business day. Accounts on the Enterprise plan receive prioritized responses and onboarding help. For incident updates, check our public status page; for billing and plan questions, see the pricing page.
See: Help Center · EasyRoutes Pricing
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.
Yes. In addition to taking photos in‑app, drivers can attach images from the phone’s gallery when you allow this option. It’s especially useful when a photo was captured by the camera app while offline; the driver adds it later, and EasyRoutes syncs the proof and timestamps once connectivity returns.
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.