One mission per row or object.
One mission per row or object.
Data and improvement
Learn how delivery teams should prepare CSV, XLSX, or JSON mission imports for cleaner route planning, dispatch, and reporting.
Import quality controls route quality. Clean mission files reduce dispatch delays and make optimization more reliable.
Primary keyword: CSV delivery import
One mission per row or object.
Consistent date, time, and timezone assumptions.
Complete address or coordinates.
Valid phone numbers and customer fields.
Clear pickup and delivery fields for pickup-delivery jobs.
No sensitive data unless necessary.
Customer or recipient name, phone, address, latitude/longitude where available, date, time window, service duration, demand, priority, and notes. For pickup-delivery work, include pickup address, pickup time window, pickup duration, delivery address, delivery time window, and delivery duration.
CSV works well for simple spreadsheet exports. XLSX helps spreadsheet users who already manage workbooks. JSON is useful for structured operational exports from another system.
Check incomplete rows, wrong branch/date context, missing coordinates, invalid time windows, and fields that do not match vehicle skills or capacity.
Guide
Guide
Guide
Feature
Feature
Feature
Feature
No. Rouptimize guide copy should mention CSV, XLSX, and JSON mission import.
Importing mission data prepares work for planning. Credits are used when missions or orders are newly scheduled onto routes.
Start with the current Rouptimize workflow and bring your dispatch, drivers, proof, and reporting into one operating system.