SleekView Kanban for WP-Property
SleekView reads the property post type WP-Property registers, joins in the structured fields the plugin stores per property type, and groups the board by property_status so agents move every listing through Active, Pending, Sold, and Off Market without touching the editor.
♾️ Lifetime License available
WP-Property is flexible, but the admin still hides the pipeline
WP-Property registers the property custom post type and lets administrators configure multiple property types (Single Family Home, Condo, Land, Commercial) each with their own field set. Status flows through property_status postmeta with values like active, pending, sold, off_market, and optional custom states added by the office. Address, price, bedrooms, bathrooms, square footage, and the listing agent are stored as postmeta keyed by the property type's configured field slugs.
SleekView reads the property post type from wp_posts, joins in the configured postmeta keys per property type, and groups the board by property_status. Each card shows the street address, list price, bedroom and bathroom count, and the assigned listing agent. A small badge in the corner shows the property type, so a mixed portfolio of homes and land does not become visually confusing on a single shared board.
Dragging a card from Active to Pending writes the property_status postmeta directly and fires the plugin's standard save_post_property hook so any third-party MLS sync, sitemap regenerator, or office Slack notifier runs. Sold and Off Market columns are configured one-way by default to prevent accidental reversion. A Reopen action on the card menu handles the rare contract-fell-through case with a reason prompt and a clean audit trail.
Workflow
From scattered postmeta to one working board
Pick the property post type as the source
Group by property_status
Configure the card face
Enable drag-and-drop
Sample board
Sample WP-Property brokerage board
Comparison
Default WP-Property admin versus a sales board
Default WP-Property admin
- Properties appear in a flat posts list with no awareness of sales stages
- Structured fields live in postmeta and never show on the listings screen
- Brokers have to filter and sort just to count Active or Pending properties
- Each status change requires opening the post and saving from the editor
- Custom statuses added through plugin settings have no visual representation in the admin
SleekView Kanban
- Reads the configured fields per property type so condos and land surface the right meta
- Card face shows address, price, beds/baths, and listing agent with property-type badge
-
Drag writes
property_statusand firessave_post_property - Sold and Off Market columns are one-way to prevent accidental reverts
- Filter bar supports property type, agent, city, and price range simultaneously
Features
What SleekView Kanban gives you for WP-Property
Property-aware cards
Each card adapts to the property type the listing belongs to. Homes show beds and baths. Land shows acreage. Commercial shows square footage and zoning. The single board can mix property types without losing the field clarity the office needs to triage each kind of listing.
Drag fires save_post hooks
Status changes write property_status through wp_update_post so save_post_property fires. That triggers MLS feed regeneration, sitemap updates, and any third-party integration listening for property changes. The board does not bypass any of the plugin's standard workflows; it just makes the trigger one drag instead of five clicks.
Closed transactions are safe
Sold and Off Market columns enforce write-once semantics by default. Once a deal closes, the card cannot accidentally drag back into Active. The Reopen card menu action exists for the contract-fell-through case, prompts for a reason, and writes a clear audit entry so the brokerage history stays accurate.
Audience
Three brokerage operations the board replaces
Weekly pipeline review
Brokers run weekly meetings from the board itself. Pending counts drive contract conversations. Active counts drive marketing discussions. Sold totals drive commission talks. The board replaces a spreadsheet that always lagged behind reality with a live, shared view the whole office reads from.
Field updates from listing agents
Agents update statuses from their phone or tablet during showings. A drag from Active to Pending the moment a contract is signed fires the MLS sync and notifies the transaction coordinator without anyone opening the WordPress editor, the MLS web app, or a separate brokerage workflow tool.
Days-on-market triage
Sort the Active column by days-on-market and the longest-standing listings rise to the top. The broker has a focused conversation with the listing agent about price reductions or marketing refreshes, backed by the same data the MLS shows, without ever leaving the WordPress admin.
The bigger picture
Why every brokerage outgrows the standard property admin
WP-Property has been a staple of WordPress real estate sites for over a decade because it ships a property schema flexible enough to handle homes, condos, land, and commercial listings with their own field sets. That flexibility is exactly what makes the default admin screen inadequate at scale. The screen is the standard WordPress posts table, which means brokers cannot answer the most basic pipeline questions without filtering, sorting, and clicking into individual records.
How many Active listings does the office have? How long has each Pending deal been waiting on contracts? Which listings are over the days-on-market target? All three questions take less than a second on a kanban board and ten minutes on the default screen. The drag actions write through the plugin's standard hooks, so MLS feed exports, the internal search index, and any third-party integration continue working without any custom code. The data stays in the property postmeta the plugin already owns.
The only thing that changes is how brokers and agents see and update the pipeline, and that single change is the difference between WordPress being part of the brokerage workflow and being a static website that nobody touches between marketing photos.
Questions
Common questions about SleekView Kanban for WP-Property
Yes. The plugin lets administrators configure multiple property types (Single Family Home, Condo, Land, Commercial) each with their own field set. SleekView reads the configured schema per type and adapts the card display so each property surfaces its relevant fields. A mixed portfolio with homes, land, and commercial listings runs on the same board without losing field clarity per type.
SleekView reads the property_status postmeta from every listing and builds one column per distinct value. The plugin's default statuses (Active, Pending, Sold, Off Market) appear out of the box, and any custom status the office added through WP-Property settings shows up automatically the next time a card with that status loads onto the board.
Yes. Drag actions write property_status through wp_update_post and fire save_post_property. Whatever MLS sync the office has configured (MLS RETS, RESO Web API, or a custom feed) runs on its next scheduled cycle and picks up the updated status without any manual feed regeneration or extra integration work.
Yes. WP-Property stores the assigned agent in postmeta (typically property_agent or a custom field configured in settings), and SleekView lets you filter the board by that field. Agents open the board pinned to their own listings, brokers see the full portfolio, and the same filter persists per user. Combined with capability checks, agents cannot edit unassigned listings.
The Sold column is write-protected by default, so a direct drag is blocked. The Reopen card menu action prompts for a reason (contract fell through, finance fell over), writes the reason into the property's history postmeta, and then moves the card back to Active. The MLS feed regenerates on its next cycle so external portals reflect the change.
Yes. Days-on-market comes from the listing date postmeta and shows as a corner badge with a warning color past the office target. The property type badge sits in the opposite corner. You can show up to two corner badges per card without crowding the address, price, and beds/baths line that the board uses to identify listings.
Yes. SleekView honors the same edit_property and edit_published_propertys capabilities the plugin uses. Agents without permission see the cards but the drag handle is disabled, and write-protected columns (Sold and Off Market) enforce extra capability checks. The board mirrors the access rules the office already configures on the standard WordPress admin.
Yes. SleekView paginates each column independently and lazy-loads as you scroll, so a brokerage with five thousand active and historic listings renders the visible board in well under a second. The database query is a single indexed lookup against wp_posts and the postmeta join, and Sold and Off Market are collapsed by default to keep the active board fast.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout