The practical answer
Choose Template, header row 3 and data start row 5. Map item_sku to sku and item_name to title, marking both required. Expect text 0007/0008 in rows 5/6, with marketplace_note and Instructions preserved. Duplicate readable labels in row 2 or occupied A5 must trigger review before writing.
Source records and the target template have different jobs
Your source supplies verified facts; the target defines where those facts belong. The tool does not infer every business requirement from a heading. Leaving a field unmapped does not establish that it is optional.
Amazon’s bulk-listing guide describes downloading, completing and uploading a template. Use the current file for your marketplace and category, including its instructions and permitted values. Our original example is a mapping exercise, not an official Amazon template or a complete listing submission.
| File | Purpose | Review still needed |
|---|---|---|
| Source CSV / JSON / XLSX | Supply identifiers and facts | Factual accuracy, complete records and field meanings. |
| Target plain-data XLSX | Define workbook positions | Current category, code row, start row and requirements. |
| Platform report | Describe actual processing issues | Locate a source record by SKU and correct it. |
Download the complete template and separate inputs from answers
The pack contains template.xlsx, occupied-template.xlsx, source.csv, processing-report.csv and expected.json. The first workbook is clean; the second has OLD-RECORD in A5. The processing report is editorial, not an Amazon response. Keep answers separate from imported product rows.
Both workbooks contain Template and Instructions. Row 2 deliberately repeats the readable label Product details. Row 3 has unique item_sku, item_name and marketplace_note codes. C5/C6 contain CHECK-CATEGORY and CHECK-CATEGORY-2 and must remain when unmapped.
sku,title
0007,Editorial Blue Mug
0008,Editorial Green Mug| Location | Purpose | Expected |
|---|---|---|
| Template row 2 | Readable labels | Repeated Product details; not the field-code row |
| Template row 3 | Field codes | item_sku / item_name / marketplace_note |
| Template rows 5/6 | Two written records | 0007 / 0008 and their names |
| C5/C6 and Instructions | Unmapped content | Retain both notes and original instructions |
Complete both mapping stages, then inspect the download
- Open Amazon Listing and select Official template preparation. Upload source.csv first, review both rows and sku/title mapping, then confirm source data.
- Under Official workbook mapping, upload template.xlsx. Choose Template, Header row 3 and Data start row 5. The source data and target workbook are different files, not interchangeable uploads.
- Map item_sku to sku and item_name to title; mark both Required for this template. Leave marketplace_note on Keep original cells. Preview both mapped records; blank unmapped preview cells cannot establish what the downloaded workbook retains.
- Select Generate and verify template XLSX, then download the prepared template. Reopen it in the receiving software or check with a reliable reader: A5/B5 are 0007/Editorial Blue Mug; A6/B6 are 0008/Editorial Green Mug.
- Verify text ID types, both C5/C6 notes and Instructions, with row 3 codes intact. After source, mapping or template changes, generate a fresh current result.
Recorded checks cover local file writing and re-reading, not a native Excel UI session or platform acceptance. For upstream values and missing states, use the CSV/JSON reconciliation guide.
Reproduce two failures and recover from their actual causes
Set Header row to 2 to trigger duplicate headers. Restore 3 and reselect mappings/required fields. Do not rename readable labels into invented official codes merely to suppress the issue; row 3 owns the field codes in this exercise.
Upload occupied-template.xlsx and reselect Template, 3, 5 and both mappings. A5 contains OLD-RECORD. Without replacement authorization, generation must report an occupied write range. For this exercise, reload template.xlsx, map again and regenerate, retaining the original conflict copy as evidence.
For a real replacement, review existing records and obtain authority for the affected range before using its overwrite option. Do not move writes to a platform-invalid row to bypass protection. Unmapped notes must remain; merged write cells and complex-workbook restrictions still require the limits below.
| Symptom | Location | Recovery/check |
|---|---|---|
| Duplicate headers | Product details repeated in Template row 2 | Restore row 3 and map again |
| Occupied write range | A5 in occupied-template.xlsx | Review old data; practice with the clean template and regenerate |
| Required column missing/blank | item_sku / item_name mapping and source | Complete confirmed data rather than removing a real requirement |
Use one fictional report row to trace back to the source
Successful re-reading establishes the specified text write, not every official allowed value or category rule. Amazon’s bulk-listing overview separates template preparation from submission. Real processing results must come from your actual account-side submission.
The exercise processing-report.csv lists SKU 0008 and fictional code DEMO-REVIEW. Expand Review a processing/error report, paste the complete record and search by SKU. Return to source.csv’s second data row to confirm the name. Without new evidence, do not invent a replacement product name.
sku,field,code,message
0008,item_name,DEMO-REVIEW,Confirm product name with sourceTwo-stage acceptance for this exercise
- Text SKUs and names match rows 5/6; both notes and Instructions are retained.
- Review duplicate headers, occupied content and required mappings by cause, preserving original files.
- Trace report SKU 0008 to its source, keeping original, working and output versions.
- Verify real template and account-side requirements separately; use variation checks and CSV reconciliation for their own tasks.
Supported workbooks and saved files
Target limits are 10 MB, 50 worksheets, 300 columns, 10,000 rows and 50 MB of expanded content. Header selection supports rows 1–30. Source imports have their own data-tool limits, and the data start plus write range must be valid.
Processing is local, with project files saved in the current browser. Export rewrites the workbook and cannot promise preservation of every complex Excel feature or format. Keep the source, original template and output as separate versions. KitNelo does not upload to Amazon or modify the store.
Common questions
Are missing leading zeros only a display issue?
Not necessarily. Read the exported cell text and compare it with the source SKU. Changing 0007 into 7 loses the original identifier.
Are unmapped fields filled automatically?
No. Their original cells are retained; a blank field may still be required by the official template. Review those requirements separately.
Does a verified export guarantee a successful listing?
No. It checks local mapping and writing. Current platform rules and processing feedback require separate acceptance.
Further reading & sources
Put the guide into practice
Open the relevant tool, preview the result and check your exported file.
