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
The Activity Feed itself isn’t exported as a single file, but you can export route and stop data that reflect the same underlying events. From the Routes page, export a date range (or open a specific route) to download CSVs containing stop details, completion timestamps, driver info, and links to proof of delivery. Use the feed to identify the timeframe or routes you need, then export those records directly.
Yes. Real‑time tracking is configurable. You can enable tracking for dispatcher visibility while keeping customer pages static, or allow a live pin to appear only as the driver approaches (configurable from 1 to 10 stops away). This setting is available on Premium/Enterprise plans across both EasyRoutes for Shopify and EasyRoutes for Web.
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. Delivery Ratings allow recipients to provide quick feedback from the tracking page right after their order is delivered. You can collect a star rating and an optional comment, then export results or segment by driver to monitor individual performance and service quality. Ratings help highlight coaching opportunities and verify customer satisfaction trends over time.
See: Delivery Ratings
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
You don’t need to be a developer to connect WooCommerce with EasyRoutes. Zapier provides no-code automation tools that let you push WooCommerce orders directly into EasyRoutes with just a few clicks. For businesses that want more control, the EasyRoutes API is available to build deeper integrations, such as syncing fulfillment statuses or creating custom routing rules. This gives you both no-code and pro-code options.
EasyRoutes uses a flexible, seat‑based model. Choose a plan (Standard, Premium, Enterprise) and activate the number of driver seats you need; you’re billed only for active seats. You can adjust seats or change tiers at any time, and SMS messaging — if enabled — is charged per message segment. Both EasyRoutes for Shopify and EasyRoutes for Web use the same pricing model.
See: Pricing · Pricing & Plans FAQ
When a driver captures an e‑signature, customers see an indicator and timestamp on the tracking page confirming that the order was signed for. The signature image is stored with the stop for internal use (support, audits) and can be accessed by admins; it is not shown directly to customers to protect privacy.
See: Proof of Delivery
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.
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. In EasyRoutes for Shopify you can choose between EasyRoutes’ customizable notifications and Shopify’s built‑in notifications. When using Shopify templates, EasyRoutes maps delivery events (e.g., Out for Delivery, Delivered; Missed Delivery for Local Delivery) to Shopify’s corresponding notifications and attaches the tracking link on fulfillment. To prevent double‑sending, review Shopify’s notification settings and disable overlapping templates when EasyRoutes emails/SMS are enabled.
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.
Yes. In addition to taking photos in‑app, drivers can attach images from the phone’s gallery when you allow this option. It’s especially useful when a photo was captured by the camera app while offline; the driver adds it later, and EasyRoutes syncs the proof and timestamps once connectivity returns.
Yes. EasyRoutes is built for fast‑moving operations. Select orders, click Create route, and dispatch in a few steps. When new requests arrive, add them to an active route, re‑optimize the remaining sequence, and the driver’s app updates immediately. Customers can receive status notifications and view tracking links with dynamic ETAs. Use Route Groups to coordinate multiple drivers for peak periods.
Yes. You can translate and brand customer‑facing tracking pages and notifications so recipients see messages in their language. EasyRoutes displays order/customer fields as they are provided by your source system (e.g., Shopify), making it straightforward to serve multilingual buyers. This applies across EasyRoutes for Shopify and EasyRoutes for Web. Additionally, the EasyRoutes Delivery Driver mobile app supports automatic translations to French, Spanish, Dutch, and German on both iOS and Android devices.
See: Language options
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. Enable automatic dispatch so newly created routes with a scheduled start time are assigned and sent to the chosen driver immediately — no extra clicks. Use this for recurring daily runs or integrations that create routes programmatically. You can still edit or un-dispatch a route before start time if plans change.
When exporting orders from Wix, ensure your CSV file contains one row per order line item so EasyRoutes can map details like product name and quantity correctly. Map columns such as name, street address, and phone number to the right EasyRoutes fields during import. This ensures clean, accurate order data for route creation.
See: Wix Import Guide
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.
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. 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
Subscriptions are processed through Shopify Billing (for EasyRoutes for Shopify) or Stripe (for EasyRoutes for Web). After your 14-day trial, app charges run on a 30-day subscription cycle that is independent from Shopify’s invoice cycle. When you add or remove driver seats during a cycle, we prorate charges/credits automatically. SMS delivery notifications are usage-based and draw from a separate balance when enabled.
See: Shopify app subscriptions · Prorated plan changes · Usage-based SMS balance
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
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.