Yes. Alongside EasyRoutes-native barcodes, drivers can scan existing product or order barcodes and QR codes — including supplier UPC, EAN, Code 128, and 2D formats like QR and Data Matrix — using the phone camera. Externally generated codes are captured and stored with the stop for reference, though match validation (the green/yellow confirmation) applies to EasyRoutes-native codes. Available in both EasyRoutes for Shopify and EasyRoutes for Web.
Can I scan supplier UPC or QR codes?
People also ask
Can drivers upload proof from their phone gallery?
Yes. If enabled in Driver Settings, drivers can upload photos from the device gallery — handy for low‑connectivity deliveries — then the app syncs them when online.
Can drivers verify a customer's age or scan an ID at the point of delivery?
No automated ID scan or age check in EasyRoutes; use a required Driver Task for drivers to confirm ID checked, plus e-signature and photo.
Can drivers mark a stop attempted/failed with a reason?
Yes. Drivers mark a stop Attempted, choose a preset reason (e.g. no answer, inaccessible, Canceled), and can add a note or proof of delivery.
Can I require a scan before completing a stop?
Yes. Make a Scanner-input task required for Delivered/Attempted, or require a Barcode Scan as proof of delivery, so a stop can’t be completed without a scan.
Can drivers use Apple Maps for turn-by-turn navigation?
Yes. Drivers can launch directions via Google Maps, Apple Maps, or Waze from each stop, and pick a default navigation app in their mobile app settings.
Are there differences for drivers between products?
No. Both EasyRoutes for Shopify and Web dispatch delivery routes to the same EasyRoutes Delivery Driver mobile app for iOS and Android. Drivers will have access to the same easy-to-use navigation and inventory tools when delivering routes with either product. Driver-facing route planning features (such as assignable driver tasks and scheduled driver breaks) are also available on both platforms.
What's the difference between EasyRoutes-native barcodes and existing product/order barcodes?
EasyRoutes-native barcodes are tied to a specific stop for match validation, while existing product/order barcodes can be scanned and recorded but aren’t stop-matched.
Do I need to code to connect BigCommerce & EasyRoutes?
No coding is required if you use Zapier or import via CSV file. For advanced customizations, API knowledge is helpful.
Still have a question?
Search the FAQs, browse the guides, or talk to a human.