Practical guidance
Map a product file to a marketplace template
A file can have the right column names and still contain the wrong category values. Header mapping and marketplace validation solve different problems.
Identify the template first
- Download the current template from your seller account or the marketplace’s official source.
- Record the platform, country, category, download date, and version if supplied.
- Match each source field to a destination field by meaning, not just spelling.
- Leave unknown requirements unresolved until you have the template’s instructions.
Test a mapping with actual values
A supplier field named Size may contain garment size, package dimensions, or a bundle count. Inspect representative values before mapping it. The original synthetic example below shows why a name match is insufficient.
Supplier field: Size
Sample values: 30 × 20 × 10 cm
Possible meaning: packed dimensions
Unsafe assumption: clothing sizeCheck what is actually supported
Golanto’s mapper accepts your source CSV and your current official CSV or XLSX template. Choose the worksheet and header record, record the platform/country/category/version, review one-to-one mappings, and export a mapped CSV. This compares structure; country/category-specific certification for Amazon, TikTok Shop, Shopee, and Lazada is not claimed.
What this check cannot establish
Header mapping does not validate unpublished requirements, category enums, or seller eligibility. Unfilled template columns are exported empty and can clear values during an update. Protected or unpublished schemas must come from the merchant’s current official template.
Check your file
Start with a copy. Review changes before downloading your import file.
Open the template mapper