You can create many Product Templates (SKUs) at once by uploading a CSV (comma-separated values) file, instead of adding them one at a time. A Product Template is the catalogue definition of a product. The bulk upload validates the whole file first, then creates every template in one go.
For background on the product type itself, see What is a Product Template?
Download the sample CSV
The easiest way to prepare your file is to start from the sample Product Template CSV. It has the exact column headers the upload expects, along with a minimal example row and a fully populated example row. Keep the header row, replace the example rows with your own, and save the file as a .csv.
Start a bulk upload
To bulk upload Product Templates with a CSV file:
Go to Ecosystem Registries > Product Templates.
Open the three-dot menu at the top of the list and choose Bulk Upload via CSV.
Select your prepared .csv file and start the upload.
File requirements
Your file must meet these requirements before it will be accepted:
Requirement | Detail |
File type | A .csv file. |
File size | Under 20 MB. |
Decimal separator | Numbers use a "." (dot), for example 12.5. |
Product dates | Use the format dd/MM/yyyy, for example 31/12/2026. An end date cannot be before its start date. |
What the columns cover
The CSV has one wide set of columns. They fall into the following groups (the sample CSV above shows the exact header names):
Column group | What it holds |
Identity and description | ID, Name, Brand, Brand Owner, Manufacturer, Visibility, Country of Origin and descriptions. |
Classification | GPC (the GS1 Global Product Classification) and Uniclass, each as a code and a title, for segment, family, class and brick. |
Dimensions, weights and volume | Physical attributes, each paired with its own unit. |
Packaging and storage | Storage temperatures and packaging type. |
Warranty and product dates | Warranty details and date ranges. |
Metadata | Free-form columns named Metadata.<Type>.<Field> for your own extra data. |
Required fields
Every row must include the following, or the upload is rejected:
Required field | Notes |
ID | Must be unique and must not already exist in your Product Template Registry. |
Name | The Product Template name. |
Brand Owner | Both the ID and the type. |
Visibility | Either public or private. |
Country of Origin | A valid country. |
GS1 segment and family titles | The top-level GS1 segment and family. |
Validation rules
The system checks each row against these rules before anything is created:
Unique ID: the ID cannot match a template that already exists.
Measurement and unit pairing: if you provide a measurement you must provide its unit, and vice versa. The unit must be valid for that measurement type, and numeric values must be positive.
Reference data: countries, GS1 and Uniclass classifications, packaging types, and the Brand Owner and Manufacturer Organisations are all checked against existing reference data.
Dates: product dates use dd/MM/yyyy, and an end date cannot precede its start date.
What happens after you upload
The upload is all-or-nothing at the validation step: every row is validated first, and if any row fails, the whole upload is rejected and you are shown a per-row list of errors. Nothing is created until the file is valid. When the file passes validation, the Product Templates are created immediately. They are not queued in the background and they are not created as drafts; they appear in your Product Templates list straight away.
Note: If a duplicate ID does slip through, it is silently skipped rather than creating a second template, though in practice the "ID already exists" check usually catches it first.