To import BigCommerce orders, export them in CSV format from your BigCommerce dashboard. Then log into EasyRoutes, go to Orders → Import new CSV, and upload the file. EasyRoutes will map fields like customer name, address, and items. Once imported, your orders will appear as pins on the map, ready for route optimization.
Put the handling steps where the driver will see them: add cooler or cold-chain instructions as a stop note or a saved customer note, which appear on the stop in the driver app. For steps you want confirmed, add a Driver Task — for example a required checkbox "Order kept in cooler until hand-off" or a note field — that the driver must complete before marking the stop delivered.
Saved task sets and Address Book stops let you reuse the same instructions across recurring routes. Works in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Driver Tasks · Driver & Stop Notes
Drivers can install the EasyRoutes Delivery Driver app from the App Store (iOS) or Google Play Store (Android) using the official links provided in our Help Center. The app works with both EasyRoutes for Shopify and EasyRoutes for Web accounts; once added as a driver, sign in using the phone number on file and the SMS code sent to that device. After dispatch, routes appear automatically in the app and can also be opened from the push notification's shared route link.
See: Where can I download the EasyRoutes Delivery Driver app?
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.
Drivers can capture multiple photos, obtain a customer e‑signature, and add notes at the stop. These items are stored with timestamps and the completion context, and they’re visible to admins on the route and stop record. When enabled in EasyRoutes Settings, customers can see PoD on tracking pages and in notifications.
See: Proof of Delivery
Yes. Enable the Rescheduled template in Customer notifications and customize its message and variables (new date, time window, tracking link). When you reschedule a stop to a new day or route, you can send the updated notification so the customer isn't left guessing — and a Missed Delivery notice can go out automatically when a stop is marked Attempted.
Notifications work over email and SMS for both Shopify orders and imported or manual stops, across EasyRoutes for Shopify and EasyRoutes for Web.
By default, CSV imports are static snapshots. For real-time updates, use Zapier to push new BigCommerce orders into EasyRoutes automatically, or build a direct integration with the API. This ensures address changes, order edits, or cancellations in BigCommerce are reflected in your delivery routes without manual intervention.
See: Zapier Integration
EasyRoutes functions like other public Shopify apps: one app install per store. If you operate multiple stores, you can plan centrally by importing stops from other stores (CSV, API, webhooks/Zapier) into the EasyRoutes workspace you use for routing. This approach lets you manage a combined delivery day while preserving each store’s native Shopify workflows.
Yes. Once invoices are imported into EasyRoutes, customers linked to those invoices can receive branded notifications via email or SMS, complete with live tracking links. This improves delivery transparency and reduces customer inquiries.
See: EasyRoutes for Xero
Yes. Open any template in the Notifications editor and use Preview with Example Data to see how your message will render, including variables. You can also send a real‑world test by creating a draft order or manual stop with your own contact details, and triggering notifications on a sample route. Preview/testing tools are available for both email and SMS on Shopify and Web.
Yes. Enable automatic dispatch so newly created routes with a scheduled start time are assigned and sent to the chosen driver immediately — no extra clicks. Use this for recurring daily runs or integrations that create routes programmatically. You can still edit or un-dispatch a route before start time if plans change.
Yes. The Analytics dashboard summarizes delivered vs. missed (attempted) stops so you can monitor delivery success across time or by driver. Use this report to identify recurring issues (e.g., address problems or access constraints) and to validate improvements after workflow changes.
For context on individual failures, open the underlying routes or stops to review notes and proof‑of‑delivery entries. You can also export the analytics view as CSV for further analysis or sharing with stakeholders.
See: Analytics Reports
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.
Every minute of Time per stop is added to the running clock as the driver works down the route, so each stop's ETA reflects both travel time and the time spent delivering the stops before it. More realistic ETAs mean fewer missed windows and better customer notifications.
Service time also counts toward Max route duration: if adding stops would push a route past your cap, optimization splits the work into additional routes instead of overrunning. Applies to both EasyRoutes for Shopify and EasyRoutes for Web.
EasyRoutes protects order and customer information with modern security practices. Traffic between your browser, the driver app, and our services is encrypted in transit; stored data is encrypted at rest. Access to accounts and APIs is token‑based and limited to the minimum required to operate features like routing, tracking, and notifications. Payments are handled by Shopify or other PCI‑compliant providers — EasyRoutes does not store card data.
We do not sell personal information. Limited sharing with subprocessors may occur solely to operate EasyRoutes as described in our Privacy Policy. Contact support if you have questions about data retention or deletion requests.
See: Privacy Policy
Yes. From any route, click Print → select Packing labels. You can output one label per stop or per order item (ideal for multiple packages). Configure label contents and sizing in Settings → Packing Slips & Labels. Use 4×6 thermal, A4/Letter sheets, or another size and scale as needed.
Shopify & Web: The label workflow is the same across products. For advanced templating on Shopify, you can send orders to Order Printer Pro from the Send to app dropdown, which can generate labels in route order.
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
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.
Time windows are interpreted in the time zone of each stop's delivery address, so a window set by your date picker is honored locally even when a route crosses time zone boundaries (for example, travelling from Chicago toward Indianapolis). Your Orders page and route columns display windows in your own local time, and stops in a different zone are annotated as such. This behavior is the same in EasyRoutes for Shopify and EasyRoutes for Web.
See: Time Windows
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.
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. When a route has a scheduled start date and time and its stops carry time windows, the EasyRoutes optimizer sequences stops to arrive within each window while minimizing overall driving time, factoring in start/end locations and stop durations. Driver and customer ETAs reflect those windows. If a stop can't be met within the route's constraints, it's moved to the rejected stops tab so you can widen the window, adjust the start time, or split routes. This works in both EasyRoutes for Shopify and EasyRoutes for Web.
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
When exporting from BigCommerce, configure your CSV template to create one row per sub-item (so multiple items in an order export properly). Map fields like First Name, Last Name, Address, and Product Qty to the corresponding EasyRoutes columns. This ensures accurate imports and prevents issues with incomplete customer or item data.
See: Importing CSV Orders
Yes. You can add an EasyRoutes-native QR code to your packing slips and packing labels from Settings > Packing Slips & Labels by enabling the Show QR code option and setting its position. Drivers can then scan these codes with the Delivery Driver app to confirm the right order at the right stop, and you can optionally require a successful scan before a stop is marked Delivered or Attempted. Supported in both EasyRoutes for Shopify and EasyRoutes for Web.
See: Barcode scanning
Yes. Workflows automate delivery tasks inside EasyRoutes, while Zapier connects EasyRoutes to external systems. Together, they create powerful end-to-end automation. For instance, a Workflow might create a route when orders arrive, while Zapier sends Slack alerts or updates a Google Sheet whenever stops on that route are completed. This layered approach ensures internal and external processes stay in sync.
See: Workflows Overview