Yes. When a route has a scheduled start date and time and its stops carry time windows, the EasyRoutes optimizer sequences stops to arrive within each window while minimizing overall driving time, factoring in start/end locations and stop durations. Driver and customer ETAs reflect those windows. If a stop can't be met within the route's constraints, it's moved to the rejected stops tab so you can widen the window, adjust the start time, or split routes. This works in 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. Creating a fulfillment from EasyRoutes writes the EasyRoutes tracking number and URL to the Shopify order, so customers and support teams can track delivery progress. The link also appears in Shopify’s order status page and, when enabled, in Shopify or EasyRoutes notification emails/SMS. Tracking remains accessible even after routes are archived.
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.
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
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.
When no one is available, the driver documents the drop instead of collecting a signature: up to four photos of where the order was left, an optional note (e.g., "left behind the side gate"), and the GPS location and timestamp captured automatically. All of it is saved to the stop's proof-of-delivery record.
You can make a photo and/or note mandatory to mark the stop delivered, and display these items on the customer's tracking page for confidence. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
CSV imports are manual, but Zapier and the EasyRoutes API let you automate the process. With Zapier, new Xero invoices can be sent directly to EasyRoutes as soon as they’re created. With the API, developers can build real-time integrations that sync orders and updates automatically, keeping your delivery pipeline fully up to date.
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web support webhooks that notify your apps when key delivery events occur—such as routes created/dispatched/updated and stops started/completed/attempted. Use them to sync delivery status into ERPs/CRMs, trigger customer communications, or update internal dashboards in real time. You can consume webhooks directly at your API endpoint or use Zapier to route events into thousands of tools (Sheets, Slack, email, etc.). Webhooks require a Premium (or higher) plan.
No long‑term contract is required. You can start on a monthly plan, adjust driver seats as your team changes, and upgrade or downgrade tiers at any time. When you change plans mid‑cycle, EasyRoutes automatically prorates the charges so you only pay for what you use.
Yes. Workflows automate delivery tasks inside EasyRoutes, while Zapier connects EasyRoutes to external systems. Together, they create powerful end-to-end automation. For instance, a Workflow might create a route when orders arrive, while Zapier sends Slack alerts or updates a Google Sheet whenever stops on that route are completed. This layered approach ensures internal and external processes stay in sync.
See: Workflows Overview
Yes. Drivers can add photos and notes for attempts (e.g., no answer, inaccessible). You can make PoD mandatory for Attempted stops, so drivers document the situation before moving on. Attempt proof appears with the stop’s history for admins and, if enabled, on customer tracking pages/notifications to explain what happened.
See: Proof of Delivery
Setup is quick: install EasyRoutes (Shopify) or sign in (Web), connect drivers, select orders with filters, and click Create route. Use the defaults for service times and route options, then print or dispatch to the driver app. Most trial users reach a working route within an hour, often faster with our step‑by‑step guide.
If you import orders from outside Shopify, start with a small CSV or a few manual stops to validate the flow before scaling.
Yes. You can keep slips digital. From the route’s Print menu, select Packing slips and choose your browser/OS option to Save as PDF. This yields a single file ordered by the route for easy sharing.
This is supported in both EasyRoutes for Shopify and EasyRoutes for Web and is useful for handing off to 3PLs or warehouse teams that prefer tablet-based picking.
Yes. EasyRoutes allows you to centralize multi-platform order management. You can import Squarespace orders via CSV or Zapier while also syncing Shopify, WooCommerce, BigCommerce, or Wix orders into the same account. This lets you plan optimized delivery routes that combine orders from different sales channels.
EasyRoutes for Shopify is seamlessly integrated into merchants’ Shopify Admin, and can be accessed directly from the navigation menu or search bar after logging into Shopify. Permissions to create, edit, and dispatch delivery routes are limited to the same individuals who have a Shopify user account with full login access to a store’s Shopify Admin.
EasyRoutes for Web uses a standalone web browser-based login, with no Shopify account required to sign up, import your orders, and access route planning tools. With EasyRoutes for Web, route planning administrators can invite additional users to their organization’s account who can then access select EasyRoutes functionality.
See: Getting started · Add collaborators
Yes. Proof of delivery (PoD) captured in the driver app — photos, signature confirmation, and driver notes — is attached to the stop and can be surfaced on the customer’s tracking page. Enable PoD display in EasyRoutes Settings → Order tracking, and use notifications to share links automatically when a stop is delivered or attempted. PoD is also visible to admins on the route and order records for auditing and support.
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
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. 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 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 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.
Yes. When a route has a scheduled start date and time and its stops carry time windows, the EasyRoutes optimizer sequences stops to arrive within each window while minimizing overall driving time, factoring in start/end locations and stop durations. Driver and customer ETAs reflect those windows. If a stop can't be met within the route's constraints, it's moved to the rejected stops tab so you can widen the window, adjust the start time, or split routes. This works in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. If you don’t use Shopify, EasyRoutes for Web provides the same core workflow — order intake, route planning, dispatch, tracking, proof of delivery, and analytics. Bring orders in via CSV uploads, the Routes API, or webhooks/Zapier. You can also mix non‑Shopify orders with Shopify orders if you operate via multiple e-commerce channels.
Customer tracking pages and notifications work the same, and drivers use the same EasyRoutes Delivery Driver app.
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
Put the handling steps where the driver will see them: add cooler or cold-chain instructions as a stop note or a saved customer note, which appear on the stop in the driver app. For steps you want confirmed, add a Driver Task — for example a required checkbox "Order kept in cooler until hand-off" or a note field — that the driver must complete before marking the stop delivered.
Saved task sets and Address Book stops let you reuse the same instructions across recurring routes. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Driver & Stop Notes