Import/Export

Version

6.1.5 or newer

Table of contents

It's easy to manage your content in Shopware 6. You can use imports and exports to review your existing content or transfer it to interfaces or evaluation tools. 

In this documentation we generally describe the options you have for imports and exports.

Import

In the tab Import you have the ability to import data into your Shopware 6 environment using CSV files.

Upload CSV file (1): 
Select the native CSV file from your PC which should be used for the import. The CSV file should contain the data to be imported into your Shopware 6 environment.

Some spreadsheet programs may affect the separators or leading zeros of CSV files. Therefore you should be careful to use a tool that creates native CSV files. A free tool that creates native CSVs is Open Office Calc.

Select profile (2):
Select the profile that is used to import the CSV file. The profile determines which data from the CSV file is stored in which database tables.

Start import (3):
With this button you start the import of the CSV file using the selected profile. Now all records are validated and all error-free records are imported. All erroneous records are combined in a new CSV file, which can be downloaded afterwards.

Import activity (4):
In the Import activity you can see a history of your past imports. All imports of the last 30 days are displayed here.
Using the context menu at the end of each line, you can download the imported source CSV file again and open the profile used. For imports with erroneous records, you can also download a CSV file that contains only the erroneous data. 

Export

In the Export tab you can export existing data from your Shopware 6 environment and convert it into a CSV file.

Export (1): 
In the Export section you select which data should be exported based on the profile. A list of which profile outputs which data can be found in the Profiles section.

Select profile (2):
Select the profile that is used to export your data to the CSV file. The profile determines which data from the database is written into the CSV file.

Start export (3):
With this button you start the export of the data using the selected profile. 
Export activity (4):
In the export activity you can see a history of your past exports. All exports of the last 30 days are displayed here.
You can open the used profile and download the CSV file again using the context menu at the end of each line. 

Profile

In the tab Profiles you manage the profiles which are used for import and export. The profile that is selected for import and export specifies which database entries are accessed during import/export.


Profile overview (1):
In the profile overview you will find all created profiles. It also indicates whether it is a standard or a user created profile.

Menu (2):
Use this context menu to open or delete the profile. In addition, the profile can be duplicated and modified using this context menu.

Create new profile (3):
Use the button to create a completely new profile.

Search (4):
If the profile overview loses its clarity due to too many created profiles, you can find each created profile by using the search function.

Create new profile

Apart from the standard profiles, which are supplied by Shopware, you also have the possibility to create your own profiles. There are two ways to create a new import/export profile.
Using the context menu next to each profile you can duplicate the corresponding profile. this will allow you to duplicate and modify an existing profile or one of the standard profiles.
With the button Add new profile you can also create a completely new profile and change and start from scratch. 

General

Profile name (1):
The profile name is used in the profile list and in the profile selection in import and export.

Object type (2):
The object type specifies which database tables and columns the profile can access. For instance, the object type Product can be used to access all product-relevant entries from the database, while the type Customer can be used to access all customer-relevant entries.

Database mapping (3):
In the database mapping you assign a column from the CSV file to the desired entries from the database. The CSV name that you assign here must be the name of the corresponding column in the CSV file that is used with this profile.

Add new mapping (4):
With this button you can add a line to the database mapping. In the still empty line you select a database entry to be accessed and enter the name of the column from the CSV file.

Delete (5):
You can remove each entry by using the context menu behind it.

Field Indicator

Separator character (1):
The separator character is used to separate the fields in the CSV file. This is the semicolon is default.

Enclosure character (2): 
The enclosure character appears at the beginning and end of a text. Within these characters, separator characters are ignored.

Database entries

When creating your own profile, you access database entries and assign them to a column in the CSV file. 
First you select an object type for your import. This determines which database entries you can access. For instance, the object type Product gives you access to all product-related database entries.

 



Product

