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. From EasyRoutes Settings → Customer notifications, tailor email and SMS templates with your branding and dynamic variables, and select exactly which events trigger messages (Ready for Delivery, Out for Delivery, Driver is X Stops Away, Delivered, Missed Delivery, plus Scheduled/Rescheduled). You can maintain separate templates for Shopify orders vs. imported/manual stops, and send messages automatically with links to branded tracking pages. This customization is available in both EasyRoutes for Shopify and EasyRoutes for Web.
Yes. The EasyRoutes Routes API accepts imported stops (customer details, address, items, notes) so you can bring orders from non‑Shopify sources into EasyRoutes. After importing, you can create new routes, add the stops to existing routes, assign drivers, and dispatch. This works for both EasyRoutes for Shopify and EasyRoutes for Web and complements CSV import when you need automation.
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.
Customizable delivery status notifications (both email and SMS), order tracking pages including delivery ETAs, real-time driver location tracking, and Proof of Delivery (photos, eSignature, driver note, delivery GPS location) are all broadly supported on both EasyRoutes for Shopify and EasyRoutes for Web.
Customers receiving deliveries via either platform will benefit from the same user experience, tailored to meet your brand’s standards.
See: Tracking pages · Delivery notifications · Proof of Delivery
Yes. You can integrate EasyRoutes with ERPs, CRMs, WMS, and custom apps using our API and webhooks. Typical use cases include importing stops from non‑Shopify channels, syncing delivery status and proof‑of‑delivery back to your system of record, and powering external analytics collection. The same platform supports both EasyRoutes for Shopify and EasyRoutes for Web.
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?
Delivery Analytics provides a consolidated view of your operations across both EasyRoutes for Shopify and EasyRoutes for Web. Key metrics include total stops and routes, completion rate, attempted/missed deliveries, average delivery time, and per‑driver performance summaries. Use it to compare activity over time, spot bottlenecks, and validate operational changes.
You can filter by time period and specific drivers to focus on a team or individual, then export results to CSV for reporting. For event‑level detail (e.g., when a stop changed status), open the route’s Activity Feed. Analytics refreshes as new delivery events are recorded, so the dashboard stays current throughout the day.
Yes. In EasyRoutes Settings → Customer notifications, enable the Rescheduled template and customize the message and variables (date, window, tracking link, etc.). Trigger it when routes or stops move to a new day/time so recipients are informed proactively. This works for both Shopify orders and imported/manual stops across EasyRoutes for Shopify and EasyRoutes for Web.
Yes. Enable SMS in EasyRoutes Settings → Customer notifications and include the tracking URL in templates such as Ready for Delivery, Out for Delivery, Driver is X Stops Away, Delivered, and Missed Delivery. SMS is supported in both EasyRoutes for Shopify and EasyRoutes for Web on Premium/Enterprise plans, and is billed per message segment by country. Use the preview tool to verify variables before sending.
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.
No technical background is needed if you use Zapier to connect Xero with EasyRoutes. Zapier provides a no-code way to set up automations like sending invoices into EasyRoutes for route creation. For advanced teams, the EasyRoutes API allows for custom integrations, syncing invoice updates, or linking to ERP/CRM systems.
See: API Getting Started
SMS usage fees and monthly pricing tiers are identical for both EasyRoutes for Shopify and EasyRoutes for Web, with the exception of our Free monthly pricing tier, which is currently only available on EasyRoutes for Shopify. EasyRoutes for both platforms continues to offer a free 14-day trial of any pricing tier for new users to give a advanced features a test drive. Both platforms function on the same driver seat model, where you only pay for the number of drivers that are active in your account at any time.
EasyRoutes for Shopify uses Shopify’s native billing tools for all subscription and SMS usage top-ups and monthly invoicing. EasyRoutes for Web functions on the same principles, but uses an independent billing provider offering industry-standard security and encryption for all transactions.
See: SMS pricing · Pricing · Proration
Yes. Drivers can start their route — triggering Out for Delivery notifications, if enabled — mark individual stops as Delivered or Attempted, and add proof (photos, signature, notes). These updates appear instantly on the route and — if enabled — update customer tracking and notifications. Admins can review all events in the route timeline and export later for records.
See: How do I mark an order as Delivered? · How do I mark an order as Attempted Delivery?
EasyRoutes offers webhook-based triggers in Zapier, such as “Route Updated” and “Stop Status Updated.” These let you automatically take action in other apps when a route changes or a driver marks a stop as delivered. For example, you can update a customer record in your CRM or notify your warehouse team when a stop is completed.
See: Zapier Setup Guide
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. 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. Drivers can add photos and notes for attempts (e.g., no answer, inaccessible). You can make PoD mandatory for Attempted stops, so drivers document the situation before moving on. Attempt proof appears with the stop’s history for admins and, if enabled, on customer tracking pages/notifications to explain what happened.
See: Proof of Delivery
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, you don’t need to be a developer to take advantage of Workflows. The Workflows feature is designed to be accessible to non-technical users by using a visual, menu-based interface. You simply select a scheduling frequency, define any conditions (like “only include orders tagged Local Delivery”), and choose an action (for example, “create and dispatch a route”).
This no-code design makes Workflows similar to popular automation tools like Zapier or Shopify Flow, where anyone can build powerful automations just by clicking and selecting from available options. That said, more advanced users can extend Workflows with APIs or webhooks to create complex, custom integrations, giving both beginners and power users maximum flexibility.
See: No-Code Automation
Yes. To reprint, open the route, click Print, and enable Packing slips and/or Packing labels. You can send the batch to a printer again or save a fresh PDF. Reprinting uses your current template settings — if you change variables or sizes in Settings → Packing Slips & Labels, the new output will reflect those changes.
If the route has been archived from your EasyRoutes account, restore it before printing. This reprint flow works the same in both EasyRoutes for Shopify and EasyRoutes for Web.
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
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.
The feed captures high‑signal delivery events so you can trace what happened and when: route creation, edits, and dispatches; assignments and self‑assign actions; stop status updates (Ready, Out for Delivery, Delivered, Attempted); proof‑of‑delivery photos/signatures/notes; and other key changes. Entries stream in real time for both EasyRoutes for Shopify and EasyRoutes for Web.
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. 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