Store Groups (Full Update)

Description

Upserts Store Group Resources synchronously. Does not handle partial successes or failures if multiple are provided.

See the Aerial Spec for more details.

File Naming Convention

TGEN_storeGroups_fullupdate_2026-08_<optionalSuffix>.csv

  • importType: fullupdate
  • apiVersion: 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 HeaderDescriptionKey InformationTypeRequired
externalIdThe external identifier of the store groupstringNo
typeType of the store group. STATIC groups have their stores assigned directly; DYNAMIC groups contain every store matching rules. Case-insensitive. Defaults to STATIC when omitted, including on update.mixedNo
nameName of the store groupstringNo
descriptionDescription of the store groupstringNo
rulesRules for membership in the store group. Valid keys: countryCode, disabled, district and storeType. Required as a non-empty object when type is DYNAMIC: omitting it or sending {} returns a 422. Not used for STATIC groups, where an empty object is stored as null.objectNo

Sample CSV

See the following storeGroups CSV sample file.

storeGroups Sample 1

Note: The sample CSV may contain sample ID fields which reference other resources that do not match the data in your environment.