Database entryDescriptionDatabase table
activeIndication whether the product is activeproduct
autoIncrementUnique decimal numberproduct
availableIndication if the product is availableproduct
availableStockAvailable stockproduct
childCountNumber of variantsproduct
configuratorGroupConfigOwn sorting of the propertiesproduct
cover.idUUID of the preview image of the articleproduct_media
cover.versionIdUUID which indicates the version of the preview image of the article.product_media
cover.media.IdUUID of the preview image of the article. A dot can be set behind media to access further fields within media.media
cover.positionPosition of the preview image in the media overview of the article.product_media
cover.customFieldsPreview image additional fieldcustom_field
cover.createdAtPreview image uploadedproduct_media
cover.updatedAtPreview image updatedproduct_media
deliveryTime.idUUID of delivery timedelivery_time
deliveryTime.nameName of the delivery timedelivery_time_translation
deliveryTime.customFieldsDelivery time additional fieldsdelivery_time_translation
deliveryTime.minMinimum delivery timedelivery_time
deliveryTime.maxMaximum delivery timedelivery_time
deliveryTime.unitDelivery time Unitdelivery_time
deliveryTime.translationsTranslations of the deliveryTime fields. A dot can be placed behind translations to access further fields.delivery_time_translation
deliveryTime.createdAtDelivery time createddelivery_time
deliveryTime.updatedDelivery time updateddelivery_time
eanEAN numberproduct
heightProduct heightproduct
IdUUID which is assigned by the system. This column should be left empty when creating new articles.product
isCloseoutSaleproduct
lengthLengthproduct
listingPricesExtended pricesproduct
manufacturer.idUUID of the manufacturerproduct_manufacturer
manufacturer.versionIdUUID which indicates the version of the manufacturer.product_manufacturer
manufacturer.linkManufacturer's websiteproduct_manufacturer
manufacturer.nameManufacturer's nameproduct_manufacturer_translation
manufacturer.descriptionManufacturer's descriptionproduct_manufacturer_translation
manufacturer.customFieldsManufacturer Additional fieldsproduct_manufacturer_translation
manufacturer.media.IdUUID of the manufacturer picture. A dot can be placed behind media to access further fields within media.media
manufacturer.translationsTranslations of the manufacturer fields. A dot can be placed behind translations to access further fields.product_manufacturer_translation
manufacturer.createdAtManufacturer createdproduct_manufacturer
manufacturer.updatedAtManufacturer updatedproduct_manufacturer
manufacturerNumberManufacturer's product numberproduct
markAsTopsellerPromote productproduct
maxPurchaseMaximum purchaseproduct
minPurchaseMinimal purchaseproduct
optionIdsVariant optionsproduct_option
optionsVariant optionsproperty_group_option
parentFields of the main product for variant articles. You can set a period after parent and thus access all fields that are also available in the Object Type Product.product
price.DEFAULT.netStandard net price. DEFAULT can be replaced by the respective currency. e.g. EURproduct
price.DEFAULT.grossStandard gross price. DEFAULT can be replaced by the respective currency. e.g. EURproduct
price.DEFAULT.currencyIdUUID of the currency. DEFAULT can be replaced by the respective currency. e.g. EURcurrency
price.DEFAULT.linkedIndicates whether the net and gross price are linked. DEFAULT can be replaced by the respective currency. e.g. EURproduct
price.DEFAULT.listPreiceExtended prices. DEFAULT can be replaced by the respective currency. e.g. EURproduct
productNumberProduct numberproduct
propertiesUUID of the properties separated by a pipe symbol (|).property_group_option
purchasePricePurchase priceproduct
purchaseStepsScalingproduct
purchaseUnitSales unitproduct
ratingAvarageAverage valuationproduct
referenceUnitBasic unitproduct
releaseDateRelease dateproduct
restockTimeRestock timeproduct
shippingFreeFree shippingproduct
stockStockproduct
tagIdsProduct tagsproduct_tag
tagsUUID of the tags, separated by a pipe symbol (|)product_tag
tax.IdUUID of the tax ratetax
tax.taxRatePercentagetax
tax.nameTax nametax.translate
tax.customFieldAdditional fieldscustom_field
tax.createdAtTax rate createdtax
tax.updatedATTax rate updatedtax
translations.DEFAULTAll language dependent product fields. DEFAULT can be replaced by the language and the respective field can be accessed by a subsequent dot. e.g. translations.en-GB.nameproduct_translation
unit.IdUUID of the measurement unitsunit
unit.shortCodeUnit of measurement Abbreviation    unit_translation
unit.nameUnit of measurement nameunit_translation
unit.customFieldsMeasurement unit Additional fieldsunit_translation
unit.translationsTranslations of the unit of measurement fields. A dot can be placed after translations to access further fields.unit_translation
unit.createdAtUnit of measurement created    unit
unit.updatedAtUnit of measurement updatedunit
variantRestrictionsExcluding variants from the variant generator    product
versionIdUUID which indicates the version of the article. product
visibilities.allUUID of the sales channel in which the article is completely availableproduct_visibility
visivilities.linkUUID of the sales channel in which the article is hidden and only accessible through the direct linkproduct_visibility
visibilities.searchUUID of the sales channel in which the article is only accessible by search.product_visibility
weightWeightproduct
widthWidthproduct



