How to create product feeds in WooCommerce

Decide where the feed will go before exporting anything. Google Merchant Center accepts tab-delimited files and XML, while other marketplaces may require their own CSV, XML, or JSON fields. The destination specification determines the column names, required values, currency format, and update method.

For a small one-off export, CSV is usually easiest to inspect. For a feed that another service fetches regularly, use the format and URL structure required by that service.

Complete the product information that the destination needs before generating the feed. At a minimum, check the product title, description, product ID or SKU, product URL, main image, price, stock status, and product type. Google also commonly needs identifiers such as GTIN, brand, or MPN, depending on the product.

Check variable products carefully. A parent product and its variations may need separate rows, variation-specific prices, stock status, images, and identifiers. Do not invent GTINs or use the same identifier for unrelated products.

Go to Products in WordPress and select Export. Choose whether to export all products or a filtered group, then download the CSV. WooCommerce includes a built-in product CSV importer and exporter for product data and bulk updates.

This is the honest manual route: the file is a product export, not automatically a finished Google, Amazon, or eBay feed. You will need to rename or add columns, format values, handle variations, and remove fields that the destination does not accept. It becomes awkward when products change regularly.

Open a copy of the export in a spreadsheet and map each WooCommerce value to the destination’s required field. Typical mappings include SKU to id, product name to title, description to description, product URL to link, image URL to image_link, price to price, and stock status to availability.

Keep prices in the required currency format, use full publicly accessible image and product URLs, and escape characters correctly in XML. Do not paste HTML into fields unless the destination specification allows it. For Google, shipping and tax are often configured in Merchant Center rather than repeated in every feed row.

Upload the finished file where the marketplace tells you to. In Google Merchant Center, you can submit a file by one-time upload or by giving Google a hosted file URL. Google accepts TXT, XML, and TSV files, but an unsupported format or incorrect field formatting can stop the feed from processing.

Read the item-level errors instead of only checking whether the file uploaded. Common failures include missing identifiers, invalid prices, inaccessible images, incorrect availability, malformed XML, and product pages that do not match the submitted data.

If prices, stock, images, or variations change often, do not rely on repeatedly editing the exported CSV. Use a feed tool that maps WooCommerce fields to channel attributes, filters products, creates XML, CSV, or JSON output, and refreshes the feed on a schedule.

Fast way: CTX Feed Pro is a practical option when you need feeds for several channels. It supports XML, CSV, and JSON feeds, field mapping, filters, and scheduled updates for destinations such as Google Shopping, Amazon, and eBay. You still need to review the destination’s requirements and fix missing product data before submitting the feed.