> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wisepim.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Managing Product Attributes
> Create and organize custom fields that define your product data model. Set up text, number, select, image, and file attributes to structure your catalog.
Attributes are the building blocks of your catalog. Each one is a custom field that holds a specific piece of product data: a color, a weight, a description, an image. Together, they form the data model every product follows. Set them up well and every product stays consistent, searchable, and easy to filter.
Attributes are shared across your project. When you create an attribute, it becomes available for assignment to any [product family](/en/products/product-families).
## Attribute Types
WISEPIM supports a range of attribute types to cover different kinds of product data:
| Type | Use case | Example |
| ---------------- | ---------------------------- | ------------------------------- |
| **Text** | Short single-line values | Product name, SKU, brand |
| **Text Area** | Longer multi-line content | Descriptions, care instructions |
| **Number** | Whole numbers | Warranty years, piece count |
| **Decimal** | Numbers with decimals | Weight, dimensions, price |
| **Date** | Date values | Release date, expiry date |
| **DateTime** | Date and time values | Sale start time |
| **Select** | Single choice from a list | Size (S, M, L), Color |
| **Multi-Select** | Multiple choices from a list | Compatible devices, features |
| **Boolean** | True/false toggle | Waterproof, wireless |
| **Color** | Color picker | Primary color |
| **Image** | Image upload | Product photo, diagram |
| **File** | File upload | User manual, certificate |
Use **Select** and **Multi-Select** instead of free text whenever the values are predictable. This keeps your data consistent and makes filtering reliable.
## Creating an attribute
The New Attribute form keeps creation fast. It captures only the essentials, so you can add a field and move on. Everything else (validation, AI, cleaning) lives in the attribute's settings, which you open after creating it.
Navigate to **Product Attributes** from the sidebar.
Click the **New Attribute** button to open the creation form.
Enter a **Label** (the human-readable name) and select the **Type**. The **Code** (the technical identifier) is generated from the label as you type, and you can edit it.
Optionally pick an **attribute group** and set a **sort order**. These control where the field appears in product forms.
Toggle whether the attribute is **required**, **unique**, **filterable**, **searchable**, or **visible** in product forms. New attributes are visible by default.
For **Select** and **Multi-Select**, choose between custom inline options or a shared options set. For **Number** and **Decimal**, you can link a [unit of measure](/en/products/units-of-measure) code set.
Click **Create Attribute**. It is now available for assignment to product families.
The attribute code cannot be changed after creation. Use a descriptive, lowercase format like `screen_size_inches` or `is_waterproof`.
## Attribute properties
Set these five toggles when you create an attribute. They shape how the field behaves across your catalog:
* **Required**: must be filled in for all products that use this attribute.
* **Unique**: no two products can have the same value for this attribute.
* **Filterable**: can be used to filter the product list.
* **Searchable**: included in product search results.
* **Visible**: shown in product forms and displays.
Mark a field **Filterable** when shoppers or your team will want to slice the catalog by it (color, brand, size). Mark it **Searchable** when its value is something people type to find a product.
## Configure attribute settings (after creating)
Creating an attribute defines the field. Configuring its settings makes the field smart: it enforces clean data, lets AI fill it in, and tunes how much it counts toward your quality score. Open these from the **gear (settings)** action next to any attribute.
The settings open in a tabbed modal. Which tabs and options appear depends on the attribute type.
### General
* **Import, export, and enrichment toggles**: choose which operations this attribute takes part in.
* **AI enrichable**: allow AI to suggest or generate values for this field.
* **Quality weight**: how much this attribute counts toward a product's completeness score, from nice-to-have to critical. For number and decimal fields you can also set a unit and a plausible min/max for smarter checks.
### Validation rules
Enforce data quality so bad values never reach your channels:
* **Text length**: minimum and maximum character limits, plus a format pattern (email, URL, alphanumeric, phone).
* **Number ranges**: acceptable min and max values, and decimal precision for decimal fields.
* **Date ranges**: earliest and latest allowed dates, and a date format.
* **Selections**: minimum and maximum number of choices for multi-select, plus per-option rules.
### Data cleaning
Cleaning rules normalize values automatically during import and editing, so your data stays consistent without manual work:
* **Basic**: trim whitespace, remove empty values, collapse extra spaces.
* **Text**: normalize case, strip special characters, fix encoding, and clean up HTML.
* **Numbers**: remove currency symbols, standardize separators, and round to a set precision.
* **Options**: deduplicate, sort, and map similar values together.
### AI enrichment
For text fields, tune how AI fills the attribute:
* **Confidence threshold**: minimum confidence score required before a suggestion is used. Higher means fewer but more reliable values.
* **Enable AI suggestions** and **require manual review**: decide whether a person checks AI output before it is applied.
* **Word limits**: minimum and maximum word counts for generated text.
* **Enrichment instructions**: tell the AI exactly what this field should contain, for example "Extract the screen size in inches from the specifications".
## Build a whole data model with the AI Data Model Architect
Starting from scratch, or moving to a new industry? The AI Data Model Architect generates a complete starting model for you: attributes, attribute groups, and families, all at once. Open it from the **AI Data Model Architect** button on the Product Attributes page.
Tell the Architect what you sell. There is a quick mode that builds a model straight from the industry, and a guided wizard where you add sales channels, catalog size, and target marketplaces for a more tailored result.
Decide what to generate: general attributes, category-specific attributes, attribute groups, and families. The Architect also recommends UOM and option sets where they fit.
Every suggested attribute comes with a reason and priority (essential, recommended, optional). It also flags overlaps with attributes you already have, so you can merge instead of duplicate.
See exactly how many attributes, groups, and families will be created or updated, then apply. Your model is built in seconds instead of hours.
The Architect is the fastest way to set up a new project. Generate a solid baseline, then refine the attributes you care about with per-attribute settings.
## Organizing with attribute groups
Attribute groups bundle related attributes for a cleaner product form. For example, you might group "Width", "Height", and "Depth" under a "Dimensions" group.
Navigate to **Attribute Groups** from the sidebar.
Create a new group with a **name** and a **code**. Set a **sort order** to control where the group sits relative to other groups.
Choose whether the group shows for **all products** or only for **specific categories**. Category scope keeps forms focused, so a "Battery" group appears only on electronics, not on apparel.
Select which attributes belong in this group.
Click **Save**. The group organizes its attributes into a section in product forms.
Group attributes by purpose: a "Specifications" group for technical details, a "Marketing" group for descriptions and features, a "Logistics" group for shipping info.
## Import and export attributes
For larger models, you do not have to build attributes one by one.
* **Import from CSV**: click **Import** and upload a CSV to create many attributes at once. You can also import attribute definitions from a connected platform such as Magento or a webshop importer.
* **Export to CSV**: export your selected attributes or your full filtered list to CSV. This is handy for backups, sharing your model with a teammate, or editing in a spreadsheet.
Pair export with import to bulk-edit: export your attributes, adjust them in a spreadsheet, then re-import.
## Views and filters
The Product Attributes page adapts to how you work, so a 20-attribute model and a 500-attribute model both stay manageable.
* **Three layouts**: switch between a **table**, **cards**, or a **grouped** view that organizes attributes by their group.
* **Density**: toggle between compact and comfortable spacing to fit more rows or read them more easily.
* **Quick filters and search**: filter by group or type, search by label or code, and combine quick filters to zero in on exactly the attributes you need.
* **Saved views**: save a set of filters as a named view and reapply it in one click.
## Troubleshooting
### Attribute not showing in product forms
* Check that the attribute is marked as **Visible**.
* Verify the attribute is assigned to the product's [family](/en/products/product-families).
* Confirm the attribute group is not collapsed or hidden.
### Validation errors during data entry
* Review the validation rules for overly strict settings.
* Check for conflicting rules (e.g., min value higher than max).
* Make sure error messages are clear so your team knows what to fix.
### Inconsistent data across products
* Switch from free-text to **Select** or **Multi-Select** where possible.
* Enable **data cleaning** rules to normalize values automatically.
* Use the [Data Quality](/en/analytics/data-quality) tools to find and fix inconsistencies.
## Related
Assign attributes to product families to define which data each product type requires.
Organize products into hierarchical categories for navigation and filtering.