AI-generatedBring supplier product data into your retail catalogue
Combine product data, variants and images from multiple suppliers in OMN, with defined mappings and traceable imports.
How do you turn supplier files into a reliable product catalogue? Define the information and media you need, map the source data to your product model and check the results before publication. OMN brings together EAI, PIM and DAM for data transfer, product information management and the associated images and documents.
AI-generatedDoes OMN fit your supplier process?
When your retail business works with many suppliers, variants, languages or sales channels, coordination between purchasing, product management and e-commerce becomes essential. A PIM with DAM is particularly relevant when product attributes and media need to be managed together. We assess the fit of OMN against your source data, required interfaces and approval processes.
Our PIM and DAM solution for retail shows how product data, variants and media work together across your catalog.
From a supplier file to an approved product
01
Agree on requirements
Define required attributes, units, languages, images and documents for each product group. Decide who follows up on missing information with the supplier and how often updates are expected.
02
Set up an import profile
In OMN EAI, map CSV or Excel columns to product attributes. Define key attributes, classification and import mode: create new records, update existing ones or do both.
03
Check the mappings
Test product, article and variant mapping with a sample file. Agree on rules for values and units. You can reuse the import profile for subsequent files with the same structure.
04
Connect images and documents
Manage product images, data sheets and manuals in DAM and link them to the appropriate products. Define identifiers and rules for article number, variant, language and image view.
05
Resolve issues and approve
Review import logs and check that the information is complete. Missing dimensions, conflicting values and unassigned images need an owner. Define which criteria must be met before approval.
06
Control subsequent updates
Test a second delivery too: Are your own descriptions preserved? Is the correct variant updated? Do approved changes reach the shop? Transfer schedules and channel rules are agreed during the project.
Example: A supplier updates a product variant
Simplified planning example: A supplier sends a new file for an existing variant and an additional product image. Before setting up regular imports, agree on these rules:
| Delivery | Agreed rule | Pilot check |
|---|---|---|
| Article number 4711-B | Supplier identifier and article number jointly form the agreed key. | The existing variant is updated without creating a second article. |
| Width: 10 cm | The target field expects millimetres; configure the conversion in the mapping. | The target value is 100 mm. Value and unit agree. |
| New supplier description | Import the supplier description separately without overwriting your own shop copy. | The approved shop description remains unchanged. |
| Image 4711-B_front.jpg | Link the file, variant and image view using the agreed mapping. | The image belongs to the correct article and its approval is checked. |
These are project rules to be configured and tested, not default automation. An import profile for product attributes does not automatically handle the entire media process.
Which OMN module handles each task?
EAI: Transfer data
Import profiles, field mapping and transformations for product data; history and logs for reviewing runs. Automated file connections are configured for your project.
PIM: Manage product information
Maintain product attributes, articles and variants centrally. Define which system owns each field and who supplies missing values.
DAM: Organise media
Manage images and documents centrally and link them to product information. Agree on rules for assignment, replacement and approval.
Import and mapping with OMN EAI · OMN PIM · OMN DAM
Workflow Management supports tasks and approvals; Channel Management prepares content for output channels. The modules and connections you need depend on your process.
Questions about supplier product data
Must every supplier use the same file format?
You can create separate import profiles with their own mappings for CSV and Excel files. Each file must match the structure expected by its profile. If a supplier changes columns or their meaning, review the mapping. Other formats and connections require a separate assessment.
How can we prevent duplicates and incorrect updates?
Use unambiguous keys, explicit import modes and a test with a repeated delivery. Article numbers from different suppliers may overlap, so distinguish products, variants and supplier offers in your data model. This does not guarantee an error-free process.
Do our suppliers need their own portal accounts?
The CSV or Excel file imports described here do not require a supplier login. A portal with uploads, feedback and supplier accounts is an additional requirement. Its provision and integration must be agreed during the project.
What are ETIM, ECLASS and BMEcat used for?
ETIM and ECLASS help classify products and describe their attributes consistently. BMEcat is an exchange format. Agree on the required version, attributes and mappings with your partners. This does not imply automatic support for every supplier format. Explore data standards.
Need to connect ERP master data and other sources too? Explore the full data onboarding process. Use the PIM implementation checklist to prepare your project.
Let’s discuss your supplier data
Which files do you receive, what information is missing and where does it need to go? In a demo, we discuss how imports, product information and media management work together in OMN.