> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/supplier-and-product-management/supplier-application/creating-and-managing-suppliers.md).

# Creating & Managing Suppliers

Perform tasks assigned to your role to advance suppliers through the Supplier Management workflow.

## Workflow Overview

The **Supplier** application operates through a single, standardized workflow: the **Supplier Management** workflow. This workflow governs the full lifecycle of a supplier, from \[...] through \[...].

<figure><img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FRo55kVLpmjMZJyRUk4Fd%2FSUP-V112-Process.png?alt=media&amp;token=5b40e6b9-715e-4a69-9603-91048415a37f" alt=""><figcaption></figcaption></figure>

***

## Interactive Tour

Explore the **Supplier Management** workflow and learn how each stage works, with key guidance and best practices along the way.

{% @howdygo/embed url="<https://app.howdygo.com/share/67f39a25-72dc-4d02-96a5-42eccee63290>" %}

***

## Workflow Initiation

A \[...] can be initiated through either of the following triggers.

{% tabs %}
{% tab title="Triggered \[...]" %}

{% endtab %}

{% tab title="Triggered \[...]" %}

{% endtab %}
{% endtabs %}

***

## Workflow Stages

The workflow is organized into **four key stages**, each with specific roles and responsibilities.

{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}

{% stepper %}
{% step %}

### \[...] New Supplier \[...]

> **Performed By:** \[...] (e.g., \[...])

**Responsibilities**:

* \[...]

<p align="center"><a href="/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events/create-new-quality-event.md" class="button primary" data-icon="circle-plus">Create New Quality Event</a></p>

***

{% endstep %}

{% step %}

### Review Supplier

> **Performed By:** \[...] (e.g., \[...])

**Responsibilities**:

* \[...]

<p align="center"><a href="/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events/review-issue.md" class="button primary" data-icon="magnifying-glass">Review Issue</a></p>

***

{% endstep %}

{% step %}

### Modify Supplier Information

> **Performed By:** \[...] (e.g., \[...])

**Responsibilities**:

* \[...]

<p align="center"><a href="/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events/modify-quality-event.md" class="button primary" data-icon="pencil">Modify Quality Event</a></p>

{% hint style="warning" %}
This stage is triggered only if \[...].
{% endhint %}

***

{% endstep %}

{% step %}

### Provide Missing Documents

> **Performed By:** \[...] (e.g., \[...])

**Responsibilities**:

* \[...]

<p align="center"><a href="/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events/contain-correct-issue.md" class="button primary" data-icon="box-circle-check">Contain / Correct Issue</a></p>

{% hint style="warning" %}
This stage is triggered only if \[...].
{% endhint %}

***

{% endstep %}
{% endstepper %}

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/supplier-and-product-management/supplier-application/creating-and-managing-suppliers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
