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. 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
Yes. EasyRoutes treats wholesale orders like any other Shopify orders for routing, dispatch, tracking, and proof of delivery. Ensure each record includes a valid shipping address; if not, correct it on the Shopify order (recommended) or add the address details to the stop in EasyRoutes. You can filter B2B orders by tags or other attributes when building a batch.
See: Working with items & fulfillments · Add a missing shipping address
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.
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 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. To repeat a regular run, open the route and use the actions menu to duplicate/copy it, then set a new date/time, driver, and any updated options. Re‑optimize to account for traffic windows or new constraints. You can also copy only a subset of stops by selecting them and sending them to a new route. This approach works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: How to Edit Routes
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. When you assign and dispatch a route, EasyRoutes sends the driver a push notification that opens the route in the EasyRoutes Delivery Driver mobile app. If the driver doesn’t receive alerts, confirm notification permission on the device and that the driver is added with the correct phone number. Drivers can also pull‑to‑refresh their route list to fetch new assignments.
See: How do I dispatch/share routes? · Troubleshooting push notifications
Yes. In Settings > Delivery Zones, click the dropdown arrow on the Create zone button and choose Import KML, then drag in your .KML file. Zone names from the file apply automatically, and you can rename them or set a route colour before saving. Boundaries drawn in tools like Google Earth work well; KMZ or GeoJSON files should be converted to .KML first. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
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?
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.
Once your BigCommerce orders are in EasyRoutes—whether through CSV, Zapier, or API—they can be used with Workflows to automate repetitive tasks. For example, you could build a Workflow that automatically creates and dispatches routes every morning for all BigCommerce orders tagged “Delivery.” This allows your BigCommerce operation to benefit from the same automation available to Shopify users.
See: Workflows Overview
By connecting Squarespace to EasyRoutes, you get access to a full delivery management toolkit: optimized multi-stop routes, real-time driver tracking, branded notifications, proof of delivery (photos, notes, signatures), and delivery analytics. This transforms Squarespace from just an eCommerce storefront into a complete last-mile logistics solution.
See: Squarespace Overview
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?
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. Real‑time tracking is configurable. You can enable tracking for dispatcher visibility while keeping customer pages static, or allow a live pin to appear only as the driver approaches (configurable from 1 to 10 stops away). This setting is available on Premium/Enterprise plans across both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. From any route, use the checkboxes to select one or more stops, then click the bulk actions bar and choose Send to another route. You can also open a Route Group and drag stops from one route to another within the group. After moving, click Save and (optionally) Re‑optimize to update the stop order and ETAs. This workflow works the same in EasyRoutes for Shopify and EasyRoutes for Web.
Use this to balance workloads mid‑day, handle late additions, or consolidate leftovers onto a cleanup route.
Yes. In both EasyRoutes for Shopify and EasyRoutes for Web you can keep route history tidy by archiving routes you no longer need to manage daily, or permanently delete them. Use the checkboxes to select desired routes from the Routes page, and use the actions menu to archive or delete. Archiving preserves stop records, proof of delivery (photos/signature/notes), and analytics, so you can still search and export later. Deleting removes the route from Route History — make sure to export any reports you need first.
Use filters on the Routes page to show active, completed, or archived runs when you’re reconciling a period.
See: How do I archive or delete routes from my route history?
Yes. While CSV imports are manual, you can connect Wix to EasyRoutes automatically using Zapier or our API. For example, you can create a Zap that triggers whenever a new Wix order is placed, sending it directly to EasyRoutes for route creation. Advanced users can also use the API to sync orders and updates in real time, keeping your delivery workflow fully automated.
See: Zapier Integration
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web can display proof of delivery (PoD) on the customer’s tracking page right after a stop is marked Delivered or Attempted. PoD can include delivery photos, e‑signature confirmation, and optional driver notes. Turn this on from EasyRoutes Settings → Order tracking, and use notifications (email/SMS) to send tracking links automatically. For internal auditing, PoD is also visible on the route and stop records for your team.
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. 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.
EasyRoutes-native barcodes are QR codes generated by EasyRoutes and printed on your packing slips and labels; each is tied to a specific stop, so a scan can be validated as a match. Existing product or order barcodes (like a supplier’s UPC) aren’t tied to a stop that way — drivers can still scan and record them as proof, but match validation is strongest with EasyRoutes-native codes. Both work in EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
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. Both EasyRoutes for Shopify and EasyRoutes for Web can surface proof of delivery (PoD) to customers. Enable PoD display on tracking pages and decide which delivery events should send links via email/SMS. When a driver completes a stop, PoD is attached to that stop and becomes available to customers according to your settings. Admins always see PoD in route and stop details for auditing or future reference.