WCFM Vendor Verification adds a KYC layer to vendor onboarding: ID documents, address proof, and tax records get uploaded to the vendor account and reviewed by marketplace operators. Documents and review state are stored in wp_usermeta on the vendor user (typically under wcfm_vendor_verification_* keys) plus uploaded attachments in wp_posts.

SleekView reads vendor verification state as a real KYC queue. Rows show vendor, submitted date, document types provided, reviewer notes, and status (pending, approved, rejected, more-info). Sort by submitted age, filter for pending in the last 24 hours, scope to a specific document type, or surface vendors stuck in 'more-info' for over a week. Each row links to the uploaded documents for inline review.

Status changes write through WCFM Verification's API where exposed, so vendor notifications, vendor approval state (which gates the rest of WCFM Marketplace), and the audit log all update together. Bulk approvals or rejections process selected vendors in sequence with the same hooks running per row.

Marketplace KYC scales worse than almost any other workflow. Vendor sign-ups arrive in bursts, the documents need real human review, regulatory deadlines for response are short, and a backlog turns into churn because vendors abandon the onboarding if the verification step takes too long. WCFM Vendor Verification gets the data layer right: documents are attachments, status is structured meta, reviewer assignment is a field.

The default admin then exposes that data per-vendor, which means the compliance team's day-to-day work happens by jumping into individual vendor profiles. That works for a marketplace processing five verifications a week and breaks at fifty a week. SleekView turns the same data into a real KYC queue with aging, reviewer load, document filters, and bulk operations.

The compliance team picks up work from a saved view, clears the easy approvals in batch, and isolates the tricky ones with the right context already attached. The data does not change and the plugin still owns every write. The workflow change shows up immediately in onboarding throughput, which is the only metric that matters when verification is the gating step between sign-up and revenue.