Stadium: marketplace guide

About this guide

This is a ChannelEngine guide on the Norrköping-based marketplace Stadium. Here you can find information on how to request a Stadium account, how to configure this marketplace on ChannelEngine, what the specific requirements are, and more.

Table of contents

Commercial information

How to request an account

Associated costs

Marketplace features

Settings and configuration

Marketplace-specific requirements and exceptions

• Setup
• Categorization
• Mappings
• Pricing
• Listed products

FAQs

Commercial information

Founded	1987
Founder	Ulf Eklöf, Bo Eklöf
Headquarters	Norrköping, Sweden
Area served (orders)	Finland, Sweden
Area served (shipments)	all EU countries
Number of monthly visits	circa 5,000
Website	Stadium
Setup cost	none
Commission	20%
Other costs	EUR 40.00/month
Payment	twice/month (1st and 15th of each month)
Product categories	electronics, games/toys, healthcare, shoes, bags, luggage, sports equipment
Input language	Finnish, Swedish
Input currency	EUR, SEK
Content creation	yes
Minimum number of SKUs	no
Advertisement options	no
Profile on ChannelEngine	Stadium

How to request an account

To start selling on Stadium, contact them via email. If approved, you receive a registration link from one of their onboarding specialists.

Note that to become a seller on Stadium, you must have a legal entity registered with the European Union – both the warehouse and the office.

Associated costs

Stadium does not charge a setup fee, but it does charge a monthly fixed fee of EUR 40 and a commission fee of 20% on sales.

Marketplace features

Supported	Not supported
Product content	Automatic relationships
Product offers	Bundles
Cancelations	Sales channels*
Returns	Repricing
Carrier mapping	HTML formatting
Marketplace fulfillment service
Product variations (size/color)
Multiple stock locations
Orders
Refurbished products
Shipments

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

Settings and configuration

Setting up each marketplace on ChannelEngine follows the same flow, though not every marketplace 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. Finish the Activation.
7. Check the Listed products overview.

Marketplace-specific requirements and exceptions

Setup

On ChannelEngine

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

Categorization

Categorization on Stadium is straightforward, and all categories are listed in English.

Mappings

Content

All products (required)

• Brand name - the product's brand. E.g.: Patagonia.
• Color - the product's color. E.g.: onyx.
• EAN - the product's unique identifier.
• Filter color - the product's filterable color. E.g.: black.
• Gender - the product's target gender. E.g.: women.
• Long description - the product's description in Swedish. The maximum number of characters is 3,999. The characters ™,&,*,|,® and " are not allowed.
• Main image - the product's main image. The requirements are:
  • File size - 10 MB.
  • Resolution - at least 800x800 px, and at most 2,500x2,500 px.
  • File format - PNG (transparent and uncompressed), JPG.
  • Background - gray (#f1f1f1).
  • No models, the product needs to be showcased by itself and photographed from the front.
• Parent product ID - used to group product variations. If you are mapping a standalone, use the product's own SKU/Merchant product number.
• Product identifier - the product's internal identifier. On ChannelEngine, this is usually the Merchant product number.
• Product title - the product's title in Swedish. The maximum number of characters is 3,999. The characters ™,&,*,|,® and " are not allowed, and the product's brand is automatically added to the title.
• Size - the product's size. E.g.: S, UK 8, EU 42, etc.

All products (optional)

• Detail image 1-6 - the product's additional images, showing details of the product.
• Long description FI - the product's description in Finnish. The maximum number of characters is 3,999. The characters ™,&,*,|,® and " are not allowed.
• Model color ID - the ID of the product's color. E.g.: 681.
• Model image 1-6 - the product's additional images, worn by a model and photographed in a studio. Note that Model image 1 must show the model photographed from the front, and model images are only allowed for clothing. For the image requirements, check out Main image.
• Sales argument 1-9 - the product's highlights in Swedish. The first sales argument should mention the product's category. E.g.: Platta sömmar som motverkar skav (Flat seams that prevent chafing).
• Sales argument FI 1-9 - the product's highlights in Finnish. The first sales argument should mention the product's category.
• Supplier model ID - the product's manufacturer ID.
• Sustainable argument - the product's sustainable characteristic in Swedish. E.g.: Återvunnet material - minst 50% av produkten (Recycled material - at least 50% of the product).
• Sustainable argument FI - the product's sustainable characteristic in Finnish.

Offer

The only mandatory offer mapping is Price. This is your desired sale price, after (re)price rules are applied.

Optional

• Discount end date - the date until when the product's sale price is valid, if applicable. The date format is YYYY-MM-DD HH:MM:SS ZZ. E.g.: 2022-12-31 23:59:59 +00.
• Discount price - the product's sale price, if applicable.
• Discount quantity threshold - the minimum quantity required for the discount rate to be available.
• Discount start date - the date from when the product's sale price is valid, if applicable. The date format is YYYY-MM-DD HH:MM:SS ZZ. E.g.: 2022-12-31 23:59:59 +00.

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.

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

• Leadtime to shipment - the number of days before you ship the product. By default, this is set to two. 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 it using the marketplace’s codes, not the labels visible in the front-end. These codes vary per marketplace. If this marketplace makes use of logistic class codes, they can be found below.

Code	Label	Description
Small	Standard	Small items, less than 5 kg and length less than 1.20 meter or less than 0.7 meter width.
Medium	Bulky	Medium items, between 5 and 25 kg and/or length over 1.20 meter.
Large	Heavy goods	Large items, over 25 kg and dimension over than 1.20 meter.
free-shipping	Free shipping	To override logistic class at the offer level.

Working with discounts

• To set up a discount, you must 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 – otherwise, the export is broken.
• To set a bulk discount, the Discount quantity threshold must be set to a value higher than 1. E.g.: a value of 2 indicates that two or more of the product must be purchased at the same time for the buyer to benefit from the discount.

Carrier

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

Pricing

Stadium requires prices to be submitted in EUR for Finland and SEK for Sweden. If you do not have pricing attributes in these currencies, you need to set a currency conversion.

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.

FAQs

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

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

Task	Frequency
Export product data to marketplace	every 60 minutes
Export product offers to marketplace	every 15 minutes
Import product offers from marketplace	every 15 minutes
Import orders from marketplace	every 15 minutes
Export order shipments to marketplace	every 15 minutes
Export returns to marketplace	every 30 minutes

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