Business Directory Plugin Premium stores every business as a wpbdp_listing custom post type with meta keys for category, region, paid plan, expiration date, and a listing status that swings between incomplete, pending payment, complete and pending review, complete, and expired. The default Business Directory admin shows those listings in the standard WordPress post table, which works for browsing but offers no visual signal for status or paid plan.

SleekView Kanban points at the same wpbdp_listing post type and groups every listing by the BD specific status meta or any enum-shaped column you pick. Use the listing status to see Incomplete, Pending, Complete, and Expired lanes side by side. Each card shows the business name, the category, the city, the paid plan, and the days until expiration so a moderator can scan the pipeline and act on each listing at a glance.

Dragging a card between columns writes the new state back to the listing through the WordPress REST API. The Business Directory front end stays in sync, the directory archive and any search facets reflect the new state on the next page load, and the moderator queue lives in one obvious board view instead of buried inside the standard WordPress post list every time.

Business Directory Plugin Premium is excellent at giving a directory site the listing schema, the paid plan tiers, and the front end submission flow that make running a business directory possible. The trade off is the admin experience for moderators. The default Business Directory admin lists every business in the standard WordPress post table, which works for a small directory but turns into a wall of rows the moment a marketing push drives a wave of new submissions.

Moderators sort by date, click into each listing to flip the status, then bounce back to scroll some more. State is implicit. The difference between a listing that is pending review and one sitting because a moderator has not gotten to it lives only in their head, or in a brittle external spreadsheet that drifts.

SleekView Kanban fixes this by treating the wpbdp_listing posts as a board. Every listing is a card, every status value is a column, and dragging a card writes the new state back to the post. The front end stays in sync, the archive reflects the new state, and the moderator queue lives in one obvious place.