Skip to content

Multi-Vendor Mode

Out of the box the plugin serves a single seller. Multi-Vendor Mode (Settings → General) turns it into marketplace plumbing: each request belongs to one vendor, vendors are notified directly and manage their own requests, and you decide how much they see and control.

How vendors work

The vendor of an item is its post author. Enable Multi-Vendor Mode and:

  • A quote request is restricted to a single vendor at a time (mixing items from two vendors prompts the customer to finish or clear the current request first).
  • The vendor receives the new-request email, with the option to silence the admin copy ("Disable Admin Notifications").
  • Vendors manage their requests on the vendor dashboard or the My Quotes admin menu — always scoped to their own requests.

Vendors need real accounts

Each vendor must be a WordPress user (with a valid email) who authors their items. Admins are exempt from every vendor restriction — so to test the vendor experience, use an actual non-admin vendor account, not your admin login.

Vendor profiles (Voxel-friendly)

On marketplaces where vendors have a public profile listing (e.g. a Voxel partner post type), you usually want the profile's name — not the WordPress username — on quotes and emails. Two settings:

  • Vendor Profile Post Type — the profile post type's slug (e.g. partner). The vendor's profile title then replaces their username everywhere: dashboards, request views, emails, the admin vendor filter.
  • Vendor City/Location Field Key — optional meta key of a city field on the profile, appended after the name: "Piccoli viaggiatori — Catania". Whether this resolves depends on how your theme stores the field; leave it empty if it doesn't.

Contact masking

For lead-based business models, Hide Customer Contact Details from Vendors (off by default) masks the customer's name, email, and phone (like m***@***) in every vendor view and vendor email — until the customer accepts the quote, at which point the details are revealed. Combined with the accept/decline flow, this supports the "vendor sees the lead only after a committed customer" model. Admins always see everything.

Vendor permissions

SettingDefaultEffect
Lock Status After Customer DecisiononAccepted requests can only be Completed; Rejected ones can't be changed
Allow Vendors to Cancel After QuotingonOff makes a sent quote final for the vendor
Allow Vendors to Delete Their SubmissionsoffOn restores a Delete button; otherwise vendors cancel (with a reason) and only admins delete

All three are enforced on the server, not just hidden in the interface.

Built by Code Wattz.