You can export WooCommerce products to CSV using the tool already in your store dashboard. To protect your product data, include the fields you need, keep variations connected to their parent products, and test the file before importing it anywhere.
The download is the easy part. Keeping the details usable takes a little preparation, especially if your store uses custom fields or product images. Let's make the process straightforward.
Key Takeaways
- WooCommerce can export product columns, types, and categories from the Products screen.
- Custom metadata needs its own export setting, even when you export all standard columns.
- Variations have separate rows, while product images are represented by URLs.
- A CSV is useful for catalog work, but a restorable site backup is your safety net.
- Test a small import and inspect the products before moving the full catalog.
Prepare a Safe WooCommerce Product Export
A little preparation makes the export easier to trust. Start by deciding what the file needs to do: provide a catalog reference, support bulk edits, or move products into another store.

Save a Restorable Site Backup
A product CSV is not a complete store backup. It doesn't replace a backup of your WordPress database and site files, including your uploaded media.
Before a large update or migration, save a restorable backup. Keep it separate from the CSV so you have a way back if an import changes more than you intended. If you have a staging site, use it for the first import test.
Identify the Product Details That Matter
Look at the products you plan to move or edit. Alongside names and prices, think about SKUs, stock, categories, attributes, variations, images, and any fields added by extensions.
Make a note of anything your store relies on that isn't part of a typical product listing. A custom specification, for example, may need metadata or a separate extension workflow. Knowing that before you export gives you a much better starting point.
Export WooCommerce Products to CSV
WooCommerce includes a built-in product exporter. You can choose which products and columns to include, then download the result as a CSV file.
Here's the basic path:
- In your WordPress dashboard, open Products > All Products and select Export.
- Choose the columns you need, or leave the selection at its default to export all columns.
- Choose product types and categories if you need a smaller set. Leave them at their defaults for the full catalog.
- Select Yes, export all custom meta if you need custom metadata in the file.
- Click Generate CSV and save the download in a secure location.
WooCommerce's product CSV documentation covers the built-in exporter and importer in detail.
We recommend saving the original download untouched. If you need to edit it, work on a copy. That gives you a clean reference when a column gets moved or a value changes unexpectedly.
Exporting a single category can be useful for a focused update. For a migration, be careful with narrow filters: a smaller file is easier to handle, but it may leave out products or variation rows you meant to keep.
Include Custom Fields Before You Download
Standard product columns cover a lot. Custom metadata is where you need to pay extra attention.

