Aelia Currency Switcher for WooCommerce stores currency configuration in the wp_options table under the wc_aelia_currency_switcher serialized option. Each currency configuration carries a code (USD, EUR, JPY), a rate against the store base currency, a symbol position, a decimals setting, a rate_source flag for manual or auto, an enabled flag for storefront visibility, and a payment_gateway_mapping for which gateways accept each currency. The native Aelia admin shows the configuration in a flat form.

SleekView Kanban reads the same Aelia currency configuration through the plugin's filters and helper functions. Pick a derived status combining the enabled flag and the rate_source as the group column and every currency becomes a card slotted under Active, Disabled, Manual, or Auto. Card fronts show the currency code, the current rate against the base, the symbol position, the decimals, the rate_source, the date last updated, and the payment gateway mapping, so finance sees every currency's full state at a glance.

Dragging a card between columns calls the Aelia helper for updating currency configuration, which writes the new state back to wp_options and refreshes the storefront currency switcher widget. Product price displays recompute through Aelia's filters, cart totals update on the next storefront request, payment gateway availability recalculates, and any extension subscribed to the Aelia filters reacts, exactly as it would after a manual update from the Aelia admin screen.

Storefronts running Aelia Currency Switcher (often bundled by WinWar) support a dozen or more currencies across the global customer base. Some sit quietly on automatic exchange rate feeds. Some have manual overrides for high-volatility currencies where the auto rate would expose the store to too much risk on every order.

A small number are disabled because of sanctions or policy decisions, and the team needs to keep those disabled until policy changes. The default Aelia admin treats them all the same form and offers no visual distinction between auto, manual, and disabled. The disconnect between what finance needs to monitor and what the admin offers shows up in the worst places.

A manual rate set during a market spike stays in place for weeks after the market stabilizes because nobody flipped it back to auto. A disabled currency mysteriously reactivates after an unrelated config save in the Aelia admin. A new currency gets added but never enabled because the auto feed failed silently overnight.

A kanban view that reads and writes the same Aelia currency option the storefront switcher reads keeps the team and the price displays honest. Every drag is a real config change, every column count reflects the real currency state, and the cards themselves carry enough context for a new finance analyst to handle a weekly currency audit on day one without Aelia training first.