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. Workflows are available across both EasyRoutes platforms, but their triggers and available actions are tailored to fit the data each platform provides. On Shopify, Workflows integrate tightly with orders, fulfillments, and Shopify-specific tags or delivery methods. On EasyRoutes for Web, you can use Workflows to automate processes based on imported orders (CSV uploads or API connections) and route activity.
This flexibility means that whether you’re using Shopify to manage your e-commerce orders or relying on EasyRoutes for Web to handle deliveries from another system, you can still benefit from automation. Businesses that operate across multiple platforms can use Workflows to keep all of their delivery processes running consistently.
See: Workflows Setup
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. After importing Squarespace orders into EasyRoutes (via CSV, Zapier, or API), they can be used with Workflows. For example, you could set up a Workflow that automatically generates delivery routes at a set time each day from all Squarespace orders and dispatches them to drivers. This helps Squarespace merchants automate repetitive tasks and maintain smooth operations.
See: EasyRoutes Workflows
On your EasyRoutes Orders page, click Configure table columns (below your active Route Options) and enable the Delivery Date and Time Window columns. Once enabled, EasyRoutes parses these values from your date picker app so you can sort, filter, and build routes by delivery date and window. The same columns are available in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. In both EasyRoutes for Shopify and EasyRoutes for Web you can enforce a start action. When a driver taps Start Delivery in the mobile app, EasyRoutes records the route start time and begins live location updates. This prevents drivers from completing stops out of context and ensures analytics include drive time from the route's start location. If a route must be paused, drivers can resume later to continue tracking.
Yes. EasyRoutes treats wholesale orders like any other Shopify orders for routing, dispatch, tracking, and proof of delivery. Ensure each record includes a valid shipping address; if not, correct it on the Shopify order (recommended) or add the address details to the stop in EasyRoutes. You can filter B2B orders by tags or other attributes when building a batch.
See: Working with items & fulfillments · Add a missing shipping address
The Delivery Driver app interface is available in English, Dutch, and German, and drivers can set their preferred app language from the app’s settings. Separately, the customer-facing side — tracking pages and email/SMS notifications — is fully customizable, so you can write that content in whatever language your customers speak. Language options apply the same way in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Both EasyRoutes for Shopify and EasyRoutes for Web can surface proof of delivery (PoD) to customers. Enable PoD display on tracking pages and decide which delivery events should send links via email/SMS. When a driver completes a stop, PoD is attached to that stop and becomes available to customers according to your settings. Admins always see PoD in route and stop details for auditing or future reference.
Yes. In both EasyRoutes for Shopify and EasyRoutes for Web, the Analytics page includes a date picker for presets and custom ranges. Choose the period you want to analyze, optionally select a driver, and the charts and tables update to reflect those filters. This lets you compare week‑over‑week or month‑over‑month performance and investigate changes after process updates or seasonal peaks.
You can export the filtered view to CSV to share with your team or archive for audit purposes.
See: Filtering by Date
Yes. Every route has a driver‑friendly manifest in the EasyRoutes Delivery Driver mobile app, and a printable version from the web. Use any route’s Print menu to generate a compact summary, packing slips/labels, and an optional inventory list. Print for clipboards or Save as PDF for digital sharing. Works the same in EasyRoutes for Shopify and EasyRoutes for Web.
EasyRoutes for Shopify is best suited for merchants who already sell goods or services within the Shopify ecosystem. Users can plan optimized delivery routes with all orders received through their Shopify storefront, created via draft orders, or imported manually as custom stops.
EasyRoutes for Shopify integrates seamlessly with the Shopify Admin and dozens of leading third-party apps, making it the ideal choice for Shopify merchants seeking a streamlined local delivery solution.
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
Zapier allows you to capture delivery events from EasyRoutes and log them automatically into a Google Sheet, Excel file, or database. For example, every time a driver completes a stop, Zapier can write details like stop ID, timestamp, and delivery outcome into a row. This creates a live delivery log that’s perfect for reporting, auditing, or customer service.
Yes for signature: in Driver settings you can require an e-signature (and/or photo) before a stop can be marked delivered, and customize the signature disclosure text shown to the recipient. For the ID portion, add a required Driver Task — a checkbox or text field confirming the ID check — so the driver can't complete a restricted stop without it.
Together these enforce a consistent, documented hand-off, though the age/ID check itself is performed by the driver rather than verified automatically. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Proof of Delivery · Driver Tasks
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. In EasyRoutes for Shopify you decide whether to send messages using EasyRoutes’ customizable templates, or Shopify’s native notification flows. EasyRoutes writes tracking details to the Shopify fulfillment so the order status page and Shopify notifications include the correct link. If you enable both systems, review your templates to prevent duplicate emails/SMS.
Configuration lives in EasyRoutes notification settings; Shopify templates are managed in your Shopify admin.
Enable live tracking from EasyRoutes Settings → Driver settings in either EasyRoutes for Shopify or EasyRoutes for Web. Next, ensure each driver signs in to the EasyRoutes Delivery Driver app (iOS/Android) and grants Always/Allow all the time location access with Precise location enabled. Once routes are started by a driver, location pins appear on the route’s Tracking tab. If privacy is a concern, you can restrict tracking for internal use only, or adjust the route expiry window for driver access.
Yes. If you use Shopify’s native notifications, you can insert proof image URLs into the Delivered or Missed Delivery templates so customers see photo links in those emails. This is optional — EasyRoutes notifications can also include tracking links that show PoD on the hosted tracking page. Choose the path that best matches your communication setup.
See: Integrating PoD with Shopify Emails · Delivery Notifications
You don’t need to code to connect BigCommerce with EasyRoutes. Zapier provides an easy no-code path to automate order syncing. For teams that need more complex, real-time integrations, the EasyRoutes API allows developers to customize imports, fulfillments, and route triggers. This gives you flexibility to choose between no-code and developer-driven solutions.
See: API Getting Started
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 use EasyRoutes' API to customize your integration and build powerful workflows to suit your specific delivery needs. You can also connect EasyRoutes webhooks to Zapier to unlock seamless, no-code workflows with your favourite apps and services, triggered by route updates in EasyRoutes.
Yes. For flexible fleets, create a self‑assign link so any active driver can claim the route from the link. This is useful for contractor pools or last‑minute coverage — whoever taps the link first becomes the assigned driver. You can share links in SMS, WhatsApp, or Slack and revoke them if needed.
Yes. When you configure a Scanner-input Driver Task, tick the Delivered and/or Attempted checkboxes to make a successful scan mandatory before that status can be applied. You can also require a Barcode Scan as proof of delivery from Settings > Driver Settings. Either way, drivers can’t mark the stop complete until the scan is captured. Available on Premium and Enterprise plans, in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver tasks · Driver settings
Go to tDrivers & Vehicles, open the driver, and edit their name, phone number, or notes. If a phone number changes, update it here so dispatch and sign‑in continue to work. Drivers may also edit their display name inside the Delivery Driver app.
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