Product Feed Formats: CSV, XML, JSON, And Common Specifications

Product Feed A structured file or data stream containing product information such as identifiers, titles, descriptions, prices, availability, images, and attributes.

Choosing the right file format for a product feed affects how quickly you can onboard channels, how reliably fields map to platform requirements, and how easy it is to validate and maintain feeds at scale. The three formats you will encounter most often are CSV (comma-separated values), XML (often RSS or Atom-like structures), and JSON (including JSON-LD). Each has trade-offs in tooling, size, human readability, and validation.

How Each Format Works

CSV files store rows and columns — each row is a product (or variant) and each column is an attribute such as id, title, price, or image link. CSV is widely supported: marketplaces, shopping engines, and spreadsheets accept it. XML expresses the same data in nested tags, making it better suited for hierarchical attributes (for example, nested variant data). JSON and JSON-LD are native to web APIs and modern integrations; they support complex nested objects and arrays and integrate cleanly with REST APIs and JavaScript-based tooling.

What The Specification Typically Requires

• Identifiers: Unique product IDs (SKU, GTIN, MPN) and any required platform IDs.
• Text Fields: Title, description, short description; follow length and language rules.
• Pricing And Availability: Currency, price, sale price, availability status, and effective dates.
• Images And Links: Primary and additional image URLs, landing page link.
• Attributes: Category path, brand, color, size, material, shipping dimensions, and tax class where required.

Why Format Choice Matters

Format choice influences validation and automation. CSV is easy to export from commerce platforms and spreadsheets, but column mismatches and escaping issues (commas inside text) are common failure points. XML enforces structure that reduces ambiguity but can be more verbose and slower to parse. JSON works well when you push updates over APIs or connect to microservices, and it's the preferred format for programmatic feeds and streaming updates.

How It Varies By Channel

Different channels prefer or require different formats: many marketplace UIs accept CSV for manual uploads; Google Merchant Center supports XML, TSV, and CSV and also accepts the Content API (JSON over HTTP) for real-time updates. Social commerce platforms and ad networks may accept only one or two formats and enforce strict attribute rules. Always consult the channel's product data specification before preparing a feed.

Practical Example: Preparing The Same Data In Three Formats

Imagine a single SKU with brand, title, price, and an image. In CSV it is one row with columns: id,title,price,brand,image_link. In XML you'd wrap fields in a product node with child tags. In JSON you'd produce an object with keys for id, title, price, brand, and an array for images. Each version delivers identical information; validation tools and the receiving system determine which format is easiest to consume.

Tips For Reliable Feeds

• Match Field Names: Use the exact attribute names and formats required by the target channel to avoid automated rejections.
• Normalize Identifiers: Use GS1 GTINs where available and keep SKU stable; platforms often rely on those identifiers for matching and variants.
• Validate Early: Run feeds through a schema validator (XML schema, JSON schema) and a channel-specific validator before upload.
• Prefer APIs For Frequent Updates: If prices, stock, or promotions change hourly, push updates via an API or the channel's streaming feed option instead of periodic full-file uploads.
• Document Transformations: Keep a mapping document that shows how your internal attributes map to channel attributes — it speeds troubleshooting and auditing.

In short, the Product Feed format you choose should match the channel requirements, your internal tooling, and update cadence. CSV is simple and universal; XML provides structure for complex hierarchies; JSON works best for API-driven, programmatic integrations. Validate feeds against channel specs and standard identifiers to avoid disapprovals and deliver accurate product data.