Yes. Use Delivery Analytics to review outcomes by driver — completed vs. missed stops, average delivery time, and overall success rate — over a selected period. Filter to focus on a single driver or compare across the team. For detailed investigations, open routes to see timestamps and proof of delivery, or export results for use in external tools.
See: Delivery Analytics
Yes. EasyRoutes opens your driver’s preferred navigation app for turn‑by‑turn directions. Drivers can choose Google Maps, Apple Maps, or Waze as their default navigation app from the mobile app's settings page. Drivers can also long tap and choose a different app on the fly if needed. Getting directions is 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
No coding is required if you use Zapier, which allows you to set up automations like sending new Wix orders into EasyRoutes with just a few clicks. For businesses needing deeper control, the EasyRoutes API allows developers to build integrations for syncing fulfillments, handling custom workflows, or connecting to other back-office systems.
See: EasyRoutes API Guide
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
Yes. EasyRoutes prints all slips for the selected route in one batch. From the route page, choose Print → enable Packing slips → print or save as PDF. Slips are ordered to match the route so packing and loading follow the driver’s sequence.
This bulk flow is available in both EasyRoutes for Shopify and EasyRoutes for Web. If you maintain custom slip templates in Shopify, you can also push orders to Order Printer Pro and print them in route order from there.
By default, CSV imports are static snapshots. For real-time updates, use Zapier to push new BigCommerce orders into EasyRoutes automatically, or build a direct integration with the API. This ensures address changes, order edits, or cancellations in BigCommerce are reflected in your delivery routes without manual intervention.
See: Zapier Integration
Yes. Manual and imported stops can send the same email/SMS notifications as Shopify orders once configured. In EasyRoutes Settings → Customer notifications, enable templates under the Imported Orders sections and ensure each stop includes an email address and or phone number. Use tracking links to provide status and proof of delivery even when the source isn’t Shopify.
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. From Proof of Delivery settings, you can force one or more PoD elements to be collected before drivers can complete a stop. Choose the combinations that fit your workflow — e.g., require a photo for attempted stops, or require e‑signatures for only completed stops. These rules apply in EasyRoutes for Shopify and EasyRoutes for Web, and can include Attempted stops.
See: Make PoD Required
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. Once imported into EasyRoutes, BigCommerce orders behave the same as other orders. Customers receive branded notifications by email or SMS, including links to real-time tracking pages. This reduces support calls and gives customers confidence in their deliveries.
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. 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.
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.
When exporting from BigCommerce, configure your CSV template to create one row per sub-item (so multiple items in an order export properly). Map fields like First Name, Last Name, Address, and Product Qty to the corresponding EasyRoutes columns. This ensures accurate imports and prevents issues with incomplete customer or item data.
See: Importing CSV Orders
Yes. Upload a CSV to create stops with customer, address, and item details — even if the orders weren’t placed in Shopify. The importer supports line‑item fields such as quantity and weight so you can use vehicle capacity limits accurately. Once imported, these stops can be filtered, optimized into routes, and dispatched to drivers like any other order source.
Yes. The EasyRoutes API enforces rate limits to ensure consistent performance for all users. Most workflows run comfortably within default limits when you batch requests, avoid unnecessary polling, and rely on webhooks to trigger updates rather than frequent reads. If you expect sustained high throughput (e.g., large imports or rapid status updates), our team can help you design an efficient approach and advise on limits for your use case.
Yes. The EasyRoutes Delivery Driver mobile app supports complete proof of delivery: capture multiple photos, obtain a customer e‑signature, and add notes (e.g., where the parcel was left). PoD is stored with the stop and visible to admins; if you enable PoD on tracking pages, customers can view it as well. PoD uploads immediately when a driver has an active internet connection, and will sync when re-connected if captured while offline.
See: Proof of Delivery
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. EasyRoutes opens your driver’s preferred navigation app for turn‑by‑turn directions. Drivers can choose Google Maps, Apple Maps, or Waze as their default navigation app from the mobile app's settings page. Drivers can also long tap and choose a different app on the fly if needed. Getting directions is available in both EasyRoutes for Shopify and EasyRoutes for Web.
EasyRoutes turns your driver’s phone camera into a scanner — no extra hardware needed. Drivers scan a barcode or QR code from the Proof of Delivery section, or from a Scanner-input Driver Task, before completing a stop. Matching codes are confirmed in green; non-matching codes appear in yellow and can be flagged back to the route planner. Every scan is stored with the stop’s proof of delivery for live or later review. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
Zapier is designed to be used without coding. To integrate EasyRoutes, you typically select “Webhooks by Zapier” as a trigger, paste a webhook URL into EasyRoutes, and then connect it to actions like sending an email or updating a spreadsheet. All steps are handled through a simple, click-based interface. This makes automation accessible to any team member, not just developers.
See: EasyRoutes Zapier
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
When a driver captures an e‑signature, customers see an indicator and timestamp on the tracking page confirming that the order was signed for. The signature image is stored with the stop for internal use (support, audits) and can be accessed by admins; it is not shown directly to customers to protect privacy.
See: Proof of Delivery
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