Convert Product Data to an Amazon Flat File

You have 500 products in a Shopify export. Or a supplier spreadsheet with columns in German. Or a CSV dump from your ERP with custom field codes that only your warehouse team understands. Amazon needs all of it in a flat file — a specific spreadsheet format with hundreds of precisely named columns, controlled vocabularies, and validation rules that reject anything that doesn't fit. The gap between your data and what Amazon accepts can easily cost two to five working days of manual reformatting. This guide shows you exactly what that conversion process involves, where each source format breaks, and how to get it done faster.

If you're not yet familiar with what a flat file actually is, start with our complete guide to Amazon flat files.

Why Can't You Just Upload Your Existing Data to Amazon?

This is the first question every seller asks when expanding to Amazon from another platform. You already have structured product data. It has titles, descriptions, prices, images, SKUs. Why can't you just upload it?

The short answer: Amazon doesn't accept anyone else's format. The long answer involves three layers of incompatibility.

1. Column names don't match. Your Shopify export has a column called Title. Amazon's flat file expects item_name. Your ERP calls it Produktbezeichnung. These aren't just cosmetic differences — Amazon's upload parser rejects any column it doesn't recognize. There's no fuzzy matching, no "close enough." Every single column must use Amazon's exact internal name, which often includes marketplace and language identifiers like item_name[marketplace_id=A1PA6795UKMFR9][language_tag=de_DE]#1.value.

2. Values don't conform to Amazon's rules. Amazon enforces controlled vocabularies for dozens of fields. Your color field says "Dark Blue." Amazon expects "Navy" — or possibly "DarkBlue" — depending on the category. Your size field says "XL." Amazon might need "X-Large" or "XL" or "Extra Large," and each category has its own accepted list. Your dimensions are in centimeters; Amazon wants inches for some marketplaces. These aren't things you can eyeball. Each category template has a Data Definitions tab specifying exactly which values are valid.

3. Structure is fundamentally different. Amazon's flat file isn't just a table of products. It's a highly structured document with parent-child relationships for variations, conditional fields that only apply to certain product types, and marketplace-specific requirements. A Shopify export is a flat list of variants. An ERP export might not even distinguish between standalone products and bundles. The structural transformation is often the most time-consuming part.

For a deeper dive into the template structure itself, see our guide on the complete Amazon flat file workflow.

What Does the Manual Conversion Process Look Like?

Let's walk through what it actually takes to convert a Shopify export with 500 products into an Amazon flat file. No tools, no automation — just you, Excel, and Amazon's documentation.

Step 1: Export from your source (5 minutes). You download a CSV from Shopify. It has around 30 columns: Handle, Title, Body (HTML), Vendor, Type, Tags, Published, Option1 Name, Option1 Value, Variant SKU, Variant Price, Variant Inventory Qty, Image Src, and so on.

Step 2: Download the right Amazon template (15-30 minutes). Log into Seller Central. Navigate to the category template library. Figure out which category your products belong to. Download the template. Open it. Discover it has 347 columns. Read the Data Definitions tab to understand what each column expects.

Step 3: Map your columns to Amazon's columns (1-3 hours). Go through each of your 30 Shopify columns. Find the corresponding Amazon column. Document the mapping. Realize that some Shopify fields need to be split (your "Body (HTML)" needs to become separate bullet points and a description). Other Amazon fields have no equivalent in your export at all (brand registration number, compliance certifications, country of origin). Start a list of gaps.

Step 4: Reformat every value (4-8 hours). Copy data from your export into the Amazon template. Strip HTML from descriptions. Truncate titles to 200 characters. Convert your free-text color values to Amazon's controlled vocabulary. Look up each size value in Amazon's accepted list. Convert weights from kilograms to the expected unit. Replace "true/false" with Amazon's expected format. Fix encoding issues with special characters.

Step 5: Handle variations (2-4 hours). Your Shopify export lists each variant as a separate row. Amazon needs parent rows (non-purchasable grouping entries) plus child rows. You need to create parent rows from scratch, assign variation themes, link children via parent_sku fields, and fill in variation-specific attributes on every child row. For 500 products with an average of 3 variants each, that's 150+ parent rows to create manually.

Step 6: Validate (1-2 hours). Check every required field. Verify controlled vocabulary values. Validate GTINs. Ensure parent-child relationships are consistent. Test-upload a small batch. Fix the errors Amazon flags. Re-test.

Step 7: Fix and re-upload (1-3 hours). Almost no flat file uploads cleanly on the first try. Download the processing report. Cross-reference error codes. Fix the offending rows. Re-upload. Wait. Check again.

Total: 10-20+ hours for 500 products. And that's for someone who's done this before. First-timers can spend significantly longer. For a detailed breakdown of what goes wrong at each stage, read our article on common Amazon flat file errors.

Source-Specific Challenges

