The Ultimate Guide to Filling Amazon Flat Files in 2025
TL;DR
- Download the right category template from Add Products via Upload and classify items first; each product type has different required fields.
- Fill mandatory identifiers (GTIN/EAN), titles, brand, product_type, variation data, price, quantity, images, and browse node(s); use Amazon’s style guides.
- Build valid parent-child variations (parent SKU with no price/quantity + child SKUs with a supported variation_theme).
- Meet image rules (pure white background, ≥1000 px longest side for zoom).
- Upload, then read the Processing Report to fix errors fast; iterate until “Success.”
- If you’re doing this weekly at scale, switch to SP-API (Product Type Definitions + Listings Items) or let tools like shopvibes auto-fill templates or list via API.
How do you fill Amazon flat files correctly in 2025-without endless rejects?
If flat files make your eyes glaze over, you’re in good company. This guide keeps things simple and practical: the exact template to download, the fields that truly matter, how to build variations that don’t break, and how to clear the processing report without guesswork. You’ll get copy-paste tables, checklists, and a clean sequence to follow-so listings go live faster and you spend less time fighting spreadsheets.
Prefer automation? We’ll point out where Shopvibes can auto-fill templates, catch errors before upload, and list via API-but everything here works perfectly fine in Excel, too. The focus is results: fewer rejects, faster approvals, and a calmer Seller Central.
Which Amazon template should you download for your product type?
- In Seller Central → Add Products via Upload, download the inventory file template for your category.
- Use the Product Classifier in that flow to ensure you pick the correct product type; requirements differ by type and marketplace.
Tip: Tools like shopvibes can help your pulls the latest templates per marketplace and product category, so you don't have to guess
What are the mandatory columns-and what do they actually mean?
Amazon’s templates mark fields as Required/Optional/Conditionally Required by product type. Below is a practical mapping (generic, works for most hardlines/Home & Living). Check your specific template for exact flags.
Core attribute mapping table
| Column (flat file) | What it is | Typical values / format | Required?* | Common mistakes |
|---|---|---|---|---|
| item_sku | Your unique SKU | Alphanumeric, no spaces preferred | Yes | Changing SKUs later |
| product_type | Amazon product type | From template dropdown/list | Yes | Using wrong type for category |
| brand_name | Brand | Exact brand string | Yes (most) | Mismatch with Brand Registry |
| item_name | Title | ≤ 200 chars, structured | Yes | Keyword stuffing; wrong order |
| external_product_id + external_product_id_type | GTIN (EAN/UPC) and type | EAN (13), UPC (12) | Often | Wrong type or check digit |
| parent_child | Variation marker | parent / child | Cond. | Pricing a parent; missing child links |
| parent_sku | Link child to parent | Parent SKU | Cond. | Typos, dangling parents |
| relationship_type | Relationship | variation | Cond. | Wrong value |
| variation_theme | Variation axis | size, color, size-name-color | Cond. | Unsupported theme |
| color_name / size_name | Variation values | Free text per theme | Cond. | Mismatched to theme |
| standard_price | Price | Numeric, marketplace currency | Yes (offers) | Wrong decimal/locale |
| quantity | On-hand qty | Integer | Yes (FBM) | Zeroed accidentally |
| update_delete | Operation | Update / PartialUpdate / Delete | Yes (ops) | Using wrong op |
| recommended_browse_nodes | Browse node ID | Numeric node ID | Often | Picking wrong node |
- “Required” varies by product type/marketplace. Always check the Data Definitions tab in your downloaded template.
Warning: Titles, bullets, descriptions, and images must meet category style guides or you’ll pass file validation but fail retail readiness later.
How do you build parent-child variations the right way?
- Create one parent (no price/quantity/images) and multiple children (each with its own price/qty/images).
- Use a supported variation_theme for your product type (for textiles often color, size, or size-name-color).
- Each child must supply the attributes referenced by the theme (e.g., color_name, size_name).
- Link children via parent_sku and set relationship_type = variation.
- Full rules are in Amazon’s variation guidance and “Create parent-child relationships.”
What image rules must you follow to avoid hidden listing issues?
- Main image: pure white background (#FFFFFF), product fills frame, no watermarks/text.
- Resolution: at least 1000 px on the longest side to enable zoom (higher is better).
- Add additional lifestyle/infographics as secondary images per style guide.
- See Amazon’s official image requirements.
How do you choose the correct browse node and why does it matter?
Browse nodes drive where a product sits in Amazon’s navigation and affect discoverability. Use the “Change a product’s category or browse path” guidance and populate recommended_browse_nodes with the correct numeric ID from your template/tools. You can later adjust category/browse path via the product editor if needed.
What’s the clean upload & validation workflow?
- Prepare & pre-check
- Use the latest category template; fill required fields; keep one tab per country/marketplace.
- Validate locally (basic formula checks) and ensure UTF-8 .txt output if exporting from Excel.
- Upload
- In Add Products via Upload → Upload your spreadsheet, submit the file to the correct target store.
- Read the Processing Report
- Download and scan for Error and Warning codes; fix and re-upload until “Done” shows zero errors. Amazon’s help page explains what common errors mean and how to correct them.
Note: It’s normal to iterate 2-3 times for a new family. Keep your parent/child structure and identifiers stable across uploads.
What does a “good” first pass look like for Home & Living?
- Identifiers: Valid EAN/UPC (or GTIN exemption).
- Titles: Format like Brand + Key Feature + Product Type + Variant.
- Bullets: 4-5, scannable benefits/materials/dimensions/care.
- Variations: Single theme per family (avoid mixing size-only SKUs into a color-size parent).
- Images: Main on white; lifestyle + detail shots at ≥1000 px.
When should you stop using Excel and switch to API?
If you list/maintain >200 SKUs, push frequent price/stock/content updates, or operate across multi-EU marketplaces, Excel becomes operationally fragile. Amazon’s SP-API offers two key capabilities:
- Product Type Definitions API: fetch JSON schemas of required/optional attributes for each product type in a marketplace-machine-readable replacements for Excel headers.
- Listings Items API: create, fully update, or partially update listings programmatically; you can even preview errors before committing.
Where shopvibes fits: We map your catalog once, auto-fill Amazon’s required/conditional attributes per product type, validate against the latest schemas, and list via API. This keeps spreadsheets and flatfiles as a backup-not your source of truth.
What are the exact steps we recommend for your team?
1) Pre-flight checklist
- Confirm product type and download the right template.
- Assemble identifiers (GTINs), brand, dimensions/weight, bullets, and images.
- Decide variation strategy (theme + values).
- Pick candidate browse node(s).
2) Fill the flat file
- Start with parents (no price/qty/images), then add children with full details.
- Complete required + conditional fields from the Data Definitions tab.
- Generate a clean tab-delimited .txt.
3) Upload & fix
- Upload to the correct marketplace and monitor status.
- Download the processing report; fix & re-upload until clean.
Tip: Tools like shopvibes can flag missing required fields, illegal values, and broken variation families before you upload, reducing Go-Live times.
How does shopvibes reduce your workload right now?
- Auto-fill templates from your PIM fields; we maintain category mappings for Amazon DE/UK/FR/IT/ES and more.
- Schema-level validation using Amazon’s Product Type Definitions; no more guessing conditional requirements.
- API listing with Listings Items API; preview errors and push partial updates in minutes.
- Cross-marketplace reuse: reuse the same mapped attributes for OTTO, Wayfair, etc., with per-channel overrides.
What risks should you watch for?
Warning: Mixing incompatible variation themes, using the wrong browse node, or failing image rules will pass basic file checks but hurt discoverability and retail readiness. Use the processing report and category style guides to find and fix these early.
FAQ
Do I need a different flat file for each Amazon marketplace (e.g., DE vs FR)?
Yes. Product type requirements and valid values can differ by marketplace; download the correct template in each store.
Can I add parent images and prices?
No. Parents are containers only-omit price/quantity/images on the parent; include them on children.
How big do my images need to be?
Use at least 1000 px on the longest side to enable zoom; follow white-background and no-text rules.
What’s the fastest way to fix “attribute missing” errors?
Open the processing report, find the error code, and correct the exact field in your file; re-upload until clean.
Where do I find the right browse node ID?
Use the category/browse path guidance and the recommended IDs in your template/tools; assign the most specific relevant node.
When should I adopt API over Excel?
When volume/frequency grows: use Product Type Definitions to fetch schemas and Listings Items API to create/update listings programmatically.
Want to figure out how to automatically fill your flatfiles or even switch to automated synching via API? Talk to us.
About the author
Author
Tim Hoffmann
Chief Product Officer, shopvibes
Tim Hoffmann is a seasoned eCommerce technology leader in product data management, marketplace integrations, and workflow automation. As Head of Product at shopvibes, he combines hands-on technical expertise with a deep understanding of merchant needs, having worked with leading brands to streamline complex multi-channel operations. Tim shares actionable strategies grounded in real-world results to help businesses improve product visibility and accelerate sales growth.