Customer

Database entryDescriptionDatabase table
activeIndication whether the customer is activecustomer
affiliateCodeAffiliate codecustomer
autoincrementUnique decimal numbercustomer
birthdayBirthdaycustomer
campaignCodeCampaign codecustomer
companyCompanycustomer
createdAtWhen was the customer createdcustomer
customFieldsCustomers additional fieldscustomer
customerNumberCustomer numbercustomer
defaultBillingAddress.idUUID of the billing addresscustomer
defaultBillingAddress.firstNameFirst name of Invoice addresscustomer_address
defaultBillingAddress.lastNameInvoice address surnamecustomer_address
defaultBillingAddress.zipcodeInvoice address postcodecustomer_address
defaultBillingAddress.cityInvoice address citycustomer_address
defaultBillingAddress.companyInvoice address companycustomer_address
defaultBillingAddress.streetInvoice address streetcustomer_address
defaultBillingAddress.departmentInvoice address departmentcustomer_address
defaultBillingAddress.titleInvoice address titlecustomer_address
defaultBillingAddress.vatIdInvoice address Tax-IdNr.customer_address
defaultBillingAddress.phoneNumberInvoice address phone numbercustomer_address
defaultBillingAddress.additionalAddressLine1Address suffix 1 of the invoice addresscustomer_address
defaultBillingAddress.additionalAddressLine2Address suffix 2 of the invoice addresscustomer_address
defaultBillingAddress.customFieldsAdditional fields of the invoice addresscustomer_address
defaultBillingAddress.customerCustomer fields of the invoice address. A dot can be placed after customer to access further fields.customer, customer_address
defaultBillingAddress.countryCountry fields of the invoice address. A dot can be set after country to access further fields.customer_address, country, country_translation
defaultBillingAddress.countryStateState fields of the invoice address. Behind countryState a dot can be set and thus further fields can be accessed.customer_address, country_state, country_state_translation
defaultBillingAddress.salutationSalutation fields of the invoice address. A dot can be placed after salutation to access further fields.customer_address, salutation, salutation_translation
defaultBillingAddress.createdAtWhen was the invoice address createdcustomer_address
defaultBillingAddress.updatedAtWhen was the invoice address updatecustomer_address
defaultPaymentMethod.idUUID of the standard payment typecustomer
defaultPaymentMethod.pluginIDUUID of the plug-in of the default payment methodpayment_method
defaultPaymentMethod.handleridentifierStorage location of the PaymentHandlerpayment_method
defaultPaymentMethod.nameName of the default payment methodpayment_method
defaultPaymentMethod.descriptionDescription of the default payment methodpayment_method
defaultPaymentMethod.positionPosition of the default payment typepayment_method
defaultPaymentMethod.activeSpecifies whether the default payment type is active.payment_method
defaultPaymentMethod.customFieldsAdditional fields of the default payment typepayment_method_translation
defaultPaymentMethod.formattedHandlerIdentifierShortened form of the HandlerIdentifierpayment_method
defaultPaymentMethod.translationsTranslations of the default payment method. A dot can be placed after translations to access additional fields.payment_method, payment_method_translation
defaultPaymentMethod.mediaFields of the payment method logo. A dot can be set behind media and thus access further fields within media.payment_method, media
defaultPaymentMethod.availabilityRuleFields of the payment type availability rule. You can set a point behind availabilityRule and thus access further fields.payment_method, rule
defaultPaymentMethod.pluginFields of the payment method plug-in. Behind the plugin a dot can be set and thus further fields can be accessed.payment_method, plugin
defaultPaymentMethod.salesChannelsSales channels in which the default payment method is stored, separated by a "pipe" symbol (|)payment_method
defaultPaymentMethod.createdAtWhen was the default payment type created?payment_method
defaultPaymentMethod.updatedAtWhen was the default payment method updated?payment_method
defaultShippingAddress.idUUID of the delivery addresscustomer
defaultShippingAddress.firstNameFirst name of delivery addresscustomer_address
defaultShippingAddress.lastNameSurname of delivery addresscustomer_address
defaultShippingAddress.zipcodePostcode of delivery address customer_address
defaultShippingAddress.cityPostcode of delivery addresscustomer_address
defaultShippingAddress.companyCompany of delivery address    customer_address
defaultShippingAddress.streetStreet of delivery addresscustomer_address
defaultShippingAddress.departmentDepartment of the delivery addresscustomer_address
defaultShippingAddress.titleDelivery address titlecustomer_address
defaultShippingAddress.vatIdTax ID number of the delivery addresscustomer_address
defaultShippingAddress.phoneNumberPhone number of the delivery addresscustomer_address
defaultShippingAddress.additionalAddressLine1Address suffix 1 of the delivery addresscustomer_address
defaultShippingAddress.additionalAddressLine2Address suffix 2 of the delivery addresscustomer_address
defaultShippingAddress.customFieldsAdditional fields of the delivery addresscustomer_address
defaultShippingAddress.customerCustomer fields of the delivery address. A dot can be placed after customer to access further fields.customer, customer_address
defaultShippingAddress.countryCountry fields of the delivery address. A dot can be set behind country to access further fields.customer_address, country, country_translation
defaultShippingAddress.countryStateState fields of the delivery address. Behind countryState a dot can be set and thus further fields can be accessed.customer_address, country_state, country_state_translation
defaultShippingAddress.salutationSalutation fields of the delivery address. A dot can be placed after salutation to access further fields.customer_address, salutation, salutation_translation
defaultShippingAddress.createdAtWhen was the delivery address createdcustomer_address
defaultShippingAddress.updatedAtWhen was the delivery address updatedcustomer_address
doubleOptInConfirmDateWhen was the doubleOptIn mail confirmed?customer
doubleOptInEmailSendDateWhen was the doubleOptIn mail send?customer
doubleOptInRegistrationWas doubleOptIn registration active during registration?customer
emailEmailcustomer
firstLoginFirst login of the customercustomer
firstNameFirst namecustomer
group.idUUID of the customer groupcustomer
group.nameCustomer group namecustomer_group
group.displayGrossTax representation of the customer groupcustomer_group
group.customFieldsCustomer groups additional fieldscustomer_group_translation
group.translationsTranslations of the customer group fields. A dot can be placed behind translations to access further fields.customer_group_translation
group.createdAtWhen was the customer group created?customer_group
group.updatedAtWhen was the customer group updated?customer_group
guestIs it a guest order?customer
hashHash value, which is used for the doubleOptIn confirmation mail,customer
IdUUID of the customercustomer
language.idUUID of the languagecustomer
language.nameName of the languagelanguage
language.customFieldsLanguage additional fieldslanguage
language.parentUUID of the language from which it is inherited.language
language.localeFields of language localization. A dot can be placed after locale to access further fields.language, locale, locale_translation
language.translationCodeISO code fields of the language. A dot can be placed after translationCode to access further fields.language, locale, locale_translation
language.salesChannelsUUID of the sales channels where the language is used.language
language.createdAtWhen was the language createdlanguage
language.updatedAtWhen was the language updatedlanguage
lastLoginLast login of the customercustomer
lastNameSurnamecustomer
lastOrderDateDate of the last ordercustomer
lastPaymentMethodsFields of the last payment method. A dot can be set behind lastPaymentMethods to access additional fields.customer, payment_methods, payment_methods_translation
legacyEncoderEncoder to decrypt foreign system passwordcustomer
legacyPasswortEncrypted password from another system, e.g. after a migrationcustomer
newsletterHas the customer opted in to the newsletter?customer
orderCountNumber of orderscustomer
passwordEncrypted hash value of the passwordcustomer
remoteAddressCustomer's IP addresscustomer
salesChannel.idUUID of the sales channel to which the customer is assignedcustomer
salesChannel.type.Fields for the sales channel type. A dot can be placed after type to access further fields.sales_channel, sales_channel_type, sales_channel_type_translation
salesChannel.language.Fields for the language of the sales channel. A dot can be placed after language to access further fields.sales_channel,
language,
language_translation
salesChannel.customerGroup.Fields for the standard customer group of the sales channel. After customerGroup, you can set a period and thus access further fields.sales_channel, customer_group, customer_group_translation
salesChannel.currencyFields for the default currency of the sales channel. You can set a period after currency to access other fields.sales_channel, currency, currency_translation
salesChannel.paymentmethodFields for the standard payment type of the sales channel. You can set a point after paymentmethod to access further fields.sales_channel, payment_method, payment_method_translation
salesChannel.shippingMethodFields for the standard shipping type of the sales channel. You can set a period after shippingMethod to access additional fields.sales_channel, shipping_method, shipping_method_translation
salesChannel.countryFields for the default country of the sales channel. You can set a period after country to access other fields.sales_channel, country, country_translation
salesChannel.navigationCategoryFields for the category that is defined as the entry point for the main navigation of the sales channel. You can set a point behind navigationCategory to access additional fields.sales_channel, category, category_translation
salesChannel.navigationCategoryDepthMain navigational levelssales_channel
salesChannel.footerCategoryFields for the category that is stored as the entry point for the footer navigation of the sales channel. You can set a point after footerCategory to access additional fields.sales_channel, category, category_translation
salesChannel.serviceCategoryFields for the category that is defined as the entry point for the service navigation of the sales channel. You can set a point after serviceCategory to access additional fields.sales_channel, category, category_translation
salesChannel.mailHeaderFooterfields for the header and footer template of the sales channel is stored. Behind mailHeaderFooter a dot can be set and thus further fields can be accessed.sales_channel, mail_header_footer, mail_header_footer_translation,
salesChannel.nameName of the sales channelsales_channel
salesChannel.shortNameSales channel abbreviationsales_channel
salesChannel.accessKeyAPI accesssales_channel
salesChannel.configurationConfig entries for the sales channelsales_channel
salesChannel.activeSpecifies whether the sales channel is activesales_channel
salesChannel.maintenanceMaintenance modesales_channel
salesChannel.maintenanceWhiteListMaintenance mode whitelistsales_channel
salesChannel.customFieldsSales channel additional fieldssales_channel_translation
salesChannel.translationsTranslations of the sales channel fields. A dot can be placed after translations to access further fields.sales_channel_translation
salesChannel.currenciesSales channel currenciessales_channel_currency
salesChannel.languagesSales channel languagessales_channel_language
salesChannel.countriesSales channel countriessales_channel_country
salesChannel.paymentMethodsSales channel payment methodssales_channel_payment_method
salesChannel.shippingMethodsSales channel shipping methodssales_channel_shippingMethod
salesChannel.createdAtWhen was the sales channel createdsales_channel
salesChannel.updatedAtWhen was the sales channel updatedsales_channel
salesChannel.themesWhich theme is assigned to the sales channeltheme_sales_channel
salutation.idUUID of the salutation     
salutation.salutationKeyTechnical name of the salutationsalutation
salutation.displayNameName of the salutationsalutation_translation
salutation.letterNameAddress by lettersalutation_translation
salutation.translationsTranslations of the salutation fields. A dot can be placed after translations to access additional fields.salutation, salutation_translation
salutation.createdAtWhen was the salutation createdsalutation
salutation.updatetAtWhen was the salutation updatedsalutation
tagsCustomer tagscustomer_tag
titleTitlecustomer
updatedAtWhen was the customer updatedcustomer



