Troubleshooting · Troubleshooting
How to Fix WooCommerce Prices Not Updating
Short answer
A price that will not update is usually a stale cache, a sale schedule that has not started or ended, or a lookup table that is out of sync after a bulk edit. First check whether the product page or only the shop listings show the old price, then clear transients and regenerate the product lookup tables at WooCommerce > Status > Tools. Re-save the product in the editor to force a fresh sync.
Key takeaways
- Listings read lookup tables, so a stale table shows old prices on the shop page.
- A sale price only shows inside its From and To dates.
- Each variation carries its own price; the parent product has none.
- CSV price updates must tick Update existing products and match by ID or SKU.
- Clear transients and purge the cache after any price change.
Why are my WooCommerce prices not updating?
A price that will not update is usually a stale cache, a sale schedule that has not started or ended, or a lookup table that is out of sync after a bulk edit.
Start by working out where the old price appears. If the product page shows the new price but the shop page shows the old one, the listings are reading stale data. If every page shows the old price, the saved price itself is wrong or a schedule is holding it back.
Do not edit the database by hand to force a change. Direct edits skip the steps WooCommerce runs when you save a product, so the listings can stay wrong even after the database value changes. Use the editor, the importer, or the tools below instead.
Check one product first and get it right, then apply the same fix to the rest. A single-product test tells you whether the cause is the product, the cache, or the store.
Is the price wrong on the product page or only in listings?
If the product page is right and the listings are wrong, the product lookup tables are out of sync.
WooCommerce keeps lookup tables that store product data for quick access, so shop pages, category pages, and price filters load fast. WooCommerce's System Tools guide states that if these tables go out of sync with the products, incorrect product details may show up.
Bulk edits and CSV imports are the usual cause, since they can update the product without updating the lookup row. Go to WooCommerce > Status > Tools and click Regenerate next to Regenerate product lookup tables. WooCommerce's System Tools guide says regenerating them ensures they match the actual product data.
While the regeneration runs, the button changes to Regenerating in progress and WooCommerce shows a View progress link. Wait for it to finish, then check the shop page in a private window. On a large catalog, run it in a quiet hour.
If the product page itself shows the old price, the lookup tables are not the problem. Move on to the sale schedule and the saved price fields below.
Why is my sale price not showing?
A sale price only shows when its schedule says so, so check the From and To dates in the product editor.
Open the product and look at Product data > General. WooCommerce's product editor guide explains that clicking Schedule next to the Sale price adds two fields: Sale price dates From, when the sale starts, and To, when it stops displaying at 11:59 pm.
A future From date means the shop keeps showing the regular price until that day. A past To date means the sale already ended and the regular price is back. Leave To empty for a sale with no end date, and leave From empty for a sale that starts as soon as you save.
Also check that the sale price is lower than the regular price. A sale price above the regular price does not display as a discount. Save the product with Update, then check the storefront in a private window.
If the sale should have started but has not, look at WooCommerce > Status > Scheduled Actions for the sale jobs. A stuck background queue can delay the switch, and our guide on how to fix past-due actions in the WooCommerce Action Scheduler covers that case.
Why do prices change back after a CSV import?
**Prices change back after an import when rows match the wrong product, or when Update existing products was not selected.
A CSV file is a plain-text table where commas separate the fields, as Wikipedia's comma-separated values article explains. WooCommerce reads each row and matches it to a product before applying the price.**
WooCommerce's CSV importer guide explains that the importer matches update rows by ID or SKU. In WooCommerce 11.2 and later, it can use the GTIN, UPC, EAN, or ISBN column when both ID and SKU are blank.
A row with a mistyped SKU creates a new product or is skipped, while the old product keeps its old price.
If Update existing products is not selected, a product that already exists with the same SKU or ID is skipped, according to WooCommerce's CSV importer guide. Tick that box before running the importer when you mean to update prices.
Check the import log after every run. It lists skipped rows and the reason, such as a column that does not match the schema. WooCommerce's CSV importer guide advises testing an import with a small file first, then reviewing the results before updating the rest of the catalog.
The Published column also matters: 1 means published, 0 means private, -1 means draft, and 2 means pending review, as WooCommerce's CSV importer guide documents. A row imported as a draft will not show its new price on the storefront at all.
| CSV column | What it does | Common mistake |
|---|---|---|
| ID or SKU | Matches the row to an existing product | Mistyped SKU creates a new product |
| Regular price | Sets the standard price | Currency symbols in the cell break the value |
| Sale price | Sets the discount price | Higher than the regular price, so no discount shows |
| Date on sale from | Starts the sale on that date | Wrong date format, so the sale never starts |
| Published | 1 published, 0 private, -1 draft, 2 pending | Draft rows never show on the storefront |
Why do variation prices not update?
Each variation carries its own price, so updating the parent product does not change any variation price.
WooCommerce's product editor guide states that for a variable product, you open Product data > Variations and set the price for each variation. The parent product has no price of its own; the shop shows the range from the lowest to the highest variation price.
Open the Variations tab and expand each variation. A variation with no price is hidden from shoppers, and a single unpriced variation can break the price range on the product page. Fill in every variation price, then click Update.
CSV imports need one row per variation, with the Parent column set to the parent product SKU or an ID in the form id:123. WooCommerce's CSV importer guide shows this layout in its example table, with a parent row and one row per variation.
After updating variations, regenerate the product lookup tables as well. The listings read the lookup table, so a stale row can keep showing the old price range even after the variations are fixed.
Could caching or transients show old prices?
Yes, so clear WooCommerce transients and purge every cache layer after a price change.
WooCommerce stores short-lived cached values called transients, and an old transient can keep showing the previous price. WooCommerce's System Tools guide lists the WooCommerce transients and Expired transients clear buttons on the Tools page at WooCommerce > Status > Tools.
Clear the page cache too. Purge your caching plugin, your host cache, and your CDN, then check the price in a private window while logged out. Logged-in views often bypass the cache and hide the problem from you while shoppers still see the old price.
If prices update for you but not for shoppers, the cache is the prime suspect. Check the cache exclusion rules for product pages, and confirm the cache really purged by loading the page with a fresh query string, such as ?v=2, in the address bar.
For cache settings that suit a store, see our LiteSpeed Cache settings for WooCommerce.
If the price problem started after a plugin update, our guide on how to fix plugin conflicts in WordPress covers conflict testing.
Could a pricing plugin or tax setting change the price?
Yes, so check tax display settings and any pricing, currency, or discount extension before assuming the saved price is wrong.
WooCommerce's product editor guide notes that the currency symbol and formatting come from your store settings. If the amount shown differs from the product price, check your tax settings and displayed prices, and any currency conversion or pricing extension.
A common case is tax display: a store set to show prices including tax displays a higher number than the price saved excluding tax. The saved price is correct, and the display setting adds the tax. Check WooCommerce > Settings > Tax and the Display prices setting.
Currency conversion plugins can also override the saved price for shoppers in another currency. Turn the extension off on a staging site and check whether the saved price appears. If it does, the extension's own settings or exchange rate are the cause, not the product.
Role-based pricing and wholesale plugins work the same way: they change the price for some shoppers and not others. Test while logged out first, since that shows the default price every visitor sees.
How do I confirm the fix worked?
Check the product page and the shop page in a private window, then sort the shop by price to confirm the listings use the new value.
Open the product page first and confirm the price, the sale badge, and the sale dates all match what you saved. Then open the shop page and a category page and confirm the same price appears there.
Sort the shop by price, low to high, and find the product in the list. Price sorting reads the lookup tables, so a correct sort order proves the tables are in sync. If the product sits in the wrong place, regenerate the lookup tables again and re-check.
Keep a note of what fixed it, since the same cause will return after the next bulk import. Add a lookup-table regeneration step to your import checklist, and always test imports on a small file first, as WooCommerce's CSV importer guide advises.
What mistakes should you avoid?
The most common mistake is editing prices in the database instead of through the editor or importer.
- Editing price fields directly in the database, which skips the sync steps WooCommerce runs on save.
- Importing a full price file without testing a small sample first.
- Leaving Update existing products unticked on a price-update import.
- Setting a sale price above the regular price and expecting a discount to show.
- Forgetting variation prices and wondering why the parent price change did nothing.
- Judging the fix while logged in, when the cache shows you a different page than shoppers see.
Frequently asked questions
Why does the shop page show the old price but the product page shows the new one?
The listings read from lookup tables, while the product page reads the saved product data. If the tables are out of sync after a bulk edit or import, the shop shows the old price. Go to WooCommerce > Status > Tools and regenerate the product lookup tables.
Why is my WooCommerce sale price not showing?
Check the sale schedule in Product data > General. The From date may be in the future, or the To date may have passed. A sale price also has to be lower than the regular price. Save the product and check again in a private window.
How do I bulk update WooCommerce prices with a CSV file?
Use the built-in CSV importer at Products > All Products > Import, tick Update existing products, and match rows by ID or SKU. Test with a small file first, check the import log, then regenerate the product lookup tables so the listings pick up the new prices.
Do variable product variations need their own prices?
Yes. Each variation has its own price, and the parent product has none. Open Product data > Variations and set a price for every variation. A variation with no price is hidden, and the shop shows the range from the lowest to the highest variation price.
I changed a price and saved, but the storefront still shows the old one. What now?
Open the product and check Product data > General for the saved price, then check the sale schedule dates. Clear transients at WooCommerce > Status > Tools, purge the cache, and regenerate the product lookup tables. Check the result in a private window while logged out.
Sources
- WooCommerce Product Editor settings WooCommerce
- Product CSV Importer and Exporter WooCommerce
- WooCommerce System Tools WooCommerce
- Troubleshooting Orders WooCommerce
- Transients API WordPress Developer Resources
- Requirements WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
