WooCommerce Custom Tabs for Product Specifications

WooCommerce custom tabs give product specifications their own space on a product page, using PHP or a tabs plugin. A small code customization works well for straightforward details, such as a product's size and material. Choose a product tabs plugin when you need reusable content or display rules. Barn2 has a free version for a simple start, plus a more feature-rich option.

The goal is simple: help shoppers find the details that support their purchase. Start with clear product information, then choose how you'll manage it.

Key Takeaways

Use the woocommerce_product_tabs filter to add, remove, or reorder tabs in WooCommerce's classic product layout.
Store specifications separately for each product, and hide the custom tab when its content is empty.
Choose a plugin for drag-and-drop management, shared tabs, or category-based rules. Your product template still needs to support the tab output.

Add WooCommerce Custom Tabs With PHP

WooCommerce product tabs include Description, Additional Information, and Reviews. Their appearance depends on available content and settings.

Back up your site and test on staging before editing PHP. Add the following snippets to your child theme's functions.php file, inside its existing PHP section, or use a custom plugin. Don't edit the parent theme.

A developer's hands rest beside an open laptop on a wooden desk with a notepad and paper samples.

Register the specifications tab

A tab is an array containing a title, priority, and callback function. The callback outputs its content.

This follows WooCommerce's product-tab customization method:

add_filter('woocommerce_product_tabs', 'zdc_add_specifications_tab');


function zdc_add_specifications_tab($tabs) {
    global $product;


    if (!$product instanceof WC_Product) {
        return $tabs;
    }


    $specs = get_post_meta(
        $product->get_id(),
        '_zdc_specifications',
        true
    );


    if ('' !== trim((string) $specs)) {
        $tabs['zdc_specifications'] = array(
            'title'    => __('Specifications', 'zdc'),
            'priority' => 25,
            'callback' => 'zdc_render_specifications',
        );
    }


    return $tabs;
}


function zdc_render_specifications() {
    global $product;


    echo '<h2>' . esc_html__('Specifications', 'zdc') . '</h2>';
    echo '<p>' . esc_html(get_post_meta(
        $product->get_id(),
        '_zdc_specifications',
        true
    )) . '</p>';
}

The tab stays hidden until you save specifications using the field below.

Set the order or remove defaults

Default priorities are 10 for Description, 20 for Additional Information, and 30 for Reviews. Lower numbers appear earlier.

Our priority of 25 places Specifications between Additional Information and Reviews. Priority 50 appears after the default tabs, not between them.

To remove Description and Additional Information, add this optional snippet:

add_filter('woocommerce_product_tabs', function($tabs) {
    unset($tabs['description']);
    unset($tabs['additional_information']);


    return $tabs;
}, 99);

Keep those defaults when they contain useful information. Removing a tab hides its storefront output; it doesn't erase the product data.

Give Each Product Its Own Specifications

Shared specifications can save time, but different products often need different details. A product-level field keeps those differences manageable.

Add a field and save its value

Add this alongside the first snippet. It creates a plain-text field in the classic product editor's Product data > General area.

WooCommerce handles its standard product-save security checks before running this save hook. The capability check below also limits editing to authorized users.

add_action('woocommerce_product_options_general_product_data', function() {
    woocommerce_wp_text_input(array(
        'id'          => '_zdc_specifications',
        'label'       => 'Specifications',
        'desc_tip'    => true,
        'description' => 'Enter specifications as plain text.',
    ));
});


add_action('woocommerce_process_product_meta', function($product_id) {
    if (
        !current_user_can('edit_post', $product_id)
        || !isset($_POST['_zdc_specifications'])
    ) {
        return;
    }


    update_post_meta(
        $product_id,
        '_zdc_specifications',
        sanitize_text_field(
            wp_unslash($_POST['_zdc_specifications'])
        )
    );
});

Open a simple product, enter its actual specifications, and update it. The first snippet retrieves the saved value with get_post_meta() and escapes it before display.

Handle rich content and variations separately

This field supports plain text. It doesn't preserve tables, images, or formatted paragraphs. For those, use an editor-based plugin, or build a wp_editor() field with wp_kses_post() sanitization and output.

Keep structured facts in WooCommerce product attributes when they also support catalog filtering. Copying everything into free-form text makes maintenance harder.

For WooCommerce variable products, this snippet reads the parent product's metadata. It doesn't change specifications when a shopper selects a variation. Variation-specific specifications require separate variation fields and frontend updates.

Use the parent tab for facts that apply across every available option.

Choose a Product Tabs Plugin for Easier Management

Prefer managing content through WordPress? A plugin makes sense when several people update products or the same information appears across your catalog.

These options suit different workloads:

Tool	Best fit	Cost
Barn2 WooCommerce Product Tabs	Unlimited tabs with global, category, tag, and per product targeting	Paid license
Additional Custom Tabs	A store needing one extra tab	Free version, limited to one custom tab
SkyVerge Tab Manager	Shared tabs, per-product overrides, and visual ordering	$99 for one year
Addify Custom Product Tabs Manager	Global rules, product overrides, and user-role restrictions	$69 per year

We recommend choosing by how content is reused, rather than how many settings a plugin offers. Choose Barn2 when shared content needs global, category, tag, or product-specific targeting.

Barn2's product tabs plugin supports unlimited custom tabs, formatted tab content, and shortcodes. Its premium controls let you apply tabs globally, by category or tag, or to individual products, then reorder them.

For a smaller need, Additional Custom Product Tabs is a product tabs plugin with a free version. Its one-tab limit suits a basic specifications section better than a large content library.

SkyVerge Tab Manager adds drag-and-drop ordering and product-specific layouts. Addify adds targeting by user role alongside product, category, and tag rules.

After installation, create a Specifications tab, enter its content, choose its display scope, and save its position. Test one included product and one excluded product before applying rules broadly. Smart Tabs is another option when responsive layouts matter.

Make Tabs Readable on Mobile and Custom Templates

A specifications tab should be easy to open, read, and close. A tidy desktop layout isn't enough if mobile shoppers face cramped labels or sideways scrolling.

Layered browser product page mockup showing a product box and specification icons in a workshop.

Keep headings and mobile layouts practical

Use short titles such as Specifications, Delivery, or Size Guide. Long labels compete for space.

Smart Tabs' responsive layouts can switch to an accordion or full-width presentation on smaller screens. Smart Tabs' accordion lets shoppers expand one section without squeezing every heading into a row.

For classic WooCommerce panels, adjust heading styles with:

.woocommerce-Tabs-panel h2 {
    font-size: 1.25rem;
    margin-bottom: 0.75rem;
}

That selector targets panel headings, not the clickable tab labels. Preview the result on a narrow screen, especially when specifications include tables.

Match the method to your product template

Elementor, WPBakery, and custom product templates may replace WooCommerce's normal tab output. Adding PHP won't create a missing product-data widget.

TheGem already provides built-in custom product tabs. Open Theme Options > Product, enable Additional tabs, and add tabs through its repeater control. Content can come from TinyMCE or a global section template.

We recommend using the theme's existing controls when they meet your needs. Running two tab systems together creates unnecessary overlap.

For block-based product templates, legacy PHP filters aren't a universal extension method. Keep the product details area in place and use an integration that supports that template.

Fix a Custom Tab That Won't Appear

A missing tab usually points to missing content, a template mismatch, or another customization. Work through those layers in order.

Check the saved value and active template

Our snippet deliberately hides empty specifications. Update the product after entering content, then open its published page.

Confirm the snippet is active in the current child theme or custom plugin. A theme change can leave code behind in an inactive functions.php file.

Next, inspect the Single Product template. Does it include the product-data tabs widget or the appropriate product details area? If the template never renders that section, the registered tab has nowhere to appear.

Also separate normal behavior from a fault. Additional Information depends on visible product attributes or relevant dimensions and weight. Reviews depend on their own settings.

Isolate conflicts and clear stale output

Two customizations can overwrite each other when they use the same tab key. Keep keys unique, such as zdc_specifications.

A plugin running later may also change priorities or remove your entry. Disable competing tab customizations one at a time on staging, then test after each change.

If the tab appears in the page source but won't open, investigate frontend JavaScript or CSS before rewriting the PHP.

Clear product-page caches after changes, including WordPress, host, and CDN layers. Then test in a fresh browser session. Avoid changing several settings together, because you'll lose track of which change worked.

Put Clear Specifications to Work

These tabs work best when they answer a purchase question without creating extra upkeep. Start with accurate content, choose one management method, and test the finished product page on desktop and mobile.

Our WooCommerce hosting checklist helps you prepare the foundation behind those pages. Choose our WordPress or cPanel hosting for your store, with 24/7 support from real people when you need help.

Keep the details clear and the setup manageable, so you can focus on products, customers, and the next sale.