Category

Database entryDescriptionDatabase table
activeIndicates whether the category is activecategory
afterCategoryIdUUID of the category before this categorycategory
afterCategoryVersionIDVersion of the category before this categorycategory
autoincrementUnique decimal numbercategory
childCountNumber of subcategoriescategory
cmsPage.idUUID of the deposited shopping experiencescategory
cmsPage.nameName of the deposited shopping experiencescms_page_translation
cmsPage.typeLayout Type of the stored shopping experiencescms_page
cmsPage.customFieldsShopping experiences Additional fieldscms_page_translation
cmsPage.lockedShopping experiencesmay not be edited.cms_page
cmsPage.translationsA dot can be placed behind translations to access additional fields.cms_page, cms_page_translation
cmsPage.previewMediaFields for preview picture of the world of experience. Behind previewMedia a dot can be set and thus further fields can be accessed.cms_page, media
cmsPage.createdAtWhen was the shopping experiences createdcms_page
cmsPage.updatedAtWhen was the shopping experiences updatedcms_page
idUUID of the categorycategory
levelCategory levelcategory
mediaFields of the category display image. A dot can be placed after media to access further fields.category, media
parentFields of the parent category. A dot can be placed after parent to access further fields.category, category_translation, media
pathPath to categorycategory
productsUUID of the products deposited in the category, separated by fine "Pipe" symbol (|)product_category
tagsCategory tagscategory_tag
translations.DEFAULT

