Get quick answers to the most common questions about EasyRoutes—setup, routes, drivers, and more.
Yes. From any route, choose Assign driver (or select from the header), then click Dispatch. The driver gets a push notification and can start the route from their phone. For busy days, dispatch multiple routes from a Route Group to release them all at once.
Driver seats control who can receive routes and use the EasyRoutes Delivery Driver app. Assign a seat to any driver in your roster to activate them; deactivate a seat when a driver is seasonal or temporarily off the road. You’re billed only for the number of seats included at your plan at any time. Deactivating preserves the driver’s details and history so you can re‑activate them later without re‑inviting.
Seat management is available in both EasyRoutes for Shopify and EasyRoutes for Web from the Drivers & Vehicles tab of the EasyRoutes navigation menu, or the Billing tab of EasyRoutes Settings for plan upgrades/downgrades.
Access the Drivers & Vehicles tab from the EasyRoutes navigation menu, click Add driver, and enter the driver’s name and phone number. EasyRoutes sends the invite; the driver installs the Delivery Driver app and signs in with an SMS code. Assign a seat to activate them and dispatch their first route.
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.
While there isn’t a separate public sandbox, you can safely test in a non‑production environment. Create a test shop (Shopify) or an EasyRoutes for Web workspace with sample data, generate a dedicated API token, and point webhooks to staging URLs. Use draft orders or manual stops that contain your own contact info so notifications and tracking tests go only to your team. When your flows are validated, switch credentials and endpoints to production.
Yes. Programmatically modify routes and stops using the Routes API — update stop status (delivered/attempted), change assignments, dispatch routes to drivers, or edit route options, then re‑optimize as needed. When your store uses EasyRoutes notifications, status changes made through the API follow the same rules and can send customer updates and refresh ETAs. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.
API access uses tokens you create in your EasyRoutes account. Follow the Getting Started guide to generate a token, store it securely, and add it to requests from your server or integration platform. Tokens work the same way for both EasyRoutes for Shopify and EasyRoutes for Web. Rotate credentials periodically and avoid embedding them in client‑side code.
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.
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.
Yes. Use EasyRoutes webhooks as Zap triggers to connect delivery events to apps like Google Sheets, Slack, Gmail, Twilio, HubSpot, and more. Common automations include updating a shared delivery log, notifying customer service when an attempt fails, or sending a custom message when proof of delivery posts. Zapier is supported for both EasyRoutes for Shopify and EasyRoutes for Web.