Every product should have a unique ID in the import. Duplicate EANs are allowed, but can have impact on product matching and market data that will be collected.
In Omnia 2.0, managing product identifiers is crucial for maintaining data integrity during imports. Here's how the system handles duplicate EANs and IDs:
Duplicate EANs
Omnia 2.0 permits importing products with duplicate EANs. This means you can have multiple products sharing the same EAN in your dataset. While EANs are essential for product matching, they are not required to be unique within your product import.
Duplicate IDs
Each product in Omnia 2.0 must have a unique ID. The system uses this ID to differentiate between products. If a duplicate ID is detected during import, only one of the duplicate IDs will be imported. Therefore, it's imperative to ensure all product IDs are unique before importing your data.
Recommendations
-
Ensure Unique IDs: Always verify that each product ID is unique to prevent import errors.
-
Manage Duplicate EANs: While duplicate EANs are allowed, consider the implications for your pricing strategies and reporting. Ensure that having duplicate EANs aligns with your business objectives.
By adhering to these guidelines, you can maintain a clean and functional product database within Omnia 2.0.