NOTE: The manual is for the MVP version of the application.

Performance

• Maximum number of imported rows: 300000
• Maximum number of exported rows: 300000
• Number of import jobs that can be launched simultaneously: 3
• Number of export jobs that can be launched simultaneously: 3
• File Limit for URL & Manual Uploads: 200Mb

Installation

The application can only be installed through your Shopware 6 backend via your Shopware Account, whether you’re using an on-premise or cloud installation.

1. Log into your store’s backend and proceed to Extensions > Store.
2. Log into your Shopware Account.
3. Search for Improved Import, Export & Mass Actions.
   
4. Click on the Improved Import, Export & Mass Actions application
   
5. Click the “Add extension” button
   
6. Tick in the checkboxes and click the “Subscribe to extension” button.

Installation Troubleshooting

Find the extension

How to import data

In the following section, we’ll guide you through the process of importing data into Shopware 6 using the Improved Import, Export & Mass Actions app.

NOTE:

1. In the current version, system properties available for Shopware products by default cannot be excluded from the import mapping.
2. To disable a product during import, the ‘Active’ product property should be left empty.

Also, check our Shopware 6 Master Table for more detailed examples of importable tables.

Step 1: Select File

Your very first step with Improved Import, Export & Mass Actions consists of the following activities:

1. Name your profile; 
2. Select an entity you want to import (e.g., products or customers);
3. Create a schedule of updates.
   Turn on the toggle(1), choose your time zone(2) (you can type in the city instead of scrolling), specify your starting frequency(3) (every hour, day, week, or month), and configure additional parameters(4) (such as the exact time if you choose daily update or day and time if you decide to update once per week).
   
4. Configure email notifications;
   1. Enable the notification toggle.
   2. Choose your notification type: succeed, failed, or succeed and failed jobs.
   3. Specify an email address to send notifications to.
   4. Select the encryption.
   5. Specify the host for your email address.
   6. Type the port.
   7. Specify a sender’s username (an email address).
   8. Provide the corresponding password.
   9. You can attach job logs to the notification emails. However, they may be huge in size.
      
5. Select the file you want to import. The app currently supports CSV, XML, and XLSX file formats.
   Additionally, you can specify the delimiters used in the CSV file manually, or click the “Auto detect delimiter” checkbox and let the extension do the job.
   
6. Choose an import source (e.g., file, FTP, URL, Google Drive). If you provide a file via FTP, follow these steps:
   1. Specify your host;
   2. Enable/disable SSL;
   3. Specify your port;
   4. Provide a user email to get access to the remote file source;
   5. Specify the corresponding password;
   6. Type the remote path to your update file;
   7. Test the connection to make sure you’ve provided the correct credentials.
      For Google Drive, let Improved Import, Export & Mass Actions use all permissions and specify a full file name with its extension, e.g., “pe5.1.xlsx”, stored in the “shopware-import-export” folder. Read more about the Shopware 6 Google Drive integration here: How to Import Files from Google Drive to Shopware 6.
      
      You can also import data from Google Sheets. It is necessary to select the corresponding file type and source and specify a link to your Google Sheets table. You can find more information here: How to Import Data to Shopware 6 from Google Sheets.
      
      Good old URL imports are possible too. Just select “URL” as your import source. Next, specify a public URL where your update is stored, for example, https://example.com/download-me. You can find more information here: Shopware 6 Import From URL.
      
   8. Configure advanced settings that include:
      1. URL rewrite behavior; 
      2. media replacement behavior;
      3. advanced price replacement behavior;
      4. stock increment strategy;
      5. data transformation.

URL rewrite behavior: 

• Display Warnings: When selected, the app alerts you if there are duplicate URLs in the imported file. If an imported product shares a URL with an existing product on your website, the app generates a new URL based on the product name.
• Increment Duplicate: With this option, the app imports products with duplicate URLs but modifies their URLs to follow the format “existing_url-n+1,” where “n” represents the duplicate number (starting at “0” for the first duplicate, resulting in “existing_url-1” after import).
• Force Overwrite: This option assigns the existing URLs to the imported products if duplicates are found in the import file. As a result, the imported products retain the existing URLs, while the original products are left without URLs.

Replace media:

Replace Advanced Prices:

Enable this option to overwrite the existing advanced prices of products on your website with those specified in your CSV file.

To combine the existing price tiers with the imported ones, keep the Replace Advanced Prices feature disabled.

Stock increment strategy: 

• If Disabled: The product quantity is updated to match the quantity specified in the import file. For example, if your store’s current quantity is 100 and the import file specifies 50, the store quantity will be updated to 50 after the import.
• If Enabled: The product quantity is increased by the amount specified in the import file. For instance, if the current quantity is 100 and the import file specifies 50, the store quantity will be updated to 150 after the import.

When this feature is enabled, a Reload Product Before Update toggle appears:

• If Disabled: The quantity is updated immediately, following the selected stock increment strategy, without reloading the product data.
• If Enabled: The product data is reloaded first, and then the quantity is updated according to the selected stock increment strategy

Data Transformation is described separately below.

Note that for XML import to Shopware 6 your file structure should be organized as follows:

Where column names (attributes or properties) are stored between <item> and </item>.

Additionally, the latest release of our app includes an XPath input feature for specifying data paths in XML files. This allows you to select relevant data structures, such as products or customers, with greater precision.

MIME Type

If you import an unsupported file, the app displays the following error:

Failed! Bad url. mime/type mismatch or max size exceeds

Step 2: Configure mapping

Shopware requires product properties to have specific names so the system can recognize them correctly. To accommodate this, we’ve made it possible for you to import files with property names that differ from Shopware’s naming conventions. This is where the mapping section comes into play:

• The first row displays the property names from the file you are importing.
• The second row allows you to select the corresponding properties from your Shopware store.

By matching these properties, you can import files with any naming format.

If your updates involve product variants, the mapping screen offers additional options. Here, you can choose to assign variants using either the parent product’s SKU or ID. You can also decide whether to add new variants to the existing ones or completely replace the old variants. This flexibility allows you to manage your products according to your specific needs and preferences.

Mapping templates

What are product properties and how to work with them

Each Shopware 6 product has multiple fields, such as ‘Name,’ ‘Product Number,’ and ‘Manufacturer.’ These fields are known as product properties or attributes. Each property is associated with a database entity where its values are stored, and each has a dedicated internal name that doesn’t allow spaces.

When importing products, you’re directly interacting with the database, so it’s crucial to use the exact names of these properties as they appear in the database. For example, the Manufacturer is stored as ‘manufacturer_id,’ and the Product Number is stored as ‘product_number.’ You can refer to an exported file to see how these properties are named.

This is important because, during the import process, the column names in your file must match the internal names of the product properties in Shopware. This ensures that the extension correctly maps the imported values to the appropriate properties.

This is where the Mapping section of the Improved Import, Export & Mass Actions app comes into play.

For instance, if your supplier, Microsoft, sends you a CSV file with products labeled as ‘microsoft_product_number’ and ‘microsoft_name’ instead of the standard ‘product_number’ and ‘name,’ you can use the Mapping section to align these custom names with Shopware’s internal property names

Step 3: Preview results

The “Preview Result” section lets you review the first 100 rows from the imported file. Once you’ve checked the results and everything looks good, you can proceed with the import procedure.

Final step: Import

When you click the “Import” button at the bottom of the Preview result step of the import, the extension starts importing the file you have uploaded.

During the import process, you’ll see the number of imported products, excluding child products of configurable items, as well as the average import time.

Once the process is complete, you can review the products you’ve imported into your Shopware 6 store.

Import Cross-Selling Data

Preparation

Before importing Shopware 6 cross-selling data, make sure you have:

1. Created the products you want to link through cross-selling
2. Created any necessary product dynamic groups for the “Dynamic Product Group” type
3. Prepared your import file with all required fields

Import Process

To import cross-selling data:

1. Go to Extensions > Improved Import, Export > Import and create a new profile
2. Select “cross selling” as your import entity type
3. Choose your import source (CSV, XML, Google Sheets, etc.)
4. Map the fields from your source file to Shopware fields
5. Run the import

Field Reference Table for Cross-Selling Import

Master table: https://docs.google.com/spreadsheets/d/1h3cDhYkSL9tisi0c0X3Okn5jQkMDQkRbPqzWp-c3Pyg/edit?gid=59713951#gid=59713951

Import Logic and Requirements

1. Identification and Updates:
   • You can update existing cross-selling entries by either:
     • Providing the id field
     • Providing both productId (or productNumber) and name fields
2. Type-Specific Requirements:
   • For productList type:
     • The assignedProducts field is required
     • Product numbers must be separated by “|” (configurable in Import Profile settings)
     • Products must exist in the system
   • For productStream type:
     • Either productStreamId or productStreamName is required
     • The product stream (productStreamName) must exist in the system (automatic creation not supported)
3. Field Validations:
   • sortBy accepts: “name”, “price”, “releaseDate”, “productNumber”
   • sortDirection accepts: “ASC”, “DESC”
   • position and limit must be numeric values
   • active accepts boolean values (true/false, 1/0)
4. Special Features:
   • Updates to existing entries completely replace previously assigned products
   • The system automatically resolves productId from productNumber if needed
   • The system automatically resolves productStreamId from productStreamName if needed

Different Data Formats for Shopware 6 Import 

The Improved Import, Export & Mass Actions app allows you to transfer various types of product data to Shopware 6, including standard fields, custom fields, translations, and properties. Each data type follows a specific format, as described below.

System Properties

Each Shopware 6 product is defined by multiple fields, such as “Name”, “Product Number”, and “Manufacturer.” These fields, also known as product properties or attributes, are stored in the database with specific internal names that do not allow spaces.

When importing products, you are directly interacting with the database, so it’s crucial to use the exact names of these properties as they appear in the database. For example, “Manufacturer” is stored as “manufacturer_id“, and Product Number is “product_number“. You can refer to an exported file to see how different properties are named.

This is essential because when importing, the column headers in your file must match the internal names of product properties in Shopware to ensure that the data is correctly mapped to the corresponding fields.

Custom Properties

By default, Shopware 6 exports products without including any custom properties you’ve added, such as “Size” or “Color”. This means custom properties won’t be part of the exported product data. While you can export custom product properties as a separate entity, this export won’t include references to the products they’re assigned to, making it difficult to re-import products with their associated custom properties.

The Improved Import, Export & Mass Actions app solves this issue by allowing you to export custom properties along with your products in a format that includes both the database ID of the custom property and the name displayed in the store’s backend for easy reference.

In the exported file, custom properties are formatted like this: color#0bde8db993684f8b92a713913aa3d9c3, where:

• color is the name of the property as displayed in the Shopware 6 backend.
• #0bde8db993684f8b92a713913aa3d9c3 is the property’s unique ID in the database.

When importing products with custom properties, you can use three different formats for column names:

• property_name#property_id – the default format as it appears in the export file.
• property_name – using only the name of the property as it appears in the Shopware 6 admin panel.
• #property_id – using only the property’s ID, preceded by the # symbol.

During the import process, you need to map all custom properties in your file by selecting the corresponding “propertiesSources” option in the dropdown for each property. This step ensures that Shopware correctly recognizes and processes the custom properties, regardless of the order or format used.

Using both the property name and ID is important because Shopware 6 allows you to create multiple custom properties with the same name. The property ID, which is always unique, helps distinguish between similarly named properties.

If you want to add translations to your custom properties, use this column title format: 

[language code].[property_name#property_id]

Where: 

• language code is the locale of the language you provide translation for, e.g., en_GB, en_US, de_DE, de_CH, etc.
• property_name is the name of the property as displayed in the Shopware 6 backend.
• property_id is the property’s unique ID in the database.

For instance, you can translate the Material custom property with the ID #a67cdd9627cb488bb4cd91f3e8d66e32 to German by adding the following column to your CSV file: de-DE.Material#a67cdd9627cb488bb4cd91f3e8d66e32.

Custom Fields

For Firebear imports, all custom field names must begin with “cf_“. Following this prefix, include the technical name of the custom field.

For instance, to import data associated with the custom_test_text_field custom field, you need to add the cf_custom_test_text_field column to your CSV.

Translations

When importing translations to Shopware, the CSV file should include specific column headers that indicate the language and type of translation. Use this general format to name your columns:

translations.[language code].[original column title]

Where:

• language code is the locale of the language you provide translation for, e.g., en_GB, en_US, de_DE, de_CH, etc.
• original column title is the name of a column associated with the translations you import, e.g., name or keywords. 

For example, to import English keywords, you would use the column header “translations.en_GB.keywords“, while for German product names, the column header should be “translations.de_DE.name“. 

Each column should be followed by the corresponding translated content, ensuring that the language code (e.g., en_GB for British English and de_DE for German) matches the translations you’re importing. This format ensures that our app correctly associates each translation with the appropriate language and content type.

You can also import translations for your custom fields. Add a column with this format: 

translations.[language code].cf_[custom_field_technical_name]

Where:

• language code is the locale of the language you provide translation for, e.g., en_GB, en_US, de_DE, de_CH, etc.
• custom_field_technical_name is the technical name of a custom field.

For instance, you can import German translations for your custom test text editor custom field with the help of the translations.de_DE.cf_custom_test_text_editor column.

Importing a New Product in Shopware 6.5:

• When importing a custom attribute of the ‘cf_’ type, values are successfully imported for all languages, not just the main language.
• There are no translation columns for custom attributes of the select type, so translations for these cannot be imported.
• Similarly, there are no translation columns for custom price attributes, preventing the import of translations for these as well.
• For custom attributes like checkboxes and active switches, the same value is imported across all languages, even if different values are specified in the import file.

Updating a Product in Shopware 6.5:

• If you update the select attribute in the ‘cf_’ column, it is only updated in the main language; other languages are not affected.
• Updating the price attribute in the ‘cf_’ column also only affects the main language.
• For checkboxes and active switches, if you specify different values for different languages, the import will maintain those distinct values without resetting or updating them to match the main language.
• For custom attributes such as text fields, date/time, number fields, media fields, color pickers, and text editors, you can successfully import translations and unique values for the custom field both when importing a new product and during updates.

Importing a New Product in Shopware 6.4:

• When importing a custom attribute of the ‘cf_’ type, values are imported only for the main language; other languages are not included.
• There are no translation columns for custom attributes of the select type, so translations cannot be imported.
• For custom attributes like checkboxes and active switches, different values are imported for different languages if specified in the import file.

Updating a Product in Shopware 6.4:

• If you update the select attribute in the ‘cf_’ column, it is only updated in the main language, with no changes in other languages.
• For checkboxes and active switches, if different values are specified for different languages, the import process will maintain these values across languages, rather than resetting them to the main language’s value.
• For custom attributes such as text fields, date/time, number fields, media fields, color pickers, and text editors, you can import translations and unique values for the custom field both when importing a new product and during updates.

In both versions, Shopware allows for flexible import and update processes, but with different capabilities regarding language support and translation of custom attributes.

Delivery Time

You can import delivery time fields into Shopware 6 using three different methods:

1. By ID: If all delivery times are already created in Shopware, you can import them using the “delivery_time_id” column in your import file.
2. By Name: If the delivery times are already set up in your store, but you don’t want to look up all the IDs, you can import them using the “delivery_time_name” column. The app will automatically find the existing ID based on the name and attach it to the product.
3. Creating New Delivery Times: To create a new delivery time during import, use four columns: “delivery_time_name“, “delivery_time_min“, “delivery_time_max“, and “delivery_time_unit” to fully describe the new delivery time.

You can find an example in the following table:

Advanced Pricing

It is possible to import advanced pricing to Shopware 6 as a part of your product update. The corresponding information can be added to a product CSV in the “advanced_prices“ column. 

The value in this column should look as follows:

ruleId:046ca0774ef543d8b606c2e2cfd0d43d,currencyId:b7d2554b0ce847cd82f3ac9bd1c0dfca,priceNet:0.8,priceGross:0.8,quantityStart:6,quantityEnd:|ruleId:046ca0774ef543d8b606c2e2cfd0d43d,currencyId:b7d2554b0ce847cd82f3ac9bd1c0dfca,priceNet:0.9,priceGross:0.9,quantityStart:3,quantityEnd:5|ruleId:046ca0774ef543d8b606c2e2cfd0d43d,currencyId:b7d2554b0ce847cd82f3ac9bd1c0dfca,priceNet:1,priceGross:1,quantityStart:1,quantityEnd:2

This complex value consists of attributes and values that describe multiple rules or price tiers. Tiers are separated by a pipe (“|”), and the attributes within each tier are separated by a comma (“,”).

The value above represents the following three price tiers:

1. The price is 1 Euro if a customer orders 1-2 items.
2. The price is 0.9 Euro if a customer orders 3-5 items.
3. The price is 0.8 Euro if a customer orders 6 or more items

Below, you’ll find a description of each advanced pricing import attribute for Shopware 6.

Note that you can replace the existing advanced prices with the ones specified in your CSV by activating the Replace Advanced Prices feature.

SEO URLs

Every successful website needs to address SEO URLs, and Shopware provides built-in SEO URL functionality to streamline your optimization efforts. The platform supports SEO URLs for both products and categories. While Shopware doesn’t natively support importing SEO URLs, our Improved Import, Export & Mass Actions app fills that gap.

Since you can add multiple custom SEO URLs for different store languages, your CSV file with product updates can include several columns for SEO URLs. Each Shopware 6 SEO URL attribute must start with “seo_url_#”, followed by the sales channel ID and the language ID, as shown in this example:

seo_urls_#1d51345c01af4236aba1b71ffa95453f#2fbb5fe2e29a4d70aa5854ce7ce3e20b

Be sure to use “#” to separate the sales channel ID from the language ID.

The attribute value can include any characters and spaces, allowing you to enter SEO-friendly URLs for your Shopware update, such as “seo-friendly-product-page”.

Below is an example of Shopware 6 SEO URL attributes and values ready for import, as outlined in our Google Sheets Master Table:

EAN Product Import (Alternative to SKU) 

We’ve introduced the ability to import products using the EAN (European Article Number) as an alternative to SKU (product_number). This feature allows you to update existing products, but please note that new products cannot be created using the EAN.

Additionally, the product_number can also be updated during import using EAN. If you do not wish to update the product_number, ensure it is not mapped or included in your import file.

All product attributes available for import can be updated using the EAN, with the exception of tags and SEO URLs – these can only be updated using the product_number. It means that you need both the ean and product_number columns to update ALL product attributes.

To update products in Shopware 6 with the help of EAN, add the ean column to your CSV file:

Create a new import profile and configure its basic settings. Next, choose EAN instead of SKU in the Lookup Attribute section on the mapping screen:

Configure other parameters and import the update. 

Data Transformation

The new feature introduces a script editor window available at the first step of the import process. This editor allows customers to write and apply scripts to modify rows of imported files directly. In other words, it is possible to edit attribute values with the help of a custom script. 

Key Functionalities

• Script Input: Users can access the editor and write scripts to modify data using the variable $row, which represents the row being processed.
• Function Whitelisting: For security purposes, only a limited set of PHP functions is allowed in the editor. These functions enable common string, array, and mathematical operations, ensuring users can perform common modifications without compromising system security.
  

Allowed PHP Functions

Example Use Cases

With the new feature, you can apply the following modifications to the imported data right in your Shopware 6 administration:

• Manufacturer Name: Remove extra $ symbols from any values.
• Options: Strip out spaces and replace ; with |.
• Stock: Increase all values by 10.
• Price Modification: If price_gross and list_price_gross are 0, set them as net * 1.19.
• Keywords: Replace , with |.
• Meta Title: Concatenate meta_title and name columns.

General Format for the $row Script

In the context of the feature allowing users to write scripts for row modification, the general format of the script involves processing each row of data through the variable $row, which is an associative array. Each key in the $row array represents a column or field from the imported data, and the corresponding value holds the actual data for that field.

Here’s how the general format can be structured:

1. Accessing Row Data:

Each column in the row is accessed using its key in the $row array.
$manufacturerName = $row[‘manufacturer_name’]; // Access the ‘manufacturer_name’ field

2. Modifying Row Data:

You can modify the data by updating the corresponding key in the $row array.
// Remove any extra $ symbol from the manufacturer name

$row[‘manufacturer_name’] = str_replace(‘$’, ”, $row[‘manufacturer_name’]);

3. Using Allowed PHP Functions:

The script can only use PHP functions from the predefined whitelist, which covers common operations like string manipulation, math, array handling, and date functions.

Example using string manipulation:
// Convert a string to lowercase

$row[‘options’] = strtolower($row[‘options’]);

4. Conditionally Modifying Data:

You can add logic to check conditions and modify values accordingly.
// Increase stock by 10 if it’s greater than 0

if (isset($row[‘stock’]) && $row[‘stock’] > 0) {

    $row[‘stock’] += 10;

}

5. Performing Calculations:

Calculations can be performed on numerical data in the row.

// If price_gross is 0, set it as net * 1.19

if (isset($row[‘price_gross’]) && $row[‘price_gross’] == 0) {

    $row[‘price_gross’] = $row[‘net’] * 1.19;

}

6. Returning the Modified Row:

After performing all modifications, the script doesn’t need to explicitly return anything as the $row is passed by reference, meaning changes to the $row will automatically reflect in the system.

Example of a Full Script

Key Points

• $row is an associative array where each key represents a field/column of the row.
• You can access and modify the row data using $row[‘column_name’] where column name is an actual column name from the imported file.
• Only a whitelist of PHP functions is allowed, ensuring the script stays secure.
• The modifications made to $row are automatically reflected in the import process.

By following this general format, you can write flexible and secure scripts for row modifications within the constraints of the whitelisted functions.

Product Import Field Reference

In this section, you’ll find a comprehensive reference table that details the key fields involved in importing product data into Shopware 6. Each row in the table provides essential information, including the field name as it appears in the Shopware interface, the corresponding system field name, a brief description of the field’s purpose, and an example value to guide your data formatting. This table is designed to help you accurately map and configure your product import files, ensuring a smooth and error-free import process.

Customer Import Field Reference

This section includes a detailed reference table outlining the fields required to import customer data into Shopware 6. The table lists each field name as it appears in the Shopware interface, along with the corresponding system field name, a description of its function, and an example value to help you correctly format your data. This resource is designed to assist you in accurately mapping and configuring your customer import files, ensuring that your customer data is imported smoothly and efficiently.

How to export data

Exporting data is straightforward and efficient. To begin, you’ll select the entity you want to export, choose the output file type, and specify the export destination. From there, you can configure the mapping to ensure the data is structured correctly and apply any necessary filters. Once everything is set, simply hit the ‘Export’ button to complete the process. This streamlined approach makes managing your Shopware 6 data hassle-free.

Step 1: Configure your export profile

Go to Extensions -> Improved Import, Export & Mass Actions -> Product Export and click the “New Profile” button. The “Configure export“ screen displays: 

1. Type your profile’s name; 
2. Select an entity you want to export – Products, Customers, or Orders;
   In the case of Orders, you can export the latest modified or the latest created orders by selecting the corresponding option.
   Follow this link for more information: How to export latest orders from Shopware 6.  
3. Enable/disable the export of inherited options. If a variant has a value, it will be exported; otherwise, the parent value will be used.
4. Configure a schedule of updates;
5. Configure email notifications;
6. Select your file format. The app lets you export CSV, XML, and XLSX files or Google Sheets spreadsheets;
7. Next, choose your output source: FTP, Google Drive, Google Sheets, or file download;
8. Specify separators;
9. Choose a batch size for your file export: a lower value is required for a low-end server.

Step 2: Configure mapping

Click “Continue” to proceed to the export mapping screen. If you plan to share your output with a third party, you can replace the default Shopware column titles with the names your partner requires. Simply enter the new values in place of the defaults, and the Improved Import, Export & Mass Actions app will automatically apply the necessary changes.

Keep in mind that you can export only the columns you need by unchecking those that aren’t necessary for your output.

It is also possible to export custom fields separately, with each custom field getting its own column. This feature applies to both products and orders. Previously, all custom fields were exported in a single column, but now you can find each custom field listed as a separate field on the mapping screen. If you have a saved export profile for orders and later create new custom fields, add values, and save the order, these new custom fields won’t be included in the export using the existing profile. To include the newly created custom fields, you’ll need to create a new profile, ensuring that everything is exported successfully.

Additionally, the latest version of our application allows you to rearrange the order of columns and add default values as needed:

• Column Sorting: Now, during export, you can easily sort columns, arranging them in the desired order within the export file. This feature provides you with greater control over the layout of your data.
• Default Values: You can also include default values when exporting. This means that if a specific attribute has no value, the export file will automatically include the designated default value in its place. This simplifies data management and ensures consistency in your exports.

Column sorting is achieved through a simple drag-and-drop interface, and these enhancements apply to all entities, including products, orders, and customers. It’s all about making your data management in Shopware more efficient and user-friendly. For more information, follow our Guide to Shopware Mapping.

Default Values

The latest version of our app allows you to apply default values to the data you export. A default value is automatically assigned if an attribute in your export file has no value specified. For example, if you set a default value of “99” for the weight attribute, this value will be applied to any products that do not have a weight specified after the export.

.

Products with a specified value for the weight attribute in the admin will retain that value – the default value will be ignored in such cases.

Step 3: Add filters

If you don’t want to export all records, you can create filters on the “Filter” screen:

1. Press the “+” button.
2. Select a product property to filter by. For example, you can choose orderDate to filter orders by their creation date.
3. Choose an operator. For instance, Range allows you to export records within a specific time interval.
4. Specify a value. If you’re exporting orders and have selected orderDate and Range, you can filter to export orders from today, yesterday, last week, last month, etc.

You can create multiple filters by clicking the “Add Filter” button. This allows you to refine your export even further by applying additional criteria. 

Final step: Export

Click the “Save & Close” button to save your Shopware 6 export profile for future use. The app will automatically execute the profile according to the scheduled time. If you click the “Export” button, the app will transfer the data from Shopware 6 immediately. 

If you selected File as your export destination, you can download it by clicking the Download button at the bottom of the export process recap.

How to export orders

Our app exports each order’s data across multiple rows. Row with linetype = order represents the order data. Rows with linetype = lineItems represent the order items.

By default, line item rows do not contain order-related data in the order columns:

To fill line item rows with order data, select the export option Fill all order line with order data in export profile settings.

When this option is enabled, all rows will contain the data from their related order.

How to Export Cross-Selling Data

Export Fields

When exporting cross-selling data, your file will include these fields:

1. Basic cross-selling information: ID, name, position, type, active status, and limit
2. Sorting settings: sortBy and sortDirection
3. Associated product information: productId and productNumber
4. Product stream information (for productStream type): productStreamId and productStreamName
5. Assigned products (for productList type): product numbers in a comma-separated list

Field Reference Table for Cross-Selling Export

Export Filters

When exporting cross-selling data, you can use filters to narrow down the results. The following fields support filtering:

• name: Filter cross-selling entries by name
• productId: Filter by the ID of the product to which the cross-selling is attached
• productNumber: Filter by the product number to which the cross-selling is attached
• type: Filter by cross-selling type (productList or productStream)
• active: Filter by active status (true/false)
• productStreamID: Filter by the ID of the product stream
• productStreamName: Filter by the name of the product stream

You can use these filters in the export profile to export only specific cross-selling entries that match your criteria.

How to Import & Export Product Properties in Shopware

By default, Shopware 6 does not export custom properties that you’ve added to your products, such as ‘Size’ or ‘Color.’ This means that when you export products, any custom attributes you’ve created won’t be included in the export file.

To address this, you can export custom product properties as a separate entity. However, this approach comes with a limitation: the exported file won’t include references to the products these properties are associated with. As a result, re-importing the products with their corresponding custom properties becomes impossible, since the connection between the products and their custom attributes is lost in the process. This makes it challenging to maintain the integrity of your product data when re-importing into Shopware 6.

With the Improved Import, Export & Mass Actions app, you can export custom properties along with your products in a convenient format. This format includes both the database ID of the custom property and the name as displayed in the store’s backend, making it easy to reference and manage.

The exported file might look like the screenshot below:

The columns highlighted in green represent custom product properties and follow this format:

color#0bde8db993684f8b92a713913aa3d9c3

Where:

• color is the name of the property as it appears in the Shopware 6 backend.
• #0bde8db993684f8b92a713913aa3d9c3 is the ID of the property as stored in the database.

When importing products along with these properties, you can import them using three different formats for the column names:

1. property_name#property_id: This is the default format you receive in the export file.
2. property_name: You can also import the property by naming the column as it is labeled in the Shopware 6 admin panel.
3. #property_id: Alternatively, you can use just the property ID, starting with the “#” symbol.

During the mapping step of the import procedure, you’ll need to assign all custom properties from your file as follows:

1. Locate the custom property, such as “color.”
2. In the dropdown menu under store properties, select “propertiesSources“.

Assign “propertiesSources” to all the custom properties you are importing. This ensures that Shopware correctly interprets and applies them, regardless of the order or format you use.

We also recommend using both the property name and ID as your import format.

In the Shopware 6 backend, you can create multiple custom properties with the same name. Therefore, if you have several properties with identical names, you’ll need a way to distinguish them. This is where the property ID comes in, such as “#0bde8db993684f8b92a713913aa3d9c3”. The property ID is always unique and ensures that each property is correctly identified and applied without confusion.

How to Import & Export Configurable Products in Shopware

Here’s a guide on how to use the import and export features for configurable products to adjust their frontend display in Shopware 6.

Import

You can use the import feature to control how configurable products with variants are displayed in product listings. Let’s explore how this feature works in Shopware versions 6.5 and 6.4.

Shopware 6.5

The import of configurable products can lead to different frontend displays depending on the values specified in your CSV table. Let’s explore 4 different cases:

Case №1

If the Display Single Product as Main Product column is set to “1” (true) and Display Single Product as Variant and Display as Expand Product are empty as shown below:

The Shopware configurable product import will display the selected Main product with an empty dropdown, meaning no variant is pre-selected.

Case №2

If the Display Single Product as Main Product column is set to “1”, the Display Single Product as Variant column contains an ID of one of the configurable product variants, and Display as Expand Product is empty:

The Shopware configurable product import will display the selected Main product with an empty dropdown, meaning no variant is pre-selected.

Case №3

If the Display Single Product as Main Product column is set to “0” (false) or is empty, the Display Single Product as Variant column contains an ID of one of the configurable product variants, and Display as Expand Product is empty:

The Shopware configurable product import will display the selected Variant in the Display Single Product section, with the variant being the product with the ID specified in the CSV.

Case №4

If the Display Single Product as Main Product column is set to “0” (false) or is empty, the Display Single Product as Variant column is empty, and the Display as Expand Product column contains the Available Property Name (Colour|Size)+ID combination (several values should be separated with “|”:

The Shopware configurable product import results in the selected Main product option in the Display single product section and the selected properties specified in the Expand property values in product listings section.

Shopware 6.4 

The Display Single Product as Variant functionality is not available in Shopware 6.4. Therefore, you cannot use import to control the Display as Expand Product feature. In the cases below, the corresponding column is empty. 

Case №1

If the Display Single Product as Main Product column is set to “1” and Display Single Product as Variant and Display as Expand Product are empty as shown below:

The Main product is selected, and the variant in the dropdown remains unchanged.

Case №2

If the Display Single Product as Main Product column is set to “1”, the Display Single Product as Variant column contains an ID of one of the configurable product variants, and Display as Expand Product is empty:

The checkmark is active on the Main product, and the variant in the dropdown is selected based on the ID provided in the import file.

Case №3

If the Display Single Product as Main Product column is set to “0” or is empty, the Display Single Product as Variant column contains an ID of one of the configurable product variants, and Display as Expand Product is empty:

The checkmark is active on the Main product, and the variant in the dropdown is selected based on the ID provided in the import file.

Export

When you export configurable products from Shopware, the output format differs between versions 6.5 and 6.4.

Shopware 6.5

In Shopware 6.5, the export includes the following three columns:

• display_single_product_as_main_product: This column corresponds to the “Display Single Product as Main Product” checkbox. It contains “1” if the checkbox is selected and is empty if it is not.
• display_single_product_as_variant: This column represents the “Display Single Product as Variant” checkbox and the selected variant in the dropdown. The exported CSV will contain the variant ID.
• display_as_expand_product: This column corresponds to the “Expand Property Values in Product Listings” checkbox. The value consists of the name and ID of the selected properties.

Shopware 6.4

In Shopware 6.4, the export includes the same three columns:

• display_single_product_as_main_product and display_single_product_as_variant: These columns correspond to the “Single Main Variant” checkbox and the Variant dropdown, respectively.
• display_as_expand_product: This column is exported empty. Even if you manually select values to expand, they will not be included in the export file in this version. Additionally, importing content into this column is not possible. However, this does not affect imports – if you have selected “Expand Property Values in Product Listings,” these settings will not be overwritten during the import/export process.

FAQ & Troubleshooting

1. I get an error message “cURL error 6: Could not resolve host”

1. Make sure your store is accessible by the external URL. Local installation of Shopware 6 is not supported by the app.
2. Possible solution:
   Change the APP_URL in the .env file from “local_store_url” to “external_store_url”. Make sure you have specified actual HTTP or HTTPS
3. Uninstall and install the app again. Switching the app on and off will not address the issue
4. Clear browser cache, or use the incognito window.

2. I get an error message “Write access to entity “acl_role” are not allowed in scope “user”

1. Make sure to change the APP_URL in the .env file from “local_store_url” to “external_store_url”. Make sure you have specified actual HTTP or HTTPS
2. Uninstall and install the app again. Switching the app on and off will not address the issue
3. Clear browser cache, or use the incognito window.