How to Fix Outdated WooCommerce Templates in Your Theme

Find outdated WooCommerce theme templates, identify the files causing warnings, and update them without losing customizations or risking a live store.

Last updated:

Reviewed for accuracy by Jesse Nickles

Find the outdated template

  1. In WP Admin, open WooCommerce → Status → System status.
  2. Scroll to Templates and look for overridden files marked as out of date.
  3. Note each file path and the reported template version. Check whether the override belongs to the parent theme or an active child theme.

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. An outdated-version warning means the override needs review; it does not by itself prove that your storefront is broken. See WooCommerce's official template update instructions.

These steps cover PHP template overrides. Block themes can also use HTML templates for store layouts; those are managed separately through the Site Editor. See WooCommerce's block theme documentation for that workflow.

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.

  1. Check for an update to the active theme and install it on staging. Theme authors often include updated WooCommerce templates in their releases.
  2. If you use a child theme, check it separately. Updating the parent theme does not replace customized templates in the child theme.
  3. Return to WooCommerce → Status → System status → Templates and see whether the warnings are gone.
  4. 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's theme source includes a global/quantity-input.php override for its quantity dropdown. That customization is intentional, so do not delete the file just to clear a warning. Check Theme Updates and WooCommerce Product Pages before changing it.

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:

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.

  1. Save a separate copy of the existing override and identify its custom changes.
  2. On staging, copy the current WooCommerce template to the matching location in your child theme.
  3. Reapply only the customizations you still need, accounting for changes to hooks, variables, and markup in the newer template.
  4. Test the affected storefront or email output and check the WooCommerce 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