Skip to main content

File Import

File Import is the primary way to onboard products into SKU Launch in bulk using a CSV or XLSX file.

S
Written by SKULaunch Support
Updated over 4 months ago

When to use File Import

Use File Import when you need to:
• Onboard large volumes of products
• Load supplier spreadsheets
• Migrate data from another system
• Apply AI assisted mapping and normalization

For one off or manual product creation, use Create Item instead.

File Import process

File Import follows a guided, step by step flow.

1. Metadata

You start by creating a new import project.

Here you define:
• Import name
• Optional taxonomy node
• Optional suppliers

The choices made at this stage directly affect how mapping and classification work later in the flow.

2. File upload

Upload a CSV or XLSX file containing your product data.

Once uploaded, SKU Launch reads the column headers and sample values to prepare them for mapping.

3. Attribute mapping

This is where file columns are mapped to SKU Launch fields.

What you can map depends on whether a taxonomy was selected in the Metadata step.

Importing with a taxonomy selected

If a taxonomy node is selected:

• All attributes for that taxonomy are automatically available
• You can map file columns to the full attribute schema
• AI tools can assist with attribute mapping and data normalization
• Products can move directly through mapping to preview and completion

This is the fastest and most complete import path.

Use this approach when:
• Product families are already known
• Supplier data aligns to a single taxonomy
• You want to enrich everything in one pass

Importing without a taxonomy selected

If no taxonomy node is selected:

• Only input attributes can be mapped initially
• Taxonomy specific attributes are not yet available
• Products must be classified before enrichment can continue

After mapping, these imports are placed into Classified Imports rather than being completed immediately.

From Classified Imports:
• Products are classified into the correct taxonomy
• The full attribute schema becomes available
• Enrichment, normalization, and validation can be completed

Once classification is complete, the products are added to the main catalog.

This approach is useful when:
• Taxonomy is unknown or inconsistent
• Supplier files contain mixed product types
• You want AI assisted classification before enrichment

4. Preview

Before finishing the import, you can preview:
• Mapped attributes
• Normalized values
• Any missing or required fields

This ensures data quality before products are created.

What happens after import

• Products are added directly to the main catalog once complete
• All imported items are grouped under the import project
• Import projects act as a reference list for tracking, validation, and follow up enrichment

Did this answer your question?