SleekView for WooCommerce Multilingual: translations & currencies as tables
Read WPML's element-translation tables and WCML's per-currency price overrides alongside WooCommerce orders. Sort, filter, and inline-edit translation status without opening each product — and surface multi-currency totals as real columns.
♾️ Lifetime License available
Stop opening products one at a time to check translation status
WooCommerce Multilingual & Multicurrency (WCML) sits on top of WPML and stores translation state in icl_translations, currency overrides in product meta and option rows, and applied currency on each WooCommerce order. The default WCML translation queue is useful but limited — anything else (which products have stale translations, which orders came in EUR vs USD, which prices haven't been overridden in a target currency) lives across multiple tables and stays invisible without per-row clicking. SleekView reads them directly so you build the columns you actually need.
Translation status, target language, last-modified date, and the linked source product all join through WPML's element-id keys. SleekView assembles them so a translation-ops view can show source product, target language, status, and last-modified date in one row. Filter to "German translations stale by 7 days" and the queue is built — no exporting and no per-product clicking.
Order data joins on the WooCommerce side. SleekView reads the order currency, total in store base, and total in customer currency from wc_orders meta so finance can reconcile by currency without opening every order. Inline-update translation status or trigger re-translation routed through WPML's API so existing automation runs as expected.
Workflow
How SleekView reads your WCML schema
Pick the source
icl_translations for translation rows, the product post type for currency overrides, or wc_orders for order-currency views. SleekView exposes joinable element-id and product-id columns automatically.
Compose your column set
Save and scope the view
Edit inline and ship
Sample columns
A typical WCML translations view
icl_translations for status and joins source product info plus per-currency override flags from product meta.
wp_icl_translations + wp_wc_orders + product meta
| Source product | Language | Status | Last modified | EUR override | USD override |
|---|---|---|---|---|---|
| Studio chair | DE | Translated | Apr 22 | Set | Auto |
| Studio chair | FR | Needs update | Mar 11 | Set | Auto |
| Linen tote | DE | In progress | Apr 24 | Auto | Set |
| Linen tote | ES | Not translated | — | Auto | Auto |
| Cedar lamp | DE | Translated | Apr 18 | Set | Set |
Comparison
Default WCML admin vs SleekView
Default WCML translation queue
- Translation queue lacks composable filters across language and freshness
- Currency overrides per product require per-product screens to inspect
- Order lists don't surface order currency as a real filterable column
- No single screen joining translation status with currency-override state
- Stale translations after a source edit aren't called out in the list
SleekView
-
Read
icl_translationsalongside product meta andwc_orders - Inline trigger re-translation across many products in one pass
- Custom columns for currency override status per target currency
- Save filtered views per role (e.g. "German translations stale by 7 days")
- Switch between table and kanban views grouped by language
Features
What SleekView gives you for WooCommerce Multilingual & Multicurrency
Custom column sets per view
Build separate views for translation ops, finance, and merchandising. Each picks columns from icl_translations, product meta, and wc_orders — no shared admin compromises.
Inline-trigger re-translation without opening products
Mark a translation as needing update or queue a re-translation right in the row. Bulk-trigger across products whose source changed yesterday — WPML hooks fire as expected.
Compose precise filters
Combine target language, status, source-modified window, and currency-override state. Save the filter as a named view your team reuses every translation cycle — no rebuilding it weekly.
Audience
Who uses SleekView for WCML
Translation operations
Stale translations across all languages sorted by source-modified date. Bulk-queue re-translation for products whose source page edited last week — one view, one action.
Pricing and merchandising
Products without explicit overrides for a target currency, surfaced as one filter. Bulk-set EUR or USD prices inline; auto-converted prices flip to merchant-chosen values.
Finance reconciliation
Orders by currency for the month with totals in both store base and customer currency. Reconcile EUR card settlements separately from USD without exporting the whole order list.
The bigger picture
Why row-level WCML ops beat per-product clicks
WCML solves the hard part well — keeping a multilingual WooCommerce store in sync across WPML's translation engine and WooCommerce's pricing layer. But its admin still treats each translation and each product as a destination. The default translation queue is useful for translators; it isn't useful for an ops lead deciding which translations to re-do this week, a finance team reconciling EUR settlements, or a merchandiser checking which products are still on auto-converted prices in a key target currency.
The data is in the database — translation status, last-modified timestamps, per-currency override flags, order currency — but it doesn't surface in the right shape on the right screen. SleekView turns the same data into the workspace each team needs: translation ops sees stale rows across all languages sorted by source-modified date, finance reconciles orders by currency for the month, merch finds products without explicit overrides in target currencies. Same WPML and WooCommerce APIs, same hooks — dramatically less clicking.
Questions
Common questions about SleekView for WooCommerce Multilingual & Multicurrency
Yes. WPML stores element-translation rows in icl_translations with stable schemas across recent versions. SleekView queries that table and joins on the source-element id so you can see source content alongside translation status, language, and last-modified date in one view.
Yes. WCML stores currency overrides in product meta keys per target currency. SleekView lists those meta keys and exposes them as columns — set/unset/auto state — so a view of "products without explicit EUR price" is one filter away.
 Yes. SleekView routes translation-status changes and re-translation triggers through WPML's API, so the same job-queue and editor hooks fire as if a translator had used the WCML translation editor. Currency override changes write through WooCommerce CRUD where supported, so price-update hooks run.
 
Each table is one view, but views are switchable inside a single SleekView page. Build a tabbed setup with one tab per source — Translations from icl_translations, Currency overrides from product meta, Orders from wc_orders. Or use a kanban view grouped by language alongside the table.
Yes. WPML records the source-modified timestamp on each translation row. SleekView exposes "source modified after translation" as a derived column or filter. A view of "German translations stale by more than 7 days" is one saved view away — exactly the queue translation-ops needs to drive their daily list.
 No — it's an additional admin surface. WCML's translation editor, language switcher, and pricing screens stay where they are for translators and merchandisers who use them. SleekView gives ops, finance, and merch teams the row-level views they actually need.
 
Queries hit indexed columns on icl_translations (element_id, language_code, trid) and the joined product tables. Filters and sorts use those indexes; pagination is keyset where possible. Aggregate columns (translation freshness counts) are opt-in per view since they're heavier.
Yes. WCML records the order currency on the WooCommerce order and the conversion to store base. SleekView surfaces both as columns, so a view of "This month's orders in EUR with both EUR total and base-currency total" is straightforward — useful for monthly close and gateway reconciliation.
 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