> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/project-docs/what-is-a-sku.md).

# What is a SKU

In order to connect your Legitimate Tags to a unique digital experience you must purchase the number of SKUs needed for your project. One SKU gives you access to one digital experience for a set number of tags. Each item type or design also needs a SKU to associate the item image, description, and title to that item category. Any additional experiences you want to associate with any number of the tags you ordered will incur an additional charge for the extra SKU setup

Examples:

* A client orders 100 tags from Legitimate to be used for both hoodies and t-shirts. 50 tags will be used for hoodies and 50 tags will be used for t-shirts. This client will need to purchase 2 SKUs for this order.
* A client orders 100 tags from Legitimate to be used for 100 hoodies. The exclusive content for 50 of the hoodies will be different than the digital experience of the other 50 hoodies. This client would need to purchase 2 SKUs.

<br>


---

# 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.legitimate.tech/public-docs/project-docs/what-is-a-sku.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.