SleekView for WPML WooCommerce Multilingual: translations & currencies as tables
WPML stores translations across icl_translations, icl_strings, and icl_string_translations. SleekView joins them so missing-language audits, translator queues, and per-product coverage live on one screen instead of buried in WPML's analytics tab.
♾️ Lifetime License available
Translation status without per-post clicks
WPML's data model is split across three tables: icl_translations tracks language relationships per content row (post, taxonomy, package), icl_strings registers translatable strings from the theme and plugins, and icl_string_translations stores the actual translated values per language. The Translation Management add-on adds icl_translation_status and icl_translate_job for queue and translator state.
SleekView queries them directly as a single workspace. A products view pivots each language as its own Yes/No/Pending column drawn from icl_translations grouped by trid, so a five-language catalog renders as five status columns next to product title and SKU. A queue view joins icl_translate_job to surface translator, language pair, and job status — so localisation managers stop opening WPML's analytics tab to triage daily work.
That layout closes the gap WPML's per-post-type screens leave open: a single product missing one language out of five is invisible at the storefront level, but it becomes a filterable row in SleekView. Bulk-send to translators happens through WPML's queue API, so the existing job pipeline keeps working unchanged.
Workflow
Translation status as a real coverage report
Join icl_translations
Layer string translations
Surface the queue
Save coverage presets
Sample columns
A typical translation status view
wp_icl_translations + wp_icl_strings + wp_icl_string_translations
| Product | EN | DE | FR | ES | Status |
|---|---|---|---|---|---|
| Studio Desk | Yes | Yes | Yes | Yes | Complete |
| Office Chair | Yes | Yes | Yes | — | Partial |
| Acoustic Panel | Yes | Yes | Pending | — | In progress |
| Lamp Pro | Yes | — | — | — | Missing |
Comparison
Default WPML admin vs SleekView
Default WPML admin
- Translation status is shown per post-type screen, not as a unified table
- Cross-language coverage reports require the analytics tab
- Filtering by missing-language across thousands of products is slow
- Bulk-send to translators is built-in but not joined with content fields
- String-translation status isn't pivoted alongside content translation
SleekView
-
Pivot
icl_translationsper language into columns - Show translation coverage per row (Yes/No/Pending)
- Filter to missing-language rows for assignment
-
Join
icl_string_translationsfor theme/plugin string status - Save views per language manager or translator
Features
What SleekView gives you for WooCommerce Multilingual & Multicurrency (WPML)
Per-language coverage
Pivot each language as its own Yes/No/Pending column on the products view. Filter to rows missing a specific language to assign work the same day a gap appears.
Strings and content together
Join icl_strings with icl_string_translations for storefront-string coverage alongside content coverage. Catches checkout-label gaps before they hurt conversion.
Translation queue triage
Filter icl_translate_job to in-progress or needs-update rows. Sort by translator and age to load-balance daily without opening WPML's analytics tab.
Audience
Who uses SleekView for WPML
Localisation managers
Cross-language coverage views to plan translation sprints. Save daily presets filtered to priority-market gaps and assign through the WPML queue inline.
Translators
Per-language assignment views with content and string status side by side, plus job age. Pick up the oldest in-progress jobs first without queue-tab roulette.
Growth marketers
Find product gaps in priority markets at a glance — Spanish or Italian holes in the catalog become a single filter, not an analytics-tab discovery.
The bigger picture
Why translation coverage needs a single screen
Multilingual catalogs decay quietly. A new product gets added, the German translation is published the same day, French goes live a week later, Spanish slips through a busy sprint and never lands. The storefront in each language looks fine because WPML hides untranslated content.
The product simply does not appear in the Spanish catalog. Conversion teams notice the gap weeks later when a campaign that targets Spain underperforms. WPML's per-post-type screens make that invisible until someone runs analytics.
A pivoted view of icl_translations exposes the gap as a filterable column the same day the product is published. The same logic applies to storefront strings: a checkout label translated for German and French but missed in Spanish breaks trust in subtle ways that A/B tests cannot easily detect. Coverage reports work when they are queryable in the database, not buried behind a per-content-type list.
SleekView turns icl_translations into the working layer it needed to be for catalogs at scale.
Questions
Common questions about SleekView for WooCommerce Multilingual & Multicurrency (WPML)
Yes. Currency mappings stored in WPML's options are exposed as a separate view with per-product price overrides where defined. Multicurrency configuration lives in serialized options that the agent parses into named columns, so default and override prices both become sortable per currency.
Yes. SleekView calls WPML's translation-queue API on row actions where supported, so jobs are created with the right language pair and source content reference. The existing translator assignment rules continue to apply, and the action is capability-gated to localisation managers.
Yes. The icl_translation_status and icl_translate_job tables are exposed as additional joinable views — translator, language pair, status, deadline, and word count all become columns. That makes them filterable in ways the Translation Management dashboard does not.
Yes. Both fields are columns on the jobs view, filterable and sortable. Combine translator with status to see one translator's open queue, or pivot status across translators to spot bottlenecks where one translator is sitting on too many in-progress jobs.
Yes. Queries are paginated and indexed; sites with hundreds of thousands of translation rows render fine. icl_translations has trid and language_code indexes that the views take advantage of, so even five-language catalogs with twenty thousand products stay responsive.
Yes. Views are gated by capability and saveable per role, so a German manager sees only German queues and German coverage gaps, while a head of localisation sees everything. Saved presets travel per role too, so each team keeps its own daily filters.
Yes. WPML registers attachments in icl_translations the same way as other content. A media view pivots languages the same way a product view does, so caption and alt-text translation coverage becomes auditable per attachment.
WPML's translation memory lives in its own tables when the relevant add-on is enabled. SleekView can read those tables directly so translators can audit memory hits and identify gaps where a phrase should be reused but is being retranslated each time.
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