Location imports

Overview

Location imports let you bulk-create or update factory locations. Column headers are matched case-insensitively and extra whitespace is trimmed.

Columns

Column	Required	Description
`name`	Yes	Location name. Must be unique within the CSV and cannot exceed 128 characters.
`original_name`	No	If renaming an existing location, this is the current name in ION. Max 128 characters. Lookup column: an empty cell means “no rename,” not `""`.
`parent_name`	No	Name of the parent location. Used to build nested hierarchies.
`description`	No	Description of the location. Max 512 characters.
`address`	No	Physical address. Max 128 characters.
`available`	No	Whether the location is available. Boolean field (see accepted values).
`archived`	No	Whether the location is archived. Boolean field (see accepted values).
`exclude_from_merge_part_inventory`	No	Exclude this location from merged part inventory views. Boolean field (see accepted values).
`can_hold_inventory`	No	Whether the location is a valid destination for inventory. Boolean field. Default-true column: an empty cell keeps the current value rather than setting `false`.
`pickable`	No	Whether kitting can pull from the location. Boolean field. Default-true column: an empty cell keeps the current value rather than setting `false`.
`latitude`	No	Latitude coordinate. Must be between -90 and 90. Empty cells are treated as unset (not `0`).
`longitude`	No	Longitude coordinate. Must be between -180 and 180. Empty cells are treated as unset (not `0`).
`type`	No	Location type. One of `workcenter`, `tote`, `warehouse`, `rack`, or `shelf`.
`supervisor`	No	Email address of the supervisor. Must match an existing user in ION.

Custom attributes

Any columns beyond the standard set are matched against your organization’s custom location attributes. If a column header does not match a standard column or a configured custom attribute, the import will fail with a validation error.

Parent-child hierarchies

You can define nested locations by specifying a parent_name for each row. ION resolves parents automatically, including parents that are created within the same import. Parents are always processed before their children regardless of row order. Circular parent-child relationships are detected and rejected. An example is Location A being the parent of Location B, which is in turn the parent of Location A.

Can Hold Inventory and Pickable are advisory until an admin turns on the matching enforcement setting in Settings > Supply Chain > Locations. With Enforce can hold inventory on, a row that turns off can_hold_inventory for a location that still holds inventory is rejected.

Getting Started

Build Hardware

Manage Supply Chain

Track Quality

Automate with ION

Administration

API

Overview

Columns

Custom attributes

Parent-child hierarchies

​Overview

​Columns

​Custom attributes

​Parent-child hierarchies

Overview

Columns

Custom attributes

Parent-child hierarchies