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
EasyRoutes integrates with Shopify fulfillments so your order system stays in sync. Marking stops Ready for Delivery, Out for Delivery, Delivered, or Attempted updates the Shopify fulfillment accordingly and adds the EasyRoutes tracking number/URL. Depending on your configuration, Shopify or EasyRoutes sends the customer emails/SMS. Partial items and multi‑item orders are supported; admins can review fulfillment history on the Shopify order and in EasyRoutes route/stop details.
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 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.
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. Packing slips are configurable so teams can show the fields drivers or packers need. In EasyRoutes Settings → Packing Slips & Labels you can: include a logo, select variables (customer details, order items, notes), set text sizes, and tweak headers and helper text. Print slips directly from any route.
Note: Some variables are only available when printing one slip per stop vs. one per item. Adjust your preference in the Print Preview if you need item-level detail.
Yes. Configure a start location (e.g., your store, a local warehouse, or a driver's home base) and an end location (e.g., a depot, final stop, or loop back to the route's start location) on each route. These points are included in optimization and time estimates, so drivers see realistic drive times and customers receive accurate ETAs. You can set defaults in Route Options, then override per route as needed. For multi‑warehouse operations, create routes that begin near each inventory location to reduce deadhead driving. In both EasyRoutes for Shopify and EasyRoutes for Web, you can adjust these locations after route creation and re‑optimize to update the sequence and times.
See: Start/End Locations
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.
By integrating BigCommerce with EasyRoutes, you get a complete delivery management solution: multi-stop route optimization, real-time driver tracking, branded customer notifications, proof of delivery (photos, notes, signatures), and analytics. This turns BigCommerce from a storefront into a powerful logistics tool, helping you scale local delivery with confidence.
See: BigCommerce Overview
Zapier expands EasyRoutes by letting you connect with thousands of popular apps like Google Sheets, Slack, Gmail, and CRMs. You can set up automated workflows such as importing new orders into EasyRoutes, sending delivery updates to your team via Slack, or logging route data into spreadsheets for reporting. This no-code integration makes it easy to streamline operations without custom development.
Yes. In both EasyRoutes for Shopify and EasyRoutes for Web you can keep route history tidy by archiving routes you no longer need to manage daily, or permanently delete them. Use the checkboxes to select desired routes from the Routes page, and use the actions menu to archive or delete. Archiving preserves stop records, proof of delivery (photos/signature/notes), and analytics, so you can still search and export later. Deleting removes the route from Route History — make sure to export any reports you need first.
Use filters on the Routes page to show active, completed, or archived runs when you’re reconciling a period.
See: How do I archive or delete routes from my route history?
Workflows are available on EasyRoutes Premium and Enterprise plans. These plans are designed for businesses that need more advanced tools to handle larger delivery volumes and complex processes. On Premium and Enterprise, you not only get access to Workflows, but also other advanced features like custom notifications, vehicle profiles, real-time driver tracking, and delivery analytics.
If you’re running a small business with only a few deliveries per week, you may be fine with a Standard plan. But if your business is scaling or you want to automate as much as possible, upgrading to Premium ensures you can take advantage of Workflows. This investment pays off quickly by saving your team time, reducing manual work, and improving consistency across your delivery operations.
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
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. From any route you can dispatch to a specific driver, or share a route link that allows self‑assignment by your driver pool. Assigned drivers receive the route in the EasyRoutes Delivery Driver app (iOS/Android) with turn‑by‑turn directions via their preferred navigation app. For busy days, combine dispatch with Route Groups to release multiple routes at once and monitor progress on a single screen. This behaviour is consistent across EasyRoutes for Shopify and EasyRoutes for Web.
See: How do I dispatch / share routes? · Route Dispatch Links / Driver Self‑Assign
Yes. The EasyRoutes Delivery Driver app runs on both phones and tablets — it’s available for iOS (including iPad) and Android devices. The interface is optimized for a phone in the vehicle, but it works on larger tablet screens too. Just install it from the App Store or Google Play and sign in with the driver’s phone number. The same app serves drivers on both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. From the Routes page or an individual route, export CSV files containing stop information (customer name, address, contact fields), timing, driver assignments, and URLs to any proof of delivery items. Use these exports for customer service, accounting reconciliation, or analysis in spreadsheets and external tools.
EasyRoutes doesn't have a setting that hard-locks a stop to one named person, but you can require and document the hand-off. Add a required Driver Task — a text field for the recipient's name, or a checkbox confirming "handed to named recipient" — that must be completed to mark the stop delivered, and note the required recipient in a stop note so the driver knows who to look for.
Pair it with a required e-signature so the signer is captured too. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Proof of Delivery
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. 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.
Yes. When you create multiple routes together, EasyRoutes groups them so you can monitor all active drivers in a single view. The Route Group page shows color‑coded pins, per‑route progress, and live stop updates. Use this view to coordinate dispatch, answer customer inquiries, and rebalance work if needed by moving stops between routes.
Yes. Your customer tracking page carries your branding — add your logo and adjust the look from EasyRoutes Settings > Order Tracking, and choose which order details and delivery information customers see. Paired with your notification settings, customers get a consistent, branded experience with live ETAs and driver location. This is separate from your email/SMS template customization. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Order tracking pages
Yes. Integrate EasyRoutes with your existing stack in two ways: (1) programmatically via the Routes API to import stops, create/dispatch routes, and update status; and (2) event‑driven with webhooks and Zapier to push delivery events into Sheets, Slack, email, ERPs/CRMs, or custom endpoints. These options are available for both EasyRoutes for Shopify and EasyRoutes for Web.
See: API Getting Started Guide · Integrate webhooks with Zapier
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.
Switching is straightforward. On Shopify, install EasyRoutes and your orders sync automatically — no data migration needed. For orders from other systems or platforms, bring them in by CSV/spreadsheet import (an AI assistant maps your columns), Zapier, or the API, then set your route options and add drivers to start routing. Most merchants are live the same day. Works with both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Use Delivery Analytics to review outcomes by driver — completed vs. missed stops, average delivery time, and overall success rate — over a selected period. Filter to focus on a single driver or compare across the team. For detailed investigations, open routes to see timestamps and proof of delivery, or export results for use in external tools.
See: Delivery Analytics