> 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/filling-in-product-data.md).

# Filling in product data

How to fill in product data, save your work and submit it to your customer

Product, variant group and variant pages work the same way. You only see the fields your customer has asked you for.

## Filling in fields

Open an item from your area's list. The fields are grouped into sections, and the panel on the right shows how complete the item is and which fields are still missing.

![A product page](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2F43urb26FWmsA7EuMYTJ0%2Fdop-product-page.png?alt=media)

* **Required** fields are marked with a red asterisk, and must be filled in before you can submit.
* **Recommended** fields are marked in orange. They count towards completeness, but never stop you.
* Fields with a lock are read only. Your customer shows them for information.
* Some fields can only be answered once. After your customer has the value, the field is locked.

Click a field in the **Required** or **Recommended** list on the right to jump to it.

A product can have **Variant groups** and **Variants** tabs, which list the item's variant groups and variants.

### Categories

If your customer asks you to place products in categories, click **Choose categories**, tick every category the product belongs in, and click **Apply**. If you choose more than one, mark one as **Primary**.

### Images and files

For image and file fields, click **Select from media archive** to pick a file you have uploaded before, or drop new files onto the field.

## Saving your work

Click **Save** at the bottom of the page whenever you want. Saved changes are marked **Pending**, with your customer's current value shown underneath.

{% hint style="warning" %}
Saving does not send anything to your customer. Your changes stay with you until you submit them from the list.
{% endhint %}

## Submitting your changes

1. Go back to the area's list. Items with saved changes can be ticked.
2. Tick the items you want to submit, and click **Submit changes**. Or click **Submit all open changes** at the top to submit everything in the area.
3. Check the summary and click **Submit** to send the items.

![The submit summary](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FDyqQ0k8QAU7trd2eUc4C%2Fdop-submit-dialog.png?alt=media)

The summary shows which changes **go live** straight away and which go to your customer **for review**. Your customer decides this for each field.

Items with required fields still empty cannot be ticked, and are left out when you submit everything. Fill in the missing fields and submit them later.

To undo changes you have not submitted, tick the items and click **Discard**. The fields go back to your customer's current values.

## After you submit

A strip at the top of the item's page shows where your changes are:

| The strip says                        | Meaning                                                                                                                |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Changes are not submitted yet         | You have saved changes. Submit them from the list.                                                                     |
| Changes are being held                | Required fields are still missing, so the changes cannot be submitted yet.                                             |
| Changes are waiting for your customer | Your customer is reviewing them.                                                                                       |
| Your customer asked for changes       | Your customer wants some values changed. Their note is under **Feedback**. Correct the values, save, and submit again. |

When your customer accepts a value, it becomes their current value and the strip disappears. If they do not accept a value, it is removed from your changes, and you see their current value again.


---

# 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/filling-in-product-data.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.
