Every Aelia Tax Display by Country store sits on a pile of accountant and shopper feedback that never gets organized. B2C shoppers in Germany expect VAT-inclusive prices on the product page. UK buyers want VAT shown separately at checkout. Wholesale buyers in the Netherlands need exclusive prices everywhere, with a clear reverse-charge note on the invoice. The signal is real, but it scatters across reviews, tickets, and accountant Slack messages.

SleekView Feedback reads any table or post type where those requests already live. Point it at a custom feedback CPT, a Gravity Forms entries table, or wp_comments filtered by a custom type. Map the numeric column you want as votes, the column that drives status pills, and the column that tags categories like Display, Inclusive, Exclusive, or B2B. SleekView renders a public board on top, no migration needed.

The result is one URL your country managers, accountants, and store owners can all point at. Tax display bugs get the same upvote treatment as B2B exemption asks. Inclusive-pricing edge cases sit next to wholesale reverse-charge wishes. You stop triaging the tax inbox one ticket at a time, because the board ranks demand by category with vote counts attached.

Aelia Tax Display by Country stores deal with the trickiest UX in ecommerce, where the price shown on a product page must shift between inclusive and exclusive based on shopper region, B2B versus B2C role, and the country-specific label that local buyers expect to see. A support inbox is the wrong place to track which display rules need fixing, because every report sits in isolation and no shopper can see that the same DE inclusive bug was already filed a month ago. Country managers triage tickets based on which client account escalated loudest, not where the actual demand concentrates.

A public board flips that. Every tax display ask gets one card, every shopper and accountant can upvote without opening a ticket, and the top of the board is the actual ranked demand by category and country. Status pills tell buyers when their B2B reverse-charge ask is Planned versus Shipped, which kills duplicate reporting.

Custom-label feature requests get a real Planned and Shipped state instead of dying in a Slack thread. The board becomes a shared signal between shoppers, accountants, country managers, and the dev team, all on the same WordPress install with the same login as the rest of the store.