Frequently Asked Questions

Can a custom tab appear on every product?

Yes. Register it without a product-specific condition, or use a plugin's global display setting. Our code requires saved specifications, so products with empty fields won't display the tab.

Can shop owners reorder tabs without editing PHP?

Yes. SkyVerge Tab Manager has a visual drag-and-drop interface. Use the Tab Manager controls to change the order, or adjust each tab's priority in code. Lower numbers come first.

Does adding a specifications tab improve product filtering?

No. A tab organizes information on the product page. Catalog filtering needs structured attributes and a compatible filter interface. Keep reusable facts in attributes, even when a custom tab presents additional buying guidance.

Submit a Comment Cancel reply

What's New?

WooCommerce / WordPressWooCommerce Custom Tabs for Product SpecificationsWooCommerce custom tabs give product specifications their own space on a product page, using PHP or a tabs plugin. A small code customization works well for straightforward details, such as a product's size and material. Choose a product tabs plugin when you need reusable content or display rules. Barn2 has a free version for a simple start, plus a more feature-rich option. The goal is simple: help shoppers find the details that support their purchase. Start with clear product information, then choose how you'll manage it. Key Takeaways Use the woocommerce_product_tabs filter to add, remove, or reorder tabs in WooCommerce's classic product layout. Store specifications separately for each product, and hide the custom tab when its content is empty. Choose a plugin for drag-and-drop management, shared tabs, or category-based rules. Your product template still needs to support the tab output. Add WooCommerce Custom Tabs With PHP WooCommerce product tabs include Description, Additional Information, and Reviews. Their appearance depends on available content and settings. Back up your site and test on staging before editing PHP. Add the following snippets to your child theme's functions.php file, inside its existing PHP section, or use a custom plugin. Don't edit the parent theme. Register the specifications tab A tab is an array containing a title, priority, and callback function. The callback outputs its content. This follows WooCommerce's product-tab customization method: add_filter('woocommerce_product_tabs', 'zdc_add_specifications_tab'); function zdc_add_specifications_tab($tabs) { global $product; if (!$product instanceof WC_Product) { return $tabs; } $specs = get_post_meta( $product->get_id(), '_zdc_specifications', true ); if ('' !== trim((string) $specs)) { $tabs = array( 'title' => __('Specifications', 'zdc'), 'priority' => 25, 'callback' => 'zdc_render_specifications', ); } return $tabs; } function zdc_render_specifications() { global $product; echo '<h2>' . esc_html__('Specifications', 'zdc') . '</h2>'; echo '<p>' . esc_html(get_post_meta( $product->get_id(), '_zdc_specifications', true )) . '</p>'; } The tab stays hidden until you save specifications using the field below. Set the order or remove defaults Default priorities are 10 for Description, 20 for Additional Information, and 30 for Reviews. Lower numbers appear earlier. Our priority of 25 places Specifications between Additional Information and Reviews. Priority 50 appears after the default tabs, not between them. To remove Description and Additional Information, add this optional snippet: add_filter('woocommerce_product_tabs', function($tabs) { unset($tabs); unset($tabs); return $tabs; }, 99); Keep those defaults when they contain useful information. Removing a tab hides its storefront output; it doesn't erase the product data. Give Each Product Its Own Specifications Shared specifications can save time, but different products often need different details. A product-level field keeps those differences manageable. Add a field and save its value Add this alongside the first snippet. It creates a plain-text field in the classic product editor's Product data > General area. WooCommerce handles its standard product-save security checks before running this save hook. The capability check below also limits editing to authorized users. add_action('woocommerce_product_options_general_product_data', function() { woocommerce_wp_text_input(array( 'id' => '_zdc_specifications', 'label' => 'Specifications', 'desc_tip' => true, 'description' => 'Enter specifications as plain text.', )); }); add_action('woocommerce_process_product_meta', function($product_id) { if ( !current_user_can('edit_post', $product_id) || !isset($_POST) ) { return; } update_post_meta( $product_id, '_zdc_specifications', sanitize_text_field( wp_unslash($_POST) ) ); }); Open a simple product, enter its actual specifications, and update it. The first snippet retrieves the saved value with get_post_meta() and escapes it before display. Handle rich content and variations separately This field supports plain text. It doesn't preserve tables, images, or formatted paragraphs. For those, use an editor-based plugin, or build a wp_editor() field with wp_kses_post() sanitization and output. Keep structured facts in WooCommerce product attributes when they also support catalog filtering. Copying everything into free-form text makes maintenance harder. For WooCommerce variable products, this snippet reads the parent product's metadata. It doesn't change specifications when a shopper selects a variation. Variation-specific specifications require separate variation fields and frontend updates. Use the parent tab for facts that apply across every available option. Choose a Product Tabs Plugin for Easier Management Prefer managing content through WordPress? A plugin makes sense when several people update products or the same information appears across your catalog. These options suit different workloads: ToolBest fitCostBarn2 WooCommerce Product TabsUnlimited tabs with global, category, tag, and per product targetingPaid licenseAdditional Custom TabsA store needing one extra tabFree version, limited to one custom tabSkyVerge Tab ManagerShared tabs, per-product overrides, and visual ordering$99 for one yearAddify Custom Product Tabs ManagerGlobal rules, product overrides, and user-role restrictions$69 per year We recommend choosing by how content is reused, rather than how many settings a plugin offers. Choose Barn2 when shared content needs global, category, tag, or product-specific targeting. Barn2's product tabs plugin supports unlimited custom tabs, formatted tab content, and shortcodes. Its premium controls let you apply tabs globally, by category or tag, or to individual products, then reorder them. For a smaller need, Additional Custom Product Tabs is a product tabs plugin with a free version. Its one-tab limit suits a basic specifications section better than a large content library. SkyVerge Tab Manager adds drag-and-drop ordering and product-specific layouts. Addify adds targeting by user role alongside product, category, and tag rules. After installation, create a Specifications tab, enter its content, choose its display scope, and save its position. Test one included product and one excluded product before applying rules broadly. Smart Tabs is another option when responsive layouts matter. Make Tabs Readable on Mobile and Custom Templates A specifications tab should be easy to open, read, and close. A tidy desktop layout isn't enough if mobile shoppers face cramped labels or sideways scrolling. Keep headings and mobile layouts practical Use short titles such as Specifications, Delivery, or Size Guide. Long labels compete for space. Smart Tabs' responsive layouts can switch to an accordion or full-width presentation on smaller screens. Smart Tabs' accordion lets shoppers expand one section without squeezing every heading into a row. For classic WooCommerce panels, adjust heading styles with: .woocommerce-Tabs-panel h2 { font-size: 1.25rem; margin-bottom: 0.75rem; } That selector targets panel headings, not the clickable tab labels. Preview the result on a narrow screen, especially when specifications include tables. Match the method to your product template Elementor, WPBakery, and custom product templates may replace WooCommerce's normal tab output. Adding PHP won't create a missing product-data widget. TheGem already provides built-in custom product tabs. Open Theme Options > Product, enable Additional tabs, and add tabs through its repeater control. Content can come from TinyMCE or a global section template. We recommend using the theme's existing controls when they meet your needs. Running two tab systems together creates unnecessary overlap. For block-based product templates, legacy PHP filters aren't a universal extension method. Keep the product details area in place and use an integration that supports that template. Fix a Custom Tab That Won't Appear A missing tab usually points to missing content, a template mismatch, or another customization. Work through those layers in order. Check the saved value and active template Our snippet deliberately hides empty specifications. Update the product after entering content, then open its published page. Confirm the snippet is active in the current child theme or custom plugin. A theme change can leave code behind in an inactive functions.php file. Next, inspect the Single Product template. Does it include the product-data tabs widget or the appropriate product details area? If the template never renders that section, the registered tab has nowhere to appear. Also separate normal behavior from a fault. Additional Information depends on visible product attributes or relevant dimensions and weight. Reviews depend on their own settings. Isolate conflicts and clear stale output Two customizations can overwrite each other when they use the same tab key. Keep keys unique, such as zdc_specifications. A plugin running later may also change priorities or remove your entry. Disable competing tab customizations one at a time on staging, then test after each change. If the tab appears in the page source but won't open, investigate frontend JavaScript or CSS before rewriting the PHP. Clear product-page caches after changes, including WordPress, host, and CDN layers. Then test in a fresh browser session. Avoid changing several settings together, because you'll lose track of which change worked. Put Clear Specifications to Work These tabs work best when they answer a purchase question without creating extra upkeep. Start with accurate content, choose one management method, and test the finished product page on desktop and mobile. Our WooCommerce hosting checklist helps you prepare the foundation behind those pages. Choose our WordPress or cPanel hosting for your store, with 24/7 support from real people when you need help. Keep the details clear and the setup manageable, so you can focus on products, customers, and the next sale. Frequently Asked Questions Can a custom tab appear on every product? Yes. Register it without a product-specific condition, or use a plugin's global display setting. Our code requires saved specifications, so products with empty fields won't display the tab. Can shop owners reorder tabs without editing PHP? Yes. SkyVerge Tab Manager has a visual drag-and-drop interface. Use the Tab Manager controls to change the order, or adjust each tab's priority in code. Lower numbers come first. Does adding a specifications tab improve product filtering? No. A tab organizes information on the product page. Catalog filtering needs structured attributes and a compatible filter interface. Keep reusable facts in attributes, even when a custom tab presents additional buying guidance. [...]
Read more...
WooCommerceHow to Hide Out-of-Stock Products in WooCommerceTo hide out of stock products, go to Settings > Products > Inventory, turn on the option to hide unavailable items from the catalog, and save your changes. The setting is built in, so you don't need another plugin. That removes a common shopping frustration: finding the right product, opening it, and discovering there's nothing available to buy in your store. Pair the setting with a quick inventory check and storefront test. Start with the visibility switch, then make sure your stock records support it. Key Takeaways WooCommerce includes a store-wide setting to hide out of stock products. Accurate stock status matters more than the number displayed on a product page. Variations, backorders, and cached pages can affect whether products appear as in stock. Catalog visibility, direct access, and purchasing permissions need separate attention. Hide Unavailable Products Without a Plugin You can make this change directly in your WordPress dashboard. No code to paste. No extension to configure. Open WooCommerce > Settings. Select the Products tab. Open Inventory. Find Out of stock visibility. Tick "hide out of stock items from the catalog." Click save changes. WooCommerce's Products Settings documentation describes this option for hiding unavailable items from the catalog. This setting hides out of stock products from catalog listings, but it doesn't delete their records. After saving, reload your shop page. Give the updated listing a moment to load before deciding whether the change worked. This setting applies across the catalog rather than to one selected product. If you only want to hide particular items, a different visibility rule may suit your store better. We recommend starting with this built-in option before adding software. For a straightforward catalog of available products, it keeps the setup simple. Leave unrelated inventory settings alone while making this change. Notification thresholds and hold-stock timing solve different problems. Make Sure the Store Recognizes the Stockout The visibility switch follows the store's recorded inventory. If that information is wrong, your catalog can look wrong too. Check Stock Tracking and Availability If you want availability to update automatically as orders arrive, enable stock management under WooCommerce > Settings > Products > Inventory. Next, open the affected item under Products, then find Product data > Inventory. Review its stock-management setting, saved quantity, and stock status. For manually managed availability, the recorded status must match what you can sell. Mark an item out of stock only when it isn't available for purchase. A quantity entered somewhere else doesn't automatically set that status. For variable products, check the stock setting for each of its variants. Turning on tracking also doesn't reconstruct earlier sales. Reconcile older orders against physical stock before entering a starting quantity. Separate Thresholds From Backorders A low-stock threshold triggers an alert. The stock threshold determines when tracked inventory becomes unavailable. Those are different jobs. Backorders add another decision. They allow customers to purchase after tracked stock reaches zero, so zero inventory alone doesn't describe your selling policy. If you intend to stop sales when stock runs out, review the product's backorder setting too. If incoming stock supports continued orders, our WooCommerce backorder settings guide explains how to keep those commitments manageable. We recommend changing one control at a time. That makes unexpected behavior much easier to trace. Test the Catalog Like a Shopper A saved setting is the starting point. A working storefront is the result you want. Open your store in a private browser window. Visit the main shop page and the relevant category or collection listing. Check internal search, related-product sections, and custom product grids added by your theme or page builder. Don't assume every listing uses the same query. Keep an in stock product as your comparison. It should remain discoverable and available to purchase. For variable products, select an available size or color from the variants and add it to the cart. Confirm the chosen option, price, and availability remain consistent. If you're changing quantities or placing test orders, use staging so testing doesn't interfere with real sales. Test the restocked state there too. A product disappearing from one grid doesn't prove every custom listing follows the same availability rule. Once the test passes, review the first time a product becomes unavailable after the change. That's a useful final check without repeatedly editing live inventory. Choose Between Hiding Products and Showing Availability A cleaner catalog helps shoppers focus on products they can buy. The catalog setting lets you hide products without deleting the product record, but hiding every unavailable item isn't right for every store. Keep a Sold-Out Message When It Helps A visible product can help explain your range, show previous designs, or support a restock-notification offer. The trade-off is browsing friction. If unavailable products dominate the first page, shoppers have more work to do. We recommend choosing based on the shopping task. A frequently replenished range may benefit from clear availability messages. A curated collection of one-off items may be easier to browse with unavailable listings removed. If you'd rather move unavailable items below available products, WooCommerce's sorting and hiding extension offers rules beyond the built-in switch. Treat Access and Search as Separate Decisions Catalog visibility isn't a complete access-control policy. Decide separately what should happen when someone follows a saved product link or already has an item in their cart. Search-engine indexing also needs its own plan. Don't treat a catalog checkbox as an instruction about Google's results. For private or wholesale catalogs, our customer-role product restrictions guide covers the distinction between discovery, prices, and permission to buy. Troubleshoot Products That Still Appear If you still can't hide out of stock products, compare the saved product record with what visitors see. This helps separate inventory problems from display problems. Inspect the Exact Product or Variation Open the affected product and review its status, quantity, threshold, and backorder choice. Confirm it's marked out of stock when its quantity reaches zero. For variable products, inspect Product data > Variations. A parent product can remain relevant while only one size or color is unavailable. Check where stock is managed. Some stores use one shared parent-level quantity; others track each variation separately. Review the record that controls the option in question. If quantities aren't changing after orders, follow our guide to troubleshoot WooCommerce stock updates. Changing a count by hand can hide the original problem. Clear Stale Pages and Inspect Custom Grids When the editor looks right but the storefront doesn't, investigate caching before adjusting inventory. Purge the affected pages from your WordPress cache, hosting cache, and CDN, where applicable. Then reopen them in a private window. Keep Cart, Checkout, and My Account outside shared full-page caching. Those pages need customer-specific information. If only a custom product grid is wrong, inspect its query settings or extension behavior. Use staging for theme switches and plugin-conflict tests, and take a backup first. Hosting can help deliver fresh pages. It can't correct an incorrect product stock setting. Hide Unavailable Products in a Shopify Collection Unlike WooCommerce, Shopify uses collection rules rather than an inventory-visibility checkbox. You can set collection membership without changing your theme, and your theme can stay as it is. Add the Inventory Condition In Shopify, open Products > Collections, then create or edit a smart collection. Set the collection condition to Inventory stock > is greater than > 0. Choose all conditions, then save the collection. Shopify's instructions for hiding unavailable products specify that you must select all conditions, not Match any condition. With all conditions, another rule can't include a product that fails the inventory stock requirement. Inventory tracking must be enabled for the products involved. Confirm the store navigation opens the intended collection, then reload the collection page and check the results. Understand Variants and Continue-Selling Settings The collection condition rules explain that one matching variant can keep a product included when it has multiple variants. The collection rule uses inventory stock to decide whether to include a product. The continue selling when out of stock setting controls whether customers can purchase it, and zero inventory remains zero. A product that fails the greater-than-zero rule can be excluded even when continued selling is enabled. Choose rules around your sales policy, especially if you accept preorders. Otherwise, you could hide an item you're prepared to sell. Give Your Store Hosting That Supports the Workload Inventory settings need a dependable website behind them. Your catalog, customer sessions, payment callbacks, and order database all rely on that foundation. Our WordPress hosting offers one-click installs and 24/7 support from real people. It's a straightforward starting point for building and running your store. If stale pages or slow requests interrupt catalog updates, include hosting and cache controls in your investigation. Choose hosting capacity that matches your workload, including the demands of your theme. Keep inventory rules accurate and give your website enough resources to support checkout. Frequently Asked Questions Does Unavailable Mean More Products Are Coming? An unavailable message describes current availability. It doesn't establish a restock date or promise another shipment. If replenishment is confirmed, give shoppers a clear delivery expectation or a restock notification option. Keep that promise separate from the inventory label. Avoid vague availability messages when you know an item won't return. Do I Need to Delete Unavailable Items? No. Hiding a product removes it from the catalog without deleting its record. Delete it only when removing the record fits your broader store plan. If an item may be offered again, keep its information organized and decide how shoppers should discover it. For discontinued products, treat catalog presentation, direct-link behavior, and indexing as separate decisions. When stock returns, update the product quantity and stock status to available. If the catalog visibility setting remains enabled, WooCommerce should show the listing again once its status qualifies. If you manually hid the product, restore its catalog visibility. If you deleted it, changing the stock won't restore it. Clear your cache if a correctly restocked product still doesn't appear. Keep the Catalog Focused on Available Products The built-in visibility setting makes this a manageable change. Accurate stock records and a proper storefront test make it dependable. We recommend starting with the checkbox, then reviewing variations, backorders, and caching only where needed. Keep availability clear, so shoppers can spend less time opening unavailable items and more time choosing what they can buy. [...]
Read more...
WooCommerce / WordPressWooCommerce Product Reviews Not Showing? Fix the SettingsMissing WooCommerce product reviews usually point to disabled settings, pending approval, or a product template that hides them. We recommend checking those layers before installing another plugin. You can restore reviews without rebuilding your store, and star ratings have their own controls. Start with the built-in settings, then work through permissions and display issues in order. Key Takeaways Enable reviews at WooCommerce > Settings > Products, then turn on star ratings separately. Check each product's Advanced tab and your WordPress moderation settings before changing themes or plugins. Use a review plugin for reminders, customer photos, or Q&A, rather than as a shortcut around broken settings. 1. Enable WooCommerce Product Reviews and Star Ratings WooCommerce includes product reviews out of the box. You don't need a paid extension to display written feedback and stars. Follow this setup: Open WooCommerce > Settings > Products. Scroll to Reviews and select Enable product reviews. Turn on Enable star rating on reviews. Choose whether customers must provide a star rating. Select your verified-owner options, then save changes. The official WooCommerce review settings cover these controls, including the verified-owner badge and verified-only submission setting. Want written feedback and a consistent rating average? We recommend enabling stars and making ratings required. Without that requirement, customers can submit text without a score. Open a product page in a private browser window after saving. Look for the Reviews tab or review section. If the section appears but stars don't, focus on rating settings and theme styling. If the entire section is missing, continue with product permissions. 2. Check Product Permissions and Review Approval Global settings are only part of the picture. A single product can still have reviews disabled. Enable reviews on the affected product Open Products > All Products and edit the item. In the classic product editor, go to Product data > Advanced and select Enable reviews. Update the product. Repeat this for affected items, especially products created before you changed the store-wide setting. Global changes don't necessarily reopen existing product discussions. If one product displays reviews correctly and another doesn't, compare their product-level settings first. That comparison can save you a long round of plugin troubleshooting. Find reviews waiting for approval WooCommerce product reviews are stored as WordPress comments. The dashboard's Comments area supports moderation; current WooCommerce installations also provide a dedicated Products > Reviews screen. Look for Pending, Spam, and Trash entries. Approve legitimate feedback that's waiting, and restore anything incorrectly flagged. Next, open Settings > Discussion. Review manual approval, login requirements, moderation keywords, and comment-closing controls. We recommend keeping sensible moderation in place. A pending review needs approval, not a complete shutdown of spam protection. Closing submissions and deleting reviews are different actions. Keep existing review records while you troubleshoot permissions. 3. Clear Cache and Check the Product Template An approved review can exist in your database while your storefront shows an older page. Fix the display layer without disturbing the feedback itself. Clear every relevant cache Purge your caching plugin, host-level cache, and CDN cache if your store uses them. Then reload the product in a private window. Check desktop and mobile layouts. A review section can be visible on one screen size and hidden by styling on another. If the latest review appears after clearing cache, the underlying data was fine. Review your caching setup rather than importing the same feedback again. Isolate theme and plugin conflicts safely Take a backup that includes your database before testing. Use a staging copy so customers can keep shopping. Check whether your product template contains the review section or appropriate WooCommerce review blocks. Page builders and custom templates can replace the standard layout. Temporarily switch to a default WooCommerce-compatible theme. Then disable review, comment-control, page-builder, and optimization plugins one at a time. Pay attention to plugins that disable comments across all content types. They can also affect product reviews. If a change restores the section, you've found the layer that needs attention. Choose a Review Plugin That Fits Your Store Once built-in reviews work, extra tools can help you collect richer feedback. Choose based on the feature you need, not the longest feature list. These options cover common store requirements. OptionEntry costBest fitWooCommerce coreFreeWritten reviews and starsCusRevFree pluginAutomated reminders and rewardsSite ReviewsFree pluginFlexible reviews with spam controlsProduct Reviews Pro$79/yearMedia, qualifier questions, and Q&AYayReviewsFree Lite; Pro from $99/yearMedia reviews and custom presentationWiserReviewFrom $81/year, billed annuallyHosted review app for collection and widgets Unlike WordPress plugins, WiserReview is a hosted review app. It collects reviews through its service and displays them with widgets. WiserReview can suit stores that prefer hosted collection and display tools. Start free if collection is your main problem. Pay when richer review content or a different display format earns its place. Free options: CusRev and Site Reviews Customer Reviews for WooCommerce, also called CusRev, is free on WordPress.org. It supports automated review requests, photo and video reviews, and coupon rewards. It's our first recommendation for a small WooCommerce store that wants automated requests without buying a premium plugin immediately. Site Reviews offers a free plugin with spam protection. Paid add-ons introduce upvoting, sorting and filtering, and image uploads. It suits stores that also need reviews elsewhere on their WordPress site. Paid upgrades: richer feedback and presentation Product Reviews Pro is an official WooCommerce extension priced at $79 per year. It adds photo and video reviews, custom qualifier questions, and Q&A. YayReviews is freemium. Its features include photo and video reviews, custom rating types, and AI summaries. Keep the original customer reviews accessible alongside AI summaries. YayReviews Pro starts at $99/year. WiserReview also offers hosted review collection and widgets for stores that want an option outside WordPress plugins. Older WiserReview free-plan descriptions list 10 text reviews and two video reviews. WiserReview's current pricing page advertises a seven-day trial and a 14-day money-back guarantee. Media features vary by tool, so compare which plans include photo and video reviews before choosing. Collect Genuine Reviews Without More Admin Work Better collection should mean useful feedback, not a bigger moderation queue. Use verified purchases and fair moderation Enable the verified-owner badge to distinguish purchase-linked feedback. Verified-only submissions reduce opportunities for outsiders to post spam. That restriction can also exclude genuine customers who bought through another channel. Choose it based on how your store sells. Require approval where needed, hold suspicious links, and review your spam queue regularly. Don't delete genuine criticism because the rating is low. Keep responses to customer feedback brief: acknowledge the problem, explain the next step, and move private order details to your help desk or business email. Send requests after customers receive their orders Give customers time to use the product before asking for feedback. Send a clear request for customer reviews with a direct link. CusRev handles automated review requests. Yotpo's Mail After Purchase guide describes requests for purchases up to 150 days old; its in-mail forms let customers provide stars and written feedback directly from email. If automated reminders stop, inspect the plugin's schedule and email delivery. Our guide to fixing failed WooCommerce scheduled actions helps with background jobs that aren't running. Offer rewards for honest participation, never for a positive score. Move Existing Reviews Out of Judge.me Judge.me has ended WooCommerce support and now focuses on Shopify. Existing feedback deserves a proper migration, not a fresh start that loses customer history. Its WooCommerce sunset guidance explains the platform change. For accounts whose admin export is no longer available, Judge.me support can provide the review file after confirming ownership. Keep the original CSV untouched. Back up your store before importing. Choose a destination that supports Judge.me CSV files, such as YayReviews. Match reviews to the correct products using the importer's supported identifiers, and preserve dates, ratings, and media where supported. Import a small batch first. Check product assignments and duplicates before loading the remaining reviews. Don't invent verified-purchase badges for records that lack purchase evidence. Put Reviews to Work for Buyers and Search Reviews answer questions your sales copy can't always settle. Fit, finish, delivery, and everyday use all matter. Real customer details help shoppers picture the purchase. BrightLocal's 2026 consumer review survey reports that 93% of consumers have made a purchase after reading reviews. That's different from claiming 93% always read reviews before buying. Northwestern University's Spiegel Research Center study found 270% greater purchase likelihood for products with five reviews than products with none. That's a study result, not a promised conversion increase for every store. For search, keep reviews visible on the relevant product page. Use product structured data that matches the ratings and review counts shown. Check that your structured data reports those same values. If a plugin displays AI summaries, keep the original reviews accessible to shoppers. Avoid multiple plugins outputting conflicting rating markup. Validate the page with Google's Rich Results Test after changing your review setup. Correct markup supports eligibility for review-rich results. Google decides whether they appear. Frequently Asked Questions How does a customer add a WooCommerce review? They open the product page, select Reviews, choose a rating, and submit their feedback. Depending on your settings, they may need to sign in or have purchased the item. Why is an approved review still missing? Check product permissions, the product template, and cached pages. If text appears but stars don't, inspect the star-rating setting and theme styling separately. Does a review plugin replace WooCommerce settings? Not always. Extensions can still depend on core permissions and WordPress moderation. We recommend restoring the built-in review section before adding a replacement display or collection tool. Should coupon rewards require a five-star review? No. Reward honest feedback regardless of rating, and disclose the incentive. A review system earns trust when customers can share both praise and problems. Keep Reviews Visible and Your Store Ready Start with settings, approval, and display. That order helps you restore customer feedback without adding unnecessary software or risking existing reviews. Once reviews work, choose reminders and media features that match your store's needs. Keep backups in place before changing plugins or importing feedback. Need a stronger hosting foundation? Our Web Hosting Plus costs $30.99/month, and our 24/7 support comes from real people. Give your store dependable support while you focus on products, customers, and the next sale. [...]
Read more...
WooCommerce / WordPressAdd Custom Fields to the WooCommerce CheckoutYour checkout should collect what you need to fulfill an order without turning payment into paperwork. Custom WooCommerce checkout fields help you capture useful details, like a purchase order number or delivery preference. We recommend starting with one clear purpose and choosing a method that supports your checkout layout. A field editor offers a no-code route, while WooCommerce's Additional Checkout Fields API supports custom development for the Checkout block. First, identify which checkout your store uses so your changes work where customers pay. Key Takeaways A useful checkout field has a job to do. Keep that job clear, and the setup gets easier. Classic checkout and the Checkout block use different customization methods. Adding a visible field is only part of the work. Its value must reach the order and the people handling it. Test changes on staging with your payment gateway in test mode before updating your live store. We recommend making fields optional unless an order genuinely can't proceed without the answer. Your checkout should help customers finish their purchase. Choose the Right Approach for WooCommerce Checkout Fields Open your checkout page in the WordPress editor. The content tells you which customization route fits. WooCommerce's cart and checkout customization guidance covers the block-based editing tools. Start with the layout already running on your store rather than switching layouts to accommodate a plugin. Classic Shortcode Checkout Classic checkout uses the shortcode. Its PHP field definitions include billing, shipping, and order sections. Developers can change those definitions with the woocommerce_checkout_fields filter. The woocommerce_after_order_notes action can also display custom field markup. Prefer settings over code? WooCommerce's Checkout Field Editor extension supports this legacy checkout. Its documented sections are Billing, Shipping, and Additional. We recommend the editor route when you need straightforward changes and want to manage them through WordPress. Checkout Block The Checkout block uses a different extension system. A classic-checkout PHP snippet won't automatically customize it. WooCommerce introduced the Additional Checkout Fields API in version 8.9.0. Developers register supported fields through woocommerce_register_additional_checkout_field(). For a visual setup, use an extension that supports the Checkout block. WooCommerce's Checkout block documentation describes its layout and available settings. Choose Fields That Help Fulfill Orders Before adding anything, decide who uses the answer and what they do with it. If nobody acts on the information, it probably doesn't belong at checkout. A purchase order number gives business customers a reference for their records. A delivery preference can help your fulfillment team. For general delivery instructions, the existing order notes field may already do the job. Choose the simplest input that fits. Text suits a reference number. A select field works for a fixed set of choices. A checkbox suits a clear yes-or-no answer. Avoid presenting a date field as a promised delivery date unless your fulfillment process supports that promise. Collecting a date doesn't create scheduling, capacity limits, or delivery guarantees. Keep account requirements separate, too. Our guide to guest checkout and account creation helps you configure whether shoppers need an account. Add Checkout Fields Without Writing Code A field editor lets you manage labels, placement, and required status through settings. It's a practical choice when your team needs to adjust checkout without editing PHP. Match the Extension to Your Checkout For classic checkout, WooCommerce's Checkout Field Editor documentation describes adding, removing, and modifying fields. For conditional requirements, Conditional Checkout Fields & Edit Checkout Fields for WooCommerce advertises support for classic checkout, Cart and Checkout blocks, and High-Performance Order Storage (HPOS). Its conditional checkout fields documentation covers that extension's settings. Conditional fields help you ask relevant questions without showing every customer every option. We recommend installing one checkout field editor. Overlapping editors can compete over field names, placement, and validation. Configure the Field and Its Destination With the classic Checkout Field Editor installed and activated, open WooCommerce > Settings > Checkout Fields. Select Billing, Shipping, or Additional, then add a field. Give it a unique internal name and a clear customer-facing label. Choose its input type, required status, and position. Set its order and email display options, then save your changes. Use a label such as "Purchase order number" rather than "Additional information." Customers shouldn't need to guess what belongs in the box. Keep the internal name stable after launch. Integrations may depend on it, even when you change the visible label. Add a Checkout Block Field With PHP Want a lightweight custom implementation? The Additional Checkout Fields API registers the field and handles its standard storage. Keep this code in a small site plugin rather than your parent theme. A theme update shouldn't remove your checkout functionality. Register an Optional Order Field Create wp-content/plugins/store-checkout-fields/store-checkout-fields.php and add: <?php /** * Plugin Name: Store Checkout Fields */ add_action( 'woocommerce_init', function () { if ( ! function_exists( 'woocommerce_register_additional_checkout_field' ) ) { return; } woocommerce_register_additional_checkout_field( array( 'id' => 'store/purchase-order-number', 'label' => 'Purchase order number', 'location' => 'order', 'type' => 'text', 'required' => false, 'sanitize_callback' => 'sanitize_text_field', ) ); } ); Activate Store Checkout Fields under Plugins > Installed Plugins on staging. This registers an optional text field for the Checkout block. The namespaced ID, store/purchase-order-number, identifies it. The sanitization callback cleans the submitted text. Choose Where the Answer Belongs The API provides three locations: contact, address, and order. Contact fields support customer contact information. Address fields are associated with billing and shipping addresses. Order fields capture information belonging to that purchase. The snippet uses order, so the purchase order number stays with the order rather than becoming a customer-profile preference. For integrations, WooCommerce recommends its CheckoutFields helper methods, including get_field_from_object(), instead of depending directly on internal metadata keys. That gives custom code a supported way to retrieve saved answers. Validate Answers and Protect Customer Information A field should accept useful information and explain problems clearly. Validation and sanitization do different jobs, and both matter. Make Required Fields Earn Their Place Validation decides whether an answer is acceptable. Sanitization cleans the value before it's stored. For block-based custom development, WooCommerce provides woocommerce_validate_additional_field for custom validation. Sanitization can use a field's sanitize_callback or the woocommerce_sanitize_additional_field filter. The purchase order field above is optional. If your business requires a particular format, add server-side validation that matches that rule. Write useful error messages. "Enter your purchase order number" gives customers a next step. "Invalid input" leaves them stuck. Collect Less and Control Access Don't ask customers to enter card details, passwords, or sensitive access codes into a general checkout field. Payment information belongs in your payment gateway's secure flow. Decide which answers should appear in customer emails, staff emails, exports, and fulfillment tools. More visibility isn't always better. We recommend treating custom fields as customer information, not harmless form decoration. Limit collection to what your store needs and give staff access according to their role. Test the Entire Checkout Before Launch A field can look perfect and still interrupt payment. Test the buying path, not only the new box. Complete Orders on Staging Use a staging copy and your gateway's test mode. Place orders as a guest and as a logged-in customer. Try desktop and mobile. Submit an empty optional field, a completed field, and an invalid answer where validation applies. Test separate billing and shipping addresses if your store supports them. Then open the order in WordPress. Follow the answer through any emails, exports, or fulfillment integrations that need it. Success means the customer can pay and your team receives usable information. Isolate Conflicts One Change at a Time If checkout stalls, record exactly when it happens. Open the browser's developer tools and look for console errors or failed network requests. On staging, disable one nonessential extension at a time and repeat the same checkout flow. Start with field editors, cart tools, currency converters, caching plugins, and analytics scripts. Test a default WordPress theme separately if the problem remains. Save screenshots and logs before resets. Keep experiments off your live checkout. Don't disable payment or access-control extensions on the live store to see what happens. Give Your Store a Dependable Hosting Foundation Custom fields run alongside your checkout scripts, payment gateway, and order database. Hosting supports that whole system. We recommend keeping a current backup before changing checkout code or installing an editor. Protect both your WordPress files and database, since order details live in the database. Our WordPress hosting offers one-click installs and 24/7 support from real people. Most of our hosting plans include free SSL, which protects information as it travels between a browser and your site. SSL doesn't replace field validation, but it belongs in every store's setup. Choose our WordPress hosting when you want a straightforward foundation for your WooCommerce store. Pair it with our website backup service before making checkout changes. FAQ Can custom fields work with guest checkout? Yes. An order-level field can capture information without requiring a customer account. Test any account-dependent conditions separately. Why doesn't a classic checkout snippet appear in the Checkout block? The two checkout systems use different extension methods. Use the Additional Checkout Fields API or a block-compatible extension for the Checkout block. Does adding a field automatically put it in every email? No. Email visibility depends on the extension or implementation. Configure the destinations your team needs and test the resulting messages. Can a custom field add a fee? A field alone doesn't calculate charges. Fee calculation needs separate logic or an extension feature designed to update order totals correctly. Build a Checkout That Collects What Matters The right WooCommerce checkout fields give your team useful answers without slowing customers down. Match your checkout type, use clear labels, and test the saved order. We recommend starting with one purposeful field, then expanding only when your workflow needs more. Build your store on our WordPress hosting and keep checkout changes controlled. Your customers get a clear path to payment, and your team gets the details it needs. [...]
Read more...
WooCommerce / WordPressWooCommerce Analytics Reports: Read Store RevenueA busy store can look successful while discounts and refunds chip away at its revenue. WooCommerce analytics reports help you see what your products bring in, what gets deducted, and how sales change over time. We recommend starting with net sales, then using orders, returns, and product reports to explain the movement. You don't need to become a spreadsheet expert to make smarter decisions. Start with the right dates, and the numbers become much easier to read. Key Takeaways Use Analytics > Revenue to separate product sales, discounts, returns, taxes, and shipping. Compare matching periods, then read net sales alongside order count and average order value. Treat report exports as sales records, not bank statements. Payment fees, payout timing, and operating costs need separate attention. The goal is simple: understand what changed before deciding what to promote, fix, or invest in next. Open WooCommerce Analytics Reports With the Right Dates Your report is only useful when its dates match the question you're asking. A weekly sales review and a month-end bookkeeping review need different views. Start in Analytics > Revenue Open your WordPress dashboard and select Analytics > Revenue. This report brings gross sales, returns, coupons, net sales, taxes, shipping, and total sales into one place. Use a preset date range for a quick review, or enter custom start and end dates for a promotion or accounting period. The WooCommerce Analytics documentation covers these date controls and the reporting interface. We recommend choosing the period before interpreting any totals. Otherwise, it's easy to mistake a partial month for a disappointing month. Compare periods that answer the same question The Revenue report lets you compare your selected range with the previous period or previous year. Use the previous period to assess recent momentum. Use the previous year when seasonal buying patterns matter. Keep the context attached to the comparison. A promotion, holiday, stock shortage, or refund batch can change the result. Avoid comparing an unfinished week with a complete week. Equal-looking labels don't always mean equal selling time. Completed periods give you a cleaner starting point. Understand Gross Sales, Net Sales, and Total Sales Three sales figures. Three different jobs. Knowing which one you're reading prevents a bigger dashboard number from becoming a misleading business decision. Here's how the core WooCommerce sales figures fit together. MetricWhat it measuresBest useGross salesProduct sales before returns and coupons, excluding taxes and shippingSee sales before deductionsNet salesGross sales minus returns and couponsTrack product revenue after deductionsTotal salesNet sales plus taxes and shippingRead the combined sales total For a straightforward revenue review, we recommend making net sales your main reference. Keep gross sales nearby to understand how much discounts and returns reduced that figure. Total sales includes charges that aren't product revenue. A shipping increase can lift total sales without any increase in merchandise sales. Taxes can create a similar distraction. None of these figures is profit. Product costs, payment processing fees, advertising, hosting, and other expenses still need their own records. Want to know whether your store is selling more? Start with net sales. Want to know whether it's keeping more money? Bring costs into the picture. Read Returns and Coupons Without Losing the Story A drop in net sales doesn't automatically mean customers bought less. The deductions deserve attention too. Put refunds in the correct period WooCommerce Analytics records refunds on the date the return occurred, rather than moving them back to the original order date. That means this month's revenue can include deductions for purchases made last month. Before blaming a campaign or product page, look at when those refunds were processed. Refunded shipping and taxes also have their own reporting treatment. Don't assume the Returns figure always equals the complete amount returned to the customer. Use the individual order when you need that full breakdown. A refund processed this month can reduce this month's reported sales even when the original purchase happened earlier. Watch what coupons leave behind Coupons reduce net sales. That's expected, but the size of that reduction helps you judge a promotion. Open Analytics > Coupons to examine coupon activity alongside the Revenue report. We recommend comparing the discount amount with order count and net sales over the same dates. More orders can be encouraging. More orders with heavy discounts deserve a closer look at product costs. Revenue reports show the sales result; they don't calculate whether the promotion was profitable. Connect Revenue Trends With Orders Revenue tells you how much. Order count helps explain how you got there. Read average order value beside net sales In core WooCommerce Analytics, average order value is net sales divided by orders. It shows the average product revenue per reported order. Read those three measures together: net sales, orders, and average order value. Rising revenue with fewer orders points toward larger purchases. Rising orders with lower average value points toward smaller purchases. Neither pattern tells the whole story alone. We recommend using Analytics > Orders to examine the orders behind a change before adjusting bundles, discounts, or shipping offers. Use the table to locate the change The Revenue table breaks the selected range into intervals. Its rows include dates, orders, gross sales, returns, coupons, net sales, taxes, shipping, and total sales. Intervals with no orders still appear. That makes gaps easier to spot instead of hiding them inside a monthly total. Look for the date where the pattern changed, then inspect the matching orders. A sudden dip needs a different response than a gradual decline. Keep promotion dates and known checkout problems alongside that review. Find the Products Behind Your Revenue Store-wide totals are the starting point. Product reports show where your sales are coming from. Open Analytics > Products and use the same date range as your Revenue report. Compare products by net sales and items sold. A high-volume item and a high-revenue item aren't necessarily the same product. For stores with sizes, colors, or other options, Analytics > Variations helps separate performance within a product. Analytics > Categories gives you a broader view of related merchandise. We recommend using these reports to guide practical decisions: which products deserve homepage space, which variations need stock attention, and which categories support your next promotion. Revenue alone still doesn't tell you margin. A popular product can carry high fulfillment or purchasing costs. If the sales records and available quantities disagree, our guide to WooCommerce stock management troubleshooting helps you trace the order and inventory settings involved. Fix that mismatch before building a promotion around stock you don't have. Resolve Reporting Gaps Before Changing Strategy An empty or unexpected report can be a reporting problem rather than a sales problem. Start with the records, not a new plugin. Review imports and excluded statuses In Analytics > Settings, review the historical data import and excluded order statuses. Older orders need to be included in the reporting data before they can appear in the expected period. An order status can also explain why an order appears in your store but not in a particular report total. Keep the order ID and current status handy when comparing records. Still using WooCommerce > Reports? Those legacy screens were deprecated with WooCommerce 4.0 in March 2020. The legacy WooCommerce Reports documentation distinguishes that older reporting area from Analytics. Separate missing data from failed payments A created order doesn't automatically mean a successful payment. Review the order notes and payment record when a revenue gap lines up with pending or failed orders. If troubleshooting requires payment-extension logging, enable it only for the investigation. Turn it off once you've collected the relevant entries. Logs can contain customer information, tokens, credentials, or request details. Store them securely and share only a redacted excerpt with support. A useful troubleshooting record includes the order ID, timestamp, status, and exact error. Export Reports and Reconcile the Money Once your dates and figures are clear, use Download in the report table header to export CSV data. Open the file in a spreadsheet for bookkeeping, comparison, or a regular revenue review. We recommend keeping the reporting period in the filename. It saves confusion when several monthly exports sit in the same folder. A Revenue CSV summarizes reporting data. It isn't a complete order-level bookkeeping export. When you need customer, order, or other detailed fields, our guide to export WooCommerce orders for bookkeeping explains that separate workflow. Then reconcile sales records with your payment processor and bank deposits. Processing fees, payout schedules, refunds, and adjustments can make a deposit differ from the report total. Keep those differences visible rather than forcing the figures to match. A report answers what your store recorded. A payout record answers what the processor transferred. Both belong in your month-end review. Keep Checkout Ready for Growing Sales WooCommerce analytics reports show completed activity. They don't count every sale a slow or broken checkout prevented. When a revenue dip overlaps with dashboard lag, checkout timeouts, or errors during a promotion, investigate the buying path too. Match the affected orders and timestamps with payment and server errors. Review memory limits, disk space, PHP compatibility, and caching rules before adding more checkout extensions. Revenue alone isn't a reason to upgrade hosting. Repeated resource-related problems are a stronger reason to assess capacity. We offer WordPress hosting, cPanel hosting, and VPS options for stores at different stages. Our 24/7 support comes from real people, and most hosting plans include free SSL. If you're launching or growing a WooCommerce store, choose our hosting with your workload in mind. Give checkout, administration, and background tasks the room they need, then use your reports to track the results. Turn Clear Reports Into Better Store Decisions Start with net sales, keep your comparison dates consistent, and follow changes into orders, refunds, and products. That gives you a useful revenue picture without treating every dashboard number as profit. We recommend making this a regular habit: review the same measures, investigate unusual movement, and keep exports connected to your bookkeeping. Pair that clarity with our hosting and support, so you can spend less time untangling store problems and more time making informed sales decisions. [...]
Read more...
WooCommerceWooCommerce Order Statuses: When to Change Each OneAn order marked "Processing" can sit there while you pack the customer's purchase, and that's perfectly normal. WooCommerce order statuses track payment and fulfillment, so the right label depends on what's happened behind the scenes. We recommend changing a status only when the order's payment or fulfillment record supports it. That keeps your team moving, your stock records clearer, and your customers informed. Start with what each status means, then connect it to the action your store has completed. Key Takeaways Processing usually means payment is received and fulfillment is next; Completed means your store has finished fulfilling the order. Compare order notes with the payment transaction before correcting a stuck status or asking a customer to pay again. Status changes can affect emails, inventory, and connected tools, so make deliberate updates rather than cycling through labels. What WooCommerce Order Statuses Mean Think of each status as a signpost for your team. It tells you what needs attention and what can move forward. WooCommerce's order status definitions describe these seven everyday statuses: StatusWhat it meansWhen to use itPending paymentThe order exists, but payment hasn't been completed.While waiting for the customer to finish payment.On holdPayment confirmation is still needed.While awaiting bank payment or a delayed gateway result.ProcessingPayment is received and fulfillment is pending.While preparing a paid order that needs fulfillment.CompletedFulfillment is finished.After your store has completed the required work.FailedThe payment attempt failed or was declined.When the payment result supports a failed transaction.CancelledThe order has been cancelled.When the purchase won't proceed.RefundedThe order has been fully refunded.After recording a full refund through the appropriate process. The useful distinction is payment progress versus fulfillment progress. Processing and Completed answer different questions, even though both usually follow successful payment. Stores using Checkout Blocks can also show Draft orders before checkout is submitted. These are checkout-in-progress records, not confirmed purchases. Your payment method and extensions can change the route an order takes. A card purchase, bank transfer, and cash-on-delivery order don't always follow the same sequence. When to Use Processing and Completed These two labels handle much of your everyday order work. Keep their meaning clear, and your fulfillment queue becomes easier to manage. Move to Processing when fulfillment can begin For a typical paid physical-product order, Processing means the payment succeeded and your team has work to do. Packing, shipping, or preparing the purchase comes next. Payment gateways normally make this update automatically. With Direct Bank Transfer (BACS), you may need to confirm that payment arrived before moving an On hold order forward. Cash on delivery is an important exception. It can place an order in Processing before you collect payment, because fulfillment starts first. We recommend treating the payment method as part of the order record. The status alone isn't enough to explain every purchase. Use Completed when your store's work is finished Completed means fulfillment is done. For shipped goods, use it when you've finished the fulfillment steps your store promises. It doesn't automatically mean the carrier has delivered the parcel. Your completion email should reflect what you finished, without promising an arrival date you can't support. Orders containing only products marked both virtual and downloadable can complete automatically after successful payment. A virtual product alone doesn't always qualify. WooCommerce Order Status Control offers additional rules for completing paid orders. Use automation when your fulfillment process supports it, rather than to make the order list look tidier. Handle Failed, Cancelled, and Refunded Orders Carefully These statuses need a little more attention because payment problems and customer requests can overlap. Separate the financial result from the decision to stop fulfillment. Investigate Failed before requesting another payment Failed usually follows an unsuccessful or declined payment. Delayed-notification methods can remain On hold before a rejection moves the order to Failed. If the customer reports a checkout timeout, locate the matching transaction before suggesting another attempt. A timeout can leave the customer unsure even when the gateway recorded activity. With Stripe, compare the transaction ID, amount, and payment result against the WooCommerce order notes. Stripe's WooCommerce status guidance explains how its payment events relate to order labels. Once the result is clear, you can give the customer an accurate next step. Separate cancellation from the refund process Cancelled means the purchase won't proceed. Use it for an abandoned or withdrawn order when cancellation matches the record. For a paid purchase, handle the money through the refund process as well. Changing the dropdown to Refunded doesn't return funds. Open the order's Refund controls and enter the items or amount being refunded. Supported gateways can return money through an automatic refund. A manual refund records the adjustment, while you arrange the payment separately. Partial refunds generally leave the existing order status in place. Reserve Refunded for a fully refunded order. How to Change an Order Status in WooCommerce You don't need a complicated workflow for a straightforward correction. You do need a clear reason for making it. We recommend updating one order at a time when payment or fulfillment needs investigation: Open WooCommerce > Orders and select the order you want to update. Read the order notes and compare the payment result with the gateway transaction where payment is involved. Review fulfillment activity, including shipment records, customer messages, or work already completed. Choose the appropriate option in the Status dropdown, then click Update. Add a private order note explaining the reason and any relevant transaction or fulfillment reference. That note gives your team something useful to follow later. "Payment received by bank transfer" is clearer than an unexplained status change. Bulk actions are useful when several orders genuinely reached the same stage. Select the relevant orders, choose the status action, and apply it. Before a bulk change, make sure every selected order belongs in that group. Mixing unpaid purchases with fulfilled orders creates avoidable cleanup. For larger corrections, take a backup first. Restore options protect your site, but restoring an older database can also overwrite newer orders. Keep recent sales in mind before any recovery. What Status Changes Can Trigger A status update can do more than change a colored label. WooCommerce and connected extensions may react immediately. Keep inventory tied to the order trail A paid order doesn't need to reach Completed before stock is reduced. Processing can already reflect a stock reduction, and On hold orders can reduce managed stock while payment confirmation is pending. The Hold stock setting applies to unpaid Pending payment orders. It isn't a timer for On hold orders. When an unpaid order expires, WooCommerce can cancel it and release the reserved stock. Before manually adjusting quantities, read the order notes and inspect the purchased product or variation. Someone may have already changed inventory. Our guide to WooCommerce stock update problems connects payment results, order events, and inventory records. Match customer emails to the actual event Processing and Completed messages should explain what the customer needs to know at that stage. Payment received? Explain preparation. Fulfillment finished? Provide the available shipment or download information. Manage built-in notifications under WooCommerce > Settings > Emails. Editing a template changes its content, but it doesn't create a new status trigger. Our guide to status-based WooCommerce order emails covers that distinction. Moving an order forward to trigger an email can also trigger inventory or extension actions. Fix the notification without misrepresenting the order. Test the full order journey with a mailbox you control, not only the email preview. Fix Stuck Statuses Before Adding More Automation An order that doesn't update can point to a payment integration issue. Adding another workflow rule won't repair the missing payment event. Follow the payment record and webhook A webhook is a message the payment gateway sends back to your store. It tells WooCommerce about events such as successful payments or refunds. If Stripe shows a successful payment while WooCommerce remains Pending payment, inspect webhook delivery and configuration. Compare timestamps and transaction IDs so you're following the same purchase. WooCommerce's order troubleshooting guidance starts with the order record and payment behavior. An order remaining Processing is different. Physical purchases normally need a fulfillment update before they become Completed. Packing and shipping still count as unfinished work. Give the store a dependable hosting foundation Hosting supports the checkout, database, and communication your order workflow relies on. SSL protects connections, backups support recovery, and accessible support helps when server-side problems interrupt the store. We offer WordPress and cPanel hosting with one-click installs and 24/7 support from real people. That gives you a simpler starting point for running your store and getting help with hosting issues. For businesses that need our Web Hosting Plus option, pricing is $30.99 per month. Choose hosting around your store's needs, then keep payment configuration and fulfillment rules accurate. A hosting plan won't turn an unpaid order into a paid one, but it supports the systems that record each step. Add Custom Statuses Only for Useful Milestones Need a "Ready for pickup" update? A custom status can help when it describes a real handoff that the standard labels don't cover. We recommend adding a status only when your team knows exactly when to use it. "Ready for pickup" should mean the items are prepared and available, not simply that payment arrived. Extensions such as WooCommerce Order Status Manager can provide custom labels and transition-based notifications. A visual email designer alone may not create those triggers. Keep the setup focused. Decide who changes the status, which transition sends the message, and what the customer should do next. Then test that journey before using it on live orders. Keep Every Order Status Grounded in the Record WooCommerce order statuses work best when each update follows a real payment or fulfillment event. We recommend keeping the order notes, transaction details, and customer messages aligned. Start with one clear rule: change the status when the work or payment record changes. Your team gets a dependable queue, and your customers get updates they can trust. Build that workflow on our WordPress hosting, then keep every order moving for the right reason. [...]
Read more...
Email / WooCommerceFix WooCommerce Order Emails Customers Never ReceiveA successful checkout shouldn't leave your customer wondering whether their order went through. When WooCommerce order emails disappear, we recommend separating the problem into three parts: the notification trigger, the sending system, and delivery. Fix the broken part first, and you avoid adding plugins that don't solve the problem. Start with the order record, then follow the message toward the customer's inbox. Key Takeaways Match the missing notification to the order's actual status before changing email settings. Use email logs to separate trigger failures, sending errors, and delivery problems. Connect an authenticated mailer, use a domain-based sender, and test a complete checkout journey. Give your store dependable hosting, but remember that hosting alone can't repair a disabled notification. Find Where the Missing Email Stops An order in your dashboard proves WooCommerce created an order. It doesn't prove a customer notification was generated or delivered. Open WooCommerce > Orders, select the affected order, and record its status, billing email, order notes, and checkout time. These details give your troubleshooting a clear starting point. Use the evidence to choose your next step. What you findWhat to investigate nextThe expected status change never happenedPayment confirmation, gateway updates, and notification triggersThe notification was disabled or skippedWooCommerce settings and extension rulesThe mail system reports a sending failureMailer credentials, connection settings, and server errorsSending succeeded but the customer received nothingSpam filtering, authentication, bounces, and delivery logs Follow the matching route rather than changing everything at once. One targeted fix is easier to test and easier to undo. Match WooCommerce Order Emails to the Right Trigger Check the Order Status Before Resending Anything A customer expecting a processing confirmation won't receive that notification if the order never reaches its triggering event. Pending payment means payment hasn't been confirmed. Processing and Completed notifications follow their own defined events and transitions. Payment gateways and extensions can also affect that workflow. Read the order notes and compare them with the gateway's transaction record. If checkout timed out, establish whether money was captured before changing the status or asking for another payment. We recommend keeping payment corrections separate from email troubleshooting. Status changes can affect stock and other store actions, too. Enable the Correct Customer Notification Go to WooCommerce > Settings > Emails, find the missing notification, and select Manage. WooCommerce's site administration documentation covers this settings area. Confirm that the notification is enabled. Then inspect the order's billing email for a typo. Where a notification offers a recipient field, make sure it points to the intended recipient. The New order notification is normally an administrator message. It isn't a substitute for the customer's processing update. Need a custom-status message? Our guide to status-based order email customization explains the difference between editing a message and creating its trigger. A redesigned template alone won't send a new notification. Read the Logs Before Changing the Mailer Look for the Notification Attempt Open WooCommerce > Status > Logs and inspect the available transactional-email records around the order's timestamp. The transactional-emails log can show Sent, Failed, Disabled, or Skipped attempts. Disabled and Skipped results point toward notification settings or dispatch conditions. A Failed result gives you a reason to investigate the sending system. Can't find the expected entries? The logging threshold can hide INFO or NOTICE records. Missing entries alone don't establish that WooCommerce never attempted the notification. WooCommerce's email troubleshooting FAQs explain how its email system works. Separate Sending Success From Inbox Delivery WooCommerce uses WordPress's wp_mail() to hand messages to the mail system. A successful result means the message was accepted for processing. A Sent entry confirms a handoff, not arrival in the customer's inbox. Next, inspect your mailer's delivery events. A rejection, bounce, or deferred delivery gives you more useful evidence than repeatedly sending the same message. Use timestamps and recipient addresses to match the notification across both systems. Order logs explain what WooCommerce did; delivery logs explain what happened afterward. Fix the Sending Route With an Authenticated Mailer Configure One Mailer Properly Default WordPress mail depends on the server's mail setup. An authenticated SMTP or email API connection gives your store a defined sending route. The WP Mail SMTP plugin connects WordPress to a configured mail provider. FluentSMTP is another established option. Choose one mailer plugin rather than installing several that compete to control outgoing mail. WP Mail SMTP supports routes including Gmail, Outlook, Amazon SES, and SendLayer. With its Other SMTP option, enter the provider's SMTP host, port, encryption method, and authentication credentials. These settings belong together. A correct password won't fix the wrong host or encryption setting. Save the configuration and resolve any connection error before testing WooCommerce notifications. Send a Mailer Test First In WP Mail SMTP, open Tools > Email Test and send a message to a mailbox you control. HTML is enabled by default. If that message fails, focus on the mailer connection. WooCommerce template edits won't repair authentication errors or a blocked connection. If it arrives, you've established that WordPress can send through the configured route. Now test the order notification itself. We recommend using a second mailbox on another email service, too. That helps distinguish a store-wide sending problem from filtering at one destination. Give Receiving Mailboxes a Trusted Sender A recognizable sender helps customers trust your messages. Authentication helps receiving servers assess them. Use a sender address on a domain you control, and complete the authentication required by your email provider. Avoid using a customer's address as the From address. Use Reply-To when replies need to reach a different mailbox. Three records matter: SPF identifies permitted senders for your domain. Keep one SPF record and combine the required services within it. DKIM adds a signature that receiving servers can validate. DMARC connects authentication with the visible From domain and defines how failed authentication should be handled. Your website's SSL certificate protects browser connections. It doesn't replace these email records. If messages reach spam, inspect their headers for authentication results. Also review the mail provider's bounce or suppression records. A previously rejected address may need attention before another send attempt can succeed. Clear Plugin Conflicts and Stuck Email Jobs Test Conflicts Away From Live Checkout Email designers, workflow tools, and other extensions can interfere with notification generation. A recent update is a useful clue. Use staging with notifications directed to mailboxes you control. Keep WooCommerce, the required payment gateway, and your configured mailer active. Disable unrelated plugins, then reproduce the affected order journey. If the notification works, reactivate plugins individually and repeat the test. Test a default WordPress theme when the problem appears tied to template overrides. WooCommerce's troubleshooting documentation covers this conflict-testing approach. Keep live customers out of the experiment. Inspect Queued Notifications Some extensions queue messages instead of sending them immediately. For those workflows, open WooCommerce > Status > Scheduled Actions and find the relevant job. A failed or overdue action can explain why a correctly configured notification never reached the mailer. Inspect the failure details before rerunning jobs. Repair the underlying problem first so you don't create duplicate customer updates. A server-side PHP error can stop execution here. Capture the error, action name, and timestamp so support has something concrete to investigate. Test the Complete Customer Journey A preview proves the message looks right. A complete order test proves the workflow works. We recommend a controlled test on staging with your gateway's test mode where available. Keep staging emails away from real customers. Place an order using a mailbox you control, including guest checkout if your store offers it. Follow the normal payment and fulfillment workflow without forcing unrelated status changes. Match each expected notification to its trigger, recipient, and delivery record. Read the received messages and compare totals, products, customer details, and next steps with the order. Test custom statuses separately. WooCommerce Order Status Manager supports transition-based notifications, but those rules still need deliberate configuration. If an email-log extension provides a resend action, use its documented workflow after fixing the original fault. Changing payment or fulfillment status simply to generate another email can create unwanted side effects. Put Reliable Hosting Behind the Fix Your email workflow depends on more than a template. WordPress must run, payment updates must reach the store, and scheduled jobs must execute. If logs show memory exhaustion, our WordPress memory limit guide explains that part of the problem. Changing SMTP credentials won't repair a PHP process that stops before the message is generated. We recommend treating hosting as the foundation for your store's operations. Backups, suitable resources, secure checkout connections, and accessible support make troubleshooting easier to manage. Ready for a stronger foundation? Ask us about ZADiC website hosting for your WooCommerce store. Share your plugin list, traffic needs, and recovery priorities so we can discuss a suitable plan without treating hosting as a blanket email fix. FAQ Why Do Administrator Emails Arrive but Customer Emails Don't? Administrator and customer notifications use different settings, recipients, and triggers. A working New order email proves only that that message followed a working route. Inspect the customer notification, order status, and billing email. Then trace its own sending and delivery records rather than assuming every notification behaves identically. Does Installing SMTP Fix Every Missing Order Email? SMTP can repair a broken sending route. It can't enable a disabled notification, create a missing custom-status rule, or complete a failed payment update. We recommend identifying the failed stage first. If the notification never reaches the mailer, focus on the trigger or execution problem. If sending fails, investigate the authenticated connection. Turn Missing Messages Into Clear Order Updates Reliable WooCommerce order emails start with accurate triggers and a working sending route. Delivery records then tell you whether the message reached the receiving system. Fix one stage at a time, and test the complete journey before changing your live workflow. If your store needs a better hosting foundation, talk to us about ZADiC. Give your checkout dependable support, and give customers the clear order updates they expect. [...]
Read more...