> For the complete documentation index, see [llms.txt](https://shoppa.gitbook.io/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shoppa.gitbook.io/knowledge-hub/shoppa-cloud/arbetsfloden/planogram.md).

# Planogram

Planogram är ett arbetsflöde för butiker vars sortiment är organiserat i planogram. Om din kedja använder planogram ser du arbetsflödet *Planogram* i sidomenyn.

Planogrammen och deras artiklar sätts upp centralt och tilldelas per butik. Varje planogram kan ha en fördefinierad mall – per planogram, per fixture eller per artikel – så att rätt skylt skapas automatiskt.

I planogramflödet väljer du artiklar via planogramlistor i stället för sökning:

* **Alla produkter** – samtliga artiklar i planogrammet.
* **Ändrade produkter** – artiklar som förändrats och behöver ny skylt.
* **Ny i planogram** – artiklar som nyligen lagts till i planogrammet.

Utskriftsordningen följer artikelordningen i planogrammet, så att skyltarna kommer ut i samma ordning som du går längs hyllan.


---

# 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://shoppa.gitbook.io/knowledge-hub/shoppa-cloud/arbetsfloden/planogram.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.