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.
No. Both products dispatch routes to the same EasyRoutes Delivery Driver app on iOS and Android. Drivers get identical navigation choices (Google/Apple/Waze), proof-of-delivery tools, barcode/driver tasks, and optional features like re-optimizing remaining stops or scheduled breaks — controlled by your admin settings. Any differences are admin-side only (e.g., Shopify-specific fields shown/hidden).
See: Delivery Driver app · Barcode scanning · Location tracking
When a delivery can't be completed, the driver marks the stop Attempted and selects a reason (customer unavailable, access denied, refused, and more), capturing proof of the attempt. To redeliver, use Send to another route to move the stop onto a new or later route — as a fresh stop, or as a copy that preserves the original's history.
This keeps failed stops from getting lost and lets you batch redeliveries into the next run. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Mark an order as Attempted · Send orders to another route
Yes for signature: in Driver settings you can require an e-signature (and/or photo) before a stop can be marked delivered, and customize the signature disclosure text shown to the recipient. For the ID portion, add a required Driver Task — a checkbox or text field confirming the ID check — so the driver can't complete a restricted stop without it.
Together these enforce a consistent, documented hand-off, though the age/ID check itself is performed by the driver rather than verified automatically. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks
Yes. When a stop can’t be completed, drivers mark it Attempted instead of Delivered from the Update Status section on the stop. They can choose a preset reason (for example, no answer, inaccessible, or Canceled) and add a note or proof of delivery to document what happened. The reason then appears on the stop’s details and feeds into your delivery analytics. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
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
Yes. The Analytics dashboard lets you pick a time period and, optionally, a second period to compare against, plus break the data down by driver. Trend lines (linear or logarithmic) help visualize the direction of your delivery metrics over time, and longer ranges roll up into weekly or monthly intervals. You can export any breakdown to CSV for deeper analysis. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Analytics
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 to colour-coding: each zone has its own route colour, set when you create or edit it, which makes overlapping territories easy to tell apart on the map. Drivers aren’t assigned to a zone directly — instead, plan the zone’s route (or generate a Route Group with one route per zone) and assign a driver when you create or dispatch it. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
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
The EasyRoutes API lets you automate your delivery workflow end‑to‑end: import orders/stops from external systems, create routes with your preferred options, assign drivers or vehicles, dispatch routes, and update stop or route status as deliveries progress. You can also read back route/stops for reporting and pair the API with webhooks to keep other systems synchronized in real time. Capabilities are consistent across EasyRoutes for Shopify and EasyRoutes for Web.
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.
Yes. Time windows are supported in both EasyRoutes for Shopify and EasyRoutes for Web. Add a window directly to a stop, or pull windows from checkout tools/date pickers (e.g., Zapiet, Buunto, and other supported third‑party apps). This way, our route optimizer sequences stops to respect open/close times while considering start/end locations, stop times, and other limits. If windows create conflicts that exceed constraints (e.g., max duration), split stops into additional routes or relax limits, then re‑optimize. ETAs displayed to drivers and customers reflect these windows so deliveries align with customer preferences as closely as possible.
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.
For extended-handling stops, increase the Time per stop or the individual stop's service time so ETAs and Max route duration account for the extra work. For two-person deliveries, note that a route is assigned to a single driver account, so you'd staff that route's vehicle with a crew operationally rather than assigning two driver logins to one route.
Driver Tasks can capture crew-specific steps at the stop. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Driver Tasks
EasyRoutes combines route planning, driver dispatch, live tracking, and proof of delivery in one system. Teams select orders (from Shopify or external sources), create optimized routes with start/end locations and options (time windows, service times), then dispatch to the EasyRoutes Delivery Driver app.
Admins monitor routes in the browser, view ETAs and driver location (Premium/Enterprise), and share branded tracking pages and notifications with customers. Proof of delivery items — photos, eSignature, notes — are captured in the field and visible on the stop record. EasyRoutes is designed for SMBs and delivery fleets of any size across industries.
Yes. The EasyRoutes Routes API accepts imported orders/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. Open any template in the Notifications editor and use Preview with Example Data to see how your message will render, including variables. You can also send a real‑world test by creating a draft order or manual stop with your own contact details, and triggering notifications on a sample route. Preview/testing tools are available for both email and SMS on Shopify and Web.
You don’t need to be a developer to connect WooCommerce with EasyRoutes. Zapier provides no-code automation tools that let you push WooCommerce orders directly into EasyRoutes with just a few clicks. For businesses that want more control, the EasyRoutes API is available to build deeper integrations, such as syncing fulfillment statuses or creating custom routing rules. This gives you both no-code and pro-code options.
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.
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. Set a scheduled start date and time when creating or editing a route. EasyRoutes will use that schedule — plus stop time intervals and any delivery time windows — to calculate ETAs for every stop. Customers can receive their individual ETAs via branded tracking pages and optional email/SMS notifications. If plans change, simply edit the route's schedule, re‑optimize the route, and ETAs will update automatically.
By integrating BigCommerce with EasyRoutes, you get a complete delivery management solution: multi-stop route optimization, real-time driver tracking, branded customer notifications, proof of delivery (photos, notes, signatures), and analytics. This turns BigCommerce from a storefront into a powerful logistics tool, helping you scale local delivery with confidence.
See: BigCommerce Overview
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.
Yes. After importing Squarespace orders into EasyRoutes (via CSV, Zapier, or API), they can be used with Workflows. For example, you could set up a Workflow that automatically generates delivery routes at a set time each day from all Squarespace orders and dispatches them to drivers. This helps Squarespace merchants automate repetitive tasks and maintain smooth operations.
See: EasyRoutes Workflows
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