> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/management-dashboard/vendors.md).
# Vendor Management
Manage vendors and their access.
The Vendor Management feature in the Management Dashboard allows suppliers to operate as independent entities within the platform. Vendors can securely access and manage their own products, orders, and analytics without visibility into other vendors’ data.
You can use Vendor Management both when onboarding new suppliers, or for enabling the existing ones to self-manage their product catalog, orders, and analytics. It works for marketplaces and multi-vendor platforms that require strong data privacy and operational independence for each supplier.
**Access control for vendors:**
* Vendors log in with assigned credentials.
* Vendors can only view and manage their own data:
* Products they own, together with their prices, availability and media
* Orders that exclusively contain their products
* Analytics related to their orders and performance
**Vendor as a Legal Entity:**
* Each vendor is represented as a distinct legal entity in the system
* A vendor admin can be assigned to manage vendor operations through the dashboard
* Vendors can have multiple locations and users associated with their account
The Vendor Management view in the Management Dashboard provides an overview of a vendor’s entity information and allows you to manage all aspects of the vendors profiles.
You can manage the following information:
* Core company details
* Subsidiary relationships
* Vendor locations, contacts and group associations
## Creating a vendor
{% stepper %}
{% step %}
#### Choose to create a vendor
Go to Vendors dashboard and choose **Create Vendor**.
{% endstep %}
{% step %}
#### Fill in the vendor details
Provide all the core information in the **Details tab**.
* **Name** – The display name of the vendor within the system.
* **Legal Name** – The official registered name of the vendor as a legal entity.
* **Tax Registration Number** – The vendor’s tax identification number.
* **Country of Registration** – The country in which the vendor is legally registered.
* **Registration Date** – The date the vendor was registered in the system.
{% endstep %}
{% step %}
#### Save the configuration
The new vendor is created and you can update the next data related to it.
{% endstep %}
{% endstepper %}
## Subsidiaries
Manage and link subsidiary companies under the main vendor entity. This enables hierarchical management for vendors operating multiple legal entities.
To create a new subsidiary choose **Add Subsidiary** and provide all the core information like when creating the vendor. After you save the configuration the subsidiary is listed in the tab.
## Locations
Define and manage the vendor’s physical or operational locations. Each location can be linked to orders, inventory, and analytics.
To create a new location choose **Add New Location** and provide the location details. After you save the configuration the location is listed in the tab.
When a mixin schema is assigned to the location entity, each location card shows a **MIXINS** bar. Open **Location Schema** to view and maintain the extra fields for that location, for example geolocation or opening hours.
{% hint style="info" %}
To create a location mixin schema, see [Mixin Schemas](/user-guides/management-dashboard/settings/mixin-schemas.md).
{% endhint %}
## Vendor Contacts
View and unassign contacts added to vendor groups. The list is empty until you assign at least one contact to a vendor group. When the contact is assigned then you can view the user's details in the list.
## Vendor Groups
When a vendor is created, it automatically creates four new user groups for your tenant: product manager, product viewer, order manager and order viewer. Each of the groups has specific access rights configured automatically. In this example for ABC Company the groups are:
* ABC Company Vendor Product Manager
* ABC Company Vendor Product Viewer
* ABC Company Vendor Order Manager
* ABC Company Vendor Order Viewer
{% hint style="info" %}
For the access rights matrix, see [Users and Groups - Vendor Groups](/user-guides/management-dashboard/administration/usersandgroups.md#vendor-groups) guide.
{% endhint %}
For each of the groups you can assign contact persons. Choose **Assign Contact to Vendor Group** or **Assign Contact** in the vendor **Edit** mode and select the tenant user you want to add to the group.
## Vendor-specific coupons
You can create coupons that apply only to products from selected marketplace vendors. In **Customer Management** -> **Coupons**, open the **Rules** tab, enable **Vendor specific**, and choose one or more vendors in **Valid For Vendors**. You can combine a vendor restriction with either a customer-audience scope or a category scope under **Applies to**.
Vendor-specific coupon settings
When a vendor-restricted coupon is applied to a cart:
* Only line items that belong to the selected vendors are eligible for the discount.
* If a **Minimum Order Total** is set, it is checked against the total of those matching vendor items, not against the full cart.
* If the cart has no items from the allowed vendors, the coupon is not applied.
* For **Free shipping** coupons with a vendor restriction, every product in the cart must belong to one of the selected vendors.
* Coupons without a vendor restriction keep their existing validation behavior.
The vendor restriction is stored with the coupon. When the coupon is applied, the same restriction is kept on the cart discount and on the resulting order. Updates to the vendor list apply on the next validation or redemption.
**Example:**
A cart contains Product 1 from Vendor A and Product 2 from Vendor B. The coupon is restricted to Vendor A with a 10% discount and a minimum order total. After you apply the coupon, the discount and the minimum order check use only Product 1. Product 2 is unchanged.
{% hint style="info" %}
For the full coupon create and edit flow, see [Coupons](/user-guides/management-dashboard/customer-management/coupons.md).
For more details about vendors, see the following guides:
* [Vendor Products](/user-guides/management-dashboard/products-module/products.md#vendor-related-products)
* [Vendor Order Split](/user-guides/management-dashboard/orders-module/orders.md#vendors-order-splitting)
* [Vendor User Groups](/user-guides/management-dashboard/administration/usersandgroups.md#vendor-groups)
* [Vendor Service](/api-documentation/api-guides/companies-and-customers/vendor-service.md)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://developer.emporix.io/user-guides/management-dashboard/vendors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
