For extended-handling stops, increase the Time per stop or the individual stop's service time so ETAs and Max route duration account for the extra work. For two-person deliveries, note that a route is assigned to a single driver account, so you'd staff that route's vehicle with a crew operationally rather than assigning two driver logins to one route.
Driver Tasks can capture crew-specific steps at the stop. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Route Options · Driver Tasks
Yes. You can generate packing slips for each stop from the route’s Print menu. Choose Packing slips to produce slips in route order, then print or save as PDF for digital handoff. Customize content (logo, variables, formatting) from EasyRoutes Settings → Packing Slips & Labels.
EasyRoutes for Shopify: Use the built-in Print Preview, or send orders to Shopify’s Order Printer/Order Printer Pro for custom templates (Order Printer Pro supports route order).
EasyRoutes for Web: Use the same Print Preview and Settings controls directly in the web app.
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. 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
EasyRoutes uses a flexible, seat‑based model. Choose a plan (Standard, Premium, Enterprise) and activate the number of driver seats you need; you’re billed only for active seats. You can adjust seats or change tiers at any time, and SMS messaging — if enabled — is charged per message segment. Both EasyRoutes for Shopify and EasyRoutes for Web use the same pricing model.
See: Pricing · Pricing & Plans FAQ
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. 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. EasyRoutes reads Shopify Local Delivery details (including delivery instructions from checkout) and adds them to the stop for drivers. If you maintain Pickup orders and want them represented on a route — for example, to stage curbside handoff or transfer to another location — you can include them with your store or pickup address so the task appears in sequence and on printed documents.
See: Where can I see delivery instructions from a Shopify Local Delivery order?
EasyRoutes pricing combines your plan tier with the number of driver seats in your current plan. Keep any number of drivers in your roster, then activate only the seats you need for your current delivery schedule. If demand spikes, add seats for a few days and deactivate later — billing automatically prorates so you pay for just the days your account contained additional seats. Seat management works the same on Shopify and Web.
See: Manage active driver seats · How prorated billing works
Yes. EasyRoutes maintains a route history so you can review previous runs, proof of delivery, and timing information on either EasyRoutes product (Shopify and Web). Use the Routes page to filter by status (unstarted/in progress/completed/archived) and date. Open any route to view stop details and the Activity Feed particulars for that route. You can also export route/stop data for period‑end reporting or audits.
If you don’t see older orders on the Orders page, adjust the Show orders from the last window in Settings; this does not affect existing route history.
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?
Capping how many orders a customer can book into a given slot is handled by your date picker app at checkout (for example, Pickeasy's order limits), not by EasyRoutes. On the planning side, EasyRoutes helps you balance the resulting workload: filter orders by delivery date and time window, then split them across multiple routes or drivers, and the optimizer sequences each route to respect its windows. Together they keep slots controlled and routes balanced. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
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.
No. Barcode scanning uses the camera on your driver’s existing iOS or Android device, so there’s no need to buy dedicated scanners or hardware. Drivers scan directly from the EasyRoutes Delivery Driver app, with a built-in flash option for low light and a manual-entry fallback if a code won’t read. It supports common linear formats (UPC, EAN, Code 128, and more) and 2D codes like QR and Data Matrix. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
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. 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
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. Use the Delivery Zones tool to outline one or more areas on the map, then filter/select orders within those zones to build your route quickly. Zones help planners batch by neighbourhood or service area and pair well with other filters like tags or dates. Once configured, zones are stored permanently to standardize your daily workflow when planning for the same areas.
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. From the Analytics page, pick your time period (e.g., last 7/30 days or a custom range) and optionally filter by driver. Use the Export option to download a CSV for spreadsheets or external tools, or use Print to generate a PDF summary. CSV exports preserve the filters you applied so downstream reports match what you saw in EasyRoutes.
Exports are available in both EasyRoutes for Shopify and EasyRoutes for Web. If you need more granular, stop‑level records, combine Analytics with route exports from the Routes page.
The EasyRoutes API lets you automate your delivery workflow end‑to‑end: import orders/stops from external systems, create routes with your preferred options, assign drivers or vehicles, dispatch routes, and update stop or route status as deliveries progress. You can also read back route/stops for reporting and pair the API with webhooks to keep other systems synchronized in real time. Capabilities are consistent across EasyRoutes for Shopify and EasyRoutes for Web.
Zapier is designed to be used without coding. To integrate EasyRoutes, you typically select “Webhooks by Zapier” as a trigger, paste a webhook URL into EasyRoutes, and then connect it to actions like sending an email or updating a spreadsheet. All steps are handled through a simple, click-based interface. This makes automation accessible to any team member, not just developers.
See: EasyRoutes Zapier
EasyRoutes combines route planning, driver dispatch, live tracking, and proof of delivery in one system. Teams select orders (from Shopify or external sources), create optimized routes with start/end locations and options (time windows, service times), then dispatch to the EasyRoutes Delivery Driver app.
Admins monitor routes in the browser, view ETAs and driver location (Premium/Enterprise), and share branded tracking pages and notifications with customers. Proof of delivery items — photos, eSignature, notes — are captured in the field and visible on the stop record. EasyRoutes is designed for SMBs and delivery fleets of any size across industries.
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. When real‑time tracking is enabled, customer tracking pages can show an anonymized, live GPS pin as the driver approaches (configurable between 1 and 10 stops away). Turn on live location in EasyRoutes Settings → Driver settings, and enable the customer display option in EasyRoutes Settings → Order tracking. This capability is available across EasyRoutes for Shopify and EasyRoutes for Web.
No. The Activity Feed is an internal operations log available to EasyRoutes admins and dispatchers. Drivers use the EasyRoutes Delivery Driver app to view assigned routes, update stop statuses, and capture proof of delivery; these events will appear in the Activity Feed for admins, but drivers do not access the account‑wide feed. This separation keeps internal data and audit trails restricted to management.
See: Activity Feed