Aelia Tax Display by Country for WooCommerce controls how prices are displayed across the storefront based on the customer's detected country, switching between tax-inclusive and tax-exclusive display per country. Configuration lives in the wp_options table under wc_aelia_tax_display_by_country as serialized data. Each rule carries a country_code, a display_mode (inclusive or exclusive), a tax_rate, a source flag for manual or auto, an enabled flag, and a last_updated timestamp.

SleekView Kanban reads the same Aelia tax display rules through the plugin's filters and helper functions. Pick a derived status combining the enabled flag and the source as the group column and every country rule becomes a card slotted under Active, Disabled, Manual, or Auto. Card fronts show the country code, the display mode, the tax rate, the source flag, the date last updated, and the product category scope if any, so finance sees every country tax display rule's state at a glance for the audit cycle.

Dragging a card between columns calls the Aelia helper for updating tax display configuration, which writes the new state back to wp_options and refreshes the storefront price display engine. Product prices show the correct tax-inclusive or tax-exclusive amount per country on the next storefront request, and any extension subscribed to the Aelia tax filters reacts, exactly as it would after a manual update from the Aelia admin screen by a finance manager.

Storefronts running Aelia Tax Display by Country show prices differently per country to comply with local tax display regulations. EU countries typically require tax-inclusive display. The US typically uses tax-exclusive display.

Switzerland, Norway, and the UK have their own rules. Some countries sit quietly on automatic tax display feeds from the plugin. Some have manual overrides for transitional or special situations.

A small number are disabled because finance is investigating a compliance issue. The default Aelia admin treats them all the same form and offers no visual distinction between auto, manual, and disabled tax display rules. The disconnect between what finance needs to monitor for compliance and what the admin offers shows up in the worst places.

A manual tax display rule set during a transitional regulatory period stays in place for months after the transition ended because nobody flipped it back to auto. A disabled country mysteriously reactivates after an unrelated config save and starts displaying incorrectly. A new country gets added but never enabled.

A kanban view that reads and writes the same Aelia tax display option the storefront price engine reads keeps the team and the tax compliance honest. Every drag is a real config change, every column count reflects the real tax display state, and the cards themselves carry enough context for a new tax analyst to handle quarterly tax display audits on day one without Aelia training first.