Yes. You can operate from several depots in both EasyRoutes for Shopify and EasyRoutes for Web. For each route, define the start and end locations (a store, local warehouse, or driver’s home base). Filter orders by zone or location tags, build multiple routes, and monitor all drivers together via Route Groups. Printed documents and ETAs reflect different depot travel times automatically.
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 maintains a route history so you can review previous runs, proof of delivery, and timing information on either EasyRoutes product (Shopify and Web). Use the Routes page to filter by status (unstarted/in progress/completed/archived) and date. Open any route to view stop details and the Activity Feed particulars for that route. You can also export route/stop data for period‑end reporting or audits.
If you don’t see older orders on the Orders page, adjust the Show orders from the last window in Settings; this does not affect existing route history.
The cutoff, lead-time, and blackout-date rules you configure live inside your date picker app and control what customers can select at checkout — EasyRoutes doesn't import those rules. What it does read is the resulting delivery date and time window the app writes onto each order, which it then uses for filtering and routing. So the customer-facing scheduling limits stay with your picker, while EasyRoutes plans around the dates and windows they produce. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: How EasyRoutes works with your Shopify setup and third-party apps · Time Windows
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. 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.
Yes. You can reshape a zone after creating it — open Settings > Delivery Zones, select the zone, adjust its points on the map, then save your changes. You can also rename it or change its route colour at any time. Updated boundaries apply the next time you use that zone to select orders for a route. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
By default, CSV imports are static snapshots. For real-time updates, use Zapier to push new BigCommerce orders into EasyRoutes automatically, or build a direct integration with the API. This ensures address changes, order edits, or cancellations in BigCommerce are reflected in your delivery routes without manual intervention.
See: Zapier Integration
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
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
Yes. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
Yes. Alongside EasyRoutes-native barcodes, drivers can scan existing product or order barcodes and QR codes — including supplier UPC, EAN, Code 128, and 2D formats like QR and Data Matrix — using the phone camera. Externally generated codes are captured and stored with the stop for reference, though match validation (the green/yellow confirmation) applies to EasyRoutes-native codes. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
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. You can operate from several depots in both EasyRoutes for Shopify and EasyRoutes for Web. For each route, define the start and end locations (a store, local warehouse, or driver’s home base). Filter orders by zone or location tags, build multiple routes, and monitor all drivers together via Route Groups. Printed documents and ETAs reflect different depot travel times automatically.
Yes. EasyRoutes supports BigCommerce orders in several ways. You can export orders from BigCommerce and import them into EasyRoutes via CSV, or use Zapier and our API for real-time automation. This lets you start quickly with spreadsheet imports and grow into fully automated workflows as your delivery operation scales.
Absolutely. EasyRoutes supports mixed sources across both products (Shopify and Web). Bring in non‑Shopify orders by uploading a CSV, sending stops through the Routes API, connecting via webhooks/Zapier, or adding custom stops manually. Once imported, they appear alongside Shopify orders on the Orders page, can be filtered like any other stop, and can be optimized together on the same route.
See: Adding custom stops from outside Shopify · Routes API · Webhooks & Zapier
Yes. Enable SMS in EasyRoutes Settings → Customer notifications and include the tracking URL in templates such as Ready for Delivery, Out for Delivery, Driver is X Stops Away, Delivered, and Missed Delivery. SMS is supported in both EasyRoutes for Shopify and EasyRoutes for Web on Premium/Enterprise plans, and is billed per message segment by country. Use the preview tool to verify variables before sending.
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.
Yes. In both EasyRoutes for Shopify and EasyRoutes for Web, the Analytics page includes a date picker for presets and custom ranges. Choose the period you want to analyze, optionally select a driver, and the charts and tables update to reflect those filters. This lets you compare week‑over‑week or month‑over‑month performance and investigate changes after process updates or seasonal peaks.
You can export the filtered view to CSV to share with your team or archive for audit purposes.
See: Filtering by Date
Switching is straightforward. On Shopify, install EasyRoutes and your orders sync automatically — no data migration needed. For orders from other systems or platforms, bring them in by CSV/spreadsheet import (an AI assistant maps your columns), Zapier, or the API, then set your route options and add drivers to start routing. Most merchants are live the same day. Works with both EasyRoutes for Shopify and EasyRoutes for Web.
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.
No. Barcode scanning uses the camera on your driver’s existing iOS or Android device, so there’s no need to buy dedicated scanners or hardware. Drivers scan directly from the EasyRoutes Delivery Driver app, with a built-in flash option for low light and a manual-entry fallback if a code won’t read. It supports common linear formats (UPC, EAN, Code 128, and more) and 2D codes like QR and Data Matrix. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
Yes. Configure a start location (e.g., your store, a local warehouse, or a driver's home base) and an end location (e.g., a depot, final stop, or loop back to the route's start location) on each route. These points are included in optimization and time estimates, so drivers see realistic drive times and customers receive accurate ETAs. You can set defaults in Route Options, then override per route as needed. For multi‑warehouse operations, create routes that begin near each inventory location to reduce deadhead driving. In both EasyRoutes for Shopify and EasyRoutes for Web, you can adjust these locations after route creation and re‑optimize to update the sequence and times.
See: Start/End Locations
Yes. Set a scheduled start date and time when creating or editing a route. EasyRoutes will use that schedule — plus stop time intervals and any delivery time windows — to calculate ETAs for every stop. Customers can receive their individual ETAs via branded tracking pages and optional email/SMS notifications. If plans change, simply edit the route's schedule, re‑optimize the route, and ETAs will update automatically.
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
EasyRoutes maintains a persistent log of account activity so admins have an authoritative record of delivery events over time. The Activity Feed retains entries for the lifetime of your account unless data is explicitly deleted (e.g., via route removal or a data‑deletion request). When you need a file for records or audits, pair the feed with route/stop CSV exports that include timestamps and proof‑of‑delivery links. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: Activity Feed · Export routes/stops