What are input attributes?
Input attributes define the data that enters SKULaunch. They represent the raw fields used to capture product information from suppliers, imports, files, APIs, and AI extraction.
Input attributes are the foundation of your data model. Everything downstream including enrichment, validation, mapping, and publishing depends on them being well defined.
Typical examples include:
Product Code
EAN / GTIN
Product Name
Existing Supplier Description
Image URLs
PDFs or datasheets
Input attributes describe what data you expect to receive, not how it is presented or published later.
Input attributes vs attributes
Input attributes are different from catalog attributes.
Input attributes capture incoming data
Attributes are structured, validated, and ready for enrichment and publishing
This separation allows SKULaunch to:
Ingest messy or inconsistent supplier data
Apply AI extraction and rules
Map clean outputs to your target schema or PIM
Viewing input attributes
To view your input attributes:
Navigate to Product settings → Input attributes
Use search, sorting, or columns to find specific attributes
Each row shows:
Attribute ID
Name
Type
Created date
Enabled status
This screen is your control centre for managing incoming product data.
Creating a new input attribute
To create a new input attribute:
Click New attributes
Select an Attribute type
Define the attribute metadata
Save the attribute
Once created, the attribute becomes available for imports, AI extraction, and supplier onboarding.
Choosing the attribute type
The attribute type defines how data is captured and validated.
Available types include:
Identifier
Used for unique product identifiers such as Product Code, SKU, or EANText
Short, single-line text valuesTextarea
Long-form content such as descriptions or specificationsURL
Web links, often used for images or reference pagesMulti-URLs
Multiple links stored against a single productImage
Image file referencesFile
Documents such as PDFs or datasheets
Choosing the correct type ensures data behaves correctly throughout the platform.
Defining general parameters
Each input attribute includes:
ID
A system-safe identifier used internally and for mapping
Example:product_codeName
A human-readable label shown to users
Example: Product CodeDescription
Explains what the attribute represents and how it should be used
This is especially useful for suppliers and internal teamsMandatory
If enabled, the attribute must be populated before products can progress
Content generation settings
Input attributes can optionally be used for:
Content generation
Tool sourcing
These toggles define whether the attribute should be considered when generating enriched content or sourcing additional data.
Most identifier and raw data fields are not used for content generation, while descriptive fields often are.
Validation parameters
Input attributes support validation rules to protect data quality.
Common options include:
Unique
Ensures values such as Product Code or EAN are not duplicatedMandatory
Prevents incomplete product records
Validation rules are enforced consistently across imports, AI extraction, and manual entry.
Editing and disabling input attributes
Existing input attributes can be updated at any time:
Names, descriptions, and guidelines can be refined
Validation rules can be adjusted
Attributes can be disabled if no longer required
Disabled attributes are removed from active use but retained for historical data and traceability.
Best practices
Create input attributes before onboarding suppliers
Use clear, descriptive names and descriptions
Keep identifiers strict and validated
Use AI guidelines to reduce ambiguity
Avoid overloading a single input attribute with multiple meanings
Well-structured input attributes make enrichment faster, automation more reliable, and integrations far easier to maintain.