How to Generate Product Feeds from Shopify and Shopware (and When They Break)

Product feeds are the central nervous system of modern ecommerce. They power platforms like Google Merchant Center, Meta Catalogs, and TikTok Shop. The quality of your source feed directly impacts your ad performance.

Many merchants treat feed generation as a set-and-forget export. In reality, the architecture of your CMS—whether the opinionated SaaS of Shopify or the flexible, self-hosted setup of Shopware 6—creates structural constraints and failure points. This guide explains how these systems work, common pitfalls, and best practices for scalable product feeds.

1. Shopify Feed Generation: The Opinionated Pipeline

Shopify's data model prioritizes storefront simplicity over complex marketing syndication. Its variant limits and API throttling tiers create unique challenges for larger catalogs.

1.1 Native Admin CSV Export

• Mechanism: Manual trigger within Shopify Admin to generate a products.csv.
• Reality: Intended for migrations, not automated feeds. No static URL for scheduled fetching.
• Failure Point: Missing crucial marketing metadata (e.g., Google Product Categories) that aren't native Shopify fields.

1.2 Native Google & Meta Channels

• Mechanism: Direct API-to-API synchronization.
• Black Box Problem: Easy to set up but almost no visibility. Rejection errors are often vague.
• Failure Point: Cannot decouple storefront from feed data. Optimizing a title for SEO without changing the website title is usually impossible.

1.3 App-Based Feed Generation (Liquid/GraphQL)

• Mechanism: Third-party apps crawl the store via Liquid templates or the GraphQL Admin API.
• System Limitation: For catalogs over 10,000 SKUs, Liquid exports often hit memory or execution limits.
• Failure Point: Poor apps often fail to map parent images to child variants, causing missing image errors in Merchant Center.

1.4 Custom API / Bulk Operations (Scalable Approach)

Enterprise stores can bypass throttling using Shopify's Bulk Operations API. This asynchronous GraphQL-based approach handles large datasets without hitting real-time execution limits.

2. Shopware 6 Feed Generation: Flexible but Complex

Shopware 6 treats feeds as headless "Sales Channels" and uses Twig templates for structured CSV/XML exports.

2.1 Twig-Based Export Profiles

• Advantage: Extreme granularity; you can embed logic like conditional stock or price adjustments.
• Failure Point: Complex Twig logic can crash PHP or slow the database if not cached correctly.

Example of conditional availability logic in Twig:

<g:availability>
    {% if product.stock >= 5 %}
        in_stock
    {% elseif product.stock < 5 and product.stock > 0 %}
        limited_availability
    {% else %}
        out_of_stock
    {% endif %}
</g:availability>

2.2 Variant Handling & UUIDs

Every variant in Shopware is a separate entity with a unique UUID. This requires careful mapping to preserve parent-child relationships in flat CSV exports.

2.3 Common Pitfalls

• Circular References: Infinite loops in category mapping.
• Context Misalignment: Exporting prices for the wrong customer group or currency leads to price mismatches.

3. Common Source Feed Anti-Patterns

• ID Instability: Changing ID formats mid-campaign resets ad platform learning and destroys historical performance.
• JS-Price Trap: Client-side pricing via JavaScript is invisible to feed exporters, leading to mismatches between feed and landing page.
• HTML Bloat: Raw HTML or CSS in descriptions can break XML parsers. Always strip HTML before exporting.

4. CMS vs. Feed Layer: Clear Responsibility Split

5. The Role of 42feeds

42feeds acts as the post-export transformation and observability layer. We help you transform, filter, and observe your data before it reaches ad platforms, preventing Merchant Center feed errors and ensuring consistency across channels.

Summary

• XML is generally superior to CSV for nested variant data.
• Avoid native "one-click" integrations for large-scale operations if you need data control.
• Use a dedicated feed layer like 42feeds to decouple marketing logic from your core CMS infrastructure.