Admins need an internet connection to create, edit, and dispatch routes. The EasyRoutes Delivery Driver app supports low‑connectivity situations: if a driver opens the route while online, stop data is cached locally so they can navigate, update status, and capture proof of delivery offline. The app queues events and syncs them to EasyRoutes once the device reconnects.
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
Yes. In both EasyRoutes for Shopify and EasyRoutes for Web you can enforce a start action. When a driver taps Start Delivery in the mobile app, EasyRoutes records the route start time and begins live location updates. This prevents drivers from completing stops out of context and ensures analytics include drive time from the route's start location. If a route must be paused, drivers can resume later to continue tracking.
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.
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. For long runs or regional routes, create a schedule that spans multiple days. Set a start time/location for each day and include an overnight break so ETAs for day two (and beyond) reflect realistic service times. This works alongside capacity limits and time windows, and customer tracking will display the correct expected dates.
EasyRoutes uses a flexible, seat‑based model. Choose a plan (Standard, Premium, Enterprise) and activate the number of driver seats you need; you’re billed only for active seats. You can adjust seats or change tiers at any time, and SMS messaging — if enabled — is charged per message segment. Both EasyRoutes for Shopify and EasyRoutes for Web use the same pricing model.
See: Pricing · Pricing & Plans FAQ
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. 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
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. 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.
Yes. In EasyRoutes Settings → Customer notifications, enable the Rescheduled template and customize the message and variables (date, window, tracking link, etc.). Trigger it when routes or stops move to a new day/time so recipients are informed proactively. This works for both Shopify orders and imported/manual stops across EasyRoutes for Shopify and EasyRoutes for Web.
Customer tracking pages can display an anonymized, live driver pin so recipients can see the driver’s progress as delivery approaches. Enable the option in EasyRoutes Settings → Order tracking, and use delivery notifications (email/SMS) to send tracking links automatically. When live location is unavailable (e.g., permissions off), the page still shows status updates and ETAs based on route progress.
See: Real-Time Driver Location Tracking · Customizable Order Tracking Pages
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
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.
Yes. Fulfilling an order from EasyRoutes creates a Shopify fulfillment that includes the EasyRoutes tracking number and URL. Customers see the link on the order status page and in applicable Shopify notifications. If templates were heavily customized, you may need to ensure the standard tracking snippet is present.
Instead of paying for individual drivers, with EasyRoutes you just pay for a driver seat and can put any driver in your roster into that seat.For example, you could have a plan with two driver seats, but have four drivers in your driver roster. You can easily change which two drivers are active at any given time. And, if you have a busy delivery weekend, you can add seats for the additional drivers for that weekend, and then remove the seats after you're done with them. We prorate the charges and credits for upgrading and downgrading based on the changes in the number of seats on your plan.
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
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
For reliable live tracking, drivers should: (1) sign in to EasyRoutes Delivery Driver; (2) allow Always/Allow all the time location access; (3) enable Precise location; and (4) keep battery optimization from restricting the app (disable aggressive battery saver if needed). These settings apply on both iOS and Android and can be checked from device Settings.
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
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. 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. EasyRoutes allows you to build Workflows in a safe, draft environment where you can preview how they would behave without actually triggering live actions. This lets you confirm that your conditions and actions are working as expected before rolling them out to your team.
For example, you might test a Workflow that creates a route every morning at 8 AM by running it with sample orders first, so you can see how the route would look. Once you’re confident it works, you can enable it in production and have it run automatically every day. This ability to test Workflows helps prevent mistakes like dispatching routes too early or sending customers duplicate notifications. It also makes it easier to experiment with new automations before committing to them.
See: Testing Workflows
Yes. The EasyRoutes Routes API accepts imported stops (customer details, address, items, notes) so you can bring orders from non‑Shopify sources into EasyRoutes. After importing, you can create new routes, add the stops to existing routes, assign drivers, and dispatch. This works for both EasyRoutes for Shopify and EasyRoutes for Web and complements CSV import when you need automation.
Yes. You can cap a route by Max route duration, Max stops per route, and Max items per route so optimization never exceeds your operational limits. These constraints shape ETAs, the stop sequence, and whether additional routes are required. Enable or edit these limits from the Route Options panel before creating routes, or open any route and choose Edit route options to apply changes and re‑optimize. This feature functions the same way in 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