After a price list was uploaded to WooCommerce, the previous product listing remained and a new one appeared beside it. This makes it harder for customers to choose a product and adds a second URL with similar content to the site. Start fixing the issue by checking identifiers and the import mode, not by adding a canonical between the duplicates.
This article covers the built-in WooCommerce CSV importer. Paid extensions and supplier integrations may use different headers and rules. Before you begin, note the store version and the tool used to upload the file: the fact that two files have the same CSV extension does not mean they behave the same way.
What data to compare between the two product listings
Open the old and new product listings in the admin panel. Record the ID, SKU, product name, publication status, and public URL. SKU is the product code you use to match the product; it is not necessarily its name or the supplier code in a neighboring column.
Find the corresponding row in the imported file. Compare the SKU character by character, including spaces, leading zeros, and hyphens. A spreadsheet editor can turn 00127 into the number 127, or an employee may rename the SKU for convenience. The product looks the same, but its matching key has changed.
Save the latest import report and note the selected mode. If there is no report, mark this as unknown. Two product listings confirm a duplicate, but do not prove which importer created it. First link the new listing to the operation using its time and log, then repeat the operation on a small sample.
How updates work with the built-in importer
The built-in tool matches existing products by ID or SKU. To update products, go to Products → All Products → Import, select the file, and enable Update existing products. Then proceed to column mapping and check which column maps to SKU and which to price. This process is described in the WooCommerce CSV documentation.
In update mode, matching products are updated. The behavior for new variations depends on the version, so this guide uses simple products for the test sample. If you are importing variable and variation products, use this separate guide to variation-parent relationships.
Mark columns that do not need to be changed as Do not import. For example, a task to update the price does not require overwriting the description. Ask the person doing the work to save a screenshot of the mapping screen: the CSV header “Price” alone does not show which field it was mapped to during a particular import.
A practice example with a leading zero
Imagine a store with an existing product with SKU 00127. Its current price is 4900; the new price is 5200. This is a fictional example. The price list was processed in a spreadsheet, and the SKU became 127. If the file is uploaded as new products, the store may get a new listing instead of the existing one being updated.
The correct test file for an update preserves the original key:
SKU,Regular price
00127,5200Before importing, open the saved CSV in a text editor and make sure it contains exactly 00127. The cell format displayed in a spreadsheet does not prove that the text was preserved in the file. Then map the columns, select the option to update existing products, and check the previous ID after the import is complete.
Expected result: the price changes on the old product listing, its ID and URL remain the same, and no new record is created. A matching total product count is a supplementary check. It does not replace checking the specific product: one product could have been added while another was accidentally deleted manually.
How to prepare a safe sample
Export several existing simple products using the built-in tool and use that file as an example of the column layout. Include a product with a leading zero in its SKU, one with a hyphen, and one with a standard SKU. If there is a product without an SKU, decide separately which existing ID to match it to.
Work on a copy of the store with an up-to-date database. Prepare a backup and save the original prices of the test products. Do not start uploading the full price list again until the result for several rows has been explained. A reproducible small example is more useful than another attempt after which it is unclear where the new records came from.
Keep only the required fields in the CSV, save it as UTF-8, and review the final file. Enter prices in the format required by the importer, without a currency symbol. If values contain the CSV delimiter, make sure the editor has enclosed them in quotes correctly. Do not substitute columns from instructions for a different extension for the built-in column layout.
How to remove duplicates that have already appeared
First determine which product listing will remain as the primary one: the old one with history, links, and orders, or the new one, if it is genuinely a separate product. Do not decide based only on the creation date. Compare variations, attributes, stock levels, and which listing the categories and external links point to.
Save a mapping table for the two records, then give the developer a plan. If it is a genuine duplicate, agree on how to transfer any missing data and handle the extra public URL. Simply deleting the new listing could leave a broken link in an ad or menu. And a canonical does not fix an incorrect SKU that will create another duplicate during the next upload.
After correcting the data, repeat the test import. Make sure the operation is repeatable: running the same file a second time updates the same products instead of creating another set. Set up a separate process for creating new products so that the updates price list is not mixed with unreviewed new items.
How to handle new products in the price list
If a supplier sends an unknown SKU, determine whether it is a new product or a renamed SKU for an existing one. In the latter case, an explicit mapping table is needed. Do not automatically treat every mismatch as a new product. For the practice store, first match row 127 to the original 00127 and correct the key; send a genuinely new model to a separate creation file. This keeps recurring price lists clear for employees.
What to include in the task and acceptance criteria
Make the task specific: “The price list with SKU 00127 must change the price of existing product ID N to 5200, while preserving the URL; importing it again must not create a record.” Attach the original CSV, both duplicate listings, a screenshot of the column mapping, and the WooCommerce version. The ID number in a work task must be real; replace the sample N with the store’s value.
After release, check the price in the editor and on the public page while logged out of WordPress. Confirm that the currency, stock level, and selected product variation are as expected. An old cached price on the storefront is a separate data-delivery issue, even if the import has correctly updated the database.
Check links from the category, the store search, and the sitemap. For the sitemap, see the WordPress sitemap guide; for accessible pages and related errors, see the technical audit. Search rankings are not an import acceptance criterion: first you need to prove that the right products are updated using stable keys and are not duplicated by the next price list.