Installing, languages, offline shifts, dashboard scanning and ePOD capture.
Dispatch & routes
Manifest imports, assignments, reassignment handshakes and bulk status updates.
Sync & connectivity
How offline queues work, retries, conflicts and what drivers see when signal drops.
Accounts & access
Roles, invites, password resets, workspace switching and impersonation for admins.
Common fixes, step by step
The four issues that solve ninety percent of support tickets.
The sync queue looks stuck
1Check the phone has any connectivity — the sync indicator shows the number of queued items.
2Pull down on the shift list to force a sync attempt.
3If items remain, keep the app open for two minutes; large photos upload one by one.
4Nothing is lost while queued: every stop, photo and signature stays on the device until the server confirms receipt.
An import keeps rejecting rows
1Open the dry-run report and sort by error type.
2Fix missing postcodes or countries first — they block geocoding.
3Merge or rename duplicate shipping references.
4Re-run the dry run before importing; only a clean or consciously overridden report should reach the fleet.
A driver cannot sign in
1Confirm the email address matches the invite exactly, including spelling.
2Resend the invite from the dispatcher portal if the link expired.
3Use the password-reset link on the portal login page.
4Still blocked? Email support with the driver's name and workspace and we will trace the account.
A photo is missing from the delivery report
1Open the stop on the driver's phone and check the photo stack — an interrupted upload leaves the photo queued on the device.
2Ask the driver to open the app with connectivity so the queue drains.
3Regenerate the proof-of-delivery report; it always includes every synced image.
Frequently asked questions
No. The driver app is offline-first: stops, photos, signatures and timestamps are stored on the device and pushed automatically as soon as connectivity returns. The dispatcher sees the stop update with its original capture time.
Open the stop from the shift list, tap the photo stack and add more images. Every photo keeps its own timestamp and is attached to the same proof-of-delivery report.
The language picker sits at the top of the driver home screen. The app supports 17 languages including right-to-left layouts, and the choice is remembered on that device. Dispatch notes and customer names stay in the language they were written in.
Yes. The app is a progressive web app built for the devices drivers actually carry: it installs from the browser, uses little storage, and keeps working in areas with weak coverage. No app-store account is needed.
Run the dry-run report first: it lists missing required columns (stop number, address, postcode, country), duplicate references and rows with unparseable dates. Fix those rows in the spreadsheet and re-import, or override a conflict with an audit reason.
Yes. Save the column mapping as a template the first time you import a customer or carrier file. The next import of the same layout applies the template automatically and only asks you to confirm the dry-run report.
The new driver receives the route with a handshake prompt on their phone. Until they acknowledge it, the dispatcher sees the assignment as pending. The previous driver keeps a read-only record of what they already completed.
Every change pushed to a driver is logged with a delivery and acknowledgement timestamp in the route update log. If a driver is offline, the update queues and is marked as acknowledged the moment their device syncs.
It blinks five minutes before the configured driving limit is reached, so the driver can find a safe place to stop. When the driver confirms the break, the countdown resets and the break is written to the compliance log.
No. The timer is a planning and awareness aid that mirrors EU 561/2006 driving and break rules. The legal record remains the vehicle's tachograph and the driver card; Depot2Door helps the driver respect those limits, it does not certify them.
The compliance layer accumulates driving and working time over the rolling week and fortnight and warns before the EU 561/2006 and Working Time Directive ceilings are reached. Thresholds are configurable per workspace to match your operator licence.
Check the account exists in your workspace and the email is confirmed. Workspace admins can resend an invite from the dispatcher portal. Passwords reset through the portal login page.
Open the portal in the phone browser, then choose 'Add to Home Screen' (iOS Safari) or 'Install app' (Android Chrome). It then launches full-screen and works offline.
There are four roles: driver, dispatcher, fleet manager and workspace admin. Drivers see only their own routes, dispatchers manage manifests and assignments, fleet managers own vehicles and compliance settings, and admins control members and billing.
Only members of your workspace. Media is stored encrypted in EU data centres and served through short-lived signed links, so a link shared in a proof-of-delivery email expires automatically.
Workspace admins manage the plan from the billing settings: change vehicle counts, add modules or cancel at the end of the current period. Your data remains exportable after cancellation.
Still need a hand?
Email support
Include the route number and stop number and we can trace the exact record.