Zapier makes it easy to send internal notifications whenever a stop status changes in EasyRoutes. For example, you can set up a Zap that listens for the STOP_STATUS_UPDATED webhook and then sends a Slack alert or email to your team with details like the order number and driver notes. This keeps staff informed in real time without needing to manually monitor dashboards.
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. With Premium or Enterprise plans, turn on live tracking from EasyRoutes Settings → Driver settings. You’ll see a live GPS pin, breadcrumb path, current/next stop, and real‑time status updates on each route’s Tracking tab. Ensure drivers grant Always/Precise location permissions in the Delivery Driver app. Route Groups let you monitor multiple drivers at once.
Drivers can capture multiple photos, obtain a customer e‑signature, and add notes at the stop. These items are stored with timestamps and the completion context, and they’re visible to admins on the route and stop record. When enabled in EasyRoutes Settings, customers can see PoD on tracking pages and in notifications.
See: Proof of Delivery
SMS delivery notifications use usage-based pricing by recipient country and message length. Costs are per segment (e.g., a U.S. segment is $0.043 USD). Longer messages or those with emojis/Unicode may use multiple segments. You fund a prepaid SMS balance and can enable auto-top-ups so notifications continue without interruption.
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 Delivery Driver supports low‑connectivity scenarios. Have drivers open or refresh the route while connected to preload stops and attachments. If signal drops, they can continue navigating (via their chosen maps app), mark stops delivered/attempted, and capture photos/signatures. The app queues events locally and syncs them back to EasyRoutes as soon as the device reconnects, updating ETAs and tracking automatically.
See: Can I use EasyRoutes Delivery Driver without a connection?
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. Both EasyRoutes for Shopify and EasyRoutes for Web let you re‑optimize a route whenever plans change. Use this feature after you add or remove stops, change stop priorities, edit time windows or service times, or adjust limits like max route duration and stop limits. You can also balance stops across multiple routes first, then re‑optimize each route to tighten the sequence. If permitted in your Driver Settings, drivers may manually re‑order stops from the driver app or re‑optimize the remaining stops in their route to recalculate ETAs after mid‑route changes. For API‑driven workflows, use the Routes API to programmatically update routes and trigger re‑optimization.
See: How do I re‑optimize a route? · How do I allow drivers to re‑order stops?
Yes. When location capture is enabled, EasyRoutes records the driver’s GPS location and a timestamp alongside each proof-of-delivery entry — photos, e-signature, notes, and barcode scans — so every completed stop has a location and time on record. You can review these details on the route’s stop entries and include driver location when exporting stop data for your files. Available in 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. Once imported into EasyRoutes, BigCommerce orders behave the same as other orders. Customers receive branded notifications by email or SMS, including links to real-time tracking pages. This reduces support calls and gives customers confidence in their deliveries.
Yes. From the Routes page or an individual route view, export to CSV for all relevant route data points. Exports include stop details, timestamps, driver assignments, and URLs to related proof of delivery (photos/signature/notes). Use these files for accounting, customer service follow‑up, or analysis in spreadsheets or external tools. Exports are supported in both EasyRoutes for Shopify and EasyRoutes for Web.
On your EasyRoutes Orders page, click Configure table columns (below your active Route Options) and enable the Delivery Date and Time Window columns. Once enabled, EasyRoutes parses these values from your date picker app so you can sort, filter, and build routes by delivery date and window. The same columns are available in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Manual and imported stops can send the same email/SMS notifications as Shopify orders once configured. In EasyRoutes Settings → Customer notifications, enable templates under the Imported Orders sections and ensure each stop includes an email address and or phone number. Use tracking links to provide status and proof of delivery even when the source isn’t Shopify.
To sign in, add the driver to your EasyRoutes account (Shopify or Web) with their phone number. The driver installs the app and enters that number; we send a one‑time SMS code to complete sign‑in. Routes assigned to that number appear automatically. If a driver changes phone numbers, update their driver profile so dispatch and permissions match.
See: How do I sign in or sign up for EasyRoutes Delivery Driver?
Yes. Once your Wix orders are inside EasyRoutes, you can use them in Workflows to automate common delivery tasks. For example, you could create a Workflow that builds a new delivery route every afternoon using all Wix orders tagged as “Local Delivery” and automatically dispatches them to drivers. This helps you scale delivery operations with minimal manual effort.
See: EasyRoutes Workflows
Yes for signature: in Driver settings you can require an e-signature (and/or photo) before a stop can be marked delivered, and customize the signature disclosure text shown to the recipient. For the ID portion, add a required Driver Task — a checkbox or text field confirming the ID check — so the driver can't complete a restricted stop without it.
Together these enforce a consistent, documented hand-off, though the age/ID check itself is performed by the driver rather than verified automatically. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks
Yes. From EasyRoutes Settings → Driver settings, define what drivers can access on mobile. Options include letting drivers manually re‑order stops, re‑optimize the remaining sequence mid‑route, and whether to show sensitive customer data (e.g., email, phone, notes). These controls apply to both EasyRoutes for Shopify and EasyRoutes for Web so you can tailor the experience to your policies.
See: Configure what is shown to the driver · Driver‑side re‑optimize
Workflows in EasyRoutes are powerful automation tools that let you design and run delivery management processes without needing to handle every step manually. Think of them as “if-this-then-that” rules that connect your orders, routes, and driver dispatching into a seamless flow. Instead of relying on a dispatcher to constantly create routes, select orders, or assign drivers, Workflows can do these repetitive tasks for you automatically.
For example, you could create a Workflow that listens for new Shopify orders tagged as “Local Delivery” and automatically builds a route every morning at 9 AM, adds matching orders to the route, optimizes route stops, and assigns it to a specific driver. By reducing manual intervention, Workflows make your operations more consistent, scalable, and error-proof.
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
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
Yes. You can direct the route optimizer to avoid tolls and or u‑turns for both EasyRoutes for Shopify and EasyRoutes for Web. These preferences guide the routing engine to favour compliant roads and turns, which may increase distance or time if alternatives cover a greater distance. Set these options globally from the Route Options panel, or add them to an existing route and re‑optimize to apply. Combine with other constraints (such as time windows, max route duration, or vehicle capacity) to keep routes realistic for drivers and accurate for customer ETAs.
See: Route Options
Setup is quick: install EasyRoutes (Shopify) or sign in (Web), connect drivers, select orders with filters, and click Create route. Use the defaults for service times and route options, then print or dispatch to the driver app. Most trial users reach a working route within an hour, often faster with our step‑by‑step guide.
If you import orders from outside Shopify, start with a small CSV or a few manual stops to validate the flow before scaling.
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web support webhooks that notify your apps when key delivery events occur—such as routes created/dispatched/updated and stops started/completed/attempted. Use them to sync delivery status into ERPs/CRMs, trigger customer communications, or update internal dashboards in real time. You can consume webhooks directly at your API endpoint or use Zapier to route events into thousands of tools (Sheets, Slack, email, etc.). Webhooks require a Premium (or higher) plan.
EasyRoutes-native barcodes are QR codes generated by EasyRoutes and printed on your packing slips and labels; each is tied to a specific stop, so a scan can be validated as a match. Existing product or order barcodes (like a supplier’s UPC) aren’t tied to a stop that way — drivers can still scan and record them as proof, but match validation is strongest with EasyRoutes-native codes. Both work in EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning