Identifiers in Excel Import

This guide explains how to use product identifiers correctly when importing products and variants through Excel files in Omnium.

---

Import Overview

Omnium supports importing products and variants via Excel files. The identifier fields determine:

1. Whether a record is a new product or updates an existing one
2. Whether a record is a product or a variant
3. How variants are associated with their parent products

---

Required Columns

For Products

For Variants

---

Import Scenarios

Scenario 1: Single-SKU Products

For products that have no size/color variants:

Notes:

• SkuId is required and typically matches ProductId
• IsSku should be TRUE
• VariantParentId is not needed

---

Scenario 2: Products With Variants (Single Import)

When importing products and variants together using the "Product Export File" format:

Products Sheet:

Same File - Variant Rows:

Notes:

• Products have IsSku = FALSE (they contain variants)
• Variants have IsSku = TRUE (they are purchasable)
• VariantParentId links each variant to its product

---

Scenario 3: Updating Existing Variants

When you need to update variant properties (price, inventory, etc.) for existing products:

Notes:

• VariantParentId is essential to locate the parent product
• The system finds the variant by SkuId within the parent product
• Other fields are updated on the found variant

---

Scenario 4: Multi-Language Products

Importing the same product in multiple languages:

Notes:

• Id includes language suffix for uniqueness
• ProductId is shared across all languages
• Products are grouped as translations in the UI

---

Common Mistakes

1. Missing VariantParentId on Variants

Wrong:

Correct:

---

2. VariantParentId Pointing to ProductId Instead of Id

Wrong:

Correct:

---

3. Inconsistent ParentId Between Product and Variants

Problematic:

Better:

While not strictly required, keeping ParentId consistent between product and variants ensures proper inheritance behavior.

---

4. Using Same Id for Product and Variant

Wrong:

Correct:

---

Import File Formats

Omnium supports several Excel import formats for products:

1. Product Import (Basic)

• Creates or updates products
• Required columns: Id
• Optional: all other product fields

2. Variant Import (ExcelImportModelVariant)

• Creates or updates variants on existing products
• Required columns: Id, Variant.SkuId, Variant.Id

3. Product Export File Format

• Full product structure with inline variants
• Required columns: Id, SkuId, IsSku, VariantParentId
• Most flexible for importing products with variants

---

Best Practices

1. Always test with a small batch first - Import 5-10 products to verify your column mappings

2. Export existing products as template - Use the product export feature to see the correct format

3. Keep identifiers consistent - Use the same ID patterns throughout your imports

4. Set VariantParentId explicitly - Don't rely on automatic association for Excel imports

5. Include IsSku column - Explicitly mark which rows are purchasable SKUs

6. Validate parent products exist - Before importing variants, ensure parent products are already in the system

---

Troubleshooting

---

See Also

• Product Identifiers Overview - Conceptual overview
• ID Property Reference - Detailed property documentation