AUTODOC: marketplace guide

About this guide

This is a ChannelEngine guide on the Berlin-based marketplace AUTODOC. Here you can find information on how to request an AUTODOC account, how to configure this marketplace on ChannelEngine, and what the specific requirements are.

Table of contents

Commercial information

How to request an account

Associated costs

Marketplace features

Settings and configuration

Marketplace-specific requirements and exceptions

• Setup
• Mappings
• Pricing
• Listed products

FAQs

Commercial information

* To use AUTODOC with currencies other than EUR, you need to set up an additional account on Mirakl and an additional plugin on the ChannelEngine dashboard.

How to request an account

To start selling on AUTODOC, click the Join our marketplace button at the bottom of this page on their website. Afterwards, wait for the AUTODOC marketplace team to review your application and conduct any necessary checks.

The requirements to sell on AUTODOC are as follows:

• Be a registered merchant in an EU country that complies with EU VAT regulations.
• Have a warehouse located in an EU country that complies with EU VAT regulations.
• Have valid VAT IDs in your registered country of business and in the delivery country.
  Or:
• Participate in the VAT One-Stop Shop (VAT OSS) scheme in your registered country of business.

Associated costs

AUTODOC does not charge a setup fee. However, it charges a monthly fee of EUR 30.00 (excluding VAT) and a variable commission based on the product category.

Marketplace features

* A marketplace that supports sales channels allows merchants to list and sell products across multiple markets (e.g.: countries, regions, and states), all from the same connection. On AUTODOC, you can only use the same connection for countries that have the same currency. 

E.g.: Belgium and France can be configured as sales channels within the same plugin because they both use EUR. However, you must set up a separate AUTODOC plugin in your dashboard for the UK because it uses the GBP currency. 

Settings and configuration

Setting up each channel on ChannelEngine follows the same flow, though not every channel includes the steps listed below.

1. Go through the Setup.
2. Create a Product selection.
3. Complete the Categorization.
4. Set up the Mappings: content, offers, and carriers.
5. Configure the Pricing: rules and currency conversion.
6. Fill in the Stock settings.
7. Finish the Activation.
8. Check the Listed products overview.

Marketplace-specific requirements and exceptions

Setup

On ChannelEngine

AUTODOC is a Mirakl-based marketplace, so you can connect it with ChannelEngine using a Mirakl Connect SSO account. For more information on this, check out the Mirakl-based channels: SSO authorization article.

If you sell in different currencies, set up one AUTODOC plugin per group of sales channels that use the same currency, e.g.: one plugin for all countries that use EUR and one channel for the UK, which uses GBP.

Invoice uploads

To configure your invoice settings, go to Advanced settings. Then, select one option from the dropdown menu in the Enable invoice uploading field, which contains the following options:

• ChannelEngine invoices - when ChannelEngine receives a shipment, ChannelEngine automatically generates an invoice and attaches it to the shipment before exporting the shipment.
• Merchant invoices (optional) - when ChannelEngine receives a shipment, ChannelEngine exports the shipment – even if there is no invoice attached to it.
• Merchant invoices (required) - when ChannelEngine receives a shipment, ChannelEngine only exports the shipment if an invoice is attached to it. If not, you receive a notification.
• None - when ChannelEngine receives a shipment, ChannelEngine takes no action other than notifying you that no invoice is present.

If you select one of the Merchant invoices options, make sure to upload the invoice to ChannelEngine via the Merchant API or via the web interface. To learn more, check out the article ChannelEngine: upload merchant invoices.

Mappings

Content

All products (required)

• Article no - the product's identifier, as defined by the brand owner.
• Brand - the product's brand. 
• Image 1 - the URL of the product's main image. The requirements are:
  • File format  - GIF, JPEG, JPG, PNG, GIF, or WEBP. 
  • GIFs are not animated. If you submit an animated GIF, AUTODOC removes the animation and displays only the first image from the series on the Product details page.
  • Maximum file size - 500 KB.
  • White background with shadows.
  • The product must fill 85% of the frame.
  • No borders, text, artwork, graphics, or watermarks.
  • Must not display any human model.
  • Must not contain information about the country of origin.

The following required attribute is common to all Mirakl-based marketplaces:

• Export strategy - choose a strategy for exporting product data. You can select from the following export strategies:
  • Yes - export all product content to the marketplace, including the EAN (GTIN), category, and other mapped attributes. This option is ideal if you manage both product content and offers through ChannelEngine for the marketplace. Before you set this option, ensure that you map all required attributes.

  • No - do not export product content to the marketplace. Choose this option to keep the product content excluded from exports and only export the offers. This option is ideal if you do not want to export the product content yet, or you want to export only the product offers because the product content already exists on the marketplace.
     

    NB: the default export strategy is Yes, even if the Export strategy attribute is left unmapped.

