Yes. Use Delivery Analytics to review outcomes by driver — completed vs. missed stops, average delivery time, and overall success rate — over a selected period. Filter to focus on a single driver or compare across the team. For detailed investigations, open routes to see timestamps and proof of delivery, or export results for use in external tools.
See: Delivery Analytics
No. The Activity Feed is an internal operations log available to EasyRoutes admins and dispatchers. Drivers use the EasyRoutes Delivery Driver app to view assigned routes, update stop statuses, and capture proof of delivery; these events will appear in the Activity Feed for admins, but drivers do not access the account‑wide feed. This separation keeps internal data and audit trails restricted to management.
See: Activity Feed
Yes. In EasyRoutes Settings → Customer notifications, enable the Rescheduled template and customize the message and variables (date, window, tracking link, etc.). Trigger it when routes or stops move to a new day/time so recipients are informed proactively. This works for both Shopify orders and imported/manual stops across EasyRoutes for Shopify and EasyRoutes for Web.
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.
EasyRoutes for Shopify is seamlessly integrated into merchants’ Shopify Admin, and can be accessed directly from the navigation menu or search bar after logging into Shopify. Permissions to create, edit, and dispatch delivery routes are limited to the same individuals who have a Shopify user account with full login access to a store’s Shopify Admin.
EasyRoutes for Web uses a standalone web browser-based login, with no Shopify account required to sign up, import your orders, and access route planning tools. With EasyRoutes for Web, route planning administrators can invite additional users to their organization’s account who can then access select EasyRoutes functionality.
See: Getting started · Add collaborators
Yes. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
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.
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. 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
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.
Importing Wix orders is easy. From your Wix dashboard, export orders as a CSV file, then log into EasyRoutes and upload the file via the “Import new CSV” option. EasyRoutes automatically maps order fields like name, address, and quantity to ensure your orders are routed correctly. Once imported, your orders appear as pins on the EasyRoutes map for route planning. See: Importing Orders from Wix
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.
Yes. When you collect an e-signature, the driver can record who signed — the "Signed for" name is stored with the stop and appears in exports. For an explicit record, add a Driver Task text field for the recipient's name, and the driver can add a note or photo as well.
All of it is saved to the stop's proof-of-delivery timeline and can be shown on the customer's tracking page. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks
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.
Yes. Programmatically modify routes and stops using the Routes API — update stop status (delivered/attempted), change assignments, dispatch routes to drivers, or edit route options, then re‑optimize as needed. When your store uses EasyRoutes notifications, status changes made through the API follow the same rules and can send customer updates and refresh ETAs. This applies to 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. When creating multiple routes as a group, use the Balance routes feature to spread stops evenly across drivers and routes. Balancing respects your other settings — such as max route duration, max stops/items, custom start/end locations, and time windows — so each route remains feasible. You can also choose to create and auto‑assign routes to selected drivers, then re‑optimize each route to fine‑tune their sequence and ETAs. This feature is available in both EasyRoutes for Shopify and EasyRoutes for Web and is especially helpful for daily batch planning.
See: Balance routes · How many routes?
Yes. The Activity Feed is designed to provide a verifiable sequence of events — who did what, and when — covering route creation, dispatch, status changes, driver assignments, and proof‑of‑delivery uploads. For external reviews or compliance checks, export related routes/stops to CSV to provide structured records and links to PoD. Together, these sources form a complete audit trail.
You don’t need to be technical to connect Squarespace with EasyRoutes. Using Zapier, you can build “if-this-then-that” workflows to automatically send Squarespace orders to EasyRoutes for route planning. For businesses that want more advanced automation, the EasyRoutes API lets developers build custom integrations and connect with other business systems. This gives you both a no-code and pro-code path to integration.
See: API Getting Started
Yes. You can constrain every route so product isn't in transit too long. Set Max route duration to cap total hours, use Max stops per route or Max items per route to limit load size, and optimization will automatically create additional routes rather than overrun your limit. Add time windows for the most sensitive stops so they're served first. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
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. 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. 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.
While CSV imports are manual, you can automate order import with Zapier or the EasyRoutes API. For example, you can use a Zap to trigger whenever a new WooCommerce order is placed, automatically sending it to EasyRoutes for routing. With the API, developers can build custom real-time integrations for order imports and updates. This ensures your delivery operations stay in sync without requiring manual exports.
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.
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.