Frequently Asked Questions

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.

See: Using Pickeasy with EasyRoutes · Order Filters

The cutoff, lead-time, and blackout-date rules you configure live inside your date picker app and control what customers can select at checkout — EasyRoutes doesn't import those rules. What it does read is the resulting delivery date and time window the app writes onto each order, which it then uses for filtering and routing. So the customer-facing scheduling limits stay with your picker, while EasyRoutes plans around the dates and windows they produce. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.

See: How EasyRoutes works with your Shopify setup and third-party apps · Time Windows

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

Orders without a delivery date or time window are still fully routable — EasyRoutes simply optimizes them for the shortest, most efficient path instead of constraining them to a window. You can mix dated and undated orders on the same route: those with windows are sequenced to honor them, while the rest fill the gaps. Use Order Filters to include or exclude undated orders, and add a window manually to any stop when you need one. This applies to both EasyRoutes for Shopify and EasyRoutes for Web.

See: Time Windows · Order Filters

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.

See: Time Windows · Route Scheduling & ETAs

Most likely, yes. EasyRoutes doesn't depend on a specific app — it reads the delivery date and time window from your Shopify orders. As long as your date picker writes that data into order attributes or order tags in a recognized format (for example, a "Delivery Date" attribute or a "8:00 AM - 12:00 PM" time value), it will appear in EasyRoutes. If it doesn't show up, enable the Order Tags and Order Attributes columns to view the raw data, or reach out to support.

See: Supported delivery date apps · How EasyRoutes works with your Shopify setup and third-party apps

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.

See: Time Windows · Filter orders by delivery date

EasyRoutes automatically reads the delivery date and time window that a date picker writes onto each Shopify order — most often as order attributes (note attributes), and also from order tags. It recognizes common attribute names such as "Delivery Date," "Delivery Time," and "Order Due Time" used by popular apps, then surfaces them in the Delivery Date and Time Window columns for filtering and routing. Metafields aren't read directly; use Shopify Flow to copy them into an order attribute. This works the same whether data comes from Zapiet, Buunto, or another supported app.

See: How EasyRoutes works with your Shopify setup and third-party apps · Time Windows

Yes. When you collect an e-signature, the driver can record who signed — the "Signed for" name is stored with the stop and appears in exports. For an explicit record, add a Driver Task text field for the recipient's name, and the driver can add a note or photo as well.

All of it is saved to the stop's proof-of-delivery timeline and can be shown on the customer's tracking page. Works in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Proof of Delivery · Driver Tasks

EasyRoutes doesn't have a setting that hard-locks a stop to one named person, but you can require and document the hand-off. Add a required Driver Task — a text field for the recipient's name, or a checkbox confirming "handed to named recipient" — that must be completed to mark the stop delivered, and note the required recipient in a stop note so the driver knows who to look for.

Pair it with a required e-signature so the signer is captured too. Works in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Driver Tasks · Proof of Delivery

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

EasyRoutes doesn't have a purpose-built haul-away field, but drivers can document a removal reliably. Add a required Driver Task — a checkbox "Old item removed," a text field for the item description, or a number field for quantity — that must be completed at the stop, and have the driver photograph the removed item as proof of delivery.

Task results and photos are stored with the stop and included in exports for your records. Works in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Driver Tasks · Proof of Delivery

Yes. There's no separate "white-glove" mode, but the pieces are built in. Use Driver Tasks to give drivers an in-home checklist (unpack, assemble, position, remove packaging) and require it before the stop is marked complete, and allow extra Time per stop or a longer per-stop service time so the schedule reflects the added work.

Drivers capture photos of the finished setup and a signature as proof. Works in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Driver Tasks · Route Options

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

EasyRoutes doesn't automate ID verification — there's no ID-document scan or built-in age lookup. Instead, use a required Driver Task to make the check part of completing the stop: a checkbox to confirm "photo ID checked, recipient of legal age," or a text field to log the ID type. Pair it with a required e-signature and photo for a complete record.

The barcode scanner captures product and package codes, not identity documents. Works in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Driver Tasks · Proof of Delivery

EasyRoutes doesn't include a dedicated age-verification or age-gating feature, so it won't automatically confirm a recipient's age. You can still operate alcohol, CBD, or other age-restricted delivery routes and enforce the check at the door: require an e-signature and/or photo to mark the stop delivered, and add a required Driver Task (e.g., "ID checked, recipient 21+") the driver must complete first.

Note that age-gated content isn't supported for SMS notifications. These options work in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Proof of Delivery · Driver Tasks

Keep product moving and time on the road low. Cap Max route duration and Max stops/items per route so no run exceeds your safe window, and let optimization split the overflow into extra routes. Use time windows and priority stops so the most temperature-sensitive orders are delivered first.

Pair the routing with physical cold-chain steps — insulated bags or coolers — and a required Driver Task to confirm handling. Works in both EasyRoutes for Shopify and EasyRoutes for Web.

See: Max route duration · Priority Stops

Use order tags or a stop note to identify refrigerated orders, or attach a required Driver Task (such as a "Refrigerated — keep insulated" checkbox) so the requirement travels with the stop and must be acknowledged. Order automation rules can apply notes or tasks automatically as orders import.

Combine this with routing limits so cold items spend less time in transit. Applies to both EasyRoutes for Shopify and EasyRoutes for Web.

See: Driver Tasks · Order Automation Rules

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

EasyRoutes doesn't currently offer a customer-facing "pick a new date" self-service tool. In practice, customers reply to your delivery notifications or use the contact details on their branded tracking page to reach you; you then move the order with Send to another route and send the Rescheduled notification with the new details.

Delivery Ratings and tracking pages keep the customer in the loop throughout. This flow is the same in EasyRoutes for Shopify and EasyRoutes for Web.

See: Customer tracking pages · Delivery Notifications