Allow marketplace administrators to control and customize the fields on the vendor registration form. Enhance the registration process by collecting tailored information from potential vendors. Enable marketplace administrators to designate existing fields as required. Allow the creation and management of new custom fields on the vendor registration form. Allow rearranging fields in vendor registration form.

We're updating the Dokan admin dashboard to make managing vendor information easier and more visually appealing. The update focuses on the vendor details page where admins can view and edit information such as general details, addresses, social media profiles, payment options, and subscription settings. A refreshing new design will help admins manage their vendors efficiently and effectively.

Hello, I’m reaching out to share an improvement idea regarding the Dokan interface. Currently, when a vendor logs into their account, they have access to two separate areas: A customer dashboard with menus such as past orders, addresses, downloads, etc. A vendor dashboard, accessible via a separate button. My goal would be to combine these two sections into a single, more ergonomic dashboard, so vendors can manage both their purchases and their sales in one place, without needing to switch between interfaces. Specifically, here is my suggestion: Create a unified dashboard with two main tabs: My Sales (all current vendor dashboard features) My Purchases (all the information currently available in the customer dashboard: orders, addresses, downloads, etc.) This way, by clicking on the My Purchases tab, the vendor could access all their purchasing information without leaving the main dashboard. This improvement would help simplify navigation and offer a smoother experience for vendors who also use the marketplace as buyers. I hope my explanation is clear, but please feel free to ask if you’d like me to provide any additional details. Thank you in advance for your feedback and for considering this suggestion.

Give access to admin to make product fileds mandatory

vendor can able to upload product videos from vendor panel to wocommerce product gallery

Grant vendors permission to edit and manage images in their media library, including basic editing capabilities like cropping, resizing, and rotating. This empowers vendors to optimize their product images without external tools.

The support ticket system needs some handy improvements. Admins should be able to see order numbers directly in tickets, get clearer messages when posting duplicate comments, and have better ways to manage and filter support tickets. Also, the ticket counter needs to work smarter when dealing with lots of tickets.

The vendor details page in the admin area needs a fresh look and better organization. All vendor information like general details, addresses, social media profiles, payment settings, and subscription plans should be laid out in a cleaner, more organized way that's easier to navigate.

Synchronize bookable products and services with Google Calendar. Vendors can manage their availability across platforms, automatically block booked time slots, and prevent double bookings for appointment-based or rental products.

When adding the thumbnail images to Products > Brands, the thumbnail image does not display on the Product Page. This is useful for brand logos etc. Thank you

Complete overhaul of the admin settings interface to improve usability and organization. This restructure will make it easier for marketplace administrators to configure and manage their Dokan marketplace with a modern, intuitive interface.

Currently, in the Dokan plugin, vendors are only able to delete images when adding or managing product images. However, they do not have access to image editing tools such as crop, scale, rotate, and flip, which are available to admins. Proposed Enhancement: Enable the image editing capabilities for vendors within the media library. This would include access to tools for cropping, scaling, rotating, and flipping images. This feature would greatly enhance the usability and flexibility for vendors managing their product images.

I would like to suggest the development of an official Dokan module that allows vendors to connect and synchronize their external stores directly with a multivendor marketplace. The goal would be to offer vendors the ability to link their existing store, whether it is based on Shopify, WooCommerce, PrestaShop, or Magento, in order to: Automatically import their products (titles, descriptions, images, prices, stock, attributes). Keep stock levels and prices updated in real time whenever they change on their main store. Automatically forward orders placed on the marketplace back into their original system to simplify order fulfillment. This type of connector would bring significant added value to marketplaces using Dokan, as many vendors prefer to manage their catalogs and inventory centrally on their own e-commerce site. Currently, only expensive third-party solutions like SyncSpider make this possible. An official Dokan module, more accessible and fully supported, would greatly enhance the attractiveness of the platform for multivendor marketplaces.

I have used an external membership plugin (Memberpress) which allows vendors to pause their subscription to the marketplace. Allowing vendors to take a payment break rather than cancelling their shop has greatly helped retain vendors. I would love to see pausing integrated into the Dokan subscription module. Thank you

