> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-review-supplier-changes.md).

# How to review supplier changes

A guide to reviewing and merging the changes suppliers submit

When a supplier submits, every value that requires review arrives in Struct PIM as a draft named after the supplier. Your live data does not change until you accept the value. This guide shows how to find the drafts, decide each change and let the supplier know what to fix.

{% hint style="info" %}
**Before you start**

To accept, reject or ask for changes, you need the **Decide the outcome of drafts** permission and permission to edit the products, variant groups or variants concerned.
{% endhint %}

## How to find drafts waiting for review

Supplier drafts are listed in the **Open drafts** dashboard widget.

1. On your dashboard, click the pencil at the bottom right to edit it, then the add widget button, and choose **Open drafts**.
2. Under **Whose drafts**, choose **Data onboarding portal**.
3. Optionally, pick one or more **Suppliers** to follow. Leave it empty to follow every supplier.

![The Open drafts widget, following the Data onboarding portal](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2Fwott8CZoOD5kRct54on6%2Fdop-open-drafts-widget.png?alt=media)

You can add the widget more than once, for example one for each supplier you are responsible for.

The widget lists each draft with the supplier who proposed it, its activity, and how many changes and conflicts it has. **Sent for review** shows only the drafts that suppliers have submitted. Drafts a supplier has saved but not yet submitted are not ready for review.

## How to review several drafts at once

Select the drafts in the widget and click **Review** at the bottom of the widget. This opens **Review changes**, with a tab for products, variant groups and variants.

Decide each change:

* **Accept** writes the value to your live data. Click a change to switch between accepting and rejecting it.
* **Reject** removes the change. The supplier cannot send the same value again.
* **Request changes** sends the change back to the supplier with a note saying what to fix. Click the speech bubble next to the value, or right-click it. A note is required.

Use **Accept all** or **Reject all** to decide every change on the current tab. Changes you do not decide stay in the draft for later.

Click **Submit review** to apply your decisions. You can review up to 50 drafts at a time.

### Choosing a layout

Use **View as** to choose how the changes are laid out:

* **Matrix** shows one row per product, variant group or variant, and the changed attributes as columns. It is best when the drafts change the same fields.
* **Queue** shows one draft at a time. It is best when each draft changes something different. Click **Approve & next** to accept a draft and move on.
* **Automatic** picks the layout for you.

### Handling conflicts

A conflict means the value in your live data changed after the supplier wrote their draft. Decide each conflict with **Keep current** or **Take draft**. Turn on **Conflicts only** to see just the conflicts.

If several drafts change the same field, you are asked to pick which value wins.

## How to review a single product

Open a product, variant group or variant from the widget with **Open**. A purple banner at the top shows that you are looking at the supplier's draft.

![The draft banner in the product editor](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FAVDs0QxE5F3fwc8jnVjz%2Fdop-draft-banner.png?alt=media)

Click **Review & merge** to compare the draft with the current data side by side. For each value, choose **Keep current** or **Take this**, then click **Submit review** and confirm with **Merge**.

When you merge, the draft is deleted by default. Any change you did not take is deleted with it.

## What the supplier sees

* **Accepted** values become the supplier's current data in the portal.
* **Requested changes** are shown to the supplier on the values concerned, with your note. They fix the value and submit again.
* **Rejected** values are removed from the supplier's draft.

Your notes are also posted to the supplier's [feedback](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-use-the-supplier-feedback-inbox.md) threads, so the conversation can continue there.


---

# 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://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-review-supplier-changes.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.
