Return Reasons (Full Update)
Description
Upserts Return Reasons synchronously. Does not handle partial successes or failures if multiple are provided.
See the Aerial Spec for more details.
File Naming Convention
TGEN_returnReasons_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 return reason. Typically used to map a primary key from a third party system to the Tulip resource. | Max Length: 255 | string | No |
disabled | Boolean dictating if return reason is disabled (true or false) | boolean | No | |
sortOrder | Sort order for this return reason in the list | integer | No | |
store | Unique Tulip identifier or External ID of the store the return reason is associated with | Max Length: 36 | string | No |
countryCode | Country ISO code in ISO-3166-1 alpha-3 format | Max Length: 3 | string | No |
country | Unique Tulip identifier or ISO code in ISO-3166-1 alpha-3 format of the country this return reason is associated with | Max Length: 36 | string | No |
Sample CSV
See the following returnReasons 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.