Limango: marketplace guide

About this guide

This is a ChannelEngine guide on the Germany-based marketplace Limango. Here you can find information on how to request a Limango 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

Additional information

FAQs

Commercial information

How to request an account

To start selling on Limango, contact its sales team via email.

The following requirements apply:

• German tax rate
• Your product data must comply with Limango's specifications, including the use of all content in German.

Associated costs

Limango does not charge monthly fees. However, it does charge a setup fee of EUR 499.00 and a commission fee on successful sales that varies according to the product category.

Marketplace features

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

The section below describes exceptions to the standard settings and configuration steps required to set up this channel on ChannelEngine. 

Setup

On ChannelEngine

Connection

1. This channel is a Mirakl-based channel. Therefore, you connect to it with your Mirakl Connect SSO account. For more information on configuring Mirakl Connect SSO with ChannelEngine, check out the Mirakl-based channels: SSO authorization article.
2. If you would like to test the order flow with this plugin, contact the ChannelEngine Support team to configure the connection of your plugin to support testing. For more information on testing orders, check out the article ChannelEngine: how to create test orders.

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

All products (required)

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.

• Age group - target age range for which the product is intended (e.g.: newborn, 0-6 months, 1-3 years).
• Brand - the brand name of the product.
• Customs tariff/Intrastat country of origin (final processing) - country where the product received its final processing or assembly for customs and Intrastat purposes.
• Customs tariff/Intrastat number – numeric - the official Intrastat/customs tariff (HS) code for the product.
• Customs tariff/Intrastat weight specification – numeric - the net weight of the product according to Intrastat requirements.
• Customs tariff/Intrastat weight unit - the unit of measure for the Intrastat weight (usually kg).
• EU responsible person - city - city of the EU responsible person according to GPSR (General Product Safety Regulation).
• EU responsible person - country - country of the EU responsible person according to GPSR.
• EU responsible person - e-mail - email address of the EU responsible person according to GPSR.
• EU responsible person - house number - house number of the EU responsible person according to GPSR.
• EU responsible person - name - name or company name of the EU responsible person according to GPSR.
• EU responsible person - postal code - postal code of the EU responsible person according to GPSR.
• EU responsible person - street - street name of the EU responsible person according to GPSR.
• Gender - target gender for which the product is intended (e.g.: male, female, unisex, baby).
• Image 1 main front image - main front view image of the product (usually the primary product image). The following requirements apply:
  • It must be a cutout (i.e.: a cropped or isolated image), with no shading.
  • Background - white or gray.
  • File format - JPG, JPEG, PNG, TIFF, BMP, GIF. 
  • Resolution - at least 720x960 px.
  • No watermarks, logos, or text.
  • No dummy pictures or sketches.
• Limango color - color designation as used and displayed on Limango.
• Long description [de_DE] - detailed long description of the product in German. The description should be well structured and contain all the essential characteristics of the product. It can consist of a combination of continuous text and bullet points. If you use both, first enter the continuous text and then the bullet points. Note the following:
  • Highlight the benefits of the product.
  • Name all purchase-relevant characteristics.
  • Use whole sentences.
  • Structure the content using paragraphs, if necessary.
  • Check your spelling.
  • Either avoid or explain uncommon terms.
  • Do not enter information about price, delivery time, etc.
  • Do not add external links.
  • Specify additional product materials as bullet points.
• Manufacturer color designation [variant attribute] - original color name provided by the manufacturer (variant-specific).
• Manufacturer product type [de_DE] - product type designation according to the manufacturer in German.
• Model name - the model name or number of the product.
• Product name [de_DE] - the official product name/title in German. The following requirements apply:
  • Product titles must be informative and concise, including the correct case sensitivity (upper and lowercase).
  • The title must be in German, except for the proper name of the model (e.g.: Flora, Move, etc.)
  • Include product-related specifications (e.g.: color, function, etc.).
  • No superfluous punctuation, symbols, or special characters.
  • No repetitions or long listings.
  • No call-to-action (e.g.: buy now).
  • No indication of the brand.
  • The default naming structure is [product type, if applicable] + [model] + [color, if applicable] + [dimensions, if applicable]. E.g.: Newton Pendel in Silber or Geldbörse "Amelie" in Grau. Certain categories require different naming structures, so make sure to check out the guidelines shared with you by Limango.
• Shop SKU - the unique SKU (stock keeping unit) assigned by the seller/shop.
• Variant group - identifier used to group product variants together (e.g.: same style in different colors/sizes).

All products (optional)

