Yes. SleekView reads whichever custom tables Dokan creates on your install. Lite tables are a subset of Pro tables — same schema, fewer of them. Pro adds modules like Stripe Connect, PayPal Marketplace, Live Search, and Vendor Verification, each writing to their own tables or postmeta. SleekView surfaces those columns automatically when the modules are active, without configuration.

Yes. Withdraw status is editable inline. SleekView writes through the Dokan API so notification hooks fire (the vendor gets emailed), balance hooks fire (their available balance updates correctly), and audit hooks fire (the action is logged). The bulk action selects multiple rows and updates them in sequence — useful for monthly payout cycles where you have dozens or hundreds of approvals to process at once.

Those modules write payment IDs and connection status into the Dokan tables (or related metadata). SleekView surfaces them as columns for reconciliation work — useful when you need to match a Dokan withdrawal record against a Stripe transfer or a PayPal disbursement. Filter for unconnected vendors to spot onboarding gaps where payment setup hasn't completed.

Yes. Reviews from the Vendor Review module are stored in WP — the schema depends on the module version, typically a custom table or postmeta. SleekView surfaces review average and review count as columns on the vendor view. Build a sub-view for individual review rows when you need to read specific feedback or moderate review content. Useful for spotting vendors with declining ratings before customer escalations.

Yes. Commission is per-order in dokan_orders as a numeric field. Aggregate per vendor for monthly or per-product breakdowns, or per-product for category analysis. A view scoped to last month with sum of commission per vendor doubles as a payout statement for vendors who request transparency on how the marketplace fee is calculated.

No. SleekView is admin-only — it doesn't touch the vendor-facing dashboard, the storefront pages, or the customer-facing order screens. Vendors keep using their frontend dashboard normally for their own data. Marketplace operators use SleekView to manage cross-vendor data on the admin side. The two are complementary and don't overlap or interfere.

Yes. Add a joined column counting refunds per vendor over a period, divided by orders in the same period. Vendors with high refund ratios surface for quality review or customer service intervention. Useful for catching quality issues before they cascade into mass disputes or marketplace reputation damage. The aggregate runs server-side so the view stays fast on large marketplaces.

Currency is stored per order in Dokan's tables. Build per-currency views for separate operations workflows, or aggregate by converted amount where currency conversion is recorded (typically by a third-party currency module). Useful for international marketplaces where finance reviews in the marketplace base currency but vendors transact in their local currency, and reconciliation needs both perspectives.