Polylang for WooCommerce extends Polylang's core taxonomy to products in wp_posts with post_type=product, variations, and WooCommerce attributes. Translations are stored as separate product rows linked through the translation taxonomy, with _price, _stock_status, and other postmeta repeated per language so each translation can carry its own pricing and inventory.

The default product table shows one language at a time and switches via the language filter, so a catalog manager checking French coverage on 4,000 products opens page after page. SleekView pivots the translation taxonomy to render one row per source product with a column per language showing whether the translation exists, whether the title is set, and whether the stock status matches across languages.

Edits route through Polylang for WooCommerce's save path so language assignments and translation links fire the same hooks as the default UI. Inline price or stock updates on a per-language product still go through WooCommerce's CRUD layer so all order, inventory, and tax logic remains consistent.

Multilingual WooCommerce stores accumulate catalog drift faster than any other site type. Each translated product is a separate row in wp_posts with its own postmeta for price, stock, and attributes. A change to the source product doesn't automatically flow to the linked variants, so a sale ends in English while German shoppers still see the discount.

The default product table cannot surface this drift because it shows one language at a time. Catalog managers compensate with spreadsheets that go stale within a week of any catalog update. Reading the translation taxonomy joined to wp_postmeta directly produces one row per source product with coverage, stock parity, and price drift visible across all languages.

Translators get scoped CSVs, catalog managers fix drift before the customer sees it, and ecommerce leads can answer how many SKUs are launch-ready in every active language with a concrete number. The plugin still owns the writes through WooCommerce's product API. SleekView just makes drift visible enough to fix before it becomes a support ticket.