Mirakl guide: settings and solutions

Mirakl does not run its own marketplace. Instead, it provides the infrastructure others use to create and manage theirs.

Because many Mirakl marketplaces use the same setup, they often have similar settings, behavior, and common issues.

Mirakl Marketplaces in Channable

• Decathlon
• Fnac
• Leroy Merlin
• fonQ
• Darty
• Bricoman
• Mediamarkt
• Conforama
• Carrefour France/Spain
• Manor
• PcComponentes
• Maxeda Brico&Praxis
• Leen Bakker
• ePrice
• Douglas
• Galeries Lafayette
• Home24
• Sprinter
• Showroomprive
• Hornbach
• Conrad
• Vtwonen
• Galeries Lafayette

---

What is the mirakl_unknown_error_code and how to solve it?

When this error occurs, it means the product is not recognized by Mirakl. Possible reasons include:

1. Missing product details like category-specific attributes.
2. Product information is still pending, displayed as "Product - submission pending."
3. Errors in the submitted data, indicated by "Product - data error" or "Product - integration error."

In short: something required by the Marketplace is missing or not correctly filled out.

While this might seem complex, the solution often involves a few straightforward steps:

• Categories: Ensure your product categories are correctly matched in the Categories step of your API. If they are not, map them accurately.
• Build: Verify the Build step of your API is accurately configured. For example, an incorrect EAN field linked here can cause errors. Adjust any mismatches.
• Attributes: In the API's Attributes step, link each field to the correct counterpart and ensure the values are appropriate for the selected category.
• Rules: Use rules to refine your data further. See the attribute builder support article for enhancing the Attributes step in your API.

Once categories and attributes are filled out in your API, go to the APIs overview and run the API by clicking the blue "Run now" button.

Best practices and settings for Mirakl

Add multiple attribute values

If you need to enter multiple values for a single attribute field for a Mirakl Marketplace, separate each value with a pipe symbol "|". This formatting ensures Mirakl correctly recognizes and processes each separate entry.

Common Mirakl errors and how to solve them

Offer - product not found

This error occurs when a product’s EAN isn’t recognized by the Mirakl database.

This usually happens when:

• The product is still being processed by Mirakl (shown as Product - submission pending).
• The product import failed due to missing or invalid required data (for example, category-specific attributes). This is usually shown as Product - data error or Product - integration error.

How to fix

1. In the Result step of your Mirakl marketplace channel, go to the Feedback tab.
2. Review other listed product-related errors.
3. Check the error feedback in the Error column. Where needed, adjust your data using rules.
4. Review and map attributes marked as required in the Build step. Check the icon and tooltips to see accepted values.
5. Click Run now to re-run your channel.

Product - submission pending

This error occurs when the marketplace is still processing your product information.

For the latest status information, download a non-integrated products report in Mirakl.

1000: Required attribute is empty

A required attribute for this marketplace hasn’t been mapped, or has an empty value.

How to fix:

1. In the Feedback tab in the Result step, click the error.
2. Click the linked ID in the ID column.
3. Scroll to see any fields marked Missing mapping for [insert attribute].
4. Click View in build. This will direct you to the affected attribute in the Build step.
5. Map the missing field. If you don’t have a field with accepted values, you can create a new field and fill it using rules.

Tip: While you’re here, review any remaining errors marked as Required by marketplace (indicated by a blue dot). Click the icon for more information/an example of accepted values.

1. Click Save.
2. Click Run now.

1001: Unknown category provided

The category value provided doesn’t match a category from the marketplace, or a label was provided instead of the code.

How to fix:

1. In the Feedback tab in the Result step, click the error.
2. Click the linked ID in the ID column.
3. Click View in build. This will direct you to the affected attribute in the Build step.
4. Map the missing field. If you don’t have a field with accepted values, you can create a new field and fill it using rules.

Tip: While you’re here, review any remaining errors marked as Required by marketplace (indicated by a blue dot). Click the icon for more information/an example of accepted values.

1. Click Save.
2. Click Run now.

2004: An attribute has a value that is too long

The mapped field for this attribute must be below the specified character limit.

How to fix:

1. In the Feedback tab in the Result step, click the 2004 error.
2. Make note of the affected attribute noted in the Errors column, and the character limit.
3. Go to the Build step and check which field you have mapped for the affected attribute.

Tip: While you’re here, review any remaining errors marked as Required by marketplace (indicated by a blue dot). Click the icon for more information/an example of accepted values.

1. Go to the Rule step.
2. Create a maximum length rule to the field you’re using to ensure it fits the character limit. Be sure to click Save to apply changes.
3. Click Run now.

2006: An attribute has a value that is not one of the allowed values

This error occurs when the field you mapped contains a value that's not accepted.

How to fix:

