WPML's data is split across multiple tables: icl_translations holds language relationships per content row, icl_strings registers theme and plugin strings, icl_string_translations stores the actual translated values, and the Translation Management add-on adds icl_translation_status and icl_translate_job for queue and translator state. The plugin's analytics tab summarizes some of this, but the cross-table picture (which products are missing one of five languages, which translator queue is backing up) reads better as a dashboard.

SleekView Charts reads those tables and renders a localisation-manager view. A Number counts products missing at least one language. A pie segments translation status across the catalog (complete, partial, in queue). A bar lists translators by open jobs so the bottleneck is visible. A time-series tracks completed jobs per day to evaluate throughput.

Translation sends still go through the WPML queue API. SleekView is the read-side dashboard that makes the daily coverage and queue picture available without flipping tabs.

A storefront with five languages can look complete on the surface and still have hundreds of products missing one language each in the long tail. WPML stores the data to detect that, but the native UI scopes it per content type. Charting icl_translations and icl_translate_job together turns the long-tail coverage problem into a single KPI plus a status donut.

The localisation team gets to spend time on translation work, not on building reports.