> 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/core-commerce/vendor-management.md).

# Vendor Management

Vendor Management Service make it possible to easily manage the suppliers and order splitting.

Here you can find an overview of the Emporix Vendor Management Service, along with its features and benefits.

{% hint style="info" %}

* Looking for APIs documentation? Check out the [Vendor Service](/api-documentation/api-guides/companies-and-customers/vendor-service.md).
* To check how the Vendor Management works in Management Dashboard, see the [Vendor Management](/user-guides/management-dashboard/vendors.md) guides.
  {% endhint %}

### Purpose

The Vendor Management feature in Emporix enables efficient management of the relationships with external suppliers. It offers a structured way to onboard, maintain, and govern vendors while ensuring proper access control and data integrity. Vendors and their employees are granted restricted access, allowing them to interact only with their own products, orders, and data.

### Features

The Emporix API Vendor Management Service introduces a set of features that make managing your orders and suppliers easier:

| Feature                        | Description                                                                                                                                                                                                                                        |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Centralized vendor data**    | All vendor information (legal, contact, and custom attributes) is stored in one secure, unified system.                                                                                                                                            |
| **Controlled access**          | Vendors and their employees can only view and manage their own products and orders ensuring data privacy and integrity. They can manage product media, availability and simple base prices. Additionally, they can publish and unpublish products. |
| **Flexible vendor management** | Update vendor statuses, maintain profiles, and adapt vendor data as business needs to evolve.                                                                                                                                                      |
| **Order Splitting**            | Orders containing products from multiple vendors can be split into suborders by vendor.                                                                                                                                                            |
| **Vendor-specific coupons**    | Coupons can be limited to selected vendors so the discount applies only to those vendors' products.                                                                                                                                                |
| **API-Driven Integration**     | Integrates with other systems enabling automated workflows and data exchange.                                                                                                                                                                      |
| **Secure and compliant**       | OAuth2-based access controls and tenant-specific scoping ensure secure and compliant vendor interactions.                                                                                                                                          |


---

# 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/core-commerce/vendor-management.md?ask=<question>&goal=<user_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.