Spreadsheet import
Upload `.xlsx` order files, preserve leading-zero ZIP codes, normalize state values, and block missing required fields before route readiness.
Waydispatch turns delivery spreadsheets into route-ready orders, validated addresses, driver assignments, optimized routes, map review, and dispatch to drivers' mobile apps.
Waydispatch is built around messy parcel-delivery order files. It validates required columns, stores parsed imports, checks addresses, and keeps correction work inside the same workflow instead of forcing another upload.
Upload `.xlsx` order files, preserve leading-zero ZIP codes, normalize state values, and block missing required fields before route readiness.
Geocode addresses through the production provider and accept exact house-number plus ZIP matches automatically.
Street-only, wrong-ZIP, coordinate-less, and classification-conflict rows are held for review so bad inputs do not enter optimization.
Fix addresses directly in Waydispatch, persist the corrected result, and move reviewed rows into a route-ready state without re-uploading.
Residential, business, commercial, and unknown classifications can come from the spreadsheet or manual review when provider data is unavailable.
Optional cutoff times from the spreadsheet are stored with the order and surfaced as missed-cutoff warnings in route results.
Drivers live in the workspace and can be imported, reviewed, activated, or excluded before optimization. Route drafts carry selected driver IDs through to persisted route results.
Driver spreadsheets require driver number, first name, and last name. Duplicate and invalid rows are blocked before persistence.
Active/inactive status controls which drivers appear in route assignment, so old or unavailable drivers do not get selected by accident.
Saved routes retain driver ID and historical driver display name, which keeps old route plans readable after roster changes.
Waydispatch starts route optimization from database-verified route-ready imports. The backend receives validated coordinates, selected driver IDs, depot coordinates, and stored order context rather than raw spreadsheet guesses.
Select route-ready orders, choose drivers, name the route, and carry that draft into route finalization.
FastAPI validates workspace access, loads route-ready rows, and runs optimization with Python, Pydantic, OR-Tools, and routing-provider data.
Saved plans keep provider status, geometry when available, warnings, mileage, drive time, and summary metrics.
Route maps render in the operational review page when geometry is available, with driver route cards and sequenced stop tables.
Persisted route plans can be reopened through the Routes page for review without rerunning the import.
Missed cutoff warnings are separated from routing-provider notices so dispatchers can see operational exceptions clearly.
Waydispatch prepares dispatch-ready outputs without pretending to send messages automatically. Dispatchers review the packet, dispatch routes to the driver app, open navigation segments, and send SMS or email drafts from their own device.
Import orders, validate addresses, assign drivers, optimize routes, and export the handoff your dispatch team needs.