| Mandatory attributes (products) | ||
|---|---|---|
| Product category (Code: category) Please provide a category for each item (either smallest subcategory or entire category tree). Assigning your product to the lowest level is mandatory and one of the most important foundations for sales success. It is therefore important to ensure that the assignment is factually correct.
|
||
| Seller Product ID (Code: Product.SellerProductID) The unique product code you use to identify the product and its orders. Usually, this is the product ID assigned by your ERP system. This ID will later also be the reference for uploading your offers and order processing. |
||
| Product title (Code: SHOP.PRODUCT.TITLE) Keep content unambiguous: each product is unique and thus should be given its own name. The name of a product must be at least 20 characters and can be up to 120 characters. Depending on ranking, channel and mobile device used to view the page, titles might be truncated. Some search engines (e.g. Reco Engine) truncate titles with more than 70 characters to save space. Please make sure that the first 70 characters of each title describe the product in a distinguishable manner. Google PLAs are limited to 70 characters by default. Start with purpose/item title, brand and MPN/type, followed by other product features sorted by importance. Research the keywords, no generalisation. Use descriptive names/titles as this improves findability and helps customers engage. Add additional keywords afterwards. |
||
Brand (Code: ATT.GLOBAL.Brandname) The detailed requirements for creating new brands can be found here. |
||
| Manufacturer’s part number / MPN (Code: ATT.GLOBAL.ManufacturerAID) Unique manufacturing part number (MPN.) The MPNs are crucial when it comes to online product findability and matching on price comparison sites. All brands (i.e. items not classified as "no name" products) require an MPN. |
||
| Sales unit / Selling unit of measure (Code: Product.BaseUnit) Provide the sales unit of your product. Choose one of the following units: Piece: One unit, may also include accessories if applicable. Examples: One tube of glue, one notepad, one digital camera + battery + charger. Pair: Two units of the same kind constitute a pair. Example: Gloves (as selling one single glove doesn’t make sense.) Pack: Multiple identical products that are sold together. Example: 10 highlighters in one wrapper. Meter: Product is sold by the metre. Prices are quoted per metre. Example: Cables. HOWEVER, tape is sold as a piece or pack. Note: Sales units are unrelated to unit prices, to SKUs and to the order units you want us to use when purchasing a product. |
||
| Content / Content units per selling unit (Code: ATT.GLOBAL.NoCUperOU) Specify the content (numerical). “Piece” refers to one item. “Pair” refers to two items. “Pack” usually means more than one piece. |
||
| Content quantity unit (Code: ATT.GLOBAL.NoCUperOU__UNIT) Unit describing the sold quantity of a product. For instance, if you sell a pack of 10 identical items, you need to choose “piece” (i.e. “10 pcs”.) Other content quantities are g, kg, ml, l, cm, m, m². |
||
| VAT - Sales (Code: Product.TaxIndicator) VAT rate applicable to the product. Usually, this means the standard rate (e. g. 19 percent in Germany). Reduced rates might apply to books or food. |
Upload product data
Catalog management
Uploading data involves two different steps, namely the product data feed and the sales details feed (offer data). Below, we take a closer look at the product data feed.
Product data needs to be uploaded to the backend first. This is necessary because otherwise, it’s impossible to assign the accurate sales details to each product.
Product data is information that doesn't change much, such as the relevant product categories, MPNs and manufacturer/brand names.
Formats
- .csv (default format as UTF-8, works for all uploads)
- .xlsx
- .xml / BMEcat (BMEcat requires manual conversion)
When it comes to importing and creating product master data, you’ve got two options. One is using a excel template from mirakl, the other one is exporting the data from your PIM system.
However, we recommend you export the data yourself and configure them in line with the Conrad requirements using the Mapping Assistant provided by the shop system backend.
Below, we’ve compiled information about attributes relevant to the product data feed.
It includes both details on mandatory attributes and some pointers on recommended attributes that will help you increase the visibility of your products on our platform.
A complete overview of all individual attributes can be viewed directly:
Marketplace-Configuration
More details here: Manage Product Data
If data export from your systems is not possible for individual reasons, an Excel template could also be filled and uploaded manually. More about it here:
There are different ways to import product data:
FTP server
Mirakl allows setting up a server connection that enables automated product data imports. Log in to:
"Settings"=>"Shop" and there the Tab: "Imports"’
Here’s a short checklist with information you need to provide to ensure a working server connection:
- Transfer Protocol (only HTTPS or SFTP)
- Host / server address
- Port
- File path (without host)
- Login details (username and password)
Product data uploads are limited to “Normal” import mode. For instance, any changes made to product titles will be applied automatically when you import an updated file.
API
Product data, offer data and pricing data need to be uploaded using separate access points.
- Product data upload -> Access point P41
- Offer data upload -> Access point OF01 (“Normal”, “Delete & Replace” import mode)
- Pricing data upload -> Access point PRI01 (“Delete & Replace” import mode only)
Import Manually
You can upload product data manually by using the Mirakl dialogue box.
To do so, go to "Catalog"
Here you can “Track Product Imports” and view the respective files and created error reports that help you rectify any mistakes.
New product imports are done here using the button "Import products" at the top right of the page.
Importing product information doesn’t always work right away. There are many reasons why your first attempt to create product master data might fail. This is why you always need to check the import history, looking for error reports. Likely errors are either data conversion errors or errors occurring during data integration.
Download your Product import error reports in your mirakl account menue "Catalog" > "See details"
You can find information and solutions to the different error messages in this article: