Create a THE ICONIC product from the Seller Center template

Which names does the Seller Center article print?

To fetch the template, the article says to expand Catalog, then All Products, click Import, expand Download template, and download the template for the product type. A new template is required for each upload because values may change. An accessories file does not go in an apparel template. Row 2 of the template carries the prompts for mandatory fields and for syntax, which the article describes as values from a list or text inputs. Row 1 is an example. Delete that row before upload.

SkuSupplierConfig is the style code including colour. The article’s example is TEST-GREY. Parent SKU should use that same style code, and the article says every unique parent SKU is one new product. Seller SKU is the size variation. The article’s example is TEST-GREY-S, and it also allows a barcode or EAN in that field. The example tables spell the headers ParentSku and SellerSku. The error glossary later writes ParentSKU and SellerSKUs. Those are the spellings on the page. They are not a licence to rename whatever header is on the file you downloaded.

SkuSupplierConfig example: TEST-GREY
Parent SKU: same style code, one parent SKU = one product
Seller SKU example: TEST-GREY-S, or a barcode or EAN
Example-table headers: ParentSku, SellerSku
Upload file: CSV
Import mode for new products: Create New Products

Which sentences are errors, and which file does the API generate?

After import, File Manager reports one of three statuses: Queued, Finished - Green Tick, or Finished - With warning symbol. Queued for more than 20 minutes is the point at which the article says to contact the seller help desk. A warning means an error report can be downloaded. The glossary rows, copied from that table, are: The description needs to be more than 6 Characters; Variation Value is not unique; SKU 'XXXX" is already used by another product; Sizesystem is not valid; Care Label is more than 255 characters; [Attribute] is not applicable to Footwear/accessories/Apparel; **Field** cannot be empty; Sizesystembrand, CompositionMaterial, Measurements, AssociatedSkus is/are not applicable to Accessories; Brand 'xxx' is not registered on Seller Center.; Field 'xxx' with the value 'xxx' does not appear to be a valid option. The warning row is Changes to Field 'price' have been applied to all product variations. Placeholders in that table are Field, Attribute, XXXX, and xxx. The article does not expand them into a header list.

The API page says product templates are structured CSV or XLSX files, and then it says the product-creation call returns an XLSX export job with exportItemId and uuid. Query type full, the default, is all visible attributes. Light is flagged attributes only. The generated names begin ProductCreationTemplate_Master_, ProductCreationTemplate_ plus the attribute-set label, or ProductCreationTemplate_ plus the category name, with a _Full or _Light suffix. categoryId does not change the columns. It only labels the filename when an attributeSetId is also sent. Unknown or non-numeric attributeSetId, a non-numeric categoryId, and a master template when that feature is off are each a 400 Bad Request. The sample 400 body says The request parameters are invalid. That sentence is an API response. It is not one of the glossary rows. The image-update call is the one that documents a format parameter of csv or xlsx, default csv. Product creation does not document that parameter.

How do you map a supplier file onto the template you downloaded?

1. Download a new Seller Center template for the product type you are listing, or generate the XLSX from the product-creation endpoint for that attribute set. Record full or light, and the date. In Golanto, choose THE ICONIC. The mapper still opens on Amazon until you change the platform.
2. Map supplier values onto the headers in that download. Use one parent value for every size of a style, and a different Seller SKU for each size. Do not give each size its own parent value. The article says that split creates a separate product per size.
3. Delete the example row. Read row 2 before you fill a cell. Leave a column out of your source only by leaving the template’s own column blank. Do not add a destination the template does not have.
4. If images go in the template, the article says they must be publicly available HTML links at the specification it starts and does not finish: (1600x2000, <1.95MB. It does not name the image column.
5. Save the Seller Center upload as CSV and choose Import Mode Create New Products. Read the File Manager status. A removal file is a different import: the article says only the SellerSku column is required, and the mode is remove product. Do not send a creation template to that mode.

Worked example

A supplier size row is not a THE ICONIC creation template

sku,title,colour,size
BEAN-07,Merino beanie,Ink,S
BEAN-07,Merino beanie,Ink,M

These headings are a synthetic supplier sketch. The help article’s own examples are TEST-GREY and the ParentSku and SellerSku rows that begin Test-ttt. One parent SKU is one product, so Ink in S and M would share a parent and each size would have its own Seller SKU. The article does not print the rest of the header. Download a new template for the product type. Save the upload as CSV. The API’s product-creation template is an XLSX.

Official references

• ICONIC MP: Bulk Product Creation (opens in a new tab)
• THE ICONIC Seller Center API: Product templates (opens in a new tab)

Schema review: the-iconic-seller-center-template-2026-11-02. Examples are synthetic. Store-specific and unpublished requirements are outside these checks.

Common questions

Continue reading

• Map a product file to a marketplace template
• Keep commas, quotes, and newlines inside CSV fields
• Marketplace file guides