Seller & Vendor Management
Onboard, manage and empower marketplace sellers with a dedicated Seller module built into Mercur. Mercur’s Seller module is the core of your multi-vendor setup. It models sellers as first-class entities with business details, store status, team members, onboarding progress and isolated resources. This is where you decide who can sell, what they can see, and how their team works inside your marketplace.
How you manage sellers in Mercur
Give your operations team a clean, structured way to run a multi-vendor marketplace without bolting together custom logic for every vendor.
With the Seller module, you can:
- Create and manage seller accounts with business information and store status.
- Onboard new vendors through a guided seller onboarding flow.
- Add team members to each seller with role-based access (owner, admin, member).
- Send and track member invitations using secure JWT-based links.
- Control store status (active, inactive, suspended) to manage who can list and sell.
- Isolate each seller’s products, orders, inventory and shipping setup from other sellers.
- Integrate seller login with Mercur’s authentication and authorization system.
Build custom marketplace with Mercur
Create your unique multi-vendor platform with our powerful, flexible marketplace solution that adapts to your business needs.
What the Seller module delivers for your business
True multi-vendor architecture
Sellers are first-class entities with their own resources and permissions, not just tags on products or customers.
Clear control over who can sell
You decide which sellers are active, inactive or suspended, and the platform reacts immediately in terms of visibility and access.
Team-ready seller accounts
Vendors can invite colleagues with the right roles instead of sharing one login, making larger sellers easier to work with.
Safe, isolated tenant boundaries
Each seller sees only their own catalog, orders and settings, which is critical for security, compliance and scale.
Built for integration and automation
The module plugs directly into Medusa workflows, Mercur payouts, request management and auth, so you are not maintaining custom vendor logic by hand.
Core capabilities
1. Seller accounts
Model vendors as dedicated entities in your marketplace:
- Store business details such as company name, description and contact information.
- Store business address and tax identifiers needed for payouts and compliance.
- Define a unique handle for each seller to be used in URLs or storefront routing.
- Link sellers to their members, onboarding status and payout configuration.
This gives you a single source of truth for everything related to each vendor.
2. Store status control
Control marketplace access with explicit store status:
- ACTIVE
- Seller is fully enabled.
- Products are visible in search and storefronts.
- New orders are allowed.
- Seller is fully enabled.
- INACTIVE
- Seller account exists but is not yet live (for example during onboarding).
- Products can be hidden until activation.
- Seller account exists but is not yet live (for example during onboarding).
- SUSPENDED
- Seller is temporarily blocked due to policy or risk.
- Products are automatically removed from search and listing.
- You can allow them to still fulfill existing orders while preventing new ones.
- Seller is temporarily blocked due to policy or risk.
Status changes can be wired to subscribers that update product visibility and other dependent behavior.
3. Team members and roles
Support real teams inside seller accounts with role-based access:
- Each seller has multiple members who can access the seller dashboard.
- Members have one of three roles:
owner - full administrative control
- Manage seller business information and branding.
- Invite and remove team members.
- Access financial and payout settings.
- Delete or close the seller account.
admin - operational management
- Manage products, inventory and orders.
- Configure shipping and promotions.
- View reports and analytics.
- Cannot modify seller business settings or team members.
member - limited access
- View and fulfill orders.
- Update inventory.
- Cannot modify products, settings or team.
This role system lets sellers delegate work while keeping sensitive operations restricted.
4. Member invitations
Add new team members with a secure invite flow:
- Owners or admins generate member invitations by email and desired role.
- The system creates a signed JWT-based invitation token with an expiration (for example 7 days).
- An email is sent with a unique invite link.
- The recipient accepts the invitation, which creates or connects an auth identity and member record.
- Expired or used invitations are invalidated automatically.
Invite data is stored in dedicated Member Invite entities so you can audit who invited whom and when.
5. Seller onboarding
Track onboarding progress and make sure only ready sellers go live.
The Seller module keeps a Seller Onboarding record that tracks boolean flags for setup steps such as:
- store_information
- Business name, description and contact details.
- Business address and tax ID.
- Store branding like logo and photos.
- Business name, description and contact details.
- stripe_connection
- Payout account creation.
- Stripe Connect onboarding.
- Bank account verification.
- Payout account creation.
- locations_shipping
- Stock location setup.
- Shipping zones and options.
- Fulfillment configuration.
- Stock location setup.
- products
- First product creation.
- Inventory configuration.
- First product creation.
You can use these flags in your UI and workflows to guide sellers through onboarding and decide when to switch them from inactive to active.
6. Resource isolation and multi-tenancy
Keep each seller’s world separate:
- Commerce resources tied per seller:
- Products and inventory.
- Orders and returns.
- Customer groups.
- Promotions and campaigns.
- Price lists.
- Products and inventory.
- Fulfillment resources per seller:
- Stock locations.
- Fulfillment sets.
- Shipping options and zones.
- Stock locations.
This isolation ensures:
- Data security - sellers only see their own data.
- Independent operations - one seller’s actions do not affect others.
Scalability - as you add sellers, the system scales per tenant rather than becoming one big shared mess.
7. Authentication and access integration
Use one auth system for customers, admins and sellers:
- Seller members are modeled as a custom actor type (for example seller).
- Auth identities store the corresponding member_id in their metadata.
- Routes that should be seller-only are protected with authenticate("seller") middleware.
- The member ID is used to resolve which seller’s resources a user is allowed to see and edit.
This lets you reuse Medusa’s authentication while adding a strong separation of roles and responsibilities across actor types.
Build custom marketplace with Mercur
Schedule a guided tour of Mercur Marketplace tailored to your specific marketplace requirements. Connect with our team to discuss how we can help bring your marketplace vision to life.