Five Star Restaurant Menu registers two custom post types: fdm-menu for whole menus and fdm-menu-item for individual dishes. Items are organized by the fdm-menu-section taxonomy (appetizers, mains, desserts, drinks). Each item carries postmeta including fdm_item_price, plus optional nutrition fields like fdm_item_calories, custom fields configured via fdm_menu_item_custom_fields, and image attachments. The admin shows you the list. It does not show you the mix.

SleekView reads wp_posts rows where post_type = 'fdm-menu-item', joined to wp_term_relationships for the fdm-menu-section taxonomy and to wp_postmeta for fdm_item_price. Group by section term for items-per-section. Bucket fdm_item_price for price-band distribution. Group by parent fdm-menu post for items per menu. Filter by section to focus on, say, just the wine list.

One restaurant group with 14 locations ran SleekView once and discovered their wine list had 71 entries with prices clustered between 30 and 80 dollars while the food menu only had 8 entries above 30 dollars. Once they saw the mix in one chart they rebalanced their food side toward higher-margin items. The fdm_item_price data was always there. They had just never charted it.

Menu engineering is a real discipline: balance items across sections, manage price bands, lead diners toward higher-margin options. Five Star Restaurant Menu captures the raw inputs cleanly in fdm-menu-item posts, fdm-menu-section terms, and fdm_item_price postmeta. Without aggregation it sits idle.

SleekView Charts turns that data into the dashboards a restaurant owner or menu engineer actually uses: items per section, price-band distribution, average price per section, cross-menu comparison for restaurants running lunch and dinner side by side. The visibility shows where menus are heavy, where they're thin, and where the price ladder breaks. None of it requires new data collection.

The plugin already writes everything. SleekView just turns it into the views menus get planned from.