Importing data

Imports is how data enters the catalog. Start an import lists the import types; Recent imports keeps every past run. When your company has value maps, they're listed at the bottom.

To open it, go to Catalog > Settings > Data flows, and then click the Imports tab.

Note

Owners, admins and editors can run spreadsheet imports, as long as product creation is allowed for them in Feature access. Editors also need Manual price editing to import prices. The Locations and Markets imports, and importing photos from Google Drive, require the owner or admin role.

Choose the import type

Type	Import	What it does
Products	Products	Create or update products, one row per variant, matched by SKU. Covers info, attributes, categories, variants, prices, stock and image URLs, and can rename SKUs and create versions.
Product images	Google Drive	Import product photos from a Google Drive folder. See Import photos from Google Drive.
Locations	Locations	Create or update warehouses and stores, matched by store code.
Markets	Markets, currencies & languages	Set up currencies, languages and single-country markets with their price list, one row per market and language. Grouping markets are skipped; their currency and language are still imported.
Attributes	Attribute values	Assign attribute values, such as color, material or season, to products, matched by SKU.
Attributes	Sales channel status	Activate or deactivate products on sales channels, matched by SKU.
Translations	Product translations	Localized titles and descriptions per language, matched by SKU.
Translations	Attribute translations	Attribute value labels per language, matched by attribute and value.

Tip

The first step of every import, and the upload step, have a Download template button. Start from the template, or from the matching export, to get columns that map by themselves.

Run a spreadsheet import

Steps

In Nucleo, go to Catalog > Settings > Data flows, and then click the Imports tab.
Next to the type, click Start import.
In Select, pick the import you need and click Continue.
In Upload, add the file: Excel (.xlsx, .xls) or CSV, up to 10 MB.
For an Excel file, in Sheet, choose the Sheet, the Header row and the First data row, and click Continue. A CSV file skips this step.
In Map columns, check how each column of your file maps to a Nucleo field, and click Continue. See Map the columns.
In Review, check the rows. See Review the check.
Click Run import.

Rows are imported in small batches, with a progress bar. When it's done, Import completed shows how many rows were created and updated, and how many were skipped or failed, with a preview of the first rows applied. Click Download result to get the result, or Download error report for the rows that failed and why. Click Import another file to start again, or Done.

Map the columns

Each row of Map columns pairs a Column in your file, with a sample value, and a Nucleo field. Recognizable headers, in English or Italian, are mapped automatically.

Click Suggest with Atomo to have Atomo propose a mapping for the columns that are still open.
Pick Ignore this column for columns you don't want to import.
If a column holds an attribute that doesn't exist yet, pick Create attribute…, enter its Name, a Code (lowercase letters, numbers and underscores, locked after creation) and a Type (Text, Number, Yes / No or Dropdown (option list)), and click Create & map. For a dropdown, the options are created during the import.
On a product import, Create attributes for … unmapped creates a text or number attribute for every column still open, and maps it.
When two columns hold the same data, Nucleo flags them: map one and ignore the others.

For a product import, the main fields are:

Group	Fields
Key	Product SKU: the key rows are matched on.
Product	Title, Description, Status (`draft`, `active` or `archived`), Brand, Product type, Attribute set, Category (for example `Clothing > Tops`), Gender, Season, Valid from, Version, Macro colour, Material, Made in (ISO country), Previous SKU, Model code, Micro colour, Composition, Image URLs (one or more, separated by spaces or pipes).
Variant	Variant SKU (one row per variant), Previous variant SKU, Barcode, Size, Cost, Weight.
Pricing & stock	Price list (the list code), Price, Discounted price, Location (the warehouse code), Stock available.
Other groups	Every attribute of your catalog, the Compliance & customs fields, a price per price list, title and description per language, and category levels.

Rename SKUs with an import

An import never renames a product by guessing: a SKU it doesn't know creates a new product. To change the SKU of products and variants that already exist, say so in the file.

Steps

In your product file, put the new SKU in the product SKU column and the old one in a column mapped to Previous SKU.
For variants, put the new code in the variant SKU column and the old one in a column mapped to Previous variant SKU.
Run the import as usual.

The product or variant with the old SKU takes the new one, and keeps its data and history. Later files that still use the old SKU keep updating the same product.

Note

If the old SKU isn't in the catalog, the row fails with a message such as The previous SKU X is not in the catalog. To rename a single product by hand, use the SKU field of the product. See Fill in the Info tab.

Create product versions from a file

When a file describes your products from a moment on, such as a collection or a revision, the import can keep the past as versions instead of overwriting it. See Product versions.

Steps

