Store Types (Full Update)
Description
If the UUID of the Store Organization Resource exists in the system, or no UUID is provided and an External ID exists, then an update is performed. Otherwise, the resouce is created.
See the Aerial Spec for more details.
File Naming Convention
TGEN_storeTypes_fullupdate_2026-08_<optionalSuffix>.csv
importType:fullupdateapiVersion:2026-08
Columns
Nested object fields are flattened into columns using dot notation (parent.child). Array fields are flattened using zero-based index notation, one element per column (field[0], field[1], and so on).
Note: A whole array cannot be passed in a single column: a literal value such as ['value-1','value-2'] will be rejected. To import multiple array elements, add one indexed column per element. Rows in the table below with type array describe the field as a whole and are not valid CSV column headers.
| Column Header | Description | Key Information | Type | Required |
|---|---|---|---|---|
externalId | Integrator provided unique identifier for the store. Typically used to map a primary key from a third party system to the Tulip resource. | Max Length: 255 | string | Yes |
name | Name of the store type | Max Length: 255 | string | Yes |
Sample CSV
See the following storeTypes CSV sample file.
Note: The sample CSV may contain sample ID fields which reference other resources that do not match the data in your environment.