Cross-platform Mapping
Full instructions and common questions
Cross-platform Mapping
Map product fields to a target CSV or TSV header. Normalize source fields first, assign each target column or leave it blank, review required columns, then export a file for your cross-platform product workflow.
How to use
- Import or paste product rows and review source mappings for SKU, title, price and other supported fields. Download the original table if needed.
- Paste and read one target CSV or TSV header row. Headers must be nonempty and unique. Assign a standard product field or a blank value to each column.
- Resolve product validation issues, check the target platform’s required and blank columns, and confirm the target template.
- Inspect column names, order and values, then download CSV or TSV. Continue checking platform-specific requirements in the official template.
Try an example
Load the mug sample and enter item_sku,item_name,standard_price as target headers. Map them to sku, title and price; export should contain both SKUs, titles and prices in that order.
Limits and privacy
Up to 10 MB per file and 10,000 rows per table. Only supported, mapped product fields are converted; blank columns remain blank. Amazon multi-row headers, target XLSX templates and every platform’s required-field rules are not parsed. No store upload or synchronization is performed.
Common questions
Can I upload an official Excel target template?
No. Target settings accept one CSV or TSV header row. Handle multi-row headers, Excel templates and category rules in the official file.
Why is an exported target column blank?
It may be assigned a blank value or its source field may be unmapped. Review both mappings and the source rows, then confirm again.