e.g.
translations.de_DE.name
translations.de_DE.description
translations.en_GB.keywords
All Language dependent category fields. DEFAULT can be replaced by the language and the respective field can be accessed by a subsequent period. For instance translations.en-GB.namecategory, category_translation
typeCategory typecategory
versionIdUUID which indicates the version of the category.category
visibleHide in the navigationcategory



Media

Database entryDescriptionDatabase table
avatarUserFields for the user to which this picture is assigned as avatar. Behind avatarUser a dot can be set and thus further fields can be accessedmedia
fileExtensionFile extensionmedia
fileNameFile namemedia
fileSizeFile sizemedia
idUUID of the media filemedia
mediaFolder.childCountNumber of subfoldersmedia_folder
mediaFolder.configuration.createThumbnailsGenerate thumbnails for this foldermedia_folder_configuration
mediaFolder.configuration.createdAtWhen were the folder settings created.media_folder_configuration
mediaFolder.configuration.customFieldsAdditional fields for the folder settingsmedia_folder_configuration
mediaFolder.configuration.idUUID of the configurationmedia_folder
mediaFolder.configuration.keepAspectRationKeep aspect ratiomedia_folder_configuration
mediaFolder.configuration.mediaThumbnailSizesThumbnail sizemedia_folder_configuration
mediaFolder.configuration.thumbnailQualityThumbnail qualitymedia_folder_configuration
mediaFolder.configuration.updatedAtWhen were the folder settings updatedmedia_folder_configuration
mediaFolder.createdAtWhen were the folder createdmedia_folder
mediaFolder.customFieldsMedia folder additional fieldsmedia_folder
mediaFolder.defaultFolderfields to the default location. Behind defaultFolder a dot can be set and thus further fields can be accessed.media_folder, media_default_folder
mediaFolder.idUUID of the folder where the media file is locatedmedia
mediaFolder.nameFolder namemedia_folder
mediaFolder.parentFields to the folder above this folder. A dot can be placed after parent to access further fields.media_folder
mediaFolder.updatedAtWhen the folder was updatedmedia_folder
mediaFolder.useParentConfigurationAdopt settings from the superordinate foldermedia_folder
mediaTpeMedia typmedia
metaDataMeta data of the mediamedia
mimeTypeInternet media typemedia
tagsMedia tagsmedia_tags
translations.DEFAULT'

e.g.
translations.de-DE.alt
translations.de-DE.title
All language dependent media fields. DEFAULT can be replaced by the language and the respective field can be accessed by a subsequent period. For instance translations.en-GB.old 
uploadedAtWhen the media file was uploadedmedia
urlURL to the media filewird generiert
user.Fields of the user who uploaded the media file A dot can be set after user to access further fields.user



Newsletter recipients

Database entryDescriptionDatabase table
cityCity of newsletter recipientnewsletter_recipient
confirmedAtWhen was the newsletter recipient confirmednewsletter_recipient
createdAtWhen was the newsletter recipient creatednewsletter_recipient
customFieldsAdditional fields of the newsletter recipientsnewsletter_recipient
emailEmail of the newsletter recipientnewsletter_recipient
firstNameFirst name of the newsletter recipientnewsletter_recipient
hashHash value to confirm the newsletter recipientnewsletter_recipient
idUUID of the newsletter recipientnewsletter_recipient
languageFields for the language of the newsletter recipient. A dot can be placed behind language to access further fields.newsletter_recipient, language, 
salesChannelFields of the sales channel in which the newsletter recipient is registered. Behind salesChannel a dot can be set and thus further fields can be accessed.newsletter_recipient, sales_channel
salutationfields of the salutation of the newsletter recipient is registered. A dot can be placed behind salutation to access further fields.newsletter_recipient, salutation
statusStatus of newsletter recipientnewsletter_recipient
streetStreet of the newsletter recipientnewsletter_recipient
tagsTags of the newsletter recipientnewsletter_recipient_tag
titleTitle of newsletter recipientnewsletter_recipient
updatedAtWhen was the newsletter recipient updatednewsletter_recipient
zipCodePostcode of the newsletter recipientnewsletter_recipient



Properties

Database entryDescriptionDatabase table
colorHexCodeColor code of the color stored in the property.property_group_option
group.displayTypeDisplay of the characteristic selectionproperty_group
group.idUUID of the property groupproperty_group
group.sortingTypeSorting the property groupproperty_group
group.translations.DEFAULT