1. Overview With the release of Dokan Pro’s modern (React-driven) vendor dashboard, many site owners have struggled to translate, hide, or reorder interface elements—especially within the new Analytics/Reports screens. Currently, numerous labels (e.g. “Show:”, dropdown options like “All products” or “Comparison,” and input placeholders such as “Type to search for product”) are neither exposed in Dokan’s own translation files nor filterable via PHP hooks. As a result, non-English‐speaking marketplaces (or single-language deployments) must resort to fragile JavaScript overrides that break on every minor UI change. This feature request proposes: Full internationalization of all UI strings (including analytics/report components, input placeholders, and dynamically loaded headings) New PHP filters/hooks to hide or reorder dashboard panels and table columns Ability to set global default tab/menu names per language—so that every new vendor sees, for example, “Продукти” instead of “Products” without manual renaming A streamlined mechanism to hide specific category/filter options in vendor tables without custom JS 2. Use Cases Single-Language Marketplace (e.g., Bulgarian): A marketplace owner wants every new vendor to see the dashboard entirely in Bulgarian, including custom‐built analytics cards and input placeholders. Relying on JS to patch untranslated strings is brittle and nearly impossible for dynamically injected React components. When a Bulgarian vendor clicks into the product search field, the placeholder (“Търсене на продукт”) must appear immediately—without a split-second flash of “Type to search for product.” Per-User / Global Default Menu Renaming: Right now, Dokan Pro’s Menu Manager works well for existing users, but there is no way to define default names for all future vendors (e.g., “Dashboard → Табло,” “Products → Продукти,” “Reports → Отчети”). Administrators must either rename each vendor’s menu manually or write custom code. A simple filter like php Copy Edit add_filter( 'dokan_vendor_dashboard_menu', function( $menus ) { $menus['products']['title'] = 'Продукти'; return $menus; } ); would solve it—if such a filter existed and applied to the React dashboard. Hiding or Collapsing Dashboard Panels / Analytics Cards: A store manager may not want “Top Products by Revenue” or “Orders Summary” visible for all vendors, or might want to collapse them by default. Ideally, a filter—e.g., php Copy Edit add_filter( 'dokan_reports_panels', function( $panels ) { unset( $panels['top_products_revenue'] ); return $panels; } ); would remove that card entirely, rather than requiring CSS/JS workarounds. Removing Specific Filters/Columns from Vendor Tables: In the “Products” table, there are category filters or columns (like “Category,” “Stock Status,” etc.) that site owners may wish to hide for a simplified view. An ability to programmatically remove columns—e.g.: php Copy Edit add_filter( 'dokan_products_table_columns', function( $columns ) { unset( $columns['category'], $columns['stock'] ); return $columns; } ); would allow a cleaner, more tailored vendor interface. 3. Proposed Solutions A. Expose All UI Strings for Translation Wrap Every Label & Placeholder in Translation Functions In PHP templates and React components, ensure all visible text uses __( 'String', 'dokan-lite' ) (or the appropriate text domain). Example: php Copy Edit And in React: js Copy Edit { __( 'Compare Products', 'dokan-lite' ) } Generate a Unified JSON/WP-Localize for React Use wp_localize_script() or @wordpress/i18n to feed a dokan-translations.json object so React components can call __() at runtime. Populate this JSON with every dynamic string, including dropdown options (“All products,” “Single product,” “Comparison”) and input placeholders. B. Add PHP Filters/Hooks for Dashboard Panels & Tabs Dashboard Panels Filter Introduce a hook like php Copy Edit /** * @param array $panels { * Array of panel definitions: 'panel_key' => [ 'title' => '', 'component' => '' ] * } */ do_action( 'dokan_dashboard_panels', &$panels ); Allow removing or reordering: php Copy Edit add_action( 'dokan_dashboard_panels', function( &$panels ) { unset( $panels['top_products_revenue'], $panels['orders_summary'] ); // Reindex or re‐order if needed. } ); Vendor Menu Titles Filter A filter before rendering menu items, for example: php Copy Edit /** * @hook dokan_vendor_dashboard_menu * @param array $menus Array of tab definitions: key => [ 'title' => '', 'url' => '' ] * @return array */ apply_filters( 'dokan_vendor_dashboard_menu', $menus ); Site owners could set default titles in functions.php or via a custom settings page. C. Control Table Columns & Filters via Hooks Products Table Columns Filter Before rendering the “Products” table, apply: php Copy Edit $columns = apply_filters( 'dokan_products_table_columns', $default_columns ); Example usage: php Copy Edit add_filter( 'dokan_products_table_columns', function( $cols ) { unset( $cols['category'], $cols['stock_status'] ); return $cols; } ); Reports/Analytics Filters Filter If the Reports page uses a PHP array for filter‐names (e.g., $filter_options), wrap it: php Copy Edit $filter_options = apply_filters( 'dokan_reports_filter_options', $filter_options ); Developers could then remove or rename specific filter labels (e.g., remove “Comparison”). 4. Benefits & Impact Maintainability & Future-Proofing Relying on PHP filters/hookable methods ensures that when Dokan or WooCommerce updates the underlying React components, existing customizations remain intact. Site owners avoid fragile JavaScript “mutation observers” that frequently break after minor UI changes. Full Localization for Single-Language Marketplaces Immediately serve a fully translated dashboard to Bulgarian vendors (or any other single-language market), without requiring site owners to learn React internals or monkey-patch elements. Encourage non-English-language adoption, expanding Dokan’s global user base. Better UX & Reduced Support Overhead When vendors see a consistent, fully translated interface (including placeholders that appear the instant an input is focused), they won’t be confused by mixed English/Bulgarian UI. Hiding unnecessary panels and columns streamlines the vendor experience, reducing clutter and support requests. Empower Developers & Integrators By offering documented filters (with code examples), third-party developers can build add-ons or theme integrations more easily. Encourages a more vibrant ecosystem of localized themes and marketplace extensions. 5. Backward Compatibility & Implementation Notes Graceful Fallback Existing installations without these new hooks should continue working as normal. The added filters/actions should default to including all panels/columns with English labels. When the filter does not exist, Dokan falls back to its current hard-coded behavior. WooCommerce Upstream Strings Because many Analytics/Reports strings come from WooCommerce core, collaborate upstream with WooCommerce to ensure those components are also internationalized. Until then, Dokan can expose filters that allow overriding the final rendered labels (e.g., a filter on $report_labels that merges WooCommerce’s translations with Dokan’s custom overrides). Documentation & Code Examples Each new hook should be documented in the official Dokan Developer Docs (https://docs.dokan.co/). Provide at least two or three code snippets per hook to demonstrate common use cases (e.g., hiding a panel, renaming a tab, customizing a table column). 6. Next Steps for Review Review & Incorporate Internationalization Hooks Identify all React components in dokan-lite/assets/js/modules/report-analytics (and similar folders) that output hard-coded text. Wrap each string in __() or _x() calls. Generate an updated POT file that includes these new strings so site owners can translate everything via Loco Translate. Define & Register New Filters in PHP Backend In includes/Dashboard/, add filter points for: Dashboard panels (dokan_dashboard_panels) Vendor menu items (dokan_vendor_dashboard_menu) Table columns (dokan_products_table_columns, dokan_orders_table_columns, etc.) Report filter options (dokan_reports_filter_options) Publish Documentation & Examples Add a “Developer” section to Dokan Docs showing how to use these new filters. Example gist or code sandbox demonstrating a single-language Bulgarian site using these hooks to fully localize and simplify the dashboard. Release Timeline & Backport Strategy Ideally, include these updates in the next minor release (e.g., 3.8.x) so that affected merchants can immediately benefit. Ensure that documentation is updated at the same time to minimize confusion. Conclusion: By adding comprehensive translation support for all dynamic UI strings and providing well-documented PHP filters to hide or rename dashboard components, Dokan Pro will dramatically improve the experience for non-English marketplaces and developer integrators. These enhancements will reduce the reliance on fragile JavaScript workarounds, streamline vendor onboarding, and strengthen Dokan’s position as a truly global, customizable multi-vendor platform.

Adding video banner and slider banner in storefront

It would be great for a Subscription course module. It allows creators to make courses to sell.

Currently,No efficient way currently exists for admins to enforce specific requirements or hide unnecessary fields in the product add/edit form, leading to a lack of control over the vendor's product management interface. This feature will enable marketplace admin to set product add/edit form fields as required or hidden for vendors. Provide an admin setting for configuring these validations and hiding entire sections if necessary. With this feature, admins will have enhanced control over the product management in the marketplace.

It's important to have a flat rate for the whole order, as customers most of the time order multiple items, and with the current setup, they have to pay multiple delivery fees.

We are proposing the addition of an "Affiliate Hub" feature to the Dokan Multivendor Plugin. This feature will introduce a hybrid model affiliate system. The Affiliate Hub will serve as a dashboard for affiliates, enabling them to manage and track their affiliate links efficiently. It is crucial to ensure that vendor earnings remain unaffected by this integration. The platform-based affiliate management will be under the admin's control.