Import file details: product_abstract.csv
Edit on GitHubThis document describes the product_abstract.csv file to configure Abstract Product information in your Spryker Demo Shop.
Import file dependencies
Import file parameters
| PARAMETER | REQUIRED | TYPE | REQUIREMENTS OR COMMENTS | DESCRIPTION |
|---|---|---|---|---|
| category_key | ✓ | String | Identifier of category key name. | |
| category_product_order | Integer | Order of the product presentation inside a category. | ||
| abstract_sku | ✓ | String | SKU identifier of the abstract product. | |
| name.{ANY_LOCALE_NAME} Example value: name.en_US |
✓ | String | Locale data is dynamic in data importers. It means that ANY_LOCALE_NAME postifx can be changed, removed, and any number of columns with different locales can be added to the .csv files. | Name of the product in the specified location (US for our example). |
| url.{ANY_LOCALE_NAME} Example parameter: url.en_US |
✓ | String | URL page of the product image in the specified location (US for our example). | |
| attribute_key_{NUMBER} Example parameter: attribute_key_1 |
✓ (if this attribute is defined) | String | Product attribute key for the attribute. Columns attribute_key_{NUMBER} and value_{NUMBER} should always come in pair. |
|
| value_{NUMBER} Example parameter: value_1 |
✓ (if this attribute is defined) | String | Product value for the attribute. | |
| attribute_key_{NUMBER}.{ANY_LOCALE_NAME} Example value: attribute_key_1.en_US |
String | Product attribute key, for the first attribute, translated in the specified locale (US for our example). Columns attribute_key_{NUMBER}.{ANY_LOCALE_NAME} and value_{NUMBER}.{ANY_LOCALE_NAME} should always come in pair. |
||
| value_{NUMBER}.{ANY_LOCALE_NAME} Example value: value_1.en_US |
String | Product value for the attribute, translated in the specified locale (US for our example). | ||
| color_code | String | Product color code. | ||
| description.{ANY_LOCALE_NAME} Example value: description.en_US |
String | Product description, translated in the specified locale (US for our example). | ||
| tax_set_name | String | Name of the tax set. | ||
| meta_title.{ANY_LOCALE_NAME} Example value: meta_title.en_US |
String | Meta title of the product in the specified locale (US for our example). | ||
| meta_keywords.{ANY_LOCALE_NAME} Example value: meta_keywords.en_US |
String | Meta keywords of the product in the specified locale (US for our example). | ||
| meta_description.{ANY_LOCALE_NAME} Example value: meta_description.en_US |
String | Meta description of the product in the specified locale (US for our example). | ||
| new_from | Date | To be considered a new product from this presented date. | ||
| new_to | String | To be considered a new product until this presented date. | ||
| avalara_tax_code | String | Avalara tax code for automated tax calculation. Add this field if Avalara is used for tax management. |
Additional information
For each attribute, where N is a number starting from 1, without gaps, it’s mandatory to have both fields:
attribute_key_Nvalue_N
For each attribute, where N is a number starting from 1, without gaps, it’s mandatory to have both fields:
attribute_key_N.{ANY_LOCALE_NAME}value_N.{ANY_LOCALE_NAME}
The number of attributes is not limited.
Import template file and content example
| FILE | DESCRIPTION |
|---|---|
| template_product_abstract.csv | Import file template with headers only. |
| product_abstract.csv | Exemplary import file with the Demo Shop data. |
Import command
data:import:product-abstract
Thank you!
For submitting the form