SleekView Charts for Pods
Read directly from Pods custom database tables for Advanced Content Types and from postmeta for standard Pods, then chart inventory levels, status mix, and trends without a Pods Template or Pods Views build.
♾️ Lifetime License available
Pods stores the rows, charts give them a reporting view
Pods is the rare content-modeling plugin that puts Advanced Content Types in their own custom database tables instead of postmeta, which is what makes them fast at hundreds of thousands of rows. Standard Pods custom post types still use postmeta, relationships can be meta-based or table-based, and bidirectional sync writes both sides. The default Pods admin shows basic columns and leaves richer summarisation to Pods Templates or custom code.
SleekView Charts reads both storage paths. ACT rows are queried directly from their custom tables for speed, postmeta-backed Pods read through the standard meta layer, and relationship counts resolve through Pods' own API. A Number card pins total stock across an ACT. A Pie shows status mix across a catalog. A Bar ranks suppliers by inventory value. An Area card plots additions per day so catalog growth is a curve, not a stat someone exports.
Both meta-based and table-based storage coexist on the same dashboard, and Pods Pro features that affect storage or validation continue to apply because SleekView reads the same Pods data layer it always has. Saved chart views per role let ops, editorial, and support each get the cards that match their workflow.
Workflow
How SleekView Charts reads Pods data
Pick a Pod
Build the chart cards
Filter on the right path
Save per role
Sample dashboard
Charts you can build from Pods data
Active catalog records
Count
Stock status mix
Count
group by stock_status
Inventory value per supplier
Sum(stock_value)
group by supplier_relationship
Records added per day
Count
group by created_at
Comparison
Default Pods reporting vs SleekView Charts
Default Pods admin
- Pods has no admin chart view, only paginated record lists
- Advanced Content Type rows sit outside WP_Query so list filters are limited
- Bulk summarisation of custom fields needs Pods Templates or custom queries
- Relationship counts across Pods don't appear in any default summary
- No simple way to share a curated chart dashboard with non-admins
SleekView Charts
- Number cards for live record counts across Pods and ACTs
- Pie or Donut cards for status, category, or select-field distributions
- Bar cards ranking related Pods using bidirectional relationships
- Area or Line cards for catalog growth over time
- Same filters as the SleekView table apply to every chart card
Features
What SleekView Charts gives you for Pods
ACT tables as chart sources
Advanced Content Types stay fast because the chart layer queries the dedicated Pods custom tables directly. No WP_Query overhead, no postmeta join, just the indexed columns Pods already built.
Relationships in charts
Bidirectional relationships power Bar cards that count related Pods per anchor. Books per author, parts per supplier, sessions per event all become single-card summaries through Pods' own API.
Mixed storage on one dashboard
Meta-based and table-based fields coexist on the same chart view because SleekView reads the storage path per field from the Pods registry, not from a hardcoded assumption.
Audience
Who builds Pods charts dashboards with SleekView
Product catalog sites
Stock value per category, low-stock counts, and daily catalog additions on one dashboard, driven directly from ACT custom tables for speed.
WordPress developers
Manage rich Pods models without writing one-off admin reporting pages. SleekView reads the registry, so a new field appears in the chart picker on the next open.
Editorial teams
Browse content health by status, related Pod, or category. Saved chart views per role keep editors focused on their slice without exposing the full Pods admin.
The bigger picture
Why Pods catalogs deserve a chart dashboard
Pods made an early bet that not every content model belongs in postmeta, and Advanced Content Types remain one of the few honest ways to run a hundred-thousand-row catalog inside WordPress without dragging WP_Query down. The downside has always been the admin and reporting story. ACTs sit outside WP_Query, and bulk summarisation tends to fall back to Pods Templates, custom shortcodes, or one-off SQL.
Teams running serious catalogs end up either exporting CSVs to spreadsheets or building dashboard pages with widgets that drift out of sync with the data. SleekView Charts closes that gap. The same ACT custom tables that give Pods its performance edge now back Number, Pie, Bar, and Area cards that aggregate live, without writing a List Table or moving rows back into postmeta.
Standard Pods, ACTs, and Pods relationships share the same chart UI; Pods Pro features keep applying on edits made through the SleekView table. The performance benefits stay where Pods put them, and the admin finally has the summary surface the model deserves.
Questions
Common questions about SleekView Charts for Pods
Yes. ACTs are a first-class chart source. Their custom database tables are queried directly through Pods' API, which is faster than postmeta-based reads at scale. The standard list filters that don't work on ACTs in the WordPress admin do work in the SleekView chart layer because the queries don't go through WP_Query.
Yes. Bidirectional and many-to-many relationships resolve through Pods' API, so a Bar card grouped by related Pod counts related items per anchor. Books per author, parts per supplier, sessions per event are all single-card summaries with no manual join.
Yes. Pods' table storage option for fields is supported alongside the standard meta-based storage, and a Pod that mixes both renders on the same chart dashboard. SleekView detects the storage path per field from the Pods registry, so reads land on the right table automatically.
Chart queries are read-only, so validation and pods_api hooks aren't involved at the dashboard layer. When you click through to the SleekView table to edit a record, writes go through Pods' update functions exactly as they would from a Pods form, so field validation and pods_api hooks still fire on the edit path.
Yes. Any chart card exports its aggregated source data to CSV, with active filters and group-bys respected. Useful for handing finance a monthly inventory report, or feeding catalog summary numbers into an external tool that doesn't have a Pods integration.
Yes. SleekView coexists with Pods Pro because it reads the same Pods data layer. There is no overlap in functionality at the chart level; Pods Pro features that affect storage, validation, or relationships continue to apply on every write made through the SleekView table.
Yes. Pods supports both single-site and multisite, and the SleekView chart layer respects the active scope. Per-subsite Pods register on the active blog and surface only there, while Pods configured at the network level become chart sources wherever they're active.
No. Pods' own admin lists and edit forms stay where they are. SleekView Charts adds a reporting surface on top of the data Pods already collects, so the plugin keeps owning the data model and the dashboard owns the summary.
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