Yes. One of EasyRoutes’ strengths is its ability to centralize delivery management. You can import WooCommerce orders via CSV or Zapier while also syncing Shopify, BigCommerce, or other platform orders into the same account. EasyRoutes will display all of them together so you can generate optimized routes across multiple sales channels.
See: WooCommerce Overview
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.
No. Barcode scanning uses the camera on your driver’s existing iOS or Android device, so there’s no need to buy dedicated scanners or hardware. Drivers scan directly from the EasyRoutes Delivery Driver app, with a built-in flash option for low light and a manual-entry fallback if a code won’t read. It supports common linear formats (UPC, EAN, Code 128, and more) and 2D codes like QR and Data Matrix. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
Yes. EasyRoutes is designed to unify multi-platform delivery operations. You can import Wix orders and combine them with orders from Shopify, WooCommerce, BigCommerce, or other sources. All orders appear in one dashboard, so you can generate optimized multi-stop routes across platforms.
See: EasyRoutes for Wix
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
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.
Capping how many orders a customer can book into a given slot is handled by your date picker app at checkout (for example, Pickeasy's order limits), not by EasyRoutes. On the planning side, EasyRoutes helps you balance the resulting workload: filter orders by delivery date and time window, then split them across multiple routes or drivers, and the optimizer sequences each route to respect its windows. Together they keep slots controlled and routes balanced. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
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. 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.
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
When exporting orders from Squarespace, ensure you only include “Pending” orders from the fulfillment filter. This ensures you’re working with unfulfilled deliveries that still need to be routed. If only certain products require delivery, you can filter by “Specific product” during export. This gives you precise control over which orders are included in your EasyRoutes import.
Dispatchers manage routes from the browser interface. On Shopify, open the Shopify mobile app and launch EasyRoutes to view routes, assign drivers, and monitor progress from supported mobile devices. For EasyRoutes for Web, sign in from your phone’s browser for a responsive experience. Drivers should use the dedicated EasyRoutes Delivery Driver app for turn‑by‑turn and proof of 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.
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
EasyRoutes factors expected traffic conditions into its route optimization and ETA calculations, using live map and traffic data to sequence stops and estimate arrival times. As conditions or your stops change, you can re-optimize at any time and EasyRoutes recalculates the most efficient order. This works alongside options like time windows, toll avoidance, and stop priorities. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options
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.
Zapier lets you automate actions inside EasyRoutes, such as importing stops from external systems. For example, a Zap could take new orders from WooCommerce or Xero and create delivery stops inside EasyRoutes automatically. This eliminates manual data entry and keeps your routes up-to-date in real time.
Drivers can install the EasyRoutes Delivery Driver app from the App Store (iOS) or Google Play Store (Android) using the official links provided in our Help Center. The app works with both EasyRoutes for Shopify and EasyRoutes for Web accounts; once added as a driver, sign in using the phone number on file and the SMS code sent to that device. After dispatch, routes appear automatically in the app and can also be opened from the push notification's shared route link.
See: Where can I download the EasyRoutes Delivery Driver app?
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.
Yes. If a driver’s phone was offline or a photo needs to be re‑added, open the stop in EasyRoutes and upload PoD from your browser. The new items join the stop’s timeline with timestamps and appear in exports and tracking (subject to your visibility settings). This works across both EasyRoutes for Shopify and EasyRoutes for Web.
See: Manually upload PoD
Workflows in EasyRoutes are powerful automation tools that let you design and run delivery management processes without needing to handle every step manually. Think of them as “if-this-then-that” rules that connect your orders, routes, and driver dispatching into a seamless flow. Instead of relying on a dispatcher to constantly create routes, select orders, or assign drivers, Workflows can do these repetitive tasks for you automatically.
For example, you could create a Workflow that listens for new Shopify orders tagged as “Local Delivery” and automatically builds a route every morning at 9 AM, adds matching orders to the route, optimizes route stops, and assigns it to a specific driver. By reducing manual intervention, Workflows make your operations more consistent, scalable, and error-proof.
See: Workflows Overview
Yes. In EasyRoutes for Shopify you decide whether to send messages using EasyRoutes’ customizable templates, or Shopify’s native notification flows. EasyRoutes writes tracking details to the Shopify fulfillment so the order status page and Shopify notifications include the correct link. If you enable both systems, review your templates to prevent duplicate emails/SMS.
Configuration lives in EasyRoutes notification settings; Shopify templates are managed in your Shopify admin.
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. 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. 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.
CSV import works well for manual workflows, but if you want orders to sync automatically, Zapier or the EasyRoutes API is the solution. Zapier allows you to create automations where new Squarespace orders are instantly sent to EasyRoutes. The API provides developers with even more control, such as syncing fulfillment statuses or building advanced integrations with other systems.
See: Zapier Integration