Yes. Set a route-wide Time per stop as your baseline, then adjust the service time on any individual stop from its Edit stop page — useful when a bulk drop, an in-home setup, or a quick curbside hand-off needs a different allowance than the rest of the route.
Because each stop's time feeds ETAs and counts toward Max route duration, mixing short and long service times still produces an accurate schedule. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Editing Routes
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.
Time windows are interpreted in the time zone of each stop's delivery address, so a window set by your date picker is honored locally even when a route crosses time zone boundaries (for example, travelling from Chicago toward Indianapolis). Your Orders page and route columns display windows in your own local time, and stops in a different zone are annotated as such. This behavior is the same in EasyRoutes for Shopify and EasyRoutes for Web.
See: Time Windows
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. EasyRoutes reads Shopify Local Delivery details (including delivery instructions from checkout) and adds them to the stop for drivers. If you maintain Pickup orders and want them represented on a route — for example, to stage curbside handoff or transfer to another location — you can include them with your store or pickup address so the task appears in sequence and on printed documents.
See: Where can I see delivery instructions from a Shopify Local Delivery order?
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
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 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.
Yes! You can use EasyRoutes' API to customize your integration and build powerful workflows to suit your specific delivery needs. You can also connect EasyRoutes webhooks to Zapier to unlock seamless, no-code workflows with your favourite apps and services, triggered by route updates in EasyRoutes.
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. 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.
Yes. In Settings > Delivery Zones, tick the zones you no longer need and click Archive to remove them from your active list. Archived zones aren’t gone for good — use the Add filter control below the map to show Archived or All, then select and Unarchive any you want back. This keeps your active zone list tidy without losing past boundaries. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
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.
If a scanned code doesn’t match the stop, the app shows it in yellow rather than the green used for a confirmed match, so the driver can tell right away. Non-matching scans can still be saved, and drivers can flag a scan issue from the alert icon on the Add Barcode screen, which sends a report to the route planner instead of a matched scan. Works the same in EasyRoutes for Shopify and EasyRoutes for Web.
Yes. From the Analytics page, pick your time period (e.g., last 7/30 days or a custom range) and optionally filter by driver. Use the Export option to download a CSV for spreadsheets or external tools, or use Print to generate a PDF summary. CSV exports preserve the filters you applied so downstream reports match what you saw in EasyRoutes.
Exports are available in both EasyRoutes for Shopify and EasyRoutes for Web. If you need more granular, stop‑level records, combine Analytics with route exports from the Routes page.
Yes. Add the instruction to a saved customer in your Address Book and it carries over to that customer's future stops; for one-off orders, add it as a stop note. Shopify local-delivery instructions are also parsed onto the stop automatically.
These notes display to the driver in the app, and a required Driver Task can prompt them to confirm the leave-at-door step. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver & Stop Notes · Address Book
By default, CSV imports are static snapshots. To enable real-time updates, you can set up a Zapier workflow that pushes new or updated Wix orders into EasyRoutes automatically. Alternatively, use the API to sync live changes such as address edits or cancellations, ensuring drivers always have up-to-date information. See: Zapier Guide
EasyRoutes for Web is best suited for merchants and service providers who do not have an existing Shopify presence. Users may currently be using spreadsheets and manual processes to track orders/stops and plan delivery routes, or may be using an alternate eCommerce platform where orders/stops can be exported into a spreadsheet. We also offer an API.
Spreadsheets containing order data can quickly be imported into EasyRoutes for Web to plan and dispatch optimized delivery routes in a fraction of the time compared to manual planning methods.
See: Import orders from CSV · API: Getting Started · Zapier webhooks
Yes. The Activity Feed is designed to provide a verifiable sequence of events — who did what, and when — covering route creation, dispatch, status changes, driver assignments, and proof‑of‑delivery uploads. For external reviews or compliance checks, export related routes/stops to CSV to provide structured records and links to PoD. Together, these sources form a complete audit trail.
Yes. When you configure a Scanner-input Driver Task, tick the Delivered and/or Attempted checkboxes to make a successful scan mandatory before that status can be applied. You can also require a Barcode Scan as proof of delivery from Settings > Driver Settings. Either way, drivers can’t mark the stop complete until the scan is captured. Available on Premium and Enterprise plans, in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver tasks · Driver settings
From your Xero dashboard, go to the Business tab → Invoices, then use the Export button to download a CSV of the invoices you want to deliver. In EasyRoutes, click “Import new CSV” and upload the file. The system maps fields such as contact name, address, invoice number, and product details to create delivery-ready routes. See: Xero Import Guide
EasyRoutes doesn't have a setting that hard-locks a stop to one named person, but you can require and document the hand-off. Add a required Driver Task — a text field for the recipient's name, or a checkbox confirming "handed to named recipient" — that must be completed to mark the stop delivered, and note the required recipient in a stop note so the driver knows who to look for.
Pair it with a required e-signature so the signer is captured too. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Proof of Delivery
No — routes are single‑driver to keep tracking, ETAs, and proof‑of‑delivery accurate. If two or more drivers are needed, split the stops into multiple routes (or create a new route for leftovers) and dispatch each separately. You can also publish a route without assigning a driver, and share a self‑assign link so someone from your pool can claim it when ready.
Yes. EasyRoutes features customizable Vehicle Profiles for different vehicle types, as well as route capacities (e.g., item or weight limits) that can be assigned to a route so our route optimizer respects those limits. Route‑level capacity controls — such as Max items per route and Max weight per route — to prevent overloading a vehicle. Pair capacity settings with other constraints (including custom start/end locations, stop time intervals, and delivery time windows) and re‑optimize to reflect changes. For commercial navigation needs, export routes to GPX and load them onto Garmin devices that support truck‑aware routing.
See: Vehicle Profiles · Max items/weight per route · Commercial vehicles & GPX Export
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
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