> 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/supplier-portal-guide.md).

# Supplier portal guide

How to deliver product data to your customer through the supplier portal

This guide is for suppliers who deliver product data to a customer through their supplier portal.

In the portal you see the products your customer has shared with you, fill in the information they ask for, and submit it to them. Questions in both directions are handled in the portal too, next to the product or field they concern.

### How it works

1. Your customer invites you to the portal and decides which products you work on.
2. You fill in the fields they ask for. Required fields must be filled in before you can submit.
3. You save your work as you go. Nothing reaches your customer until you submit it.
4. You submit your changes. Some go straight into your customer's data, and the rest are reviewed by them first.
5. If your customer has a question or wants something changed, it shows up under **Feedback**.

### Guides

* [Getting access](/tutorials/supplier-portal-guide/getting-access.md)
* [Finding your work](/tutorials/supplier-portal-guide/finding-your-work.md)
* [Filling in product data](/tutorials/supplier-portal-guide/filling-in-product-data.md)
* [Talking to your customer](/tutorials/supplier-portal-guide/talking-to-your-customer.md)
* [Managing your team](/tutorials/supplier-portal-guide/managing-your-team.md)
* [Troubleshooting](/tutorials/supplier-portal-guide/troubleshooting.md)

{% hint style="info" %}
You can open **Help** at the bottom of the menu in the portal at any time. It explains the statuses and can take you on a guided tour of the portal.
{% 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://docs.struct.com/tutorials/supplier-portal-guide.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.