The WooCommerce Product Table alternative for any CPT, not just products
WooCommerce Product Table by Barn2 is excellent at one specific job: turning the WooCommerce product catalogue into a sortable, filterable table. SleekView generalises that idea: tables, kanban, and feedback boards over any CPT with ACF or Meta Box fields, with the shop case as just one of many.
♾️ Lifetime License available
Any post type, not just WooCommerce products
WooCommerce Product Table by Barn2 is the long-running standard for shop catalogues rendered as tables. It reads the WooCommerce product post type, maps product fields and attributes into columns, adds an Add to Cart button, and ships filters tuned for product attributes. For wholesale ordering, restaurant menus, parts catalogues, and large product lists, it is genuinely the right tool.
SleekView is a more general-purpose view layer. It reads any post type, including WooCommerce products, and any ACF or Meta Box field on those posts. The shop catalogue is one of many shapes it can render, alongside team directories, project boards, release logs, and feedback walls. Filters bind to the underlying field, sort and search live on the view config, and the same view definition can render as a table, a kanban board, or a feedback board.
WooCommerce Product Table wins clearly when the goal is a shop catalogue with cart actions baked in. SleekView wins when the project needs the same table-and-filter experience over non-product CPTs, when the team needs view types beyond tables, or when WooCommerce-shaped tables need to live alongside CPT-shaped views in the same plugin.
Workflow
How a non-product table becomes a SleekView
Pick a non-product CPT
Create a SleekView on the CPT
Add filters and sort
Standardise across the site
Comparison
SleekView vs WooCommerce Product Table at a glance
Differences
What changes when you move off WooCommerce Product Table
The WooCommerce Product Table way
- Built specifically for the WooCommerce product CPT
- Filters tuned for product attributes and taxonomies, not arbitrary CPT fields
- Tables only, no kanban or feedback board
- Other CPTs need a different plugin to render the same way
- Inline editing of product data is not the focus
The SleekView way
- Reads any CPT, ACF, and Meta Box, including WooCommerce products
- Tables, kanban, and feedback boards as view types
- Per-field filters, search, and sort across all CPTs
- Inline cell editing in the table view
- Same plugin for shop, directory, roadmap, and feedback use cases
Features
Three things that actually change how you work
Any CPT, not just products
WooCommerce Product Table is locked to the product post type and its attribute model. SleekView treats every CPT, ACF, and Meta Box field as a first-class source, so the same view-builder UI handles directories, projects, releases, and feedback walls.
More than a table
WooCommerce Product Table renders one layout: a sortable, filterable table with cart actions. SleekView ships table, kanban, and feedback-board views over the same data, so non-table use cases (roadmaps, project boards) stay in one plugin.
Filters tied to fields
WooCommerce Product Table's filters are tuned for product attributes and taxonomies. SleekView's filters bind to whatever CPT, ACF, or Meta Box field drives the column, with the right control type chosen automatically.
Migration
When to migrate (and when to keep WooCommerce Product Table)
1. Decide on the shop case
If the table is a shop catalogue with cart actions, variations, and product attribute filters, WooCommerce Product Table is genuinely the right tool. Keep it for that use case and reach for SleekView for everything else.
2. Identify non-product tables
Any table or list outside the shop, including team rosters, project boards, downloadable resources, release notes, FAQ-style lists, is a candidate for SleekView.
3. Create matching SleekViews
For each non-product table, create a SleekView on the relevant CPT and map columns to CPT, ACF, or Meta Box fields. Add filters, sort, and search per field on the view config.
4. Standardise the view layer
Once the non-product tables are SleekViews, the team has one view layer for the whole site (with WooCommerce Product Table still handling the shop tables it was built for).
Audience
Who tends to combine WooCommerce Product Table with SleekView
Shops that need more than a product table
Stores still use WooCommerce Product Table for the catalogue but reach for SleekView when they need a customer directory, an order-status board, or a feedback wall over WooCommerce data.
Sites with mixed CPTs
Sites with multiple CPTs (products, courses, events, team members) standardise on SleekView for the non-product tables instead of stacking single-purpose table plugins.
Roadmaps and feedback over WooCommerce data
Group products by status into a kanban, or expose a feedback board over a 'feature requests' CPT, all on the same view-layer plugin.
The bigger picture
Why a shop-specific plugin and a general view layer can coexist
WooCommerce Product Table by Barn2 has earned its place because it answers a very specific question well: how should a shop render its catalogue as a table with cart actions and product attribute filters. Every part of its design optimises for that case, from variation handling to Add to Cart in a row to attribute-aware filtering. The trouble is that most sites do not only have a shop.
They also have team members, projects, courses, releases, FAQs, feature requests, and any number of other CPTs that want the same table-and-filter treatment. WooCommerce Product Table is, by design, out of scope for those. SleekView fills that gap.
It treats every CPT, ACF, and Meta Box field as a first-class source, ships table, kanban, and feedback-board views over the same data model, and keeps filters and sort tied to the underlying field rather than the column position. The two plugins compose well: WooCommerce Product Table handles the shop catalogue with all its e-commerce specifics, and SleekView handles the rest of the site as a single, consistent view layer. Most shops that try both end up running them in parallel rather than picking one over the other.
Questions
Common questions about switching from WooCommerce Product Table
Only when the goal is general-purpose CPT views. WooCommerce Product Table by Barn2 has shop-specific features (Add to Cart, variations, product attribute filters, lightbox) that SleekView is not trying to match. For shop catalogue tables it remains the right tool. SleekView replaces it on non-product tables and on cases that need view types beyond tables.
Yes. WooCommerce products are a CPT, so SleekView can read them and render filters, sort, and search over product fields and ACF/Meta Box additions. What it does not include is the cart-focused functionality (Add to Cart from the row, inline variation pickers) that WooCommerce Product Table is built around.
Yes, and many shops keep both. WooCommerce Product Table handles the cart-focused shop tables; SleekView handles everything else (team directories, projects, release notes, feedback walls). They do not share storage or hooks.
Yes. SleekView's filters bind to taxonomies and to ACF/Meta Box fields, with the right control chosen per type. For WooCommerce attribute taxonomies the filter behaves like a multi-select. For shop-specific UX patterns (price slider, in-stock toggles), WooCommerce Product Table is more tuned out of the box.
No. Cart-focused interactions are not the primary focus. The right pattern is to keep WooCommerce Product Table for the shop catalogue and use SleekView for non-shop CPT tables, kanban boards, and feedback walls.
On non-product CPTs, WooCommerce Product Table is out of scope, so the comparison is really between SleekView and a different plugin. SleekView's per-field filter, sort, and search work the same way across every CPT, which is the main reason teams adopt it as a general view layer.
Yes, in the table view. With the right user capability, editors can click a cell, change a value, and save it back to the post or ACF/Meta Box field. This is rare for shop catalogues but useful for internal directories and project boards.
WooCommerce Product Table is a single commercial plugin from Barn2 with a per-site licence. SleekView is also a single commercial plugin, available standalone or as part of the Sleek All Access Pass. The two cover different scopes, so they tend to coexist rather than compete on price.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout