Pick exactly what vendors see — and what they can’t.
Granular admin control over the Dokan Products page — without writing code. Show or hide columns, row actions, top filters, and individual add/edit fields. Lock required fields, rename labels, add helper-text hints, restrict allowed product types, and pick alternative add-product layouts. Field hiding is enforced server-side, not just by CSS — vendors can’t POST around it.
- Column visibility (image, SKU, stock, price…)
- Row-action visibility (edit, duplicate, delete…)
- Filter visibility (status tabs, type, search)
- Per-field show/hide on add/edit product
- Required-field lock — data-loss-safe
- Custom labels & helper-text per field
- Product type whitelist (simple, grouped…)
- Alt add-product layouts (Stepper, Cards, 2-col)
Six tabs of admin control over a vendor experience you used to fork the theme for.
Every setting is enforced both client-side (CSS / JS to hide UI) and server-side (filtered post-data on save). Works against both the classic Dokan dashboard and the new React/SPA dashboard.
Show / hide list columns
Per-column toggles for image, SKU, status, stock, price, type, date, and the columns added by Dokan Pro modules. Cleaner list view for vendors that don’t need everything.
Row-action visibility
Toggle Edit, View, Quick Edit, Delete, Duplicate, Translate independently. Removed actions disappear from the row hover menu and are blocked server-side.
Top-of-page filter visibility
Show or hide status tabs, date picker, category, brand, type, search box, “Add new product” and bulk actions — without writing CSS to override Dokan’s output.
Per-field add/edit toggles
Every field on the add/edit product page can be hidden. Server-side post-data stripping ensures hidden fields can’t be sneaked in via crafted POST requests.
Required-field lock
Mark a hidden field as required and we’ll lock it instead of hiding — preventing accidental data loss when vendors save updates.
Custom labels & helper text
Rename any field label and add a one-line helper hint shown directly under the label. Tailor the dashboard’s wording to your marketplace’s voice.
Product type whitelist
Decide which product types vendors can create: Simple, Grouped, External, Variable, Booking, Auction, Subscription. Hidden types vanish from both the picker and the filter.
Alternative add-product layouts
Switch the add-product form from Dokan’s default to a Stepper (guided), Card sections (visual), or Two-column (info-dense) layout.
Classic + SPA dashboard support
Detects whether the current request is the classic dashboard or the new React/SPA dashboard. Classic gets inline CSS + JS; SPA gets MutationObserver-based field hiding.
Per-tab reset to defaults
Each settings tab has its own Reset button — recover from a misconfiguration without losing settings in other tabs.
CSS builder, no hand-coding
The plugin generates the field-hide CSS rules itself, scoped to the vendor dashboard. You never touch a CSS file.
Licence-gated
Vendor-facing customisations short-circuit cleanly when the licence is inactive. Admin pages and the licence form stay reachable for self-service re-activation.
From tabbed settings page to a vendor-friendly Products screen.
Activate & licence
Upload, activate, paste your licence key. Defaults match Dokan’s out-of-the-box behaviour, so nothing changes until you tweak.
Configure across six tabs
General, Products List, Add/Edit Fields, Product Types, Labels & Helpers, Add-product Layout. Each setting takes seconds; per-tab Reset if you change your mind.
Vendors see the new shape
The Dokan Products dashboard reflects your settings on the next page load. No vendor onboarding needed — the UI is simply cleaner.
One plugin, every feature included.
Pick monthly or save with yearly — both unlock the full feature set. One subscription per production site. Cancel any time.
- Column / row-action / filter visibility toggles
- Per-field show / hide on add & edit product
- Required-field lock (server-side enforced)
- Custom labels & helper text per field
- Product type whitelist
- Alt add-product layouts (Stepper / Cards / 2-col)
- Classic + SPA dashboard support
- Continuous updates & email support
- 14-day refund window
- Column / row-action / filter visibility toggles
- Per-field show / hide on add & edit product
- Required-field lock (server-side enforced)
- Custom labels & helper text per field
- Product type whitelist
- Alt add-product layouts (Stepper / Cards / 2-col)
- Classic + SPA dashboard support
- Continuous updates & email support
- 14-day refund window
1 production site per licence · staging / dev / .local exempt · 14-day refund window · prices exclusive of tax
Architecture & integration.
Plugin name
Dokan Vendor Product Manager by ONVORE
Slug / text domain
dokan-vendor-product-manager-by-onvore
Requires
WordPress 6.2+, WooCommerce, Dokan Lite or Pro, PHP 7.4+
Enforcement
Server-side post-data stripping via dokan_insert_product_post_data; client-side CSS/JS for visual hiding; required-field lock prevents data loss.
Row actions
Hooked via dokan_product_row_actions filter. Hidden actions never reach the hover menu and are blocked at the controller layer.
Product types
Filtered via dokan_product_types. Hidden types disappear from both the type picker and the filter sidebar.
Dashboard detection
DashboardContext helper detects classic vs SPA dashboard; assets are enqueued conditionally based on the active mode.
Storage
All settings in a single option array. No custom tables. Per-tab reset rewrites only that section.
Licensing & updates
Daily validation via account.onvore.com with a 72-hour grace window. Auto-updates over the same channel.
Screenshots from the plugin.
A quick tour of the main screens. Live screenshots will replace these wireframe previews shortly.
The quick answers.
Can vendors bypass a hidden field by editing the HTML?
No. Field visibility is enforced both client-side (CSS hides the field container) and server-side (post-data is stripped on save via Dokan’s dokan_insert_product_post_data filter). Adding back the field via DOM manipulation doesn’t help — the data is dropped server-side.
What happens if I hide a required field?
We detect that case and lock the field instead of hiding it. Required fields like SKU (in many configurations) or product title can’t silently be removed — you’d lose data on save. The lock is shown with a small warning so admins know.
Does it work with the new Dokan SPA / React dashboard?
Yes. The plugin detects the active dashboard type. Classic gets inline CSS + JS for field hiding. SPA gets a MutationObserver-based approach that finds field containers by text-match heuristic, because the SPA has no stable CSS class anchors.
Will it conflict with other Dokan add-ons that add columns or fields?
Toggles only affect columns / fields that exist. If another plugin adds a column we don’t know about, it shows by default; you can’t hide it from the standard toggle. We can extend the registry via a filter on request — FieldCatalog is the extension point.
Can I rename a field label?
Yes — every field has a label-override and a helper-text field in Settings. The override is rendered scoped to the dashboard, so the field name elsewhere on your site (e.g. in admin posts) is unchanged.
Can I restrict vendors to only Simple products?
Yes — under Settings → Product Types, untick Variable / Grouped / External / Booking etc. The hidden types disappear from both the type picker and the filter.
What does the Stepper layout actually do?
Breaks Add Product into 3–4 guided steps (Basics, Inventory, Shipping, Publish). Each step shows only its relevant fields. Helpful for first-time vendors who get overwhelmed by Dokan’s long single-page form.
If I uninstall, do my settings persist?
Settings stay in the database (under onvore_vendor_product_manager_* options) so reactivating restores your configuration. There’s no schema migration to roll back.
Your question isn't here?
Send your questionStop forking themes just to hide a column.
Six tabs of settings. Real server-side enforcement. Start monthly to try, or save with yearly.