WpResidence uses the estate_property CPT in wp_posts as its listings model. The fields brokers triage on, property_price, property_bedrooms, property_bathrooms, property_size, property_status, property_address, and property_agent, all live in wp_postmeta. The default WordPress posts list cannot show postmeta columns, so the admin defaults to title and date.

SleekView reads the estate_property CPT, joins postmeta at query time, and exposes each meta key as a first-class column. WpResidence taxonomies (property_category, property_status, property_city, property_county_state) attach as filterable columns, so a saved view of active 3-bed homes in a given city becomes one stored slice.

Edits route through wp_update_post and update_post_meta, so the price-change emails, agent assignment hooks, and status filters WpResidence registers still fire. Bulk price adjustments, status flips, and per-agent inventory views finally become a saved view rather than a per-row click.

WpResidence is one of the longest-running real estate WordPress themes, with a clean CPT-and-meta data model that holds up to thousands of listings. The problem is the admin in front of that model. The default WordPress posts list shows title, author, and date, none of which describe a property.

Brokers want to compare price, beds, status, and agent at a glance, and the only way the default admin allows that is by clicking into each record. SleekView's pivot rewrites that surface entirely. The same estate_property rows render as a real inventory table with named columns for everything stored in wp_postmeta.

Saved views replace the daily spreadsheet exports a broker office tends to accumulate, capability gating gives each agent their own desk without custom code, and inline edits route through WpResidence's own update path so syndication and notification hooks keep working unchanged. The data was always there; SleekView just makes it usable.