Product creation options

There are three ways to create a product: create a SKU template, duplicate a similar product, or import products from a CSV file. Always start with the product's pre-defined fields and use attributes only for additional information that describes the product.

A basic product is a regular purchasable product that doesn't need a separate package, product group, or variant model. Decide on the structure before adding inventory lines or customer selections.

Create a product AI Commerce from a SKU base

To start creating a product, open Products at /products and select Create new product . Enter a unique SKU and select Create .

Creating a SKU template opens a new product in the editor. Name, price, manufacturer, or image are not required in this first window; they will be filled in after creation.

In the editor, fill in the product Overview, Descriptions, Pricing, Categories, Media, Balance, SEO and, if necessary, Attributes. The basic overview information uses auto-save when fields are edited; some of the separate sections use their own Save function. Always check the section's storage capacity before moving on.

The product is immediately created with the SKU entered in the database, so do not use a temporary identifier that you plan to change later. If the SKU is already in use or the format is invalid, creation will be blocked and the editor will not open.

Option 2: multiple products

Use the Duplicate Product feature when a new product is similar to an existing product. Open the product you want to copy from the Products view and select Duplicate Product at the top of the editor.

The editor's pending master data changes are saved first. The service creates a copy and assigns it the first available SKU in the format alkuperäinen-copy , alkuperäinen-copy-2 , and so on, up to a maximum of 99 attempts.

Duplicate copies the main product fields, language descriptions, tags, additional images, media, attribute values, package structure, and category links. It resets view, order, and placement counters. Inventory variants and Custom selections are not included in this copy chain.

At a minimum, change the SKU, name, URL, status, prices, tax category, images, categories, balance, and product-specific attributes from the copy. Also check campaign prices, tags, media, package components, and other copied information before deploying the product.

Option 3: Import products using CSV

Creating or updating a product using CSV is done by opening Data Exchange at /data-exchange . Select Product Import Template if you are starting from scratch, or export current products if you need to compare to existing data.

The import template includes accepted columns such as SKU, manufacturer code, status, balance, base and promotional price, tax category, physical dimensions, and active language names and descriptions. The template does not include current product data.

Fill in the CSV, open Product Import , upload the file, and run Preview . Preview will check the base and campaign prices, campaign discount types and dates, and show line-by-line differences.

The execution updates the existing product based on the SKU and creates a new one if the SKU is not found. Row execution is not atomic for the entire file: successful rows may be written even if others fail. Therefore, fix any preview errors before executing and check the result row by row.

Fill in the Overview

The Product Overview includes the basic structure and commercial flags. Check at least:

• Status , SKU , Display Profile , Supplier ID , Manufacturer , and Order .
• Base balance , Minimum quantity , Quantity step , Package size and Packaging unit .
• Availability Date , In Stock Date and End Date .
• Free shipping , Google feed and Hide from guests .

Price, original price, purchase price, and tax category are maintained in the Pricing section of the current editor. Weight and shipping settings are in the Shipping section. Do not create duplicate attributes for these.

The base balance cannot be edited in the Overview if the product balance is managed by variants. In that case, make a quantity change in the right Inventory row.

Fill in the Descriptions and SEO

The Product Descriptions tab maintains language-specific content. At a minimum, check the Name , URL , Short Description , Description , Image Description , Material , and Comment Guidelines in the languages in which the product is sold.

On the product's SEO tab, check the SEO Title , Target Phrase , and Meta Description . The URL should be relevant and unique to the store structure in question.

Only fill in Attributes when the product's own fields are correct. SKU, name, URL, price, tax category, balance, and other pre-defined fields are not included in attributes.

Select product structure and warehouse

A basic product uses the product's own balance if no separate options are needed. When the customer's choice affects the SKU, barcode, price, or balance, use Product Options , Variants , and Inventory Lines .

A product-specific additional option that is not a separate stockable variant is considered a Custom Option . Package and Product Group are separate constructs and should not be used as a substitute for a standard size or color variant.

Make sure that each Inventory SKU is unique and that the product option value matches the actual option being sold.

Check before use

Product Deployment Checklist:

• The space is purposeful and the SKU is unique.
• The product belongs to the right categories.
• The price, purchase price, tax category, and possible promotional price are correct.
• Base Product, Product Options, Variants, Inventory Lines, Custom Selections, Package, or Product Group correspond to the actual sales model.
• Hide from guests is only available for logged-in B2B selections.
• The Google feed setting, URL, and SEO content have been reviewed.
• The correct Attribute Family has been selected and the required attributes have been filled in.

A missing required attribute does not prevent the product attributes from being saved, but it does reduce the fill rate of Required data. Please check for any missing items before leaving the product in the Enabled state.

Summary

Product creation is done from a SKU base, a carefully checked duplication, or by Data Transfer for a large group. Fill in the product's own fields before the attributes.

Always check SKU, URL, status, prices, tax category, categories, media, balance, SEO and Attribute family. In duplication, check all copied structures; in CSV import, check both the preview and the row-by-row execution result.

Keep the new product in the Inactive state until all information affecting shoppability and visibility is correct. Only check the store view after the saves are complete to avoid mixing the pending price, inventory, or content state with the previous cached version.