> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/data-model/products/sku-lists.md).
# SKU lists
{% hint style="info" icon="lightbulb" %}
SKU lists group multiple SKUs into a collection. Items can be added manually or via a regular expression. Use them for promotions, filtering, and building bundles with a special market price.
{% endhint %}
## What is a SKU list?
[SKU lists](/core-api-reference/sku_lists.md) are used to group many SKUs into a collection that can be filtered and exposed to customers in the presentation layer. You can create a SKU list by selecting and sorting items from the available SKUs manually, or by using a regular expression to populate and sort them automatically.
SKU lists let you:
* Filter, display, or apply rules to a selected set of SKUs, including their prices and availability.
* Enable and manage promotions for a set of SKUs.
* Restrict the scope of a promotion to a set of SKUs.
* Group SKUs into a bundle assigned to a market with a special price.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.commercelayer.io/data-model/products/sku-lists.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.