Every source format brings its own headaches. Here's what to expect from the most common ones.

Shopify Exports

Shopify's CSV export is one of the better-structured source formats, but it still requires substantial transformation for Amazon.

Field name mismatches: Shopify uses Title, Body (HTML), Vendor, Tags. Amazon uses item_name, product_description, brand_name, and has no direct equivalent for tags. Every column needs manual mapping.

HTML in descriptions: Shopify stores product descriptions as HTML. Amazon's product_description field doesn't accept HTML in most categories. You need to strip tags, convert lists to plain text, and restructure the content.

Variant structure mismatch: Shopify lists each variant as a row with Option1 Name, Option1 Value, etc. Amazon uses a completely different parent-child structure with dedicated variation theme fields. The structural transformation is non-trivial — you can't just rename columns.

Missing Amazon-specific attributes: Shopify doesn't track manufacturer part numbers, country of origin, compliance certifications, or dozens of other Amazon-required fields. These gaps need to be filled from other sources or entered manually.

Image handling: Shopify exports image URLs. Amazon accepts image URLs in flat files, but they must be publicly accessible HTTPS URLs meeting specific resolution requirements (minimum 1000x1000 pixels, white background for main images). Shopify CDN URLs usually work, but you'll need to verify each one.

WooCommerce Exports

WooCommerce's CSV export format differs from Shopify's in several ways that add extra conversion work.

Variable product structure: WooCommerce handles variations differently than Shopify. Variable products and their variations export as linked rows with parent and variation types. While this is conceptually closer to Amazon's parent-child model, the field names and relationship mechanism are still completely different.

Custom attributes: WooCommerce stores product attributes in a pipe-delimited format within single columns (e.g., Color: Blue | Size: Large). These need to be parsed, split, and mapped to Amazon's separate attribute columns.

Plugin-dependent exports: Different WooCommerce export plugins produce different CSV formats. If you use WooCommerce Product Export or a third-party plugin, the column names and structure may vary. There's no single "WooCommerce format."

WordPress-specific content: Description fields often contain WordPress shortcodes, Gutenberg block markup, or custom field plugin syntax that needs to be cleaned before Amazon will accept it.

ERP Systems

ERP exports are often the most challenging source because they're designed for internal operations, not marketplace listings.

Internal codes instead of human-readable names: Your ERP might use MAT-4721-BLU-XL as a product identifier. Amazon needs a properly formatted title, brand, and attribute values. The translation from internal codes to consumer-facing content is rarely automated.

Custom field names: Every ERP has its own schema. SAP, Oracle, Microsoft Dynamics, Odoo — each uses different terminology. MATNR, Material Description, ArticleDescription, Bezeichnung. None of these map directly to Amazon's column names without a manual mapping exercise.

Unit mismatches: ERPs often store measurements in units that differ from Amazon's expectations. Weights in grams when Amazon wants pounds. Dimensions in millimeters when Amazon wants inches. Currency in EUR when the marketplace expects USD. Every value needs conversion.

Language mismatches: If your ERP runs in German but you're listing on Amazon US, every text field needs translation. Product titles, descriptions, bullet points, material descriptions — all of it.

Missing consumer-facing content: ERPs store operational data — stock levels, costs, supplier codes. They typically don't store SEO-optimized titles, marketing bullet points, or lifestyle product descriptions. This content needs to be written from scratch.

Supplier Spreadsheets

Supplier data is almost always the messiest source format. There's no standard, and quality varies wildly.

Inconsistent formatting: One supplier sends Excel files with merged cells. Another sends CSVs with semicolon delimiters. A third sends PDFs. Even within a single supplier's catalog, formatting may change between product lines.

Missing required fields: Suppliers rarely provide all the data Amazon requires. EAN/UPC codes might be missing. Dimensions might be incomplete. Compliance certifications are almost never included. You end up manually researching and filling in dozens of fields per product.

Incorrect or outdated data: Supplier catalogs frequently contain errors — wrong weights, outdated descriptions, incorrect model numbers. Blindly importing this data into Amazon leads to listing suppressions and policy violations.

Multiple languages in one file: International suppliers sometimes mix languages within a single spreadsheet. Column headers in English, values in German, product names in French. Amazon needs everything in one consistent language per marketplace.

Common Pitfalls When Converting Data Manually

Beyond source-specific issues, certain mistakes show up repeatedly regardless of where your data comes from.

Field name confusion. Amazon has fields like item_name, product_description, generic_keyword, and recommended_browse_nodes. Confusing item_name with product_description — or worse, mapping to deprecated fields — causes silent failures that only surface as rejected listings.

Value format errors. Amazon expects specific formats: TRUE/FALSE (not Yes/No), specific date formats, numeric values without currency symbols, dimensions with separate value and unit columns. Getting any of these wrong triggers validation errors that are tedious to debug.

Character encoding issues. Exporting from one system and importing into another often corrupts special characters. German umlauts (a, o, u), accented characters, trademark symbols — any non-ASCII character is at risk. Saving in the wrong encoding turns your carefully written descriptions into gibberish.

Variation structure errors. Parent rows missing required fields. Child rows not linked to their parent. Variation themes inconsistent within a family. Size values that don't match Amazon's accepted list. These structural errors are particularly painful because they often affect entire product families, not just individual rows.

Overwriting existing listings. If you already have products on Amazon and upload a flat file with the same SKUs, Amazon overwrites the existing data. Leaving a field blank in the flat file can erase data from your live listing. This is especially dangerous during migration — you might wipe out months of optimized content.

How AI Changes the Conversion Process

The manual process described above has a fundamental problem: it's repetitive, error-prone, and scales linearly with product count. Whether you have 50 products or 5,000, someone has to map every column, reformat every value, and validate every row.

This is exactly the kind of work that AI handles well. Pattern recognition across field names. Value transformation based on rules. Validation against structured requirements. The core of the conversion problem isn't creative — it's mechanical. But it's mechanical work that requires understanding context, which is why simple find-and-replace scripts don't cut it.

Automatic field mapping. Instead of manually matching your columns to Amazon's, AI analyzes your column headers and sample data to propose mappings. Title maps to item_name. Body (HTML) maps to product_description and bullet_point. Variant Price maps to standard_price. You review the suggestions and confirm — what took hours takes minutes.

Intelligent value transformation. AI can recognize that "Dark Blue" should become "Navy" in Amazon's controlled vocabulary, that "50cm x 30cm x 20cm" needs to be split into three separate dimension fields with unit conversion, and that HTML tags need to be stripped while preserving the content structure.

Real-time validation. Instead of uploading to Amazon and waiting for a processing report to tell you what's wrong, validation happens as you work. Every cell is checked against Amazon's rules. Errors are highlighted with clear explanations — not the cryptic error codes Seller Central returns.

Structure transformation. AI can detect which products are variations of each other, propose family groupings, and generate parent rows with the correct variation themes — turning the most painful part of the conversion into a guided process.

This is the approach we built Flat Magic around. You upload your data in whatever format you have — Shopify export, WooCommerce CSV, ERP dump, supplier spreadsheet, or even a product URL. The AI handles the mapping, reformatting, validation, and structure transformation. You review the results in a visual interface, make any adjustments, and export a validated flat file that Seller Central accepts on the first try.

The entire conversion — from raw data to export-ready file — typically takes 10 to 20 minutes regardless of product count. That's a 95% reduction compared to the manual process.

FAQ

Can I convert data from multiple sources into a single Amazon flat file?

Yes. In practice, most sellers combine data from several sources — product descriptions from their website, specifications from supplier sheets, images from a DAM system, compliance data from certification documents. The conversion process needs to merge all of these into one coherent flat file. Tools like Flat Magic support uploading supplementary sources that get merged into the primary data automatically, with conflict resolution for overlapping fields.

What if my source data is missing fields that Amazon requires?

This is extremely common. Shopify exports don't include manufacturer part numbers. Supplier sheets rarely have compliance certifications. ERP dumps lack marketing content. You have three options: fill in the missing data manually, pull it from a supplementary source (product URLs, spec sheets, compliance documents), or — for fields like brand, material, or country of origin — use AI to extract the information from your existing descriptions and images. Required fields that remain empty will be flagged during validation so you know exactly what still needs attention.

Do I need to convert my data into a specific intermediate format first?

No. The whole point of modern conversion tools is accepting data in whatever format you already have. Excel spreadsheets (.xlsx, .xls), CSV files with any delimiter, WooCommerce exports, Shopify exports, ERP dumps — they all work as input. You shouldn't have to reformat your data before the reformatting tool even touches it.

How do I handle products that exist on both Shopify and Amazon?

Carefully. If you already have active listings on Amazon, uploading a flat file with the same SKUs will overwrite existing data. Any field left blank in your flat file could erase data from your live listing. The safest approach: export your current Amazon listings first, use them as a baseline, and merge your Shopify data on top. This way you enrich existing listings rather than accidentally wiping out optimized content.

The Bottom Line

Converting product data from Shopify, WooCommerce, ERPs, or supplier sheets into an Amazon flat file is one of the most time-consuming tasks sellers face when expanding to Amazon. The manual process is well-understood but brutally repetitive — and it scales poorly as your catalog grows.

The good news: this is a solved problem. AI-powered tools can handle the mapping, reformatting, validation, and structure transformation that used to consume days of manual work. The data conversion that took 10-20 hours now takes 10-20 minutes.

If you're sitting on product data that needs to become an Amazon flat file, try Flat Magic free and convert your first file in minutes instead of days.