✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WooCommerce Multilingual & Multicurrency

WooCommerce Multilingual & Multicurrency (WPML) stores every product translation as a row in wp_icl_translations with state, source, and destination. SleekView Kanban reads that data, groups product translations by status, and lets the team drag a published card back to untranslated w

♾️ Lifetime License available

SleekView Kanban board for WooCommerce Multilingual & Multicurrency (WPML)

Why WCML product translations fit a kanban view

WooCommerce Multilingual & Multicurrency (WPML) keeps every product translation as a row in wp_icl_translations with the state, source, destination, and runtime stored alongside the slot. Related metadata lives in wp_woocommerce_log. The default admin screen shows that data as a flat list sorted by date, fine for record lookup but slow when an overnight product translation has stalled and a store localisation lead needs to see whether it is untranslated, in progress, or has moved to published state.

SleekView Kanban renders the same records as four columns: Untranslated, In progress, Reviewed, and Published. Each card surfaces the product translation label, the destination handle, and the runtime. When a published product translation needs another attempt, the team drags the card back into untranslated and WooCommerce Multilingual & Multicurrency (WPML) picks it up on the next pass. No second list, no retry through a settings screen.

The team can filter the board by destination, schedule, or scope, then save that view as a board for one site or one client. The kanban reads from live records, so retrying a card triggers the same code path as the standard run button, with the same hooks firing for notifications.

Workflow

From the default WCML list to a live board

1

Connect WCML as the source

Pick WooCommerce Multilingual & Multicurrency (WPML) from the SleekView data source picker. It auto-detects the wp_icl_translations store and the wp_woocommerce_log metadata so the board reads
2

Group cards by the status field

Select the status field as the kanban column. SleekView reads every distinct value, surfaces Untranslated, In progress, Reviewed, Published, and lets the team rename, reorder, hide, or recolor each column without
3

Pick the card front fields

Choose the product translation label, the destination handle, and the runtime as the card front. Add a secondary line for schedule and log line. The card editor previews real product translation data so the team
4

Enable drag-and-drop writeback

Turn writeback on and dragging a card writes the new status back to the WooCommerce Multilingual & Multicurrency (WPML) record via the WordPress REST API. Capability checks honor the existing admin role, and every move

Sample board

Sample WCML board grouped by status

Four real status columns showing how a store localisation lead moves WCML product translations across Untranslated, In progress, Reviewed, and Published during a single working session.
Untranslated
62
Product Coffee Premium untranslated FR
Variants 4, attributes 12
Product Espresso Beans untranslated ES
Variants 3, attributes 8
Product Cold Brew untranslated for DE
Variants 2, attributes 6
In progress
14
Translating Coffee Premium for French
Translator Marie, 60 percent
Translating Espresso Beans for Spanish
Translator Diego, 50 percent
Translating Cold Brew for German now
Translator Anna, 80 percent
Reviewed
10
Coffee Premium French ready for review
Reviewer Sophie, awaiting
Espresso Beans Spanish ready review
Reviewer Carmen, awaiting
Cold Brew German ready for review
Reviewer Klaus, awaiting
Published
1480
Coffee Premium French live with prices
Published May 14, EUR price
Espresso Beans Spanish live with prices
Published May 18, EUR price
Cold Brew German live with EUR prices
Published May 22, EUR price

Comparison

Default WCML screen vs SleekView Kanban

Default WCML dashboard

  • Default screen is a flat sortable list hiding product translation status behind a small
  • Updating a product translation status takes three clicks and a full page reload every time
  • No live counts per state, so workload across product translations stays hidden from the
  • Bulk actions cover delete and trash but never bulk status moves across many rows
  • Filtering by destination resets when navigating between pages of product translations li

SleekView Kanban

  • Drag a card from published to untranslated and the status writes ba
  • Column counts update live so the store lead sees workload without filtering or scrolling
  • Save filtered boards as URLs, one per destination, schedule, or scope across the site
  • Card front maps to the product translation label, destination handle, runtime, and last log l
  • Permissions inherit from WooCommerce Multilingual & Multicurrency (WPML) roles, no second aut

Features

What SleekView Kanban gives you for WooCommerce Multilingual & Multicurrency (WPML)

Status columns you can rename

WooCommerce Multilingual & Multicurrency (WPML) ships with Untranslated, In progress, Reviewed, Published as the four core states. Rename them to match the runbook, reorder them to match the flow, and recolor each column so the

Drag to publish not re-trigger

Every card move writes back to the same status field that WooCommerce Multilingual & Multicurrency (WPML) already reads, so retried product translations run through the same pipeline as fresh ones. No second queue, no shadow

Filter by destination or scope

Add a secondary filter on the destination handle, the scope, or the schedule slot and SleekView narrows the board to that subset. Ops sees the full board, the store lead sees one destination, and the manager keeps the high-level

Audience

Where store leads use the WCML kanban first

Morning language triage

Open the board at 9am, scan the published column for overnight issues, drag failed product translations back into untranslated, and watch the in progress column drain as the next pass processes the

Pre-release language checkpoint

Before a release, fire a manual product translation card, watch it move from untranslated to in progress to reviewed, then promote the deploy. If the product translation fails, the card stays in

Multi-site capacity view

Filter the board to one client site at a time and watch the in progress column count as a live capacity gauge. If running stays full while untranslated grows, stagger schedules before the queue

The bigger picture

Why a kanban beats the default WCML screen

WooCommerce Multilingual & Multicurrency (WPML) is a great language engine. The records hold the state, the destination map holds the targets, and the schedule slot holds the timing. What it does not give the team is a daily operating picture of which product translations are healthy and which are not.

The default screen is a record list, designed to inspect a single product translation, not to triage a column of published product translations at once. The store localisation lead ends up keeping a separate sticky note of failed runs or wiring a notification plugin just to know which product translation died overnight while the team slept. A kanban changes the shape of the work.

Instead of asking which product translations need attention today, the team sees the answer as soon as the page loads, because every published product translation is in the published column and every in progress one is in the in progress column. Moving a card writes the new status back to the record, so the picture stays accurate.

Questions

Common questions about SleekView Kanban for WooCommerce Multilingual & Multicurrency (WPML)

No. The board reads from the same wp_icl_translations store that the plugin already uses. When the team drags a card, SleekView writes the new status back to that store, so there is only one source of truth for every product translation on the site and every WooCommerce Multilingual & Multicurrency (WPML) hook still

 

Yes. The column titles are display labels, not the underlying status values. Rename untranslated to waiting, published to broken, or anything else that matches how the team writes incident notes. SleekView stores the rename separately so the data still uses the standard WooCommerce Multilingual & Multicurrency (WPML) values.

 

SleekView Kanban inherits the WooCommerce Multilingual & Multicurrency (WPML) capability map. If a user can run a product translation or view the admin screen, they can drag the matching card on the board. If they only have view rights, the board renders in read-only mode and the drag handles stay hidden from each card.

 

Yes. Add a filter on the destination handle or the schedule slot, then save the filtered view as a named board. Each board gets its own URL so one destination board lives next to another, and a single board can stay open on a status monitor without losing the rest.

 

The kanban polls the WooCommerce Multilingual & Multicurrency (WPML) record store at a configurable interval, with two minutes as the default. New reviewed and published entries appear in the matching column within that window. Existing cards refresh in place so dragging a card never loses its position when a sibling updates.

 

Yes. SleekView reads every distinct value in the status field, including the extra states that add-ons register for cloud destinations and remote stores. The team chooses which of those columns to show on the board and hides the rest without removing the underlying data.

 

Yes. The card editor lets the team pick any field stored on the product translation record, including the destination handle, the runtime, and the last log line. A common layout shows the product translation label, destination, and runtime on the front, with the log line visible on hover for the engineer.

 

Yes. The plugins do not conflict because SleekView only reads and writes the same records that WooCommerce Multilingual & Multicurrency (WPML) already manages. Many teams use the admin screen for one-time setup and configuration, and the kanban for daily triage and retries from across the whole site at once.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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