Yes. EasyRoutes supports pickups alongside deliveries in both EasyRoutes for Shopify and EasyRoutes for Web. Add pickup stops the same way as deliveries (Shopify orders, CSV/API imports, or manual stops). Set the pickup location (store/warehouse/customer) and, if needed, add instructions or required items to the stop notes.
Pickups appear in the route in sequence with other stops, on printed documents, and in the driver app. If only pickups are needed, create a pickup‑only route and dispatch to the driver as usual.
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.
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 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. EasyRoutes supports Xero data by letting you export invoices from Xero and import them into EasyRoutes via CSV. For automation, you can connect Xero through Zapier or build custom workflows with the EasyRoutes API. This flexibility allows businesses to start with manual exports and move toward fully automated integrations as they scale. See: Importing Orders from Xero
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
The Activity Feed provides an up‑to‑date audit trail across EasyRoutes for Shopify and EasyRoutes for Web. It records events like route creation/dispatch, stop status updates (Out for Delivery, Delivered, Attempted), driver assignments, and proof‑of‑delivery uploads. Use it to investigate issues, answer customer inquiries with precise timestamps, and validate operational changes during a delivery day.
See: Activity Feed
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 a route and click Print to generate driver‑friendly documents in stop order: a compact route summary, packing slips, or packing labels. You can adjust content and sizing in Settings → Packing Slips & Labels, then print or choose Save as PDF for tablet use or record‑keeping. This workflow is identical in EasyRoutes for Shopify and EasyRoutes for Web.
For multi‑package orders, print one label per item; for quick loading, include the Route Inventory/Packing List so teams can stage by stop.
Yes. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
Yes. For long runs or regional routes, create a schedule that spans multiple days. Set a start time/location for each day and include an overnight break so ETAs for day two (and beyond) reflect realistic service times. This works alongside capacity limits and time windows, and customer tracking will display the correct expected dates.
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.
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.
From your Orders page, open Add/edit options, find the Driver tasks card and click Enable, then Add new task and choose the Scanner input type. Give it a name (e.g. “Scan product barcode”) and, if you want it enforced, tick Delivered and/or Attempted to require a scan before the stop can be completed. Save, and drivers are prompted to scan at each stop. Driver tasks are available on Premium and Enterprise plans.
See: Driver tasks · Barcode scanning
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. From any route you can dispatch to a specific driver, or share a route link that allows self‑assignment by your driver pool. Assigned drivers receive the route in the EasyRoutes Delivery Driver app (iOS/Android) with turn‑by‑turn directions via their preferred navigation app. For busy days, combine dispatch with Route Groups to release multiple routes at once and monitor progress on a single screen. This behaviour is consistent across EasyRoutes for Shopify and EasyRoutes for Web.
See: How do I dispatch / share routes? · Route Dispatch Links / Driver Self‑Assign
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
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 Proof of Delivery settings, you can force one or more PoD elements to be collected before drivers can complete a stop. Choose the combinations that fit your workflow — e.g., require a photo for attempted stops, or require e‑signatures for only completed stops. These rules apply in EasyRoutes for Shopify and EasyRoutes for Web, and can include Attempted stops.
See: Make PoD Required
Yes. If you need to drive the same set of stops in the opposite direction (e.g., afternoon run), open the route, choose the actions menu (three dots), and click Reverse route. The stop list flips order and ETAs update based on your scheduled start time and stop service times. This tool is available in both EasyRoutes for Shopify and EasyRoutes for Web. You can still drag‑and‑drop to fine‑tune any exceptions or stops that require particular attention.
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
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. The EasyRoutes API enforces rate limits to ensure consistent performance for all users. Most workflows run comfortably within default limits when you batch requests, avoid unnecessary polling, and rely on webhooks to trigger updates rather than frequent reads. If you expect sustained high throughput (e.g., large imports or rapid status updates), our team can help you design an efficient approach and advise on limits for your use case.
No long‑term contract is required. You can start on a monthly plan, adjust driver seats as your team changes, and upgrade or downgrade tiers at any time. When you change plans mid‑cycle, EasyRoutes automatically prorates the charges so you only pay for what you use.
Yes. From Proof of Delivery settings, you can force one or more PoD elements to be collected before drivers can complete a stop. Choose the combinations that fit your workflow — e.g., require a photo for attempted stops, or require e‑signatures for only completed stops. These rules apply in EasyRoutes for Shopify and EasyRoutes for Web, and can include Attempted stops.
See: Make PoD Required
Admins need an internet connection to create, edit, and dispatch routes. The EasyRoutes Delivery Driver app supports low‑connectivity situations: if a driver opens the route while online, stop data is cached locally so they can navigate, update status, and capture proof of delivery offline. The app queues events and syncs them to EasyRoutes once the device reconnects.