In your product file, add a column with the date each row starts from, mapped to Valid from (for example 2026-07-01 or 01/07/2026), a column with its name, mapped to Version (for example rev. B), or both.
Run a product import up to Review.
In the Versions card, turn on Create versions from this file.
Click Run import.

For each product, the most recent row becomes today's values; every difference becomes a version in the product's Activity. A row older than what the product has today doesn't change the product: it's written only in its history.

Note

With the switch off, the file just updates the products. Templates and product exports already include the Valid from and Version columns, empty: the Versions card then appears, and you leave it off.

Review the check

Before anything is written, Nucleo checks every row. The top of Review counts the rows, how many are ready, how many carry an alert and how many have errors. Each row has an icon for its result and a note.

Result	What happens
Ready	The row imports.
Alert	The row imports; read the note, for example a value that will be created.
Error	Blocking, such as a missing product SKU or a value that doesn't fit the field. The row is skipped. Fix the file and import it again.

Some checks happen while the import runs, such as a SKU that should already exist: those rows end up as failed in the result and in the error report.

When a product import brings a market, a currency or a language that doesn't exist yet, Review lists what it will also create. Set the country of a new market so its prices can be imported.

Note

If every row has a blocking error, there's nothing to import and Nucleo tells you so.

Import a file from a data source

When a product file comes from a PLM or an ERP connected as a data source, say so in the Review step, under Where does this file come from?. The question appears when your company has a data source or a Shopify connection.

Steps

In the Review step of a product import, pick the source instead of Manual import (you).
Click Preview. Nothing is written: Nucleo shows how many products are new or would change, and how many values would be written, overwritten or skipped as an echo of what Nucleo sent.
If the preview is right, click Run import.

A manual import and a source import both write every field in the file; the source import is recorded as coming from that source. See Data from other systems.

Import product photos from Google Drive

Before the first import, an owner or admin connects the company's Google service account: go to Catalog > Settings > Connections, open Google Drive (or add it from the Library), and in Service account click Configure. Paste the Service account JSON, optionally an Admin email to impersonate (optional), and click Save & test. Share the Drive folder with the service account as Viewer; access is read-only.

Steps

In Imports, next to Product images, click Start import.
Under Analyse a Drive folder, paste the Drive folder (URL or id) and, for a shared drive, its Shared drive id (optional).
Click Analyse with Atomo. Atomo reads the folder names and proposes a rule that ties folders to products, with a preview.
4Check the Proposed rule and adjust it if needed:
1. Match folder to: Product SKU or an attribute, with Value from folder (regex, group 1) to take only part of the folder name.
2. Image order (first = hero): by the number in the file name, by file name, or by last modified.
3. Min. long side (px, 0 = all) to skip images that are too small.
4. Deep scan (nested folders) for folders inside folders. With it on, choose the SKU match (Exact (folder = full SKU), Suffix (SKU ends with folder) or Contains (folder inside SKU)) and Import all into channel, or All channels (global).
5. With it off, you can take the channel from the folder name with Channel from folder (optional) and Add channel mapping.
Click Re-check preview and check the Folder, SKU, Channel, Product, Images and Hero columns. Folders with no product won't import.
Enter a Rule name and click Save rule.
Under Saved rules, click Sync to pull the images. The progress shows while it runs.

When the sync ends, a message says how many images were added, how many products matched, and how many images were already there, skipped or failed. Run Sync again at any time: only new images are downloaded. To change a saved rule, click its pencil icon, edit it above and save it again; to remove it, click its delete icon. Images already imported stay.

Note

Only one Drive sync runs at a time for your company. If one is running, wait for it to finish.

Read recent imports

Recent imports lists the last files processed for your workspace, newest first, with the File and its type, the Result, the Applied and total rows, When and By whom. Click Download report for the rows that were skipped and why; the report lists up to 200 rows.

Result	Meaning
Completed	Every row was applied.
Completed · … skipped	Some rows were skipped; download the report to see which.
Failed	No row was applied.

Edit value maps

Value maps are lookup tables of your workspace, for example a supplier's fit codes next to your own values. The card appears at the bottom of Imports only when your company has value maps, set up with your Nucleo contact.

Steps

Under Value maps, open a map and click Edit.
Edit the Key and the Value of each row, or click Add row.
Click Save.

Note

Value maps can't be created or deleted from Nucleo. Map the columns of your file in the Map columns step as usual.

Considerations for imports

Imports update the products and fields the file touches, and leave everything else as it is. Columns you ignore aren't written.
Every change an import makes is logged in the Activity of each product. See Product history.
Atomo can run an import for you; it always shows a preview first and waits for your confirmation.

Importing data

Related articles