How to Check WooCommerce Product Data Tables: A Complete Guide

Understanding where WooCommerce stores product information — and how to access it — is essential for anyone managing an online store, debugging pricing issues, or building custom queries. Whether you're a store owner, developer, or site admin, knowing how to read and interpret WooCommerce product data tables gives you far greater control over your catalog. 🛒

What Is the WooCommerce Product Data Table?

WooCommerce stores product information across multiple database tables within WordPress's MySQL database. There isn't a single monolithic "product data table" — instead, data is distributed across several related tables that work together.

The core tables involved in product data include:

TableWhat It Stores
wp_postsCore product records (title, status, post type)
wp_postmetaProduct metadata (price, SKU, stock, dimensions)
wp_wc_product_meta_lookupOptimized lookup table for product queries
wp_wc_order_product_lookupSales data linked to products
wp_terms / wp_term_relationshipsCategories, tags, and attributes

The wp_postmeta table is where most product-specific fields live — stored as key-value pairs tied to a product's post ID. Fields like _price, _regular_price, _sale_price, _sku, _stock, and _manage_stock all live here.

The wp_wc_product_meta_lookup table was introduced in WooCommerce 3.7+ to improve query performance. It mirrors key product fields in a structured, indexed format specifically optimized for catalog filtering and sorting.

How to Access the WooCommerce Product Data Table

Via phpMyAdmin

The most direct method for most users is through phpMyAdmin, typically accessible through your hosting control panel (cPanel, Plesk, or similar).

  1. Log into your hosting control panel
  2. Open phpMyAdmin
  3. Select your WordPress database from the left sidebar
  4. Browse to wp_postmeta (your prefix may differ — e.g., mystore_postmeta)
  5. Use the Search tab to filter by meta_key values like _price or _sku

To view all data for a specific product, note its post ID from the WordPress admin URL (e.g., post.php?post=42) and then query:

SELECT * FROM wp_postmeta WHERE post_id = 42; 

This returns every metadata field associated with that product.

Via WP-CLI

Developers and technically comfortable users can query the database directly using WP-CLI from the server command line:

wp db query "SELECT * FROM wp_postmeta WHERE post_id = 42 AND meta_key LIKE '%price%';" 

WP-CLI is particularly useful for bulk inspection or scripted data audits without opening a GUI tool.

Via the WooCommerce Admin Interface

For most store owners, the easiest place to review product data is simply the WooCommerce product editor in WordPress admin. Under Products → All Products, opening any product reveals the Product Data panel, which displays:

  • General tab: Pricing fields
  • Inventory tab: SKU, stock quantity, backorder settings
  • Shipping tab: Weight and dimensions
  • Linked Products tab: Upsells and cross-sells
  • Attributes tab: Custom and global attribute assignments
  • Advanced tab: Purchase notes, menu order, reviews

This interface reads directly from the same database tables — it's simply a visual layer on top of the raw data. 💡

Understanding the Product Meta Lookup Table

The wp_wc_product_meta_lookup table deserves special attention because it's often misunderstood. Unlike wp_postmeta, which stores data in a flexible but slow key-value format, the lookup table uses dedicated columns for commonly queried fields:

  • product_id
  • sku
  • virtual / downloadable
  • min_price / max_price
  • stock_quantity
  • stock_status
  • rating_count / average_rating

This table is automatically managed by WooCommerce — you shouldn't edit it directly. If you notice discrepancies between this table and wp_postmeta, it usually indicates the lookup table needs regenerating, which can be triggered via WooCommerce → Status → Tools → Regenerate product lookup tables.

Variables That Affect What You See

How product data appears in these tables depends on several factors specific to your setup:

Database table prefix: WordPress installations use a configurable prefix (wp_ by default, but often customized for security). Your actual table names may differ.

WooCommerce version: The lookup table structure and available meta keys have evolved across versions. Stores running older versions may be missing certain optimized columns.

Variable products vs. simple products: Variable products store their pricing and stock data at the variation level (each variation has its own post record and meta entries), not just at the parent product level. This significantly expands the data spread across tables.

Third-party plugins: Plugins for memberships, subscriptions, product bundles, or custom pricing add their own meta keys to wp_postmeta. This can make reading raw product data more complex, as you'll encounter unfamiliar key names alongside WooCommerce's native fields.

Custom product types: If your store uses custom post types or non-standard product structures, the table relationships may differ from the default WooCommerce schema.

Different Setups, Different Experiences

A store running simple products only on a standard WooCommerce installation will find the data tables relatively clean and easy to navigate — a handful of consistent meta keys per product, predictable structure throughout.

A store using variable products, subscription plugins, dynamic pricing rules, and product bundles will encounter a significantly more complex data landscape. Multiple variation records, plugin-specific meta keys, and conditional pricing fields create a layered structure that requires more careful querying to interpret correctly.

Similarly, developers comfortable with SQL will find direct database access the most efficient inspection method. Store owners without database experience will get more practical value from the WooCommerce admin interface or a dedicated plugin like WPML, WP All Export, or table view plugins that surface this data in readable formats without direct database interaction.

The depth at which you need to inspect product data — whether for a one-time audit, ongoing development, or automated integration — shapes which access method and which tables are actually relevant to your situation.