e.g.
group.translations.de-DE.description
group.translations.en-GB.
All language-dependent fields of the property group. DEFAULT can be replaced by the language and the respective field can be accessed with a subsequent period. For instance group.translations.en-GB.descriptionproperty_group_translations
idUUID of the property valueproperty_group_option
mediaFields of the default picture of the property profile. A dot can be placed after media to access other fields.property_group_option,
media
productOptionsUID of the variants that use this property valueproduct_option
productPropertiesUUID of the products to which this property value has been assigned as a property. product_property
translations.DEFAULT

e.g.
translations.de-DE.name
translations.en-GB.position
All language-dependent fields of the property value. DEFAULT can be replaced by the language and the respective field can be accessed with a subsequent period. For instance, translations.en-GB.nameproperty_group_option_translation



Variant configuration

Database entryDescriptionDatabase table
createdAtWhen was variant configuration createdproduct_configurator_setting
customFieldsVariant configuration of additional fieldsproduct_configurator_setting
isUUID of variant configurationproduct_configurator_setting
mediaMedia fields of the property pictures from the storefront viewproduct_configurator_setting
option.idUUID of the property valueproperty_group_option
option.groupFields of the property group of the property attribute. You can set a period after group and thus access other fields.property_group_option, property_group
option.IdUUID of the property valueproperty_group_option
option.mediaFields on the screen for the characteristic value.
A dot can be placed after media to access other fields.
property_group_option, media
option.productOptionsUUID of variants that use this optionproduct_option
option.propertiesUUID of the products to which this option has been assigned as a property.product_property
option.translations.DEFAULT

e.g.
translations.de-DE.name
translations.en-GB.position
All language-dependent fields of the property value. DEFAULT can be replaced by the language and the respective field can be accessed with a subsequent period. For instance, translations.en-GB.nameproperty_group_option_translation
positionPosition in the storefront displayproduct_configurator_setting
price.DEFAULT.netNet surcharge. DEFAULT can be replaced by the respective currency. For instance EURproduct_configurator_setting
price.DEFAULT.grossGross mark-up. DEFAULT can be replaced by the respective currency. For instance EURproduct_configurator_setting
price.DEFAULT.currencyIdUUID of the currency. DEFAULT can be replaced by the respective currency. For instance EURproduct_configurator_Setting, currency
price.DEFAULT.linkedIndicates whether the net and gross price are linked. DEFAULT can be replaced by the respective currency. For instance EURproduct_configurator_setting
price.DEFAULT.listPreiceExtended prices. DEFAULT can be replaced by the respective currency. For instance EURproduct_configurator_setting
productFields of the product to which variant configuration is assignedproduct_configurator_setting
updatedAtWhen was variant configuration updatedproduct_configurator_setting
 

Import variants

The following 4 steps are necessary to import variants: 

Importing products

In the attached CSV file you enter the new products. Leave the column id and parent_id empty. These are generated by the system or are not required in this case. Then import this file in the Import/Export module with the default product profile.

Default product profile.csv
 

Importing properties

The next step is to import the properties on the basis of which the variants are to be created. If you have already created the properties you want to use, you can skip this step. 

You can use the attached CSV file to import new properties. Leave the id column empty so that it is generated during the import. In the column group_id you enter the UUID of the property group. You can find this in the address line of the browser when you call up the property group in the Shopware Admin.
 
Alternatively, you can also get them if you export the properties using the default properties profile.

If you leave this column empty, the property group will also be recreated by the import and a UUID will be created for this group. Once you have filled the CSV file, import it in the Import/Export module with the default properties profile.

Default properties profile.csv
 

Import variant configuration

Once products and properties are available, they must be linked in the form of variant configurations in order to be able to create the variants in a later step. In the attached CSV file you enter the option_id. This is the automatically created UUID of the properties. You will get this ID if you export the properties from the last step again. 
Then enter the product_id. This is the UUID of the main products for which variants are to be created. You can find this in the address bar of your browser when you call up the products in the Shopware Admin.
 

Alternatively, you can also get them if you export the properties using the default variant configuration settings profile

Just leave the id column blank and import it in the Import/Export module with the default variant configuration settings profile.

default variant configuration settings profile.csv
 

Generate variants

With the previous steps you have prepared the variants so far that you now just need to generate them. 
Open the product for which you have imported the variants in the Shopware Administration and open the tab generate variants, click on generate variants (1).
 

In the window that opens, click on generate variants (1).
 

Was this article helpful?