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. You can integrate EasyRoutes with ERPs, CRMs, WMS, and custom apps using our API and webhooks. Typical use cases include importing stops from non‑Shopify channels, syncing delivery status and proof‑of‑delivery back to your system of record, and powering external analytics collection. The same platform supports both EasyRoutes for Shopify and EasyRoutes for Web.
No. Both products dispatch routes to the same EasyRoutes Delivery Driver app on iOS and Android. Drivers get identical navigation choices (Google/Apple/Waze), proof-of-delivery tools, barcode/driver tasks, and optional features like re-optimizing remaining stops or scheduled breaks — controlled by your admin settings. Any differences are admin-side only (e.g., Shopify-specific fields shown/hidden).
See: Delivery Driver app · Barcode scanning · Location tracking
Yes. Time windows are supported in both EasyRoutes for Shopify and EasyRoutes for Web. Add a window directly to a stop, or pull windows from checkout tools/date pickers (e.g., Zapiet, Buunto, and other supported third‑party apps). This way, our route optimizer sequences stops to respect open/close times while considering start/end locations, stop times, and other limits. If windows create conflicts that exceed constraints (e.g., max duration), split stops into additional routes or relax limits, then re‑optimize. ETAs displayed to drivers and customers reflect these windows so deliveries align with customer preferences as closely as possible.
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. 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 Workflows support a wide variety of actions that cover the full delivery process, from order intake to customer communication. You can automatically generate new routes based on incoming orders, apply filters (such as only including orders tagged with “Priority” or due on a specific date), and dispatch routes directly to the correct driver. This level of automation means you can build a Workflow that matches your exact delivery process, no matter how simple or complex.
See: Workflow Actions
From any route or the Orders page, click the + Add button under the map and choose Custom stop, then fill in the stop details with a valid address — EasyRoutes auto-fills matches from your Address Book as you type. Tick “Save to address book” to reuse a frequent stop later, and re-optimize if you’d like it slotted into the best position. It’s the same flow whether you’re on EasyRoutes for Shopify or EasyRoutes for Web.
See: Add a custom stop · Address Book
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
EasyRoutes helps protect perishable and temperature-sensitive goods by keeping product moving and time on the road to a minimum. Cap each route with Max route duration and Max stops per route so no run exceeds your safe window, assign delivery time windows to fragile stops, and let optimization sequence and split orders across drivers for faster dispatch. This works the same in EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Time Windows
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.
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. 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.
No, you don’t need to be a developer to take advantage of Workflows. The Workflows feature is designed to be accessible to non-technical users by using a visual, menu-based interface. You simply select a scheduling frequency, define any conditions (like “only include orders tagged Local Delivery”), and choose an action (for example, “create and dispatch a route”).
This no-code design makes Workflows similar to popular automation tools like Zapier or Shopify Flow, where anyone can build powerful automations just by clicking and selecting from available options. That said, more advanced users can extend Workflows with APIs or webhooks to create complex, custom integrations, giving both beginners and power users maximum flexibility.
See: No-Code Automation
Customer tracking pages can display an anonymized, live driver pin so recipients can see the driver’s progress as delivery approaches. Enable the option in EasyRoutes Settings → Order tracking, and use delivery notifications (email/SMS) to send tracking links automatically. When live location is unavailable (e.g., permissions off), the page still shows status updates and ETAs based on route progress.
See: Real-Time Driver Location Tracking · Customizable Order Tracking Pages
Yes. 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?
Yes. Use the Delivery Zones tool to outline one or more areas on the map, then filter/select orders within those zones to build your route quickly. Zones help planners batch by neighbourhood or service area and pair well with other filters like tags or dates. Once configured, zones are stored permanently to standardize your daily workflow when planning for the same areas.
Yes. When optimizing, set per‑route limits (max items/weight) so loads fit the assigned vehicle. You can also create Vehicle Profiles for an additional indicator for routes that have specific restrictions by vehicle, and enable route constraints (e.g., avoid tolls or U‑turns), and reuse them across routes. These settings help prevent overloads and keep route planning aligned with your real fleet.
See: Creating routes by vehicle capacity · Vehicle Profiles · Max items per route
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. If you use Shopify’s native notifications, you can insert proof image URLs into the Delivered or Missed Delivery templates so customers see photo links in those emails. This is optional — EasyRoutes notifications can also include tracking links that show PoD on the hosted tracking page. Choose the path that best matches your communication setup.
See: Integrating PoD with Shopify Emails · Delivery Notifications
Zapier allows you to capture delivery events from EasyRoutes and log them automatically into a Google Sheet, Excel file, or database. For example, every time a driver completes a stop, Zapier can write details like stop ID, timestamp, and delivery outcome into a row. This creates a live delivery log that’s perfect for reporting, auditing, or customer service.
During import, make sure CSV columns from Xero are mapped correctly: ContactName (first name), SAAddressLine1 (address), SARegion (province/state), SAPostalCode (postal code), SACountry (country), InvoiceNumber (order name), Quantity, and Description (item details). Proper mapping ensures invoices are imported as accurate delivery stops.
See: Xero Import Guide
Yes. Use the driver filter on the Analytics page to view metrics for a single driver or compare across drivers by switching the filter. This helps you evaluate utilization, completion rates, average stop times, and trends over time. It’s supported in both EasyRoutes for Shopify and EasyRoutes for Web and respects any date range you’ve selected.
If a driver worked on multiple routes per day, those results roll up in the selected period. For route‑by‑route detail, open the route list and drill into specific days.
See: Filtering by Driver
Analytics reports are viewed in the dashboard and exported on demand — open any breakdown and use Export to copy the data or download a CSV. There isn’t a built-in scheduler that emails recurring reports automatically. If you need that, you can export on a cadence yourself, or use the EasyRoutes API and webhooks (with a tool like Zapier) to pull delivery data into your own reporting. Applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: Analytics
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.
Yes. For contactless or leave-at-door drops, a driver can complete a stop without a signature by photographing where the order was left, capturing the GPS delivery location, and adding a note. Up to four photos, an automatic timestamp, and the location are stored with the stop as proof.
You can require specific proof — for example a photo — before a stop can be marked delivered, and show it on the customer's tracking page. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery