EasyRoutes doesn't include a dedicated age-verification or age-gating feature, so it won't automatically confirm a recipient's age. You can still operate alcohol, CBD, or other age-restricted delivery routes and enforce the check at the door: require an e-signature and/or photo to mark the stop delivered, and add a required Driver Task (e.g., "ID checked, recipient 21+") the driver must complete first.
Note that age-gated content isn't supported for SMS notifications. These options work in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks
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. 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
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
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
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.
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. From any route, use the checkboxes to select one or more stops, then click the bulk actions bar and choose Send to another route. You can also open a Route Group and drag stops from one route to another within the group. After moving, click Save and (optionally) Re‑optimize to update the stop order and ETAs. This workflow works the same in EasyRoutes for Shopify and EasyRoutes for Web.
Use this to balance workloads mid‑day, handle late additions, or consolidate leftovers onto a cleanup route.
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.
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. If you don’t use Shopify, EasyRoutes for Web provides the same core workflow — order intake, route planning, dispatch, tracking, proof of delivery, and analytics. Bring orders in via CSV uploads, the Routes API, or webhooks/Zapier. You can also mix non‑Shopify orders with Shopify orders if you operate via multiple e-commerce channels.
Customer tracking pages and notifications work the same, and drivers use the same EasyRoutes Delivery Driver app.
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.
When no one is available, the driver documents the drop instead of collecting a signature: up to four photos of where the order was left, an optional note (e.g., "left behind the side gate"), and the GPS location and timestamp captured automatically. All of it is saved to the stop's proof-of-delivery record.
You can make a photo and/or note mandatory to mark the stop delivered, and display these items on the customer's tracking page for confidence. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
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 — routes are single‑driver to keep tracking, ETAs, and proof‑of‑delivery accurate. If two or more drivers are needed, split the stops into multiple routes (or create a new route for leftovers) and dispatch each separately. You can also publish a route without assigning a driver, and share a self‑assign link so someone from your pool can claim it when ready.
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.
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
Yes. Workflows automate delivery tasks inside EasyRoutes, while Zapier connects EasyRoutes to external systems. Together, they create powerful end-to-end automation. For instance, a Workflow might create a route when orders arrive, while Zapier sends Slack alerts or updates a Google Sheet whenever stops on that route are completed. This layered approach ensures internal and external processes stay in sync.
See: Workflows Overview
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.
Yes. As assigned routes are dispatched from EasyRoutes, drivers get a push notification that opens the route in the app. If a driver doesn’t see alerts, confirm notification permission is enabled and the driver is added to your store with the correct phone number. Drivers can also pull‑to‑refresh their route list in the app to fetch new routes available to them.
See: How do I dispatch/share routes? · Troubleshooting push notification permissions
Yes. EasyRoutes continues to receive driver location while the app runs in the background, as long as device permissions allow background/precise access and battery optimization doesn’t suspend the app. If the user force‑quits the app, turns off location, or the OS stops background services to save power, live updates may pause. Reopening the driver app resumes tracking and ETAs will refresh accordingly.
See: Real-Time Driver Location Tracking · Troubleshooting mobile issues
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
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
Workflows are closely integrated with EasyRoutes’ existing notification and dispatch systems. This means you can set up a Workflow that not only creates a route but also automatically assigns it to a driver and triggers delivery notifications to customers at the right moments. For example, you could design a Workflow that dispatches a route to a driver as soon as it’s created, ensuring they receive a push notification in the EasyRoutes Delivery Driver app. As soon as the driver starts their route, EasyRoutes can send customers an email or SMS letting them know their delivery is on the way. This seamless integration ensures your team doesn’t need to remember to click multiple buttons — communication and route management just happen automatically.
Yes. Once imported into EasyRoutes, Wix orders benefit from the same notification system as Shopify or BigCommerce orders. Customers can receive branded notifications by email or SMS, complete with real-time tracking links, helping reduce “Where’s my order?” calls and improving delivery transparency.
Yes. Access to the EasyRoutes API and webhooks requires a Premium (or higher) subscription across both products (Shopify and Web). If you’re evaluating, you can prototype with CSV import or the driver app while you finalize your integration plan, then enable API once you upgrade.