Turn On the Metadata Option
Custom metadata is excluded by default. Selecting all standard columns doesn't automatically include it, so choose Yes, export all custom meta when those fields matter to your store.
WooCommerce uses headers beginning with meta: for included metadata. For example, a stored key named product_depth appears as meta:product_depth. Keep that prefix when preparing the file for WooCommerce's built-in importer.
Account for Extension Data
A plugin can add details that aren't obvious in the standard product editor. That might include extra specifications or data used by a specialized product type.
Exporting metadata is a helpful step, but it doesn't promise that every extension's complete setup will move with the file. For example, WooCommerce documents separate Product CSV Import Suite integrations for subscription products. If your catalog depends on those features, use the workflow intended for them and test the result.
Keep Variable Products and Variations Together
A variable product is a family of related rows. The parent holds the main product, while each variation has its own row and a relationship back to that parent.
That matters when you're filtering or editing your CSV. Keep the parent and its relevant variations together, along with their type and parent fields. Otherwise, the destination store may not have the information needed to rebuild the product choices as intended.
Protect Product IDs and SKUs
SKUs help identify products and variations. Keep them as text when opening a CSV in spreadsheet software, especially if codes contain leading zeros.
IDs need care too. An ID identifies a product in its own store, but another store can have different IDs. For an update, start with an export from the destination store and use its existing IDs or SKUs to match the right products.
Before importing new items, compare their SKUs with the destination catalog. A repeated code can turn an intended addition into a matching conflict.
Keep Attributes Attached to Their Rows
Variation choices depend on product attributes. If a shirt has size and color options, the parent and variation rows need the relevant attribute information in the expected columns.
Don't remove those columns simply because they make the spreadsheet wider. They help describe which choices belong to the product and which combination belongs to each variation. After a test import, open the product page and select the available options to see whether they behave as expected.
Preserve Product Images During a Move
Product photos make a catalog feel complete, and the CSV handles them as links. The Images field contains image URLs rather than the image files themselves.
The first URL identifies the featured image. Additional URLs represent gallery images, so their order matters. Keep the field intact when editing the file.
Keep Source Images Available
If you're importing into another store, the image URLs need to remain accessible for the import. Don't take down the original site or remove its media before you've completed the move and inspected the destination products.
Your site backup should include the media files too. That gives you a separate copy of the images, rather than relying only on addresses stored in a spreadsheet.
Inspect the Finished Product Pages
After a test import, open several product pages and look beyond the main image. Check gallery order and any variation images your products use.
A CSV can contain an image address while the destination page still doesn't look right. The storefront check catches the practical problem: what your customers will actually see.
Edit the CSV Without Changing the Wrong Values
Spreadsheets make bulk edits easier, but they can also change the shape of your data. We like to keep the original export untouched and make changes in a separate working copy.
Treat SKUs as Text
A code such as 00125 is an identifier, not a number to calculate. If your spreadsheet drops the leading zeros, the SKU no longer matches the original value.
Use your spreadsheet's import options to treat SKU columns as text. Give the same attention to other identifier fields that must remain exactly as exported. Before saving, compare a few edited rows with the original file.
Move Complete Rows, Not Individual Cells
Each row belongs to one product or variation. If you sort only one column, product names, prices, and SKUs can end up beside the wrong items.
Select the full data range when sorting, and keep the column headers with their corresponding values. Save the working file as CSV when you're ready to import it. Then reopen it and look for shifted columns or unexpected changes.
Test the Import Before Updating the Full Catalog
A successful download tells you the export ran. A small import tells you much more about whether the file works for your destination store.
Choose a sample that reflects your catalog: a simple product, a variable product with its variations, and a product with custom fields if you use them. Run the test on staging when possible.
Choose Addition or Update Mode
In WordPress, open Products > All Products > Import and upload the sample CSV. Review the column mapping and make sure WooCommerce recognizes the fields you intend to use.
Select Update existing products only when the file is meant to change products already in that store. The built-in importer matches updates by ID or SKU and skips rows it can't match in update mode.
For a closer look at matching and conflict prevention, our WooCommerce product import guide walks through duplicate SKUs and safe updates.
Review the Report and Storefront
After the import, inspect the report and open the affected products. Look at names, prices, stock, SKUs, variation choices, custom fields, and images where they apply.
If rows fail, pause before uploading the file again. Save the report, identify what succeeded, and resolve conflicts first. Repeating an import without that review can make it harder to tell which products were changed.
For live stores, remember that stock can change while you test. Refresh the quantities you intend to update before the final run.
Know When You Need a Different Export
The built-in exporter is a practical starting point for product data. It isn't a full-store migration tool, and a product CSV doesn't include every kind of store record.
Need order records for bookkeeping? Our WooCommerce order export guide covers that separate workflow. Product reviews may also need their own tool; WooCommerce documents an extension for importing and exporting product reviews.
For specialized product types or plugin data, choose a tool that supports the fields involved. Follow that tool's import instructions rather than mixing its file structure with the built-in WooCommerce importer.
Give Your Store a Strong Hosting Foundation
A clean CSV helps with the catalog. Good hosting supports the WordPress store that runs it.
We offer WordPress hosting and cPanel hosting for businesses building and managing their sites. Our 24/7 support is there when you need help with the hosting side of your store, whether you're preparing a move or managing your site after launch.
Keep your backup plan, product export, and import test in place alongside that hosting foundation. Each has a different job, and together they give you a more controlled way to make changes.
Frequently Asked Questions
Does a WooCommerce Product CSV Include Images?
It includes image URLs, not the image files themselves. Keep the source images accessible during an import and inspect the destination product pages afterward.
Can I Export Only One Product Category?
Yes. The built-in export screen lets you choose categories and product types. Review your selection carefully if you also need variations or related products.
Does Exporting All Columns Include Custom Metadata?
No. Custom metadata has a separate option on the export screen. Select Yes, export all custom meta when you need those fields in your CSV.
Move Your Catalog With Confidence
A WooCommerce product export gives you a useful file for moving or updating your catalog. The details make the difference: include custom metadata, keep variation rows connected, and protect your image sources.
Save the original CSV and a restorable backup, then test a small batch before the full import. You'll have a clearer view of what moved and a safer path forward.





