Skip to main content

Importing work orders from a CSV file

File format​

Each row in your CSV is one work order. Operations are copied automatically from the matched route, so you do not list them in the file.

Your CSV should have the following columns:

  • wo_number: the work order's unique identifier
  • component: the component's unique identifier (must already exist)
  • route_version: which route version of the component to use
  • issue: the component issue / revision to build
  • quantity: quantity expected

To add extra information, you can include these columns:

  • due_date: due date (e.g. 2026-06-10)
  • status: planned (default), released, in_progress, completed or cancelled
info

Every row must reference a component, route version and issue that already exist in your organisation. Importing work orders does not create components or routes — import those first from Importing components.

How to import​

  1. Go to Work Orders, then click Import
  2. Select your CSV file
  3. Click Start Review to validate the data
  4. Check the preview — any rows that can't be matched are listed as errors
  5. Click Confirm Import once every row is valid

Matching rules​

For each row the importer looks up:

  • the component by its unique identifier,
  • the route version on that component,
  • the issue on that component (matched case-insensitively).

If any of these can't be found, or a work order with the same wo_number already exists, that row is reported as an error and nothing is imported until it is fixed.

Example​

Download example CSV

wo_number,component,route_version,issue,quantity,due_date,status
WO-1001,155332,1,A,50,2026-06-10,planned
WO-1002,155333,2,B,25,2026-06-12,released