Yes. EasyRoutes keeps your order list synchronized with Shopify so recent orders, edits, and fulfillment changes are available for routing without manual imports. If an expected order isn’t visible, confirm the Show orders from the last… window, and other filters on the Orders page, then refresh. You can also import non‑Shopify orders alongside synced Shopify orders when needed.
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. Use EasyRoutes Order Filters to build the batch you want to route. Common filters include delivery date ranges, order/fulfillment status, tags, and geography (postal/ZIP code, city, country, or your own delivery zones). Filters apply to Shopify orders and any imported/manual stops so a single route can cover precisely the area and schedule you intend.
See: Order Filters
Yes. Even though WooCommerce doesn’t have the same native integration as Shopify, once orders are imported into EasyRoutes they behave the same as any other order. This means customers can receive branded email or SMS notifications, along with live tracking links. This reduces “Where’s my order?” calls and improves the customer experience.
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.
Each stop supports multiple PoD elements: up to four photos, an e‑signature with timestamp, and any driver notes. Use photos for placement/context and the signature for hand‑off confirmation. These items appear in admin views, can be shown on tracking pages (per your settings), and are included via links in route/stop exports for record‑keeping.
See: Proof of Delivery
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. Access to the EasyRoutes API and webhooks requires a Premium (or higher) subscription across both products (Shopify and Web). If you’re evaluating, you can prototype with CSV import or the driver app while you finalize your integration plan, then enable API once you upgrade.
Yes. From the Routes page or an individual route, export CSV files containing stop information (customer name, address, contact fields), timing, driver assignments, and URLs to any proof of delivery items. Use these exports for customer service, accounting reconciliation, or analysis in spreadsheets and external tools.
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
API access uses tokens you create in your EasyRoutes account. Follow the Getting Started guide to generate a token, store it securely, and add it to requests from your server or integration platform. Tokens work the same way for both EasyRoutes for Shopify and EasyRoutes for Web. Rotate credentials periodically and avoid embedding them in client‑side code.
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.
Workflows are available on EasyRoutes Premium and Enterprise plans. These plans are designed for businesses that need more advanced tools to handle larger delivery volumes and complex processes. On Premium and Enterprise, you not only get access to Workflows, but also other advanced features like custom notifications, vehicle profiles, real-time driver tracking, and delivery analytics.
If you’re running a small business with only a few deliveries per week, you may be fine with a Standard plan. But if your business is scaling or you want to automate as much as possible, upgrading to Premium ensures you can take advantage of Workflows. This investment pays off quickly by saving your team time, reducing manual work, and improving consistency across your delivery operations.
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
Absolutely. EasyRoutes supports mixed sources across both products (Shopify and Web). Bring in non‑Shopify orders by uploading a CSV, sending stops through the Routes API, connecting via webhooks/Zapier, or adding custom stops manually. Once imported, they appear alongside Shopify orders on the Orders page, can be filtered like any other stop, and can be optimized together on the same route.
See: Adding custom stops from outside Shopify · Routes API · Webhooks & Zapier
While there isn’t a separate public sandbox, you can safely test in a non‑production environment. Create a test shop (Shopify) or an EasyRoutes for Web workspace with sample data, generate a dedicated API token, and point webhooks to staging URLs. Use draft orders or manual stops that contain your own contact info so notifications and tracking tests go only to your team. When your flows are validated, switch credentials and endpoints to production.
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
When you plan a route with the Delivery zones option enabled, only orders that fall inside the selected zone’s boundary are added. Any orders outside the boundary are held back for review rather than dropped, so nothing gets lost — you can route them separately, assign them to another zone, or handle them manually. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
The majority of EasyRoutes’ core route planning and optimization features are included in both products, including our intuitive user interface, customizable route options, and visual route planning via map views.
EasyRoutes features that rely on Shopify-native functionality or APIs (such as Shopify email & SMS notifications, order tags, subscription order generation, and fulfillment workflows) are not currently available on EasyRoutes for Web. Select EasyRoutes automation tools (including import automation rules) are also currently exclusive to EasyRoutes for Shopify.
See: Notifications (Shopify + Web) · Order automation (Shopify-only)
Yes. While the PoD gallery itself isn’t a single file download, route/stop exports include links to each proof item plus completion timestamps and driver details — suitable for audits, customer service, or further analysis with external tools. Use Analytics for high‑level performance metrics and the Activity Feed to review the exact sequence of events.
See: Exporting proof of delivery · How do I export routes/stops?
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. Both EasyRoutes for Shopify and EasyRoutes for Web let you re‑optimize a route whenever plans change. Use this feature after you add or remove stops, change stop priorities, edit time windows or service times, or adjust limits like max route duration and stop limits. You can also balance stops across multiple routes first, then re‑optimize each route to tighten the sequence. If permitted in your Driver Settings, drivers may manually re‑order stops from the driver app or re‑optimize the remaining stops in their route to recalculate ETAs after mid‑route changes. For API‑driven workflows, use the Routes API to programmatically update routes and trigger re‑optimization.
See: How do I re‑optimize a route? · How do I allow drivers to re‑order stops?
Yes. Mark COD orders and include collection instructions in stop notes. Drivers can record payment received using notes and attach custom notes containing any COD amounts collected. Back at the office, export routes/stops to reconcile COD activity. This workflow is supported across EasyRoutes for Shopify and EasyRoutes for Web.
See: Cash on Delivery
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.
The WebToffee “Order Export & Import for WooCommerce” plugin is one of the recommended tools for exporting WooCommerce orders to CSV. It lets you configure export settings like separating line items, which ensures EasyRoutes can correctly map customer and order details. Other export tools may work, but WebToffee is the most commonly documented and tested option.
Yes. When you collect an e-signature, the driver can record who signed — the "Signed for" name is stored with the stop and appears in exports. For an explicit record, add a Driver Task text field for the recipient's name, and the driver can add a note or photo as well.
All of it is saved to the stop's proof-of-delivery timeline and can be shown on the customer's tracking page. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks