Section 6 : Exporting of Data
6.1 Export Data
To export data, Users will select first the rows they want to export and then will click on Export data button. They will be redirected to a new screen, from where they will choose the export channel to be used. Once the action is complete, the excel document is downloaded locally and the columns it contains will match the columns defined for the selected export channel.
To check if a row has been exported or not for a specific channel, Users can refer to Export status column available for each export channel.
If selected rows include rows of data that is not defined in the export channel For example, the export chanel does not require size information, but sizes are shown on the product grid.
Also, to check if a product has all required information for a specific export channel, Users can refer to the Completeness column associated to each available export channel.
If groups have been enabled, users can select all the products from one group by simply selecting the group. They can select multiple groups and as well deselect specific product rows.

6.2 Export to csv/xls
Users can export a file as CSV type file, or .xlsx type file.
For csv exporting, once the file is attached on Export data page, the user must select the used delimiter.

6.3 Export to Shopify
Users can export to Shopify via API, if the API configuration has been set up.
Select the Shopify channel, and select the API Integration. Select the appropriate API option from the drop down list (specifically if multiple Shopify stores are in use.)

6.4 Export to SFTP
Users can export to xls/csv file to a predefined SFTP location, if the SFTP configuration has been set up.
Select the required export channel and select the SFTP Integration. Select the appropriate SFTP option from the drop down list (specifically if multiple SFTP locations are in use[GW1] .)
Select if the required output is xls or csv.

6.5 Consolidated export view
In some cases, users need to export summarised data rather than the fully expanded data shown in the product grid. For example, when managing style sizes, certain export channels require only style-level data and not individual sizes. While the product grid displays sizes because they are required for other channels, they may not be necessary for all exports.
Based on the export channel mapping, if specific data (such as sizes) is not required, PIMdrop will remove duplicate rows by de-duplicating on the remaining required columns during export.
For example The demo export does not require individual sizes as an export column, but it does require the size range.
In the example below, the Alani Skirt has two colourways—navy and white—available in sizes XS–XL. In the product grid, this results in a separate row for each size (XS, S, M, L, XL).
During export, individual sizes are not required and are therefore treated as duplicates. These duplicate rows are removed, leaving a single row per colourway in the exported output, as shown in the example below. Please also consider Occasion has one variable for Casual not Evening. As this is a variant it is not considered a duplicate, so this row of data will be included in the export.

The example returned the following data removing the non-required size data

7.1 Exports History page
On the Export History page, Users have an overview over the exports that have been done with the following details:
number of products that have been exported
number of products with Missing data
Number of Products with Format issue
who has made the export, the date and time
Users can also download the exported excel documents at any time.

Last updated
