Where should a marketplace dashboard for FluentCart live?
I'm building a marketplace plugin for FluentCart and gotta take some decisions. Iβm asking because most marketplace plugins, like Dokan and similar tools, create their own separate vendor dashboard. That usually means users on front end are moving between two different dashboards: the native commerce dashboard and the marketplace dashboard.
For FluentCart, Iβm wondering if the better UX is to keep everything inside one connected dashboard, especially because it would work smoothly inside the FluentCart SPA without full page reloads.
My current thinking is that a unified dashboard may feel cleaner because users do not have to jump between separate admin/vendor areas. But a frontend dashboard could also be useful for communities, vendors, and public-facing marketplace workflows. Curious what FluentCart/FluentCommunity users would prefer.
I agree : the better UX is to keep everything inside one connected dashboard
live inside fluent community
Bryan WilliamΒ the products and vendors can be mounted on FCOM SPA, but vendor dashboard seems better on FCART account dashboard which isn't currently mounted on FCOM SPA.
When do you plan to lunch it
AndrΓ© GΓ³isΒ this marketplace and some other addons for fluentcart, maybe a month maybe more. I have 2 other ecosystems kind of ready, will upload videos here to show it.
Well, i think it needs to be as an option for admin to choose and my work is to make it work in both, fcart and fcom... No shortcuts
You're working on a multi-vendor marketplace? That's great! So vendor onboarding, split payments, and EU and other VAT regulations ?
Let us know if you need beta testers this summer
@maude_27141
- Split payment - yeah stripe connect. But crypto payments too. Im looking into ability to have cards for vendors, its posssible.
- Vendor onboarding. This is boring, nothing exciting.
- EU and other regulations. Nothing to be worried about.
- Product sync with individual stores, and some other never seen features. But first i gotta launch cointacted. βΊοΈ
I read an interesting comment recently: not all sellers want to manage an online store. Perhaps an easy to implement shop manager role could provide an option for a fairly hands-off store?
Maude VuilleΒ Yes, this is a real use case.
Not every seller wants to manage a full online store. Some vendors may only want to sell, while someone else handles day-to-day operations.
Our planned role model is capability-based:
- Marketplace Admin: controls marketplace settings, vendors, listings, commissions, integrations, and global configuration.
- Tenant Operator: manages a specific marketplace/tenant configuration.
- Vendor Owner: owns the vendor account, listings, offers, and business relationship.
- Vendor Staff: helps manage the vendorβs own listings/products.
- Booking Staff: manages bookings/calendars for service-based vendors.
- Support Staff: can view reports/support information without sensitive admin access.
A βShop Managerβ preset would fit well here: able to manage listings, products, bookings, and support tasks for a vendor, but not access payouts, commissions, API keys, or marketplace settings.
Wow, that's intricate! Are you planning on delivering one step at a time or all at once?
Maude VuilleΒ many things will be there on launch. I have strong engine for marketplace, its a lot of code. But i have two other ecosystems to launch before that π and this marketplace will be one of the ecommerce plugins, more such as live shopping, pod, etc...