Setup is quick: install EasyRoutes (Shopify) or sign in (Web), connect drivers, select orders with filters, and click Create route. Use the defaults for service times and route options, then print or dispatch to the driver app. Most trial users reach a working route within an hour, often faster with our step‑by‑step guide.
If you import orders from outside Shopify, start with a small CSV or a few manual stops to validate the flow before scaling.
EasyRoutes pricing combines your plan tier with the number of driver seats in your current plan. Keep any number of drivers in your roster, then activate only the seats you need for your current delivery schedule. If demand spikes, add seats for a few days and deactivate later — billing automatically prorates so you pay for just the days your account contained additional seats. Seat management works the same on Shopify and Web.
See: Manage active driver seats · How prorated billing works
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.
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.
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. As assigned routes are dispatched from EasyRoutes, drivers get a push notification that opens the route in the app. If a driver doesn’t see alerts, confirm notification permission is enabled and the driver is added to your store with the correct phone number. Drivers can also pull‑to‑refresh their route list in the app to fetch new routes available to them.
See: How do I dispatch/share routes? · Troubleshooting push notification permissions
Yes. Barcode scans are stored alongside the stop’s other proof of delivery — photos, e-signature, and notes — and can be reviewed live on the Route page or after the route is complete. When you export stop data, you can include Scanned barcodes and Scanned barcode issues columns for your records. This applies in both EasyRoutes for Shopify and EasyRoutes for Web.
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. 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
No. The Activity Feed is an internal operations log available to EasyRoutes admins and dispatchers. Drivers use the EasyRoutes Delivery Driver app to view assigned routes, update stop statuses, and capture proof of delivery; these events will appear in the Activity Feed for admins, but drivers do not access the account‑wide feed. This separation keeps internal data and audit trails restricted to management.
See: Activity Feed
Yes. 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?
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. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
Yes. EasyRoutes supports multi‑location operations. You can set unique start/end locations on routes (store, warehouse, driver home base), segment orders by delivery zone or location tags, and dispatch drivers from different hubs on the same day. Route Groups make it easy to manage several routes per location and monitor all drivers together.
This applies across 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
Yes. You can add an EasyRoutes-native QR code to your packing slips and packing labels from Settings > Packing Slips & Labels by enabling the Show QR code option and setting its position. Drivers can then scan these codes with the Delivery Driver app to confirm the right order at the right stop, and you can optionally require a successful scan before a stop is marked Delivered or Attempted. Supported in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
While there isn’t a separate public sandbox, you can safely test in a non‑production environment. Create a test shop (Shopify) or an EasyRoutes for Web workspace with sample data, generate a dedicated API token, and point webhooks to staging URLs. Use draft orders or manual stops that contain your own contact info so notifications and tracking tests go only to your team. When your flows are validated, switch credentials and endpoints to production.
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web support webhooks that notify your apps when key delivery events occur—such as routes created/dispatched/updated and stops started/completed/attempted. Use them to sync delivery status into ERPs/CRMs, trigger customer communications, or update internal dashboards in real time. You can consume webhooks directly at your API endpoint or use Zapier to route events into thousands of tools (Sheets, Slack, email, etc.). Webhooks require a Premium (or higher) plan.
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. 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.
Setup is quick: install EasyRoutes (Shopify) or sign in (Web), connect drivers, select orders with filters, and click Create route. Use the defaults for service times and route options, then print or dispatch to the driver app. Most trial users reach a working route within an hour, often faster with our step‑by‑step guide.
If you import orders from outside Shopify, start with a small CSV or a few manual stops to validate the flow before scaling.
Yes. Once your Wix orders are inside EasyRoutes, you can use them in Workflows to automate common delivery tasks. For example, you could create a Workflow that builds a new delivery route every afternoon using all Wix orders tagged as “Local Delivery” and automatically dispatches them to drivers. This helps you scale delivery operations with minimal manual effort. See: EasyRoutes Workflows
Yes. When creating multiple routes as a group, use the Balance routes feature to spread stops evenly across drivers and routes. Balancing respects your other settings — such as max route duration, max stops/items, custom start/end locations, and time windows — so each route remains feasible. You can also choose to create and auto‑assign routes to selected drivers, then re‑optimize each route to fine‑tune their sequence and ETAs. This feature is available in both EasyRoutes for Shopify and EasyRoutes for Web and is especially helpful for daily batch planning.
See: Balance routes · How many routes?
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. Workflows are available across both EasyRoutes platforms, but their triggers and available actions are tailored to fit the data each platform provides. On Shopify, Workflows integrate tightly with orders, fulfillments, and Shopify-specific tags or delivery methods. On EasyRoutes for Web, you can use Workflows to automate processes based on imported orders (CSV uploads or API connections) and route activity.
This flexibility means that whether you’re using Shopify to manage your e-commerce orders or relying on EasyRoutes for Web to handle deliveries from another system, you can still benefit from automation. Businesses that operate across multiple platforms can use Workflows to keep all of their delivery processes running consistently.
See: Workflows Setup
Yes. EasyRoutes keeps your order list synchronized with Shopify so recent orders, edits, and fulfillment changes are available for routing without manual imports. If an expected order isn’t visible, confirm the Show orders from the last… window, and other filters on the Orders page, then refresh. You can also import non‑Shopify orders alongside synced Shopify orders when needed.