All products (optional)

• Compatibility K-types - map the product (part or accessory) to one or more numeric identifiers assigned to compatible vehicle models in the TecDoc database.  E.g.: if a car model, such as the Volkswagen Golf VII 1.4 TSI (140 HP, 2013–2017), has a specific K-type number, map this attribute to this number. Use the format [KTYPE 1];[KTYPE 2];[KTYPE 3].
• Compatible vehicles - select the names of the product's compatible vehicles from the list.
• Description [country] - the product's description in the local language. HTML formatting is supported. The maximum number of characters is 3,000.
• GTIN - the product's unique GTIN, such as an EAN. 
• Image 2-3 - the product's additional images. For image requirements, see Image 1.
• Manufacturers and OENs - if this is a compatible after-market product that is not made by the original vehicle manufacturer, map this attribute to indicate that the product is a replacement for the original parts. Provide the name of original manufacturers and their corresponding unique original equipment numbers (OENs). Use the format [manufacturer 1]:[OEN 1],[OEN 2];[manufacturer 2]:[OEN 3],[OEN 4].  
• Multiplicity - the order increment of the product in the listing. E.g.:
  • If set to 2, the product can only be purchased in multiples of 2 (2, 4, 6, etc.).
  • If set to 3, the product can only be purchased in multiples of 3 (3, 6, 9, etc.).
• Title [country] - the product's title in the local language. For search optimization reasons, AUTODOC automatically generates the title in the format [brand] [article number] [category name]. However, you can provide an alternative title in advance of this changing in the future. The maximum number of characters is 150.
• Unique key - the unique identifier for the product on AUTODOC used for deduplication of products instead of an EAN. You can leave this attribute empty. AUTODOC automatically generates this value in the format [brand] [article number] and displays it in the Reference number field on the Product Details page.
• Universal for cars - indicates whether the product is compatible with most cars - 'Yes' or 'No'.
• Universal for motorbikes - indicates whether the product is compatible with most motorbikes - 'Yes' or 'No'.
• Universal for trucks - indicates whether the product is compatible with most trucks - 'Yes' or 'No'.

Offer 

Required

• Price - the product's selling price. Enter a numeric decimal value and do not include the currency.

Optional

The following offer attributes are common to some Mirakl-based marketplaces:

• ECO #1-5 amount - the amount due for the eco-contribution related to the product. E.g.: 2.50.
• ECO #1-5 EPR category code - the extended producer responsibility (EPR) code that applies to the product. For a list of category codes, check out the article Providing data to comply with circular economy regulations in Mirakl's help center (note that you need to be logged in to Mirakl to access this page). E.g.: DE-WEEE, FR-DEA, etc.
• ECO #1-5 producer ID - your producer ID, received upon registering with a packaging register, such as Germany's LUCID. The maximum number of characters is 255.
• Category-specific ECO attributes - depending on your sales country, you might be required to map additional ECO attributes for products in specific categories. Review which ECO attributes to map within each category.

If pricing v2 is activated in your environment, you will see the following offer attributes, which are common to all Mirakl-based marketplaces:

• Allow promotion below min price - set it to ‘true’ to allow the promotion price to drop below your product's minimum price. To learn more, check out the article ChannelEngine: promotions.
• Strike price - the regular selling price. Use it in combination with the Price attribute to set up a discount/strikethrough pricing. To learn more, check out the 'Working with discounts' section of this article. 
• Additionally, the Fee groups attribute appears in Mappings, Fee group mappings, if pricing v2 is activated. Map the marketplace fee group ID of the product there.  

The following offer attributes are also common to all Mirakl-based marketplaces:

• Discount start date - the date from which the product's sale price is valid, if applicable. Input the date as a fixed value. The date format is YYYY-MM-DD HH:MM:SS ZZ. All dates follow ISO month-day formatting, and all times follow 24-hour formatting in the UTC timezone. E.g.: 2026-10-25 15:30:00 +01 will start your discount on 25 October 2026 at 3:30 PM, one hour ahead of UTC time.
• Discount end date - the date until which the product's sale price is valid, if applicable. Input the date as a fixed value. The date format is YYYY-MM-DD HH:MM:SS ZZ. All dates follow ISO month-day formatting, and all times follow 24-hour formatting in the UTC timezone. E.g.: 2026-10-30 23:59:59 +01 will end your discount on 30 October 2026 at 11:59 PM and 59 seconds, one hour ahead of UTC time.
• Discount price - the product's sale price, if applicable. This attribute must have a lower value than the Price attribute. This attribute only applies if you use pricing v1.
• Discount quantity threshold - the minimum quantity required for the discount rate to be available.
• Leadtime to shipment - the number of days before you ship the product. You can create your own unique rules, if applicable. For more information on this, check out the article Lead time to ship in Mirakl's help center.
• Minimum quantity alert - map this attribute to receive a notification from Mirakl if your stock drops below the threshold defined.
• Offer state - the product's condition. Find your option from the dropdown menu by selecting the fixed value to apply to all.
• Product tax code - the taxation code applicable to the product.
• Logistic class - your optional shipping class. Make sure to map the shipping class using the marketplace’s codes and not with the labels that are visible in the partner portal's user interface. These codes vary per marketplace. If this marketplace makes use of logistic class codes, they can be found below.

Carrier

Carrier mapping is not required on Mirakl-based marketplaces. However, with carrier mapping, you can map your carrier to a specific list of carriers maintained by this marketplace. Carrier mapping enables ChannelEngine to automatically send the tracking codes to this marketplace, allowing buyers to eventually track the shipment themselves. If your carrier is missing from the list, please directly contact the marketplace.

Pricing

AUTODOC requires prices to be submitted in EUR. If you do not have pricing attributes in EUR, you must set up a currency conversion.

Working with discounts

These instructions apply to most Mirakl marketplaces. If there are any exceptions on this marketplace, these are noted below. 

Pricing v1

• To set up a discount, map the Discount price, Discount start date, and Discount end date attributes. If you want to set a permanent discount, map the Discount end date attribute with a date in the far future instead of leaving it unmapped. Otherwise, the offer is not exported, and errors are shown on the Validation and feedback tab.
• The discounted price is only exported if it is lower than the base price.
• If you do not want to set a bulk discount, leave the Discount quantity threshold attribute unmapped.
• To set a bulk discount, the Discount quantity threshold must be set to a value higher than 1. For example, a value of 2 indicates that the buyer must purchase two or more products at the same time to benefit from the discount.

Pricing v2

• To set up a discount, in the Offer mappings step, map the Strike price attribute to your regular price. Then, map the Discount start date and Discount end date attributes to indicate the start and end dates of your discount.
• If you do not want to set a bulk discount, leave the Discount quantity threshold attribute unmapped. To learn how to set up a bulk discount, check out Bulk discounts.
• In the Pricing step, go to Price rules. Map the Price attribute to the discounted price. Both Min. price and Base price fields must be mapped. Note that ChannelEngine exports the higher of the two values – typically the Base price. To learn more, check out ChannelEngine: price rules v2.
• The Price and Strike price attributes cannot be mapped with the same value. ChannelEngine only sets a discount if the value in Price (Base price) is lower than the value in Strike price.
• If set up correctly, your product displays a discount label and a strikethrough price on the channel.

Listed products

If you have problems with products not appearing on Mirakl-based marketplaces – especially if you are trying to create products, check the Listed products page for more information. Use the Channel status filter or the Validation and feedback tab to view all known errors for specific products.

If you see either of the below statuses, refer to the article ChannelEngine: why is my product listed as 'Product not found' in the inventory report?:

• Product not found in inventory report
• Product not in offer file

Products that ChannelEngine has failed to export are shown as Invalid, e.g.: products with an empty GTIN or that do not yet exist on the marketplace.

Alternatively, download the error report generated by Mirakl. To do so:

1. Log onto the Mirakl platform and go to Catalog, Product imports.
2. Identify the latest report and click the See details button.
3. Download the CSV file Non-integrated products report.

FAQs

How often does each task run on Mirakl-based marketplaces?

By default, Mirakl-based marketplaces follow the schedule below:

Can I map attributes on ChannelEngine and on the Mirakl platform?
No. Mapping attributes on the Mirakl marketplace platform interferes with ChannelEngine's content export. Therefore, it is recommended to categorize and map content only on ChannelEngine.

Why am I not receiving feedback on my content and/or offer exports?
Chances are that you are receiving the feedback. However, different types of error reports can take a couple of hours or several days to be generated:

• Offer feedback
  • Error reports are mostly generated automatically and are imported quickly.
• Content feedback
  • Transformation error report - this is automatically generated, and usually imported within a maximum of one day.
  • Conventional error report - this requires a manual review by the Mirakl-based marketplace, and not all do so. It can take several days for this report to be imported.

Note that the previous feedback report is not removed from ChannelEngine until both the latest transformation and the conventional reports have been fully processed by ChannelEngine. If there are no errors to report, no new reports are generated.