• Customs tariff/Intrastat length specification (cm) – numeric - length specification of the product in cm for Intrastat/customs purposes.
• Image_2-10 - additional product images.
• Non-EU manufacturer - city - city of the manufacturer located outside the EU (for GPSR/traceability).
• Non-EU manufacturer - country - country of the manufacturer located outside the EU.
• Non-EU manufacturer - e-mail - email address of the non-EU manufacturer.
• Non-EU manufacturer - house number - house number of the non-EU manufacturer.
• Non-EU manufacturer - name - name or company name of the non-EU manufacturer.
• Non-EU manufacturer - postal code - postal code of the non-EU manufacturer.
• Non-EU manufacturer - street - street name of the non-EU manufacturer.
• Occasion/holidays - occasion or holiday for which the product is suitable (e.g.: Christmas, Birthday, Easter).
• Product line - the specific product line or collection the item belongs to.

Category-specific

• If available, map the Material name, Material part, and Material part percentage attributes if they are available in your product's category, e.g.: fashion products or home textiles. Follow these guidelines:
  • For products made of a single component, (e.g.: T-shirt that is made of 80% cotton and 20% elastane), map Material name and Material percentage as follows:
    • Material name 1 = Baumwolle (cotton)
    • Material name 2 = Elasthan (elastane)
    • Material percentage 1 = 80
    • Material percentage 2 = 20
  • For products consisting of multiple parts (e.g.: an inner and outer jacket), map Material part, along with its Material part name(s) and Material part percentage(s):
    • Material part 1: Außenjacke (outer jacket)
      • Material part 1 name 1: Baumwolle (cotton)
      • Material part 1 percentage 1: 100
    • Material part 2: Innenjacke (inner jacket)
      • Material part 2 name 1: Baumwolle (cotton)
      • Material part 2 percentage 1: 60
      • Material part 2 name 2: Elasthan (elastane)
      • Material part 2 percentage 2: 40
• It is also important to map the product's dimensions. Follow these guidelines:
  • Only map the product's dimensions for one-size products.
  • Map both the dimension (length, height, depth) and its unit of measure. E.g.: Dimensions depth unit and Dimensions depth value.
  • Do not confuse dimensions with Intrastat dimensions. While regular dimensions are optional, Intrastat dimensions are legally required if your warehouse is located outside of Germany.
  • If your warehouse is outside Germany:
    • Intrastat dimension weight is required and must be provided in kg (unit).
    • Intrastat dimension length is optional.

Offer

Required

• Gross selling price - country - the code of the country where the product's price is valid. E.g.: DE.
• Gross selling price - currency - the currency in which the product's gross selling price is indicated. E.g.: EUR.
• Gross selling price - price - the product's gross selling price, with the decimals separated by a period – not a comma. E.g.: 19.99.
• Inventory - the product's stock.
• RRP - country - the code of the country where the product's recommended retail price (RRP) is valid. E.g.: DE.
• RRP - currency - the currency in which the product's RRP is indicated. E.g.: EUR.
• RRP - price - the product's RRP, with the decimals separated by a period – not a comma. E.g.: 24.99.

Optional

• Base price - basic quantity - the product's basic quantity, used in the calculation of its base price – if applicable. E.g.: 1.
• Base price - country - the code of the country where the product's base price is valid. E.g.: DE.
• Base price - currency - the currency in which the product's base price is indicated. E.g.: EUR.
• Base price - price - the product's base price, with the decimals separated by a period – not a comma. E.g.: 4.99.
• Base price - unit of measure - the measurement unit used to calculate the product's base price. E.g.: ml.

Offer

Required

• Price - the item’s base price/regular sales price. If a discount is created in the Pricing step, this price becomes the 'from' price. Enter a decimal value. Do not enter a currency. If pricing v2 is activated in your tenant, the Price attribute does not appear. Follow the steps in the section “Working with discounts”.
• EAN/GTIN - the product's unique international article number (13-digit EAN or GTIN) used for product identification and matching on Limango.
• Recommended retail price DE (EUR) - the manufacturer's recommended retail price for Germany in EUR (RRP/UVP).
• VAT class Germany - the applicable VAT/tax class for the product in Germany (e.g.: normal or reduced).

Optional

• VAT class Austria - the applicable VAT/tax class for the product in Austria (e.g.: normal or reduced).

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.

Logistic class codes

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

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.

Additional information

Order extra data items

When an order is imported to ChannelEngine, ChannelEngine also retrieves extra data items related to the order itself – or to order lines. This extra data is specific to this marketplace. An explanation of each can be found below: 

Order extra data

*Conditional fields are only displayed if the marketplace provides a value.

Shipments

Your shipments must include: 

• Limango's printed delivery note
• A printed, pre-paid return label (preferably from DHL)
• Tracking code

To retrieve Limango's delivery note via ChannelEngine:

1. Acknowledge your order. After you acknowledge the order, ChannelEngine retrieves the delivery note from Limango.
2. Retrieve the delivery note via the Merchant API with GET /v2/orders/documents.
3. Download the physical delivery note with GET /v2/orders/documents/file. Specify the channel ID and the document IDs from the previous step as request parameters. 
4. Acknowledge the receipt of the documents with POST /v2/orders/documents/acknowledge. 

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.