WPC Product Table 3.1.8 – for WooCommerce

I tested WPC Product Table on a real WooCommerce setup, not in some clean demo sandbox where everything magically behaves. My store had variable products, a bloated theme, WP Rocket, Rank Math, and one of those “premium” builders that injects six wrappers just to print a button. Lovely stuff.

The good news: WPC Product Table actually works. The table renders products cleanly, the add-to-cart flow is usable, and I didn’t have to sacrifice a weekend to make it display SKUs, prices, stock status, and variations in one place.

The bad news: like most WooCommerce table plugins, it can get cranky when your theme already thinks it owns every WooCommerce hook on the planet.

Where I configured it

Most of the useful stuff sits in:

WP Admin -> WPClever -> Product Table

That’s where I changed columns, button behavior, pagination, sorting, and responsive options. No mystery “theme options” maze, thankfully.

For inserting the table, I used the shortcode block in Gutenberg and also dropped the shortcode directly into a custom template. On one landing page I used:

Appearance -> Theme File Editor -> page-product-list.php

Yeah, I know, editing there is ugly. In the actual project I moved it into a child theme because I’m not completely feral.

WPC Product Table pulled products from normal WooCommerce data, so nothing weird was stored in some custom nightmare table. Product data still lives where it should:

wp_posts, wp_postmeta, wp_terms, wp_term_relationships

That matters if you ever need to debug missing SKUs or broken stock filters with SQL instead of praying at the admin screen.

The thing that annoyed me first

My theme was already overriding WooCommerce button markup through:

wp-content/themes/my-theme/woocommerce/loop/add-to-cart.php

So the table button looked fine on desktop and then exploded on mobile like a cheap accordion menu. I opened DevTools, checked the Elements panel, and saw the theme dumping its own .button.product_type_variable classes into the table.

Classic WordPress nonsense.

My fix was not beautiful, but it worked. In the child theme functions.php, I added a small conditional style override only on the page using WPC Product Table:

add_action('wp_enqueue_scripts', function () {
    if (is_page('bulk-order')) {
        wp_add_inline_style('wpcpt-frontend', '
            .wpcpt-table .button { white-space: nowrap; min-width: 110px; }
            .wpcpt-table td { vertical-align: middle; }
        ');
    }
});

If your handle is different, check it in DevTools under Network -> CSS. Don’t guess. Guessing is how people end up with twelve useless snippets.

JS conflicts, because of course

With WP Rocket, the cart buttons initially failed after I enabled “Delay JavaScript execution”. Console showed:

jQuery is not defined

and sometimes Woo fragments didn’t refresh after adding a product.

I had to exclude these from delay:

jquery-core
jquery-migrate
wc-add-to-cart
wc-cart-fragments
wpcpt-frontend

After that, WPC Product Table stopped acting drunk. If you minify everything blindly, WooCommerce variations are usually the first thing to catch fire. I absolutely hate that this is still a thing in 2026, but here we are.

Builder settings vs hardcoded pain

Stuff I could handle in the plugin/admin UI:

• columns
• product image size
• add-to-cart button display
• pagination
• sorting
• category/product source
• responsive table behavior

Stuff that needed code or template digging:

• theme button markup
• spacing inside table cells
• mobile overflow behavior
• custom badges from ACF
• hiding columns based on user role
• changing how variation labels are printed

For role-based column hiding, I used the shortcode in a PHP template and wrapped it:

if (current_user_can('wholesale_customer')) {
    echo do_shortcode('[wpc_product_table columns="sku,name,price,stock,cart"]');
} else {
    echo do_shortcode('[wpc_product_table columns="name,price,cart"]');
}

Not elegant. Effective. That’s basically WordPress development in one sentence.

Performance reality check

I opened DevTools -> Network and watched the page load with 96 products in the table. The plugin itself wasn’t the biggest pig. The theme was loading three icon fonts, Elementor frontend assets, and five font weights from Google Fonts. What were they thinking?

Still, don’t render 300 products at once and then blame WPC Product Table. Use pagination. Keep it sane. The DOM gets fat fast when every product row includes image, price HTML, stock badge, quantity field, and cart button.

For my bulk order page, 25–40 products per page felt like the sweet spot.

GPL and updates

I tested a GPL copy of WPC Product Table and it was fully working for me with no domain cap — basically Unlimited Website Usage. No feature wall popped up during normal use.

Activation wasn’t dramatic. The plugin ran without me typing a license key for the actual table features. A key may matter for official automatic updates and vendor support, but the plugin itself didn’t stop rendering tables.

Manual updates were boring: download the new ZIP, back up the site, deactivate the old plugin, replace:

wp-content/plugins/wpc-product-table/

then reactivate. I also checked the table page after update because WooCommerce plugins love tiny frontend regressions.

FAQ

Why does the add-to-cart button not refresh the mini cart?

Usually delayed JS. Exclude jquery-core, wc-add-to-cart, wc-cart-fragments, and the WPC frontend script from WP Rocket or LiteSpeed delay.

Why does the table look broken on mobile?

Your theme CSS is probably leaking into table buttons or cells. Inspect .wpcpt-table in DevTools and override inside the child theme, not global Customizer soup.

Can I add ACF fields as columns?

Not nicely from the UI in every setup. I usually hook it in PHP or print a custom shortcode column. Check product meta in wp_postmeta first.

Is WPC Product Table heavy?

Not by itself, but huge product lists create a nasty DOM. Use pagination and avoid loading 100+ product rows with images and variation controls.