Aelia CurrencySwitcher writes the customer currency into WooCommerce order meta like _order_currency and the conversion rate into _base_currency_exchange_rate, then stores the converted totals in _order_total_base_currency. The order admin still uses the regular WooCommerce list with post_status values like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded. A multi-currency store ends up with one long table where you cannot tell at a glance which currency a row belongs to or how many orders sit at each stage today.

SleekView Kanban reads the same orders through the WooCommerce REST endpoints, pulls the Aelia currency meta with each row, and turns the status column into the natural grouping axis for a board. Each card shows the customer name, the original currency total, the converted base total, and the payment method. Columns mirror your actual order statuses, so a glance at the board tells you how many orders are waiting on payment, how many are being processed in each currency, and how many have shipped.

Drag a card from Processing to Completed and SleekView writes through the WooCommerce APIs that Aelia listens on. Currency conversion meta stays intact, the original currency receipt still sends, and any Aelia reports still see the order with its original currency context. Refund drags trigger the standard WooCommerce refund flow with the converted amounts preserved.

A multi-currency WooCommerce store has two layers of state on every order: the operational status that decides what staff need to do next, and the currency that decides what the customer actually paid. The default WooCommerce admin gives you the status as a small column you can filter on and hides the currency behind the order detail page, which means a CS rep handling a EUR order and a USD order back to back has to click into each one just to remember what currency they are working in. The board view fixes both layers at once.

Status is the primary axis, so the work that needs doing today is visible without filters. Currency lives on the card itself, with the original amount and the converted base amount side by side, so the rep never has to ask. Drag updates the WooCommerce order through the same REST endpoints Aelia listens on, which means conversion meta is preserved, the receipt still ships in the original currency, and refunds run on the original amount.

The result is an operational view that respects how multi-currency stores actually run: status drives the workflow, currency informs the conversation.