Yes. In both EasyRoutes for Shopify and EasyRoutes for Web you can keep route history tidy by archiving routes you no longer need to manage daily, or permanently delete them. Use the checkboxes to select desired routes from the Routes page, and use the actions menu to archive or delete. Archiving preserves stop records, proof of delivery (photos/signature/notes), and analytics, so you can still search and export later. Deleting removes the route from Route History — make sure to export any reports you need first.
Use filters on the Routes page to show active, completed, or archived runs when you’re reconciling a period.
See: How do I archive or delete routes from my route history?
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web can surface proof of delivery (PoD) to customers. Enable PoD display on tracking pages and decide which delivery events should send links via email/SMS. When a driver completes a stop, PoD is attached to that stop and becomes available to customers according to your settings. Admins always see PoD in route and stop details for auditing or future reference.
Yes. From the Analytics page, pick your time period (e.g., last 7/30 days or a custom range) and optionally filter by driver. Use the Export option to download a CSV for spreadsheets or external tools, or use Print to generate a PDF summary. CSV exports preserve the filters you applied so downstream reports match what you saw in EasyRoutes.
Exports are available in both EasyRoutes for Shopify and EasyRoutes for Web. If you need more granular, stop‑level records, combine Analytics with route exports from the Routes page.
Importing WooCommerce orders is straightforward. Using a plugin like WebToffee, you can export orders from your WooCommerce dashboard in CSV format. Once exported, you simply drag and drop the CSV file into EasyRoutes. The system will map fields like customer name, address, and quantity automatically, and you can confirm or adjust mappings before creating optimized delivery routes. This makes it easy to bring WooCommerce data into your delivery workflow.
Yes. The EasyRoutes Routes API accepts imported orders/stops (customer details, address, items, notes) so you can bring orders from non‑Shopify sources into EasyRoutes. After importing, you can create new routes, add the stops to existing routes, assign drivers, and dispatch. This works for both EasyRoutes for Shopify and EasyRoutes for Web and complements CSV import when you need automation.
EasyRoutes is built for dynamic operations. When an order changes or a new request arrives, open the active route, add or remove stops, and click Re‑optimize to calculate the best new sequence for the remaining stops. ETAs and the driver’s stop list update immediately in the mobile app. If needed, move stops between routes to balance workloads, then re‑optimize each route.
Customer tracking pages and notifications reflect the new schedule so recipients stay informed.
See: Adding orders or stops to routes · Re‑optimizing routes
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.
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. The Analytics dashboard summarizes delivered vs. missed (attempted) stops so you can monitor delivery success across time or by driver. Use this report to identify recurring issues (e.g., address problems or access constraints) and to validate improvements after workflow changes.
For context on individual failures, open the underlying routes or stops to review notes and proof‑of‑delivery entries. You can also export the analytics view as CSV for further analysis or sharing with stakeholders.
See: Analytics Reports
Yes. Packing slips are configurable so teams can show the fields drivers or packers need. In EasyRoutes Settings → Packing Slips & Labels you can: include a logo, select variables (customer details, order items, notes), set text sizes, and tweak headers and helper text. Print slips directly from any route.
Note: Some variables are only available when printing one slip per stop vs. one per item. Adjust your preference in the Print Preview if you need item-level detail.
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. 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.
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. 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. From EasyRoutes Settings → Driver settings, enable the options to let drivers reorder stops and re‑optimize the remaining sequence when plans change (traffic, customer requests). Re‑optimization recalculates the fastest order for what’s left, while respecting your route constraints (time windows, priorities). Admins can still edit routes from the web at any time.
See: How do I re‑optimize remaining stops? · Re‑ordering stops
Go to Settings > Delivery Zones and click Create zone above the map. Use the polygon tool to click points on the map and trace your area, then click back on your first point to close the shape. Give the zone a title and pick a route colour, then save. Once created, enable the Delivery zones Route Option to limit a route to orders inside that zone. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
Yes. EasyRoutes for Shopify and EasyRoutes for Web work in many countries around the world. Address geocoding, map tiles, and driving directions are available globally, and core features — route optimization, driver app, tracking links, and proof of delivery — operate the same. In certain regions, map data or SMS availability may differ based on local providers.
Before rollout, confirm your country is supported and run a quick pilot to validate address formats (postal codes, provinces) and notification deliverability.
Admins can monitor each active route from the Tracking tab: view a live GPS pin, the recent breadcrumb path, and which stop the driver is headed to now. Stop tiles update in real time with status changes and completion times, and proof of delivery (photos, signature, notes) appears as soon as it’s captured. You can also open a Route Group to watch multiple routes/drivers concurrently.
See: Real-Time Driver Location Tracking · EasyRoutes Activity Feed
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
The EasyRoutes API lets you automate your delivery workflow end‑to‑end: import orders/stops from external systems, create routes with your preferred options, assign drivers or vehicles, dispatch routes, and update stop or route status as deliveries progress. You can also read back route/stops for reporting and pair the API with webhooks to keep other systems synchronized in real time. Capabilities are consistent across EasyRoutes for Shopify and EasyRoutes for Web.
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
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 continues to receive driver location while the app runs in the background, as long as device permissions allow background/precise access and battery optimization doesn’t suspend the app. If the user force‑quits the app, turns off location, or the OS stops background services to save power, live updates may pause. Reopening the driver app resumes tracking and ETAs will refresh accordingly.
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
Analytics reflects new data shortly after drivers complete or update stops in the EasyRoutes Delivery Driver app. Because updates depend on device connectivity and permissions, you may see a brief delay if a driver is offline; once the device reconnects, metrics catch up automatically. For the most granular timeline, open the route and review the Activity Feed, which lists each delivery event as it occurred.
This live‑update behaviour applies to both EasyRoutes for Shopify and EasyRoutes for Web. If numbers look stale, refresh the page or adjust your date/driver filters and try again.
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 supports Shopify Subscription orders, so recurring deliveries can be filtered and routed with your daily batch. Many subscription and checkout tools are supported out of the box; you can also combine with imported/manual stops for non‑Shopify channels. Tracking, notifications, and proof of delivery function the same as for one‑time orders.
See: How does EasyRoutes work with subscriptions? · Supported third‑party apps