You will find the following error message there:Object 0:Object code:"700001 - MOIN_ALREADY_KNOWN" title:"This variant is already known on the OTTO marketplace. To be able to offer the variant for sale, please confirm the content by sending the MOIN back to us with the next update." Trigger:"cli: artisan otto:item:marketplace-status" No action is required here; the MOIN will be automatically sent to Otto with the next product data update.If you have further questions about the MOIN, please contact Otto Market.

You will find the following error message there:0:Object code:"600022 - UNALLOWED_PRODUCT" title:"This product is prohibited in the EU and therefore may not be offered on the OTTO marketplace. Please submit a ticket via the Partner Helpdesk on this topic for any possible queries." Trigger:"cli: artisan otto:item:marketplace-status"** The product is not allowed to be sold on Otto Market and should therefore be deactivated for Otto Market. For this, you can, for example, remove the market availability OTTO market under Article > Variant > Availability > Markets.

You will find the following error message there:Object 0:Object code:"600003 - BAD_WORD" title:"The term '#Example#' or the product is not allowed on otto.de. Please familiarise yourself with the terms of use. If the product is allowed to be sold, please remove the term from your product data. If the product is not allowed to be sold, please deactivate it." Trigger:"cli: artisan otto:item:marketplace-status" You can find the terms of use here: AGB - otto.marketChange or remove the affected text.If you have any further questions, please contact Otto Market.

You will find the following error message there:Object 0:Object code:"300007 - INCOMPLETE_MEDIA_ASSET_IMPORT" title:"The images are currently being processed. Please be patient. Ensure that the submitted images meet our requirements. (Requirements: https://account.otto.market/s/article/Mediendaten) If the status does not change within the next 24 hours, please submit a support ticket in the Partner Helpdesk." Trigger:"cli: artisan otto:item:marketplace-status" The processing of images can take a little longer at Otto. If your images are being processed, your variant will be activated shortly.If you have further questions, please contact Otto Market.

If such a case has occurred, you will find current log entries in your system: First, open the menu under Data > Log . Filter your search by selecting the following log under Integration:Plenty\Modules\Otto\Item\Commands\MarketplaceStatusImportCommand Such a log entry indicates a rejection: Open the entry and display the details.You can search here using your variant ID, MOIN or SKU.

It is possible to download the reports from OTTO directly in the OPC. You can find this option in the OPC under Analyses > Product Data Analysis. Filtering of the data is also possible via the download.

This error message indicates an incorrectly configured category mapping in the catalogue.For the categories, values should not be maintained side by side, but if necessary, stored as a fallback (alternative field, below the first field).If it looks like this, please correct it: (otherwise the category value is transmitted twice) It should then look like this: (then the category "Outdoor lights" only applies if "LED Outdoor lights" is not maintained on the item)

In this case, Otto expects an image linked to Otto Market from you.Accordingly, at least one image for Otto Market must have been approved on the item, tab: images.You can check this under availability.

In this case, Otto expects valid values for the base price unit and the base price quantity, both of which you can find in the catalogue. Usually, the error occurs because one of the values has not been configured or is missing from your variant.Make sure that meaningful values are stored in the catalogue for your variants.Example:You sell items in pieces and millilitre quantities.Base price quantityYou must then store the base price quantities 1 and 100 in the catalogue and link them to your variants.Base price unitValid values must be present in the catalogue and on your variants for all units you use.

In this case, OTTO expects all the information required to calculate the base price from you. 

In this example, the field "Material composition" in your applied catalogue would be affected.Therefore, check your link to the "Material composition" field of the catalogue with the variant. The link can most likely be made with a property.

You can find the following error message there:Object 123456:Array[1] 0:Object code:"400007 - WRONG_SALE_PRICE_PERIOD" title:"The start date for the reduced price must be today or later." path:"/products" jsonPath:"$.productVariations[?(@.sku==\"123456\")].pricing.sale.startDate" This indicates that your start date in the variant 123456 is in the past.However, it must necessarily be in the future, as due to technical reasons we have a time offset of about 2 hours (Background: Otto Market uses a different time zone than PlentyONE).Therefore, adjust the start date of your variant so that it can be accepted by Otto.

Object 6988:Array[2] 0:Object code:"100003 - ONLY_EAN_ALLOWED" title:"The EAN (GTIN) must be specified as a numeric value with 8 or 13 digits and must be within a globally unique value range according to the GS1 standard, so it must not, for example, start with 2." path:"/products" jsonPath:"$.productVariations[?(@.sku==\"6988\")].ean" If the EAN criteria are met (8 or 13 digits, within the unique value range), check whether the EAN is valid.You can check its validity, for example, here:Verified by GS1 | Barcode GTIN GLN Company Lookup Verification

You may find the following error message there:Object 1234:Array[1] 0:Object code:"100013 - EAN_MUST_BE_UNIQUE" title:"This EAN is already used under another active SKU. Deactivate this SKU to be able to reuse the EAN." path:"/products" jsonPath:"$.productVariations[?(@.sku==\"1234\")].ean" Trigger:"cli: artisan otto:item:report:result" This indicates that the same EAN has been assigned multiple times on the marketplace. Therefore, you should search for the EAN of this variant in the error message (here: 1234) in PlentyONE and, if necessary, adjust your EANs.Assigning barcodes multiple times is generally not recommended.

You may find the following error messages there:Object 5113:Array[1] 0:Object code:"100008 - INVALID_VALUE" title:"Brand not available" path:"/products" jsonPath:"$.productVariations[?(@.sku==\"5113\")].productDescription.brand" Check your mapping of the affected catalogue under Brand and consult with Otto Market which brand can be used instead or whether the brand needs to be reactivated afterwards.Attention! If you use more than one brand, you cannot use Custom Values. Instead, use properties, for example.

You can find the following error message there:Object 1234:Array[1] 0:Object code:"100008 - INVALID_VALUE" title:"TESTMARKE is not a valid brand. Please enter a valid value. Please only select brands that you can query via the Brands endpoint in the API." path:"/products" jsonPath:"$.productVariations[?(@.sku==\"1234\")].productDescription.brand" Trigger:"cli: artisan otto:item:report:result" Due to the change of the product API to v3 from Otto Market, there have been adjustments regarding brands, among other things. These are no longer transmitted as names, but as so-called BRAND_ID.Therefore, when using Custom Values, it must be ensured that the value stored there exactly matches the Brand ID, otherwise no transmission will take place.Check your mapping in the catalogue under Brand and change the Custom Value to the Brand ID.

An example message might look like this:Object 123456789:Array[1] 0:Object code:"500009 - MISSING_WEEE_NUMBER" title:"If the product falls under the ElektroG, you must mandatorily maintain the attribute WEEE-Reg.-Nr. DE with the corresponding number. If the product does not fall under the ElektroG, please enter the value Product does not fall under the ElektroG for the attribute Device type according to ElektroG." path:"/products" jsonPath:"$.productVariations[?(@.sku==\"123456789\")].productDescription.attributes[?(@.name==\"WEEE-Reg.-Nr. DE\")]" On 01.07., the inspection obligation under the ElektroG came into effect at OTTO market.This means that the »Device type according to ElektroG« and the »WEEE-Reg.-Nr. DE« must be maintained on your variants.Due to this inspection obligation, all items that do not comply with these requirements will be taken offline by OTTO market from 01.07. onwards!In the catalogue, there are the fields »Device type according to ElektroG« and »WEEE-Reg.-Nr. DE«, which you must link in the catalogue and t...

First open the menu under Data > Log . Filter your search by selecting the following log under Integration: Plenty\Modules\Otto\Item\Commands\ItemReportResultCommand Such a log entry indicates a rejection:Open the entry and display the details.Error messages from this integration are only sent once if there was no change in the article dataOTTO only sends us detailed error messages from this log once. For example, this happens when the item export of your variant takes place for the first time. If you do not fix the error immediately, OTTO rejects the content of the item in future exports and you will receive the message in the log underlevel: info and the integration \ItemReportResultCommand “Variants discarded by OTTO due to no change.”The message alone does not indicate an error, but only informs you. If you do not know exactly when the variant was first exported, simply change the content of the variant. The next day you can check the log again for errors. A content change counts as soon as even one character has been added or...

Are you seeing messages of this kind there: The following applies:The error is also shown in the log, for example under "SKU 1234 not generated", or "0:„sku“In the catalogue, it is defined in the first place from which source the SKU should be generated. We distinguish here between a "Parent SKU" and a "Variation SKU". The chosen source should refer to a data row that exists uniquely. It is therefore not possible to assign the same SKU again for different articles.As an example, one could use the "Article ID" as well as the "Variation ID". Both IDs are assigned by the system when creating the article and exist only once.However, it could happen that the article export has taken place and the export has failed due to missing information in the catalogue. The SKU was nevertheless written and is now visible in the variation under the "Availability" tab. At the next export, the system would again try to create an SKU from the sources selected in the catalogue. Since this SKU already exists, the following error occurs:Duplicate entry. C...

Enter the following values in the log to search for a variant:Integration: Plenty\Modules\Otto\Item\Templates\Mutators\DefaultSkuMutatorIdentifier: OTTO MarketLevel: errorReference type: VariationIdReference value: your variant ID

This concerns the VAT rate or sales tax.This must be stored on the variant (Item/Settings under Costs)and must be correctly mapped in the catalogue. For example, the value from Otto (under Sales Tax) or the link to the item's tax rate must not be missing.

Both errors usually have the same cause. Check whether a link to the sales price of the respective variant has been stored in the "Sales price*" field of the catalogue. Additionally, open the menu Setup > Items > Sales prices and check whether the sales price stored in the catalogue has been released for the Origin "OTTO Market".

Both errors usually have the same cause. Open your item in the Tab: Images. Check your item images and make sure that the availability "OTTO Market" has been set:

Check your linked data fields for the "Brand*" field of the catalogue. Brands can most easily be linked via already existing manufacturers (Tab: Global) of the article, or via properties (Tab: Properties) of the variants. Therefore, check that there is a link to the variant in each case. If you want to link via the manufacturer, select Add data field > Manufacturer > and your desired manufacturer.It should also be noted that the linked ID of the OTTO brand should be selected in the dropdown. Manual entry of the ID should not be done.An example mapping:If mapping is based on the manufacturer name, the Comparative Value must be specified:This value corresponds 1:1 to the value stored on the variant. Custom values should only be used if no other brand is to be transmitted. Otherwise, all other underlying mappings will be ignored and only the custom value will be transmitted to Otto.If your brand/ID does not exist in the OTTO brand field (left), you can have the brand registered with OTTO Market. More details can be found in the Helpde...

Check your linked data fields to the "Brand*" field of the catalogue. Brands can most easily be linked via existing manufacturers (Tab: Global) of the item, or via attributes (Tab: Attributes) of the variants. Therefore, make sure that there is a link to the variant in each case. If you want to link via the manufacturer, select Add data field »´> Manufacturer > and your desired manufacturer.It should also be noted that the linked OTTO brand should be selected in the dropdown. Manual entry of the brand should not be made.If your brand does not exist in the OTTO brand field (left), you can have the brand registered with OTTO Market. More details can be found in the Helpdesk at OTTO Market.

Check your linked data fields for the "Category*" field of the catalogue. Categories can most easily be linked via already existing categories (Tab: Categories) of your variants or via attributes (Tab: Attributes). Therefore, check that there is a link to the variant in each case.

Your variant does not have a positive net stock in the linked warehouse of your catalogue.If no warehouse has been linked in the catalogue, the total of all sales warehouses will be transmitted.Alternatively, you can also link the virtual total warehouse.

Check your linking to the fields "Parent-SKU*" and "SKU*" in the catalogue.Make sure you have linked at least 2 data fields to both fields (each as fallback data field).

Check if your variant has an EAN.Check if the barcode linked in the catalogue in the field "EAN*" matches the barcode type assigned to your variant.Check if your barcode type is approved for the marketplace "OTTO Market". To do this, open the menu Setup > Items > Barcode.

If all requirements and all links are stored for your variants, and yet no export of the variant takes place, here you will find your possible errors: First open the menu under Data > Log. Filter your search by selecting the following log under Integration: Plenty\Modules\Otto\Item\Services\ItemExportService Now you will see all item transfers that have already been made. Using Level you can find out whether an item was transferred successfully or not: “info”: Log entries with this message indicate a successful transfer. This can look like the following, for example:“error”: Log entries with this message indicate an error during the transfer. Usually, this means that your variant is not valid. Therefore, no export of the respective variant took place. This can look like the following, for example:Messages of this kind can be opened and the details displayed:In this case, for example, it is an error in variant ID 1167. The field “productDescription.category” is criticised.