How to Fix Outdated WooCommerce Templates in Your Theme
Find outdated WooCommerce templates in your theme, review which overrides need updates, and test changes on staging before touching your live store.
Last updated:
Reviewed for accuracy by Jesse Nickles
Find the outdated template
- In WP Admin, open WooCommerce → Status → System status.
- Scroll to Templates and look for overridden files marked as out of date.
- Record each flagged relative file path and version, then identify whether the override lives in your active parent theme or child theme's
woocommerce/folder. You will need the exact path to compare it with WooCommerce's original.
A theme can copy WooCommerce's PHP templates into its own woocommerce/ folder to change the store's layout or behavior. Unlike WooCommerce's built-in templates, those copies do not automatically update with the plugin. WooCommerce compares the @version comment near the top of each override with the current core template's version. An outdated warning identifies a version mismatch that needs a compatibility review; it does not prove the storefront is broken or mean every override must be replaced immediately. See WooCommerce's official template update instructions.
These steps address PHP template overrides. Block themes may instead use HTML store templates edited through Appearance → Editor; those are a different system and are not repaired by copying WooCommerce PHP templates. If you choose to reset a customized Site Editor template, first preserve your changes because resetting it discards that template's saved edits. See WooCommerce's block theme documentation.
Update your theme first
Do not start by editing template files on a live store. Back up the site's files and database, then test changes on a staging copy.
- Check for an update to the active theme and install it on staging. Theme authors often include updated WooCommerce templates in their releases.
- If you use a child theme, inspect its
woocommerce/overrides separately. These can take precedence over matching parent-theme overrides, and updating the parent does not replace them. - Return to WooCommerce → Status → System status → Templates and see whether the warnings are gone.
- Test an affected product page, product variations, the cart, and checkout. If an email template was flagged, test the relevant transactional email too.
If your theme still includes outdated templates, ask its developer for an updated version before attempting a manual repair.
HoverCraft intentionally overrides global/quantity-input.php to render its quantity dropdown through a theme-specific helper. Replacing that file with WooCommerce's stock template could remove the dropdown behavior; neither delete nor replace it merely to dismiss a warning. Review Theme Updates and WooCommerce Product Pages before making changes.
Repair a custom template override
If you maintain the theme or child theme yourself, compare the flagged file with the matching template in your installed WooCommerce version. A typical path maps like this:
- WooCommerce original:
wp-content/plugins/woocommerce/templates/[relative-path] - Parent-theme override:
wp-content/themes/your-theme/woocommerce/[relative-path] - Child-theme override:
wp-content/themes/your-child-theme/woocommerce/[relative-path]
Preserve any subfolders in [relative-path]. For example, emails/admin-new-order.php belongs inside the child theme's woocommerce/emails/ folder, not at its root.
- Back up the existing override and compare it with the original template from the WooCommerce version installed on staging. Record both your custom changes and WooCommerce's changes to hooks, PHP variables, and HTML markup.
- Determine whether an update is needed. If so, prepare a revised file based on the installed WooCommerce template, carefully reapplying only the required customizations rather than blindly replacing the override.
- Place the revised file at the correct relative path in your child theme on staging. Do not edit the plugin's template or overwrite a parent theme maintained by its author.
- Test the affected product, cart, checkout, or email output, and check the status report again before deploying.
Do not change only the template's @version header to silence a warning; that does not update the code. Never edit WooCommerce's plugin templates directly, because a plugin update will replace those edits. Parent-theme changes can also disappear on update. WooCommerce's template override documentation explains the file structure and why a child theme is safer for site-specific changes.
If the warning remains or something is broken
- Warning remains after a theme update: Check for an older child-theme override or ask the theme developer whether the flagged file has been updated.
- Changes not showing on the storefront: After confirming the revised file is in the active theme's correct location, go to WooCommerce → Status → Tools and use Reset template cache if available. This refreshes cached template information; it neither rewrites the override nor makes outdated code compatible. See WooCommerce's system tools documentation.
- Product page or checkout still fails: On staging, test with a default WordPress theme or Storefront. If the problem disappears, investigate the original theme; if it remains, check plugins and extensions. Follow WooCommerce's conflict testing guide.