[tim.zimmerli]

Hi everyone,

I’m currently building a custom vendor dashboard for MultiVendorX because the default UI doesn’t fit my project requirements. I need a clean technical path to fully replace the default MVX vendor dashboard, so that after vendor login, my custom dashboard loads instead of the MVX one.

Key question:
Which hooks/filters or template overrides are the correct entry point for this?
Is a standard template override under multi-vendorx/templates/… sufficient, or do I need to intercept the mvx_vendor_dashboard routing logic? If the latter, what’s the recommended, update-safe way to do that?

Goal: Vendor logs in → they see my dashboard UI (SPA / custom layout), while MVX’s backend logic stays intact.

Thanks in advance for pointing me to the right implementation approach.

[Sangita Support Squad]

This reply has been marked as private.

[Sangita Support Squad]

We’re glad to inform you that we have released the revamped versions of our plugins. In this update, we’ve completely restructured the code architecture, refined existing features, and introduced several new advanced functionalities.

We kindly request you to update the plugin to the latest version on your end and verify everything accordingly.

For now we will be closing this thread. If you have any questions regarding the new version or encounter any issues, please feel free to create a new support thread, and we’ll be happy to assist you.

[Author]

Posts