Yes. If a driver’s phone was offline or a photo needs to be re‑added, open the stop in EasyRoutes and upload PoD from your browser. The new items join the stop’s timeline with timestamps and appear in exports and tracking (subject to your visibility settings). This works across both EasyRoutes for Shopify and EasyRoutes for Web.
See: Manually upload PoD
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?
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
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. Upload a CSV to create stops with customer, address, and item details — even if the orders weren’t placed in Shopify. The importer supports line‑item fields such as quantity and weight so you can use vehicle capacity limits accurately. Once imported, these stops can be filtered, optimized into routes, and dispatched to drivers like any other order source.
Yes. EasyRoutes integrates with Wix through multiple methods: you can export orders from Wix to a CSV and import them into EasyRoutes, or use Zapier and our API for automated, real-time workflows. This flexibility means businesses can start quickly with spreadsheet imports and later upgrade to automated integrations as they scale.
See: EasyRoutes for Wix
EasyRoutes Workflows support a wide variety of actions that cover the full delivery process, from order intake to customer communication. You can automatically generate new routes based on incoming orders, apply filters (such as only including orders tagged with “Priority” or due on a specific date), and dispatch routes directly to the correct driver. This level of automation means you can build a Workflow that matches your exact delivery process, no matter how simple or complex.
See: Workflow Actions
Importing WooCommerce orders is straightforward. Using a plugin like WebToffee, you can export orders from your WooCommerce dashboard in CSV format. Once exported, you simply drag and drop the CSV file into EasyRoutes. The system will map fields like customer name, address, and quantity automatically, and you can confirm or adjust mappings before creating optimized delivery routes. This makes it easy to bring WooCommerce data into your delivery workflow.
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
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. 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?
CSV imports are manual, but Zapier and the EasyRoutes API let you automate the process. With Zapier, new Xero invoices can be sent directly to EasyRoutes as soon as they’re created. With the API, developers can build real-time integrations that sync orders and updates automatically, keeping your delivery pipeline fully up to date.
Yes. If a driver’s phone was offline or a photo needs to be re‑added, open the stop in EasyRoutes and upload PoD from your browser. The new items join the stop’s timeline with timestamps and appear in exports and tracking (subject to your visibility settings). This works across both EasyRoutes for Shopify and EasyRoutes for Web.
See: Manually upload PoD
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
From your Xero dashboard, go to the Business tab → Invoices, then use the Export button to download a CSV of the invoices you want to deliver. In EasyRoutes, click “Import new CSV” and upload the file. The system maps fields such as contact name, address, invoice number, and product details to create delivery-ready routes.
See: Xero Import Guide
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. If a Shopify order arrives without a valid shipping address, EasyRoutes highlights it so you can fix the address before planning. Edit the order in Shopify (preferred for data accuracy) or add the correct address details to the stop in EasyRoutes, then refresh and route. For pickup orders, set the address to your store or pickup point so drivers and staff can see the correct location on the route map and in documents. Address completeness ensures accurate ETAs, navigation, and proof‑of‑delivery records.
See: My order does not have a shipping address—how do I add one?
Yes. EasyRoutes supports Shopify Subscription orders, so recurring deliveries can be filtered and routed with your daily batch. Many subscription and checkout tools are supported out of the box; you can also combine with imported/manual stops for non‑Shopify channels. Tracking, notifications, and proof of delivery function the same as for one‑time orders.
See: How does EasyRoutes work with subscriptions? · Supported third‑party apps
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.
Yes. There's no separate "white-glove" mode, but the pieces are built in. Use Driver Tasks to give drivers an in-home checklist (unpack, assemble, position, remove packaging) and require it before the stop is marked complete, and allow extra Time per stop or a longer per-stop service time so the schedule reflects the added work.
Drivers capture photos of the finished setup and a signature as proof. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Route Options
EasyRoutes tracks distance and drive time for your routes, shown in metric or imperial units, and surfaces route metrics in Analytics. To gauge fuel and cost, set up Vehicle Profiles (which store each vehicle’s fuel economy) and assign them to routes, then break Analytics down by vehicle to compare efficiency. There isn’t a single built-in dollar “savings” figure, but comparing periods lets you see the trend. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
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.
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
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. 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. EasyRoutes supports Xero data by letting you export invoices from Xero and import them into EasyRoutes via CSV. For automation, you can connect Xero through Zapier or build custom workflows with the EasyRoutes API. This flexibility allows businesses to start with manual exports and move toward fully automated integrations as they scale.