YITH Request a Quote captures every B2B inquiry as a yith_request_quote custom post with line items in postmeta and a status field that moves through new, processing, sent, accepted, rejected and expired. The default Quote Requests screen lists one row at a time, which is right for opening a single quote and wrong for running the pipeline as a queue.

SleekView reads the yith_request_quote posts joined to wp_postmeta and renders the inbox as a sortable, filterable table. Filter to new and processing only to triage the live pipeline. Sort by customer email to spot accounts with multiple open quotes. Group by request_status to see where the queue is stalling. The same data the chart view aggregates becomes a row-level surface sales reps can actually work from.

The plugin keeps owning the quote form, the PDF and the customer notifications. SleekView owns the pipeline surface, so the requests YITH already records stop hiding in a flat list and become something sales ops can query, sort and assign.

YITH Request a Quote captures the right event reliably, the gap is that the captured row only ever renders one at a time. Sales reps and sales leads work the pipeline by switching between an inbox view that lacks columns and spreadsheet exports that lack live status. SleekView reads the same yith_request_quote posts and renders them as a queryable table with status, customer, total and rep_id as first-class columns.

Filters stack into a single query so the active-pipeline view, the stale-quote audit and the per-rep queue become saved views rather than reconstructions. The plugin keeps owning the quote form, the PDF and the email notifications, while sales teams get the per-row surface the dataset always deserved.