[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.

[Author]

Posts