Yes. You can constrain every route so product isn't in transit too long. Set Max route duration to cap total hours, use Max stops per route or Max items per route to limit load size, and optimization will automatically create additional routes rather than overrun your limit. Add time windows for the most sensitive stops so they're served first. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
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?
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
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. Aggregate missed vs. completed counts appear in Analytics, and when a stop cannot be completed, the driver can select or enter a reason in the mobile app. Those reasons are recorded on the stop and visible to admins for follow‑up. Reviewing these notes helps you spot patterns — like frequent access issues at certain buildings — and take corrective action.
Use Analytics to quantify the impact over time, then drill into routes and stops to see the exact explanations and any attached proof (photos/notes). This behaviour is consistent across EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Integrate EasyRoutes with your existing stack in two ways: (1) programmatically via the Routes API to import stops, create/dispatch routes, and update status; and (2) event‑driven with webhooks and Zapier to push delivery events into Sheets, Slack, email, ERPs/CRMs, or custom endpoints. These options are available for both EasyRoutes for Shopify and EasyRoutes for Web.
See: API Getting Started Guide · Integrate webhooks with Zapier
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. See: Squarespace Integration
Yes. For flexible fleets, create a self‑assign link so any active driver can claim the route from the link. This is useful for contractor pools or last‑minute coverage — whoever taps the link first becomes the assigned driver. You can share links in SMS, WhatsApp, or Slack and revoke them if needed.
Yes. EasyRoutes supports WooCommerce order data in multiple ways. You can export orders from WooCommerce and import them into EasyRoutes via CSV, or you can set up automated workflows using Zapier or our API. This flexibility allows you to start with simple drag-and-drop imports and scale up to real-time order syncing as your delivery needs grow.
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. 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. 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. 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.
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.
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. 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. 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. EasyRoutes features customizable Vehicle Profiles for different vehicle types, as well as route capacities (e.g., item or weight limits) that can be assigned to a route so our route optimizer respects those limits. Route‑level capacity controls — such as Max items per route and Max weight per route — to prevent overloading a vehicle. Pair capacity settings with other constraints (including custom start/end locations, stop time intervals, and delivery time windows) and re‑optimize to reflect changes. For commercial navigation needs, export routes to GPX and load them onto Garmin devices that support truck‑aware routing.
See: Vehicle Profiles · Max items/weight per route · Commercial vehicles & GPX Export
Yes. Programmatically modify routes and stops using the Routes API — update stop status (delivered/attempted), change assignments, dispatch routes to drivers, or edit route options, then re‑optimize as needed. When your store uses EasyRoutes notifications, status changes made through the API follow the same rules and can send customer updates and refresh ETAs. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
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.
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. See: Zapier Integration Guide
Pick any plan to start a 14-day trial with full feature access. Cancel during the trial to avoid charges; continue and your subscription begins at the end of day 14. Trials apply to any tier, and billing starts on your first post-trial cycle through Shopify (for EasyRoutes for Shopify) or Stripe (for EasyRoutes for Web). Seat changes you make later will be prorated within your billing cycle.
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.
EasyRoutes doesn’t provide a native accounting app, but it connects cleanly via exports and integrations. Export route/stop CSVs for reconciliation, or use the Routes API and webhooks to sync delivery events (e.g., Delivered, Attempted) to tools like QuickBooks, Xero, or an ERP. Zapier can automate common tasks — posting mileage, closing jobs, or notifying finance of COD deliveries — without complicated code.
See: EasyRoutes Webhooks · Integrate with Zapier · Export routes/stops
To sign in, add the driver to your EasyRoutes account (Shopify or Web) with their phone number. The driver installs the app and enters that number; we send a one‑time SMS code to complete sign‑in. Routes assigned to that number appear automatically. If a driver changes phone numbers, update their driver profile so dispatch and permissions match.
See: How do I sign in or sign up for EasyRoutes Delivery Driver?
Open a stop’s Actions menu (the three-dot icon) and mark it as High or Low priority, or select several stops and set their priority in bulk. When a route has limits (like max stops, items, or duration), High Priority stops are included first and Low Priority ones are dropped first. You can also auto-apply priority through order import rules. Priority stops are a Premium and Enterprise feature, in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Priority stops