How to Export Individual Products in WooCommerce in 2026
WooCommerce’s built-in export tool is built for bulk work, select everything or filter by category, dump it all to CSV. What it doesn’t do well is grab one specific product’s data on its own, which is exactly the task that comes up constantly: pulling a single listing to hand to a copywriter, archiving a product before a price change, or pulling one row to debug why a specific SKU is behaving oddly in a feed. Here’s how to actually export individual products in WooCommerce, using the native tools where they stretch far enough and a plugin where they don’t.
Why You’d Want a Single Product Export
A few situations come up over and over. You’re updating pricing or descriptions and want a clean before/after record in case something needs rolling back. You’re migrating one product line to a new platform without touching the rest of the catalog. You’re debugging a data issue, a product showing wrong stock status in your Google Shopping feed, say, and need to see exactly what WooCommerce has stored for that item without wading through a 2,000-row export. Or you’re handing off product data to a freelancer or agency and don’t want to expose your entire catalog to do it.
In every one of these cases, exporting the whole store is overkill, and it makes the resulting file harder to use, not easier.
What WooCommerce’s Native Export Actually Supports
Go to Products > All Products, and you’ll see an Export button at the top of the screen. Click it and WooCommerce opens a screen letting you choose which columns to include (SKU, price, stock, categories, custom fields, and so on) and filter by product type or category. This is genuinely useful, but the filtering options stop short of “just this one product.” There’s no search-by-name or search-by-SKU field on the native export screen.
The workaround with native tools alone: filter by category if the product happens to be the only one in a narrow category, or export everything and then delete every row except the one you need in a spreadsheet afterward. Both work, but they’re clumsy for a task that should take thirty seconds.
The Cleaner Path: A Dedicated Export Plugin
For real single-product control, a plugin with per-product filtering does the job properly. A few options exist in this space, each with a different balance of power and simplicity:
- WP All Export, the most flexible of the group, lets you filter by specific product ID, SKU, or name, choose exactly which fields go into the file, and even set up a template you can reuse for future one-off exports.
- Product CSV Import Suite, a premium option built specifically around WooCommerce’s product data structure, with strong handling of variations and custom attributes.
- Lighter, single-purpose export plugins that skip the advanced field mapping in exchange for a simpler one-click export per product.
For most stores, WP All Export’s free tier covers a single-product export need without any additional cost.
Step-by-Step: Exporting One Product with a Plugin
The exact screens vary slightly by plugin, but the flow is consistent enough to walk through generically:
Install and activate. Go to Plugins > Add New, search for your chosen export plugin, then install it and click through to activate.
Start a new export. Look for a new menu item (often All Export or similar) in your dashboard sidebar, and click to start a new export job.
Choose WooCommerce Products as the export type. Most plugins ask what kind of content you’re exporting before showing filter options.
Filter down to the one product. This is the step the native tool skips. Filter by product ID, SKU, or exact title match, whichever your plugin supports. Confirm in the preview that exactly one row shows up before continuing.
Pick your fields. Decide what actually needs to be in the file. For a pricing audit you might only need SKU, regular price, and sale price. For a full migration you’ll want everything, description, images, attributes, categories, stock status, and any custom meta fields the product carries.
Preview and export. Check the preview screen before generating the file. A misconfigured field mapping is much cheaper to catch here than after you’ve handed the file to someone else.
Download the file. You’ll get a CSV or Excel file depending on your settings. Save it somewhere you’ll actually find it again, a dedicated exports folder beats a downloads folder that also has three years of random screenshots in it.
Also Read: How to Apply Multiple Shipping Classes to a Product in WooCommerce
Exporting a Variable Product Correctly
If the product you’re exporting has variations (different sizes, colors, or configurations under one parent product), pay close attention to how your export tool handles the parent-variation relationship. Some exports flatten every variation into its own row, which is correct if you plan to re-import the data or need every SKU’s individual price and stock level visible. Others export just the parent product’s shared data and skip the variation-level detail entirely, which is fine for a quick content review but useless for a pricing audit across variations.
Check the preview screen specifically for this before running the export. Getting three rows when you expected one (or one row when you needed twelve) is the most common surprise with variable product exports.
What to Do With the File Once You Have It
Open it before you send it anywhere. A CSV that looks fine in the export tool’s preview can still open with garbled special characters, misaligned columns, or truncated descriptions depending on the encoding settings and the spreadsheet software reading it. Open the file in whatever tool the recipient will actually use (Excel, Google Sheets, a plain text editor for a quick sanity check) rather than trusting the export tool’s own preview screen as the final word.
If you’re archiving the file for a rollback scenario, name it with the date and product SKU rather than a generic “export.csv” that will be indistinguishable from the next five exports you run. A file named sku-8842-backup-2026-08-05.csv tells you everything at a glance six months later. A file named export (3).csv tells you nothing.
Common Problems and Fixes
A few issues come up repeatedly with single-product exports, worth knowing before you hit them cold.
The export plugin conflicts with another active plugin, most often something touching the product data structure itself (a custom fields plugin, a multi-vendor plugin, an inventory sync tool). If your export comes back empty or throws an error, deactivate other plugins one at a time and retry to isolate the conflict.
Custom fields don’t show up in the field picker. This usually means the export plugin hasn’t detected the meta key yet, some plugins need you to run one export first (even an incomplete one) before newer custom fields register in their mapping interface.
The exported description strips HTML formatting. If your product description uses bold text, bullet lists, or embedded links, check whether your export tool preserves raw HTML in the field or converts it to plain text. For a content-review export this might not matter, for a re-import into another system it matters a great deal.
Exporting Without a Plugin, the Manual Way
If installing another plugin feels like overkill for a one-time need, there’s a lower-tech option. Open the product in the WooCommerce admin editor, and copy the fields you need directly into a spreadsheet or document by hand. For a single product with a handful of fields (title, price, short description), this can genuinely be faster than configuring an export plugin, especially if you’ll never need to repeat the task. It doesn’t scale past one or two products, but for a true one-off, don’t discount the low-tech option just because it isn’t automated.
Exporting a Single Product for a Marketplace Feed
One case worth calling out separately: pulling one product’s data to feed into a specific channel like Google Shopping, Amazon, or a comparison-shopping engine. Each of these channels expects its own field structure, Google Shopping wants GTIN and product category codes formatted a particular way, for instance, and a generic WooCommerce export won’t automatically match that structure.
Most stores solve this with a feed-specific plugin rather than a general export tool, since feed plugins handle the field mapping and formatting rules for you. If you’re troubleshooting why one product isn’t showing correctly in a shopping feed, though, a plain single-product export from your general export plugin is still the fastest way to see exactly what data WooCommerce has stored, before you go hunting through the feed plugin’s own logs.
Exporting Product Images Alongside Data
A CSV export captures image URLs, not the image files themselves. If you need the actual image files, not just links to where they live on your current site, you’ll need to download them separately from the Media Library or via FTP access to your uploads folder. This distinction trips people up constantly during migrations: the spreadsheet looks complete, every field is filled in, but the images are just pointers back to a server that won’t exist once the migration is done. If you’re moving a product to a new platform or a new host, grab the actual image files at the same time you export the data, not as an afterthought once the CSV is already in someone else’s hands.
Exporting Custom Product Meta and Third-Party Plugin Data
If your product carries data added by other plugins, custom fields from an extended product options plugin, warranty information, bundled product relationships, that data lives as post meta attached to the product, separate from WooCommerce’s core fields. Whether your export tool picks this up automatically depends entirely on the plugin. Some export tools scan and expose every meta key on a product automatically. Others only show WooCommerce’s own core fields unless you manually add the custom meta key to the field list.
If a field you expect is missing from your export, check the product in the database directly (via a tool like phpMyAdmin, or ask a developer to check) to confirm the meta key actually exists and get its exact name, then add it manually to your export configuration if your plugin supports custom field mapping.
Comparing Your Options
| Method | Best for | Setup time | Handles variations well? |
|---|---|---|---|
| Native WooCommerce export + manual filter | One-off, low frequency need | Low, but tedious to isolate one row | Partially |
| WP All Export or similar plugin | Repeated single-product exports | Moderate, one-time setup | Yes, configurable |
| Manual copy-paste | True one-off, few fields needed | Very low | No |
Building a Habit Around This
If you find yourself needing single-product exports more than a couple of times a month, it’s worth setting up a saved export template in your plugin of choice rather than reconfiguring the field list every time. Most export plugins let you save a configuration and reuse it, so the next time you need to pull one product, you’re filtering by ID and clicking export rather than rebuilding the whole job from scratch. That five-minute setup investment pays for itself the third or fourth time you use it.
Re-Importing After You’ve Made Changes
Exports rarely exist in isolation, most of the time you’re pulling data out to edit it somewhere else, then bringing it back in. If that’s your plan, use the same plugin for both the export and the eventual import. Mismatched tools between export and import often disagree on column naming, date formats, or how they handle empty fields, which turns a simple round trip into a debugging session.
Before importing edited data back into a live store, test the import on a staging copy first if you have one available. A malformed CSV column, a stray comma inside a description field that wasn’t properly escaped, can overwrite the wrong field or blank out data you didn’t intend to touch. This is the single biggest risk in the whole export-edit-import cycle, and it’s also the easiest one to avoid with a five-minute staging test.
When a Single Product Export Isn’t the Right Tool
If you find yourself exporting the same handful of products weekly to track pricing changes or monitor stock levels, a one-off CSV export is the wrong solution to a recurring problem. At that point, look at a proper inventory dashboard, a reporting plugin, or a scheduled export that runs automatically and lands in a folder or inbox without you having to trigger it by hand each time. Manual exports are for one-off needs. Recurring needs deserve recurring automation.
Frequently Asked Questions
Can I export a product along with its reviews?
Native WooCommerce export doesn’t include reviews since they’re stored as comments rather than product meta. A dedicated export plugin with comment or review support can pull them separately, but check this capability before assuming it’s included by default.
Will exporting a product affect the live listing?
No. Exporting reads data, it doesn’t modify or remove anything from your live store. The product stays exactly as it was before you exported it.
Can I schedule automatic exports of specific products?
Some premium export plugins support scheduled exports on a recurring basis, useful if you’re feeding a specific product’s data to an external system regularly. Check your plugin’s scheduling options under its export settings.
What file formats can I export to?
CSV is the most universal choice and works with virtually any spreadsheet tool or import system. Most export plugins also offer XML or Excel format directly, useful if you’re feeding the file into a system that expects a specific structure.
Do I need admin access to export a product, or will a lower-level user role work?
This depends on the export plugin’s own permission settings as much as WordPress’s default roles. Shop Manager accounts typically have enough capability to view and export product data, but a plugin can restrict its export screen to Administrators only. Check the plugin’s settings if a Shop Manager reports they can’t see the export option.
Is there a limit to how much data I can put in a single export?
For a single product this is a non-issue, but if you scale up to exporting many products with full descriptions, images, and variation data, very large files can hit server memory or execution time limits on shared hosting. That’s a bulk-export problem more than a single-product one, but worth knowing if today’s small export is the first step toward a bigger migration later.
Keeping Your Product Data Portable
A single product export is a small thing to set up but a genuinely useful thing to have on hand, whether you’re fixing pricing, cleaning up a listing, or preparing to migrate part of a catalog elsewhere. Once a plugin is installed and configured, repeating the export takes a couple of minutes. Having that habit in place means you’re never stuck reconstructing product data from memory or screenshots when something needs fixing fast.
The native WooCommerce export button is fine for bulk work, but treat it as a starting point rather than the finish line the moment you need surgical precision on one row. A dedicated plugin costs a few minutes to set up once and pays that back every single time you need to isolate one product from a catalog that’s grown too large to filter by hand.
Interesting Reads:
How to Change WooCommerce Magnifying Glass