1. In the Feedback tab in the Result step, click the 2006 error.
2. Click the linked ID in the ID column.
3. Scroll to see any fields marked Invalid value for [attribute name]. Next to it, click View in build. This will direct you to the affected attribute in the Build step.
4. Make note of the field you mapped for the affected attribute.

Tip: While you’re here, review any remaining errors marked as Required by marketplace (indicated by a blue dot).

1. Click the icon next to the affected attribute to view Example and Possible values.
2. Use rules to update or create a new project field with the accepted values. Be sure to click Save to apply changes.

   1. If creating a new project field, be sure to re-map it in the Build step to that new field.
3. Click Run now.

2007: An attribute value doesn't match a regular expression

This error occurs if the value in the attribute isn’t in the expected format.

How to fix:

1. In the Feedback tab in the Result step, click the 2007 error.
2. Click the linked ID in the ID column.
3. Scroll to see any fields marked Invalid value for [attribute name]. Next to it, click View in build. This will direct you to the affected attribute in the Build step.
4. Make note of the field you mapped for the affected attribute.

Tip: While you’re here, review any remaining errors marked as Required by marketplace (indicated by a blue dot).

1. Click the icon next to the affected attribute to view Example and Possible values.
2. Use rules to update or create a new project field with the accepted values. Be sure to click Save to apply changes.

   1. If creating a new project field, be sure to re-map it in the Build step to that new field.
3. Click Run now.

Mirakl error reports

You can download different error reports in Mirakl to investigate different errors. You can find them all under Catalog > Product imports.

• Source file error report: Shows what’s wrong in your source file or format. The data displayed will show the exact same feedback as appears in your marketplace channel in Channable.
• Non-integrated products report (recommended): Tells you what the marketplace rejected/is reviewing after your submission was processed.

  • Use when: You successfully ran your channel, but you see ‘Product - submission pending’ errors.
• Added products report: Confirms which products/lines were successfully integrated

  • Use when: You want proof of what is live, or to reconcile what was created vs sent.

How to download a non-integrated products report

Note: This is a detailed report that may take several days for Mirakl to generate. For urgent matters, contact Mirakl’s support team.

1. Log in to your Mirakl account.
2. Go to Catalog > Product Imports.

1. In the File name column, find which items were imported by Channable, and their timestamps.
2. For those items, click See details to view the most recent import information.

1. Click Download next to Non-integrated products report to download the error report automatically.

Note: The file is a CSV. If you’re using Microsoft Excel or Google sheets, you may need to transform/import the file to view it.

1. Open the file in your software.
2. Check the Errors column to see specific error(s) for each item.
3. Fix what you can based on the error description. Mirakl receives this feedback from the marketplace.

If you're not sure what the description means, contact the marketplace for more information.

Check product status in Mirakl

Products on the platform have three primary statuses:

• Validation
• Acceptance
• Synchronization

Combinations of these produce various meta statuses.

1. In your Mirakl backend, go to Catalog > Catalog Manager. You will see an overview of all your items.
2. In the Product updates column, click for more information on what a certain status means.
3. To view a more detailed description, open the product page and click .

Tip: Use the filters to view statuses in bulk.

Products on the platform have three primary statuses: Validation, Acceptance and Synchronization. Combinations of these produce various meta statuses.

Mirakl Catalog Manager statuses

Status	Meta status	Description
Validation	Valid data	The Product Data is compliant with the Marketplace requirements.
	Invalid data	The Product Data is not compliant with the Marketplace requirements.
	Pending media	The media (images, videos, documents) of the product data is not yet processed by the Mirakl platform.
	Not computed	When the Marketplace activates product data validation for a channel, the validation statuses for the products are not automatically recomputed. In this case, these products get the 'Not computed' status for the given channel. Several actions can trigger the re-computation of the validation status of a product: - After the rebuild of the Product Data Sheets - when you modify the Source Product Data Sheet and these modifications are reflected in the Master Product data Sheet - when you modify a Master Product Data Sheet All new products get the suitable validation status for each activated channel.
Acceptance	New	The product is new, and the Marketplace must accept or reject it.
	Changes required	Your Marketplace has rejected the product due to data quality issues. You must update your products before your Marketplace reviews the product again. You can view the rejection reason by hovering your mouse over the question mark (?)
	Pending verification	You have been asked to update a product or products. Changes have been made. The marketplaces must now decide to accept or reject the product/products.
	Accepted	Your Marketplace has accepted the product.
	Rejected	Your Marketplace has rejected the product. You can view the rejection reason by hovering your mouse over the question mark (?)
Synchronization	Synchronized	The product is integrated into the Marketplace platform.
	Not synchronized	The product is not integrated into the Marketplace platform.
	Synchronization error	An error occurred during the integration of the product.

For more information on Mirakl statuses, you can visit their help center.