ASOS: marketplace guide

About this guide

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

* Submit all product content in English. ASOS translates it into the respective language if necessary.

How to request an account

If you are interested in selling your products on ASOS, please contact your ChannelEngine customer success manager via email. ASOS is currently a closed marketplace.

To qualify as a merchant, you must sell fashion products that align with the interests and preferences of ASOS customers, such as trendy clothing, accessories, or footwear.

Associated costs

ASOS does not charge any setup or monthly fees. However, it does charge a commission fee, which must be agreed on during the initial onboarding with ASOS.

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 ASOS, you can request a Mirakl account for each currency, such as a EUR account for Germany, France, Italy, and Spain.

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

ASOS 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.

Invoice uploads

To configure your invoice settings, click Advanced settings. You can then click the dropdown menu Enable invoice uploading, which contains the following options:

• ChannelEngine invoices - when ChannelEngine receives a shipment, it automatically generates an invoice and attaches it to the shipment before exporting it.
• Merchant invoices (optional) - when ChannelEngine receives a shipment, it exports it – even if there is no invoice attached to it.
• Merchant invoices (required) - when ChannelEngine receives a shipment, it only exports it if an invoice is attached to it. If not, you receive a notification.
• None - when ChannelEngine receives a shipment, it 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: merchant invoices.

Mappings

Content

To ensure your products are accurately represented and easier to find, ASOS requires several attributes to be mapped. You can also map optional attributes to enhance product discoverability.

If your product images do not meet the requirements below (e.g.: dimensions are too small), they must be approved by ASOS during the onboarding process.

The following attributes are specific to each merchant: Buyrachy, Supplier, Brand, Size grid, and Size value.

All products (required)

• Available to sell date - the date when the product is available for sale, e.g.: has sufficient stock. The format is 'DD-MMM-YY'. E.g.: 13-Jan-23.
• Back image - the image displaying the back of the product. The requirements are:
  • Background - light grey, close to 240 RGB.
  • Recommended dimensions - 2116x2700 px.
  • Minimum dimensions - 1500x1900 px.
  • Shape - portrait (not landscape or square).
  • Resolution - 300 dpi.
  • Maximum file size - 3 MB.
  • File format - JPEG
  • Color profile - sRGB.
  • No overlaid text or banners.
  • No metadata on images.
• Brand - select the product's brand.
• Buyrarchy - the department structure on ASOS from highest to lowest. E.g.: Heritage Brands|EU Heritage|EU Heritage MB Main|Voi Jeans.
• Care label - the information on the product's care label, such as washing, ironing, or cleaning instructions.
• Color group | reporting color - the product's color group and the specific color. Use pipe (|) as a separator and apply capital case. E.g.: GREY|CHARCOAL.
• Country of manufacture - the country where the product was manufactured.
• Customer segmentation - the type of the model family used by ASOS studios.
• Detailed image - the image displaying the product's detail. For image requirements, check Back image.
• Element fabric [element]- fabric composition - the percentage breakdown of materials that make up a specific product element (e.g.: lining, pocket, mesh, etc.). This information must match what is shown on the product's care label. At least one element attribute must be provided. The format is [fiber code]|[percentage];[fiber code]|[percentage]. The sum of percentages must equal 100%. E.g.: REPA|78;EL|22.
• Flow - indicate if the product follows a flow style, meaning it is repeated or continues with every season. 
• Front image - the image showing the front of the product. The shape must be landscape or square. For image requirements, check Back image. 
• Hazmat - indicate if the product contains a hazardous material.
• Name - the product's name. ASOS appends the brand name and color to the name, so do not provide these. 
• Production end use - the product's intended use. E.g.: going out.
• Prop 65 for US imports - set it to 'yes' if the product falls under the Proposition 65 in the state of California, and requires a warning label.
• Range/shop by fit - the product's style according to how it fits. E.g.: Plus size.
• Size grid - the set of sizes applicable to the product. The size grid is specific to each merchant.
• Size value - the size of the product, according to the indicated size grid.
• Styled image - the product's styled image. This must be a full-length image with additional styling relevant to the product. For image requirements, check Back image.
• Supplier - the name of your product's supplier or brand.
• Supplier article reference - the product's SKU, also known as Merchant product number.
• Supplier reference - the parent product's SKU. This is the reference that groups product variations together. This attribute is used to build product relationships on ASOS.
• Sustainable materials - indicate any sustainable materials used in the product's manufacturing.
• Variant group code - the parent product's SKU. This is the reference that groups product variations together. This attribute is used to build product relationships on Mirakl.
• Website color - the product's color. This is a free-text field.
• Website gender - the gender that a product is intended for. This allows buyers to filter products by gender.

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)

ASOS expects several optional attributes for your products. Some of them are listed below.

• Coordinate - set this attribute to true if the product is designed to be paired with another product that is sold separately. These two products are displayed on the image together. E.g.: matching jacket and pants.
• Description - the product's short description. 
• Eco edit - if you selected sustainable materials in the Sustainable materials attribute, choose 'Eco edit' from the dropdown. If no materials are selected in the Sustainable materials attribute, choose 'Not applicable'. Both selections must be made correctly so that sustainability information is displayed on ASOS.
• Electrical equipment - indicate if the product is electrical so that the WEEE symbol is added to its description.
• Fabric composition fibers - the list of acceptable fiber codes to use in fabric composition. This attribute displays values and does not require input. Use this attribute to look up the values for the Element fabric [element]- fabric composition attribute.
• Long description - the product's long description. HTML formatting is not supported.
• Multipack size - indicate the number of products included in a package. This attribute only applies to multi-pack items, such as socks, T-shirts, or underwear.
• PIM product type [product type] - the specific type that describes your product best. At least one PIM product type attribute must be provided. A value for this attribute must be specific, e.g.: sport bras.
• Planned go live date - the date when the product becomes available on ASOS. The format is 'DD-MMM-YY'. E.g.: 13-Jan-23.

Offer

Required

• Price - the product's regular selling price, including sales tax. E.g.: 29.99.
• EAN - the product's GTIN. ASOS uses this number to link product content with product offers. The expected format is EAN-13. If your product uses a different format, contact ASOS for assistance.

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.

Logistic class codes

Carrier

Carrier mapping is not required on ASOS. However, you can map your carrier to a specific list of carriers maintained by ASOS. This allows for working tracking codes in the back-end, as well as for the buyer. If your default carrier is missing, please contact ASOS.

Pricing

ASOS requires the prices to be submitted in one of the following currencies: DKK, GBP, EUR, PLN, or SEK. If your pricing attributes are not in these currencies, you need to set 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.

You can either use the Channel status filter (e.g.: products that ChannelEngine has failed to exported, such as those with an empty GTIN or that do not exist on the marketplace yet, are shown as Invalid) or the Validation and feedback tab to see all known errors for specific products.

Alternatively, you can access the marketplace's back-end and download the error report generated by Mirakl. To do so:

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

Additional information

Order extra data items

When an order is imported to ChannelEngine, ChannelEngine also fetches 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.

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 in the Mirakl back-end?
No. Mapping attributes in the Mirakl marketplace back-end interferes with ChannelEngine's content export. Therefore, it is recommended to stick to categorizing and mapping content only on ChannelEngine.

Why am I not receiving feedback on my content and/or offer exports?
Chances are, 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 conventional reports have been fully processed by ChannelEngine – or no new reports have been generated because there are no errors to report.