> 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-create-submission-templates.md).

# How to create submission templates

A guide to deciding which attributes suppliers are asked for

A submission template decides what suppliers are asked for: which attributes, at which level, how strictly, and whether their answers need your review. Every area uses one submission template, and many areas can share the same one.

Submission templates are found under **Settings > Data onboarding > Submission templates**.

## How to create a submission template

Click **Create submission template**. The template is set up in four steps: **General**, **Data templates**, **Classification** and **Category attributes**. Click **Create template** on the last step to save it.

### General

Enter a **Name** that tells your colleagues what the template is for, for example "Textiles". Suppliers do not see the template name. The **Description** is optional.

### Data templates

A data template states what is asked for about one kind of product. Add one data template for each product structure your suppliers work with.

![A data template with its attributes per level](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FqH5pNqTibgs4lzTxdfwv%2Fdop-data-templates.png?alt=media)

1. Give the data template a **Name**. Suppliers see this name as the kind of product, so choose something they understand, for example "Bed linen".
2. Choose the **Product structure** it applies to. Each product structure can only have one data template in a submission template.
3. Click **Add attributes** and pick the attributes you want the supplier to fill in.

The attributes are shown as rows, with a column for each level the product structure has: **Product**, **Variant group** and **Variant**. A new attribute is **Required**, editable and **Requires review** on every level where the product structure places it.

Click a cell to change what is asked for at that level:

* **Asked for** sets the attribute as **Required**, **Recommended** or **Optional**, or as **Read only** if the supplier should see the value but not change it.
* **Unchangeable** lets the supplier answer only once. Afterwards they cannot change the value.
* **When the supplier submits a value** decides whether the value **Requires review** or can **Merge directly** into your live data.
* **Not in this level** stops asking for the attribute at that level.

![Choosing what is asked for in a cell](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FFjpuL4ndVgJc4B6dcupK%2Fdop-cell-menu.png?alt=media)

To change every attribute in a column at once, click the menu next to the level's name. Drag rows to set the order suppliers see the attributes in.

{% hint style="info" %}
Suppliers cannot submit until every required value is filled in. Recommended values are highlighted for the supplier, but never stop them.
{% endhint %}

#### Base template

If several data templates ask for the same attributes, for example a brand and a description, you can state them once in a base template. Click **Create base template** below the data templates and pick the attributes every data template should share.

Every data template inherits what the base template asks for, marked **From base**. To ask for something else in one data template, click the cell and choose another setting. That overrides the base for that data template only. **Clear override** returns the cell to what the base template says.

### Classification

Classification decides whether suppliers can place products in your categories.

For each level, turn on **Allow supplier to classify**, choose a **Classification requirement**, and select the **Categories** the supplier may choose from. A selected category includes all the categories below it.

### Category attributes

Some attributes belong to a category rather than a product structure, for example "Thread count" for bed linen. On this step, click **Add categories** and set what suppliers are asked for when they place a product or variant in that category.

Category attributes are set the same way as in a data template. Suppliers see them after the attributes of the data template.

## How to edit a submission template

Click the submission template in the list. The edit page has the same four tabs as the wizard, saved together with **Save**.

Changes apply straight away to every area that uses the template, and to the suppliers working in those areas.

## How to delete a submission template

A submission template cannot be deleted while an area uses it. Choose another template on those areas first, then delete the template from the list.


---

# 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-create-submission-templates.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.
