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.
Yes. In EasyRoutes for Shopify you decide whether to send messages using EasyRoutes’ customizable templates, or Shopify’s native notification flows. EasyRoutes writes tracking details to the Shopify fulfillment so the order status page and Shopify notifications include the correct link. If you enable both systems, review your templates to prevent duplicate emails/SMS.
Configuration lives in EasyRoutes notification settings; Shopify templates are managed in your Shopify admin.
EasyRoutes doesn't have a purpose-built haul-away field, but drivers can document a removal reliably. Add a required Driver Task — a checkbox "Old item removed," a text field for the item description, or a number field for quantity — that must be completed at the stop, and have the driver photograph the removed item as proof of delivery.
Task results and photos are stored with the stop and included in exports for your records. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Proof of Delivery
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.
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. 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?
Yes. Access to the EasyRoutes API and webhooks requires a Premium (or higher) subscription across both products (Shopify and Web). If you’re evaluating, you can prototype with CSV import or the driver app while you finalize your integration plan, then enable API once you upgrade.
Yes. When you create several routes together, EasyRoutes places them in a Route Group so you can manage a delivery day (or multiple zones) as a single unit. From the group page you can dispatch all routes, view colour‑coded live driver pins, move stops between routes, and balance workloads. Route Groups work the same in EasyRoutes for Shopify and EasyRoutes for Web and are ideal for medium/large fleets or recurring delivery days.
See: Route Groups
The WebToffee “Order Export & Import for WooCommerce” plugin is one of the recommended tools for exporting WooCommerce orders to CSV. It lets you configure export settings like separating line items, which ensures EasyRoutes can correctly map customer and order details. Other export tools may work, but WebToffee is the most commonly documented and tested option.
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 Workflows support a wide variety of actions that cover the full delivery process, from order intake to customer communication. You can automatically generate new routes based on incoming orders, apply filters (such as only including orders tagged with “Priority” or due on a specific date), and dispatch routes directly to the correct driver. This level of automation means you can build a Workflow that matches your exact delivery process, no matter how simple or complex.
See: Workflow Actions
Yes. From any route, click Print → select Packing labels. You can output one label per stop or per order item (ideal for multiple packages). Configure label contents and sizing in Settings → Packing Slips & Labels. Use 4×6 thermal, A4/Letter sheets, or another size and scale as needed.
Shopify & Web: The label workflow is the same across products. For advanced templating on Shopify, you can send orders to Order Printer Pro from the Send to app dropdown, which can generate labels in route order.
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
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. 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. Use the driver filter on the Analytics page to view metrics for a single driver or compare across drivers by switching the filter. This helps you evaluate utilization, completion rates, average stop times, and trends over time. It’s supported in both EasyRoutes for Shopify and EasyRoutes for Web and respects any date range you’ve selected.
If a driver worked on multiple routes per day, those results roll up in the selected period. For route‑by‑route detail, open the route list and drill into specific days.
See: Filtering by Driver
Yes. The Time per stop route option lets you set how many minutes a driver spends at each stop — parking, walking, and handing off — so routes reflect real service time, not just drive time. Set it when creating a route, and it's applied to every stop on that route.
You can also fine-tune the service time on an individual stop from its Edit stop page when a particular delivery needs longer. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
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.
The Activity Feed itself isn’t exported as a single file, but you can export route and stop data that reflect the same underlying events. From the Routes page, export a date range (or open a specific route) to download CSVs containing stop details, completion timestamps, driver info, and links to proof of delivery. Use the feed to identify the timeframe or routes you need, then export those records directly.
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. EasyRoutes supports pickups alongside deliveries in both EasyRoutes for Shopify and EasyRoutes for Web. Add pickup stops the same way as deliveries (Shopify orders, CSV/API imports, or manual stops). Set the pickup location (store/warehouse/customer) and, if needed, add instructions or required items to the stop notes.
Pickups appear in the route in sequence with other stops, on printed documents, and in the driver app. If only pickups are needed, create a pickup‑only route and dispatch to the driver as usual.
Barcode scanning is available on EasyRoutes Premium and Enterprise plans. Scanner-input Driver Tasks and barcode-based proof-of-delivery requirements both live in those tiers, in both EasyRoutes for Shopify and EasyRoutes for Web. If you’re on a lower plan and want to validate stops by scan, upgrading to Premium or above enables it.
See: Driver tasks · Barcode scanning
EasyRoutes tracks distance and drive time for your routes, shown in metric or imperial units, and surfaces route metrics in Analytics. To gauge fuel and cost, set up Vehicle Profiles (which store each vehicle’s fuel economy) and assign them to routes, then break Analytics down by vehicle to compare efficiency. There isn’t a single built-in dollar “savings” figure, but comparing periods lets you see the trend. Available in 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
Yes. Enable automatic dispatch so newly created routes with a scheduled start time are assigned and sent to the chosen driver immediately — no extra clicks. Use this for recurring daily runs or integrations that create routes programmatically. You can still edit or un-dispatch a route before start time if plans change.