Attributes

Attributes define characteristics used to identify, filter, and generate products. Common examples are size, color, material, model, season, or any other repeatable product characteristic used in the catalog.

In Putaway WMS, attributes can be used in two ways:

• as descriptive information on a simple product or parent product;
• as variant axes when a product has child variants generated from value combinations.

Note

Attributes do not create stock and do not change physical warehouse operations. They describe products and help with catalog organization, filtering, imports, and variant generation.

What You See On The Page

To open the page, go to Catalog -> Attributes.

The list shows the attributes for the current account, sorted by name. For each attribute, you can see:

• Name: the attribute name;
• Values: the number of values available for the attribute;
• Actions: edit or delete, depending on the user’s permissions.

The page uses pagination. The number of rows selected by the user is stored locally in the browser for future visits.

When To Use Attributes

Use attributes when the same product family has repeatable characteristics.

Examples:

Attribute	Possible values	Usage
Size	S, M, L, XL	Variants for apparel or footwear.
Color	Black, White, Red	Filtering and visual variants.
Material	Cotton, Leather, Metal	Catalog description and internal search.
Season	Summer, Winter	Organization and reporting by collection.

For a simple product, attributes are product information. For a multi-variant product, some attributes can become variant axes.

Creating An Attribute

To create an attribute:

1. Click Add.
2. Complete Attribute Name.
3. Enable Allowed for product variants only if the attribute must be used for variant generation.
4. Add the attribute values in the Attribute Values section.
5. Save.

The attribute name is required. In the backend, the name is trimmed, and duplicate names for the same client are rejected.

Tip

Create the attribute once and add all relevant values under it. For example, use Size with S, M, and L values, not separate attributes named Size S, Size M, and Size L.

Attribute Values

Values are the concrete options of an attribute. An attribute without values can exist in the list, but it is not useful for products or variants until values are added.

For each value, complete the value name. The order of values can be changed by drag and drop in the attribute form.

Values are validated under their own attribute. The same value should not be duplicated under the same attribute.

Example:

Attribute	Correct values
Size	XS, S, M, L, XL
Color	Black, White, Beige
Material	Cotton, Wool, Leather

Caution

Do not delete a value that is already used on products or variants without checking the catalog impact. The value will no longer be available for new selections, and products that used it can be affected.

Allowed For Product Variants

The Allowed for product variants checkbox controls whether the attribute can be used as a variant axis.

Setting	What it allows
Disabled	The attribute can be used as product information, but it does not appear as an axis for variant generation.
Enabled	The attribute can be selected in the variants section for multi-variant products.

Example: for T-shirts, Size and Color should be enabled if you want to generate variants such as T-shirt M Black or T-shirt L White.

Attributes such as Material, Collection, or Season can remain disabled if they are only descriptive information and should not generate variants.

Note

The backend validates this rule. An attribute that is not allowed for variants cannot be used as a variant axis, even if a user tries to send a modified request manually.

Using Attributes On Products

In Products, attributes are used in the Product Attributes section.

For a simple product:

1. Select the attribute.
2. Select one or more values.
3. Save the product.

For a multi-variant product, there are two different areas:

• Product Attributes: general information for the parent product;
• Variant Axes: the attributes that generate variant combinations.

An attribute used as a variant axis is not used at the same time as a descriptive attribute on the multi-variant parent. Putaway WMS separates these two purposes so variants stay clear.

Child variants receive the attributes that define their combination, for example Size: M and Color: Black. Child variant attributes are managed through the variant flow, not by directly editing the child product.

Generating Variants

When creating a multi-variant product, choose one or more variant axes. Each axis must be an attribute enabled for variants and must have values.

Example:

Axis	Selected values
Size	S, M
Color	Black, White

Putaway WMS generates the combinations:

• S + Black;
• S + White;
• M + Black;
• M + White.

For each combination, the user completes the SKU and, if needed, the barcode, MPN, weight, dimensions, and minimum stock level.

If a parent product already has variants, the attributes used by those variants remain locked as axes. This prevents inconsistent combinations between existing variants and variants added later.

Product Import

Attributes can also be used in Product Import.

For imports, attribute columns use this format:

Attributes:Attribute name

Examples:

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

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

Tip

Use the same names in imports as in the catalog. Writing differences can create duplicates that are harder to clean up later.

Catalog Sync And Integrations

In synchronization flows with external channels, attributes and attribute values can be mapped to Putaway WMS attributes.

Use the same internal structure regardless of source:

• the external channel can send different names;
• Putaway WMS keeps the standardized internal attribute;
• imported or synchronized products use the internal values after mapping.

This approach helps avoid duplicates between manually created products, CSV-imported products, and products synchronized from external channels.

Editing An Attribute

When editing, you can change:

• the attribute name;
• the Allowed for product variants checkbox;
• the value list;
• the value order.

After changing values, saving replaces the list with the values that remain in the form. Values removed from the form are removed from the attribute.

Caution

Changing an attribute already used by products or variants should be done carefully. Renaming is safer than deleting and recreating because it keeps the existing links.

Deleting An Attribute

Deleting an attribute is available only to users with delete permission.

Putaway WMS does not allow deleting an attribute that is already used by products. In this case, the attribute must first be removed from the products that use it, or it should be kept and renamed if it is still needed.

When an attribute can be deleted, its values are removed together with the attribute.

Plan Limits

Attributes and attribute values are counted against the WMS plan limits.

Two different limits can apply:

• the maximum number of attributes;
• the maximum number of attribute values.

If a limit is reached, Putaway WMS rejects creating or adding new values and displays the message for the current plan.

Permissions

Page access and available actions depend on the user’s permissions:

Action	What it allows
View attributes	Opening the attributes list.
Create attributes	Adding a new attribute.
Edit attributes	Changing the attribute and its values.
Delete attributes	Deleting unused attributes.

If an action does not appear on the page, the user does not have the required permission or the action is not available for that attribute.

Recommended Rules

• Use short and clear names: Size, Color, Material.
• Avoid writing duplicates, for example Color and Colour used in parallel.
• Mark as allowed for variants only the attributes that truly define variants.
• Do not use attributes for information that already has a dedicated field, such as SKU, barcode, supplier, brand, unit, or lot.
• Do not delete values used in products without checking.
• Keep the same structure for manual products, CSV imports, and external synchronizations.
• Check products after import or synchronization if attributes were created automatically.