GPSR: CSV import (records and product assignments)

With the import you assign hundreds of products at once or bring records over from another system. It has four steps and writes nothing until you confirm the dry run.

Before you start

a CSV file (download the template on the import page),
for products: the records already entered in the module, since the file refers to their codes.

1. Upload the file

Catalog › GPSR › Import

Choose what you import: Product assignments or Parties. Choose the file (at most 10 MB), the delimiter and the encoding (UTF-8, or Windows-1250 for files from older Excel versions). The templates for both kinds are at the top right.

The first import step: kind of import, file, delimiter and encoding — The first step. The templates for records and products are at the top right.

Columns of product assignments: sku (required), manufacturer and responsible (record codes; none means none, inherit inherit), model, batch, warnings and instructions (separate paragraphs with |), pictograms (codes separated by commas), exempt (1 = GPSR not required) and store (store view code for the texts).

2. Check the column mapping

The module recognises the columns itself, also by Slovenian, Croatian and German names. Check them and correct if needed; set columns you do not want to import to - do not import -.

Column mapping: column in the file, example value and field in the module — The mapping with an example from the first row. The note column is not imported.

3. Dry run

Click Dry run. The module checks every row, writes nothing and shows how many rows will be imported, how many have no changes and how many have an error.

Dry run: two rows to import, four with an error and the error report with reasons — The error report: unknown SKU, empty SKU, a typo in a code with a suggestion and a manufacturer instead of a responsible person.

Common errors: no product has this SKU, the record code does not exist (the module suggests a similar one), a manufacturer in the responsible person column, an inactive record, a text that is too long. Download the errors as CSV, fix the file and upload it again, or import only the valid rows.

4. Import

Click Import. Rows with an error are skipped, the others are written, and the Missing data report and the cached product pages are refreshed.

The import result: imported rows, rows without changes and skipped rows — The import result with a link to the Missing data report.

You can run the import again with the same file: rows without changes are not written again.

Was this article helpful?

Badges and labels on productsExtensions Product questions and answersExtensions Product enquiry formExtensions Product attachments (data sheets, manuals)Extensions Back in stock notificationExtensions

Cookie name	Cookie purpose
PHPSESSID	Preserves the visitor's session state across page requests.
magelan_geo	Remembers that the visitor closed the suggestion of the other language version of the store, so it is not shown again.
form_key	Protects visitor's data from Cross-Site Request Forgery Attacks.
guest-view	Stores the Order ID that guest shoppers use to retrieve their order status. Used in “Orders and Returns” widgets.
login_redirect	Preserves the destination page the customer was loading before being directed to log in.
mage-banners-cache-storage	Stores banner content locally to improve performance.
mage-cache-sessid	The value of this cookie triggers the cleanup of local cache storage.
mage-cache-storage	Local storage of visitor-specific content that enables ecommerce functions.
mage-cache-storage-section-invalidation	Forces local storage of specific content sections that should be invalidated.
mage-messages	Tracks error messages and other notifications that are shown to the user, such as the cookie consent message, and various error messages. The message is deleted from the cookie after it is shown to the shopper.
private_content_version	Appends a random, unique number and time to pages with customer content to prevent them from being cached on the server.
section_data_ids	Stores customer-specific information related to shopper-initiated actions such as display wish list, checkout information, etc.
user_allowed_save_cookie, cookie_consent	Stores the user's cookie consent state for the current domain.
X-Magento-Vary	Configuration setting that improves performance when using Varnish static content caching.

Cookie name	Cookie purpose
product_data_storage	Stores configuration for product data related to Recently Viewed / Compared Products.
recently_compared_product	Stores product IDs of recently compared products.
recently_compared_product_previous	Stores product IDs of previously compared products for easy navigation.
recently_viewed_product	Stores product IDs of recently viewed products for easy navigation.
recently_viewed_product_previous	Stores product IDs of recently previously viewed products for easy navigation.
_fbp	This cookie is installed by Facebook to store and track visits across websites.

Cookie name	Cookie purpose
dc_gtm_*	Throttles request rate when Google Analytics is deployed with Google Tag Manager.
_ga, _gat, _gid, _ga_, _gat_	This cookie is installed by Google Analytics. They are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone.