> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/websites/product-categorisation/category-warnings.md). # Category Warnings Category-level warnings are a useful tool in your Pakk stores to communicate important information to customers. {% embed url="" %} Category warnings tutorial videa {% endembed %} Category-level warnings are a useful tool in your Pakk stores to communicate important information to customers. Think of them as a replacement for the things you'd say to a customer if you were serving them in person. Category level warnings can be standard, or "pop up" style and always needs to be dismissed by the shopper. They will not show again during that browsing session. Warnings can be jazzed up with markdown, including images and links. Warnings attached to categories will show on the top-level category, all contained subcategories and all product pages for products that fall into that category --- # 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.pakk.io/websites/product-categorisation/category-warnings.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.