Import products

Import products lets you upload products from a CSV file. Use it when there are many products and creating them manually is not efficient.

The import is not a blind upload. Putaway WMS asks you to map columns, checks the file before processing, and keeps the history of each import.

Note

The import creates products in the catalog. It does not create stock, receive goods, or move products inside the warehouse.

Before Import

Before importing products, check the master data that will be used in the file:

• suppliers, if products must be linked to suppliers;
• categories, if you already use a catalog structure;
• brands, if products are filtered or reported by brand;
• units, for quantities and operations;
• attributes, if you work with variants such as size, color, or material.

Putaway WMS can automatically create some values from the file, for example units, suppliers, categories, brands, attributes, and attribute values, but they count toward the plan limits.

Opening The Page

To open the import page, go to Catalog -> Import products.

The page is shown only to users who have the Product import permission. From the page header, you can also open Product imports, where the import history is displayed.

Import File

The file must be CSV. Putaway WMS accepts CSV files with comma or semicolon delimiters, and the import template uses semicolons.

The page includes an action for downloading an import template. Use the template as a model for column names and the recommended order.

Recommended fields:

• product name;
• SKU;
• parent SKU, for variants;
• barcode;
• MPN;
• supplier;
• category;
• brand;
• unit;
• serializable product;
• perishable product;
• weight;
• length;
• width;
• height;
• attributes;
• minimum stock level.

The required columns in the mapping screen are:

WMS field	Role
Product name	The product name from the catalog.
SKU	The unique internal product code.
Barcode	The column used to read the barcode. For parent products, the row value can be empty, but the column must be mapped.
Unit	The measuring unit for the simple product or parent product.

Caution

Do not start the import if SKU, name, barcode, or unit are mapped incorrectly. Incorrect mapping can create products with wrong data.

Simple Products

For a simple product, fill in at least:

• Product name;
• SKU;
• Unit;
• Barcode, if the product is scanned in operations.

Supplier, category, brand, MPN, dimensions, weight, and minimum stock level are optional, but recommended if you use them in operations or reports.

Products With Variants

For variants, use the Parent SKU column.

The parent product row must exist before the child rows, or the parent product must already exist in the catalog. Variants use the parent SKU as the link.

For a child row:

• SKU is the variant SKU;
• Parent SKU is the parent product SKU;
• Barcode is required for the variant;
• supplier, category, brand, unit, perishable, and serializable fields are taken from the parent product logic and are not used as the main source for the child product.

Tip

For products with variants, keep the parent row immediately before its variants. The file is easier to check and reduces the risk of a variant being rejected because the parent SKU is missing.

Categories, Suppliers, And Brands

The category can be written as a hierarchical path, for example:

Shoes > Kids > Winter

Putaway WMS trims the spaces around the > separator and creates or uses the existing category levels for the current client.

The supplier can be filled in by name in the mapped column. If the supplier does not exist, it can be created automatically and linked to the product.

The brand can be filled in by name. If the brand does not exist, it can be created automatically.

The measuring unit is searched by name. If it is missing, it can be created automatically.

Attributes For Variants

To import attributes, use columns with this format:

Attributes:Attribute name

Examples:

• Attributes:Color
• Attributes:Size
• Attributes:Material

The value from the cell becomes the attribute value for the product on that row. If the attribute or value does not exist, Putaway WMS can create it automatically.

Perishable And Serializable

For the Perishable and Serializable columns, use the values from the template.

The value yes activates the option. The value no or an empty cell does not activate it.

For perishable products, lots are not created by the product import. Lots are managed separately in Lots and are used later in Goods receiving.

For serializable products, serial numbers are not imported here. Serial numbers are entered in the operational workflows where the product is received, adjusted, or traced.

Column Mapping

After selecting the file, Putaway WMS reads the CSV header and tries to automatically map known columns.

In the mapping step, you see:

• the WMS field;
• the file column;
• a preview of the value read from the file.

Check all required fields before pressing Start import.

Checks Before Processing

Before import, the file is checked for:

• valid CSV format;
• UTF-8 encoding;
• Excel or Google Sheets formulas;
• dangerous command-like fragments in cells;
• invalid characters;
• rows that are too long;
• missing required fields;
• existing SKU;
• barcode already used;
• plan limit overflow.

Caution

Do not import files received from untrusted sources without checking them. Cells that start with formulas or contain dangerous command-like content are rejected.

Starting The Import

After mapping, press Start import.

Putaway WMS uploads the file, creates a queued import, and confirms that the import was registered. Processing runs in the background.

After confirmation, you can:

• start a new import;
• open Product imports for progress and results.

Product Imports

The Product imports page shows the import history.

For each import, you can see:

• import date;
• file name;
• status;
• progress;
• successful rows;
• errors;
• skipped rows;
• warnings.

Important statuses:

Status	Meaning
Pending	The import was registered and is waiting for processing.
Running	The import is being processed by the import processor.
Completed	All rows were processed without issues.
Completed with issues	The import finished, but there are errors, skipped rows, or warnings.
Failed	The import could not be completed. Check the details.
Cancelled	The import was cancelled before completion.

Import Details

From the imports list, open an import detail with the view action.

The detail page shows:

• imported file;
• import date;
• status;
• progress;
• total processed rows;
• errors;
• skipped rows;
• warnings.

If the import has issues, the results table shows the row, status, SKU, product name, and error or warning message.

Reading The Results

Successful Row

The product was created in the catalog. Check the product in Products before using it in receiving, orders, or integrations.

Skipped Row

The row did not create a new product. The most common causes are an existing SKU or a reached plan limit.

Existing products are not updated by this import. If the SKU already exists, the row is skipped.

Error

The row was rejected. Check the message in the details, correct the file, and rerun the import if needed.

Warning

The import can continue, but there is an issue that should be checked. For example, a category may not be found or a value may need verification.

What The Import Does Not Do

Product import does not:

• create stock;
• create lots;
• create serial numbers;
• receive goods;
• move products into locations;
• update existing products with the same SKU;
• automatically resolve duplicate barcodes.

After import, products enter the normal operational workflows: Goods receiving, Putaway, Stock, and Traceability.

Rules

• The import creates products, not stock.
• Check imported products before receiving.
• Do not import files with formulas or cells generated from untrusted sources.
• For variants, the parent SKU must exist or be imported before the variants.
• Do not reuse the same barcode on different products.
• Use the same naming for units, suppliers, categories, and brands to avoid duplicates.
• Read imports completed with issues before rerunning the file.