Yes. EasyRoutes prints all slips for the selected route in one batch. From the route page, choose Print → enable Packing slips → print or save as PDF. Slips are ordered to match the route so packing and loading follow the driver’s sequence.
This bulk flow is available in both EasyRoutes for Shopify and EasyRoutes for Web. If you maintain custom slip templates in Shopify, you can also push orders to Order Printer Pro and print them in route order from there.
Yes. In Settings > Delivery Zones, click the dropdown arrow on the Create zone button and choose Import KML, then drag in your .KML file. Zone names from the file apply automatically, and you can rename them or set a route colour before saving. Boundaries drawn in tools like Google Earth work well; KMZ or GeoJSON files should be converted to .KML first. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Delivery Zones
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.
Customer tracking pages can display an anonymized, live driver pin so recipients can see the driver’s progress as delivery approaches. Enable the option in EasyRoutes Settings → Order tracking, and use delivery notifications (email/SMS) to send tracking links automatically. When live location is unavailable (e.g., permissions off), the page still shows status updates and ETAs based on route progress.
See: Real-Time Driver Location Tracking · Customizable Order Tracking Pages
By default, CSV imports are static snapshots. To enable real-time updates, you can set up a Zapier workflow that pushes new or updated Wix orders into EasyRoutes automatically. Alternatively, use the API to sync live changes such as address edits or cancellations, ensuring drivers always have up-to-date information.
See: Zapier Guide
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. 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
Yes. Once imported, Squarespace orders behave like any other EasyRoutes order. Customers can receive branded delivery notifications via email or SMS, including live tracking links that show where their driver is in real time. This helps reduce “Where’s my order?” calls and improves customer satisfaction.
Yes, when available. Expanding an Activity Feed entry and opening its details shows who initiated the event — a user’s email address (or Shopify user ID) or a driver’s name — along with the IP address and device details captured for that action. This makes the feed useful for tracing changes and for compliance review. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Activity Feed
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. 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. Add the instruction to a saved customer in your Address Book and it carries over to that customer's future stops; for one-off orders, add it as a stop note. Shopify local-delivery instructions are also parsed onto the stop automatically.
These notes display to the driver in the app, and a required Driver Task can prompt them to confirm the leave-at-door step. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver & Stop Notes · Address Book
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. 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. You can operate from several depots in both EasyRoutes for Shopify and EasyRoutes for Web. For each route, define the start and end locations (a store, local warehouse, or driver’s home base). Filter orders by zone or location tags, build multiple routes, and monitor all drivers together via Route Groups. Printed documents and ETAs reflect different depot travel times automatically.
Analytics reports are viewed in the dashboard and exported on demand — open any breakdown and use Export to copy the data or download a CSV. There isn’t a built-in scheduler that emails recurring reports automatically. If you need that, you can export on a cadence yourself, or use the EasyRoutes API and webhooks (with a tool like Zapier) to pull delivery data into your own reporting. Applies to both EasyRoutes for Shopify and EasyRoutes for Web.
See: Analytics
Open a stop’s Actions menu (the three-dot icon) and mark it as High or Low priority, or select several stops and set their priority in bulk. When a route has limits (like max stops, items, or duration), High Priority stops are included first and Low Priority ones are dropped first. You can also auto-apply priority through order import rules. Priority stops are a Premium and Enterprise feature, in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Priority stops
To import Squarespace orders, go to your Squarespace dashboard, navigate to “Orders,” and click the “Download CSV” button. Make sure only “Pending” orders are selected for export. Once downloaded, upload the CSV file into EasyRoutes via the “Import new CSV” option. Orders will appear as pins on the EasyRoutes map, ready for optimized route planning. This simple process makes it easy to bring Squarespace order data into your delivery workflow.
Yes. EasyRoutes allows you to build Workflows in a safe, draft environment where you can preview how they would behave without actually triggering live actions. This lets you confirm that your conditions and actions are working as expected before rolling them out to your team.
For example, you might test a Workflow that creates a route every morning at 8 AM by running it with sample orders first, so you can see how the route would look. Once you’re confident it works, you can enable it in production and have it run automatically every day. This ability to test Workflows helps prevent mistakes like dispatching routes too early or sending customers duplicate notifications. It also makes it easier to experiment with new automations before committing to them.
See: Testing Workflows
EasyRoutes turns your driver’s phone camera into a scanner — no extra hardware needed. Drivers scan a barcode or QR code from the Proof of Delivery section, or from a Scanner-input Driver Task, before completing a stop. Matching codes are confirmed in green; non-matching codes appear in yellow and can be flagged back to the route planner. Every scan is stored with the stop’s proof of delivery for live or later review. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Set a route-wide Time per stop as your baseline, then adjust the service time on any individual stop from its Edit stop page — useful when a bulk drop, an in-home setup, or a quick curbside hand-off needs a different allowance than the rest of the route.
Because each stop's time feeds ETAs and counts toward Max route duration, mixing short and long service times still produces an accurate schedule. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Editing Routes
Yes. Use EasyRoutes Order Filters to build the batch you want to route. Common filters include delivery date ranges, order/fulfillment status, tags, and geography (postal/ZIP code, city, country, or your own delivery zones). Filters apply to Shopify orders and any imported/manual stops so a single route can cover precisely the area and schedule you intend.
See: Order Filters
Yes. After your WooCommerce orders are imported into EasyRoutes (via CSV, Zapier, or API), you can use EasyRoutes’ Workflows to automate the next steps. For instance, you could create a Workflow that builds and dispatches routes every morning from all WooCommerce orders tagged as “Local Delivery.” This ensures WooCommerce data flows into the same automation engine used across EasyRoutes.
See: Workflows Overview
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.
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
The Activity Feed itself isn’t exported as a single file, but you can export route and stop data that reflect the same underlying events. From the Routes page, export a date range (or open a specific route) to download CSVs containing stop details, completion timestamps, driver info, and links to proof of delivery. Use the feed to identify the timeframe or routes you need, then export those records directly.