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.
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. EasyRoutes supports multiple label sizes. Pick a base size and text scale in EasyRoutes Settings → Packing Slips & Labels, then confirm your printer uses the matching paper (e.g., 4×6) with an appropriate print scale.
Yes. If a driver is seasonal or temporarily inactive, they can be temporarily deactivated until required again. The driver’s profile, history, and assignments remain in your account, but they cannot receive routes or sign in until re‑activated. This helps control costs without losing configuration.
Manage seats from the Drivers & Vehicles tab of the EasyRoutes navigation menu. Works in EasyRoutes for Shopify and EasyRoutes for Web.
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. Use EasyRoutes webhooks as Zap triggers to connect delivery events to apps like Google Sheets, Slack, Gmail, Twilio, HubSpot, and more. Common automations include updating a shared delivery log, notifying customer service when an attempt fails, or sending a custom message when proof of delivery posts. Zapier is supported for both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. On Premium/Enterprise plans, you can send SMS notifications for key delivery events (e.g., Ready for Delivery, Out for Delivery, Driver is X stops away, Delivered, Missed Delivery, and optionally Scheduled/Rescheduled). Messages are billed per segment based on the recipient’s country. Customize content and variables in the template editor, and preview with example data before enabling. Pair SMS with email and customer tracking links for full visibility.
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
Use order tags or a stop note to identify refrigerated orders, or attach a required Driver Task (such as a "Refrigerated — keep insulated" checkbox) so the requirement travels with the stop and must be acknowledged. Order automation rules can apply notes or tasks automatically as orders import.
Combine this with routing limits so cold items spend less time in transit. Applies to both EasyRoutes for Shopify and EasyRoutes for Web.
Drivers can install the EasyRoutes Delivery Driver app from the App Store (iOS) or Google Play Store (Android) using the official links provided in our Help Center. The app works with both EasyRoutes for Shopify and EasyRoutes for Web accounts; once added as a driver, sign in using the phone number on file and the SMS code sent to that device. After dispatch, routes appear automatically in the app and can also be opened from the push notification's shared route link.
See: Where can I download the EasyRoutes Delivery Driver app?
Invite drivers from the Drivers & Vehicles tab, then assign a driver seat to activate them. Deactivate drivers anytime to free a seat without deleting their profile or history. You can switch which people occupy seats as staffing changes — ideal for seasonal or on-call drivers. These controls are available in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. EasyRoutes processes order and customer information to plan routes, power tracking/notifications, and provide proof‑of‑delivery records. We protect this data with modern security practices and retain it according to your account activity and legal requirements. We do not sell personal information; limited sharing may occur with subprocessors strictly to operate EasyRoutes, as described in our privacy policy.
For data removal requests, contact support and we’ll guide you through available options.
See: Privacy Policy
Customizable delivery status notifications (both email and SMS), order tracking pages including delivery ETAs, real-time driver location tracking, and Proof of Delivery (photos, eSignature, driver note, delivery GPS location) are all broadly supported on both EasyRoutes for Shopify and EasyRoutes for Web.
Customers receiving deliveries via either platform will benefit from the same user experience, tailored to meet your brand’s standards.
See: Tracking pages · Delivery notifications · Proof of Delivery
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. 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. Barcode scans are stored alongside the stop’s other proof of delivery — photos, e-signature, and notes — and can be reviewed live on the Route page or after the route is complete. When you export stop data, you can include Scanned barcodes and Scanned barcode issues columns for your records. This applies in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Start with these checks:
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
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.
EasyRoutes doesn't currently offer a customer-facing "pick a new date" self-service tool. In practice, customers reply to your delivery notifications or use the contact details on their branded tracking page to reach you; you then move the order with Send to another route and send the Rescheduled notification with the new details.
Delivery Ratings and tracking pages keep the customer in the loop throughout. This flow is the same in EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Enable automatic dispatch so newly created routes with a scheduled start time are assigned and sent to the chosen driver immediately — no extra clicks. Use this for recurring daily runs or integrations that create routes programmatically. You can still edit or un-dispatch a route before start time if plans change.
When you plan a route with the Delivery zones option enabled, only orders that fall inside the selected zone’s boundary are added. Any orders outside the boundary are held back for review rather than dropped, so nothing gets lost — you can route them separately, assign them to another zone, or handle them manually. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
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
By default, CSV imports are static snapshots. To achieve real-time updates, you can set up Zapier workflows or use the EasyRoutes API. For example, if an order’s address changes in WooCommerce, Zapier or a custom API connection can automatically push that update into EasyRoutes, ensuring drivers always have the latest information.
See: Zapier Guide
Yes. You can try any plan — including Premium features like real‑time driver tracking and notifications — for 14 days at no cost. Trials are available on both products (Shopify and Web). During the trial you can invite drivers, dispatch routes, and send tracking/PoD to validate the full workflow before choosing a tier and seat count.
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. 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?