> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/1.-essential-flaik-related-rtp-recommendations-and-best-practices/product-headers.md).

# Product Headers

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FrajsNYtuFyypm4yLGGOQ%2Fimage.png?alt=media&amp;token=e3f7b149-3c7f-47af-adb5-21a516b01f04" alt=""><figcaption></figcaption></figure>

Elements of a product header configuration that are relevant in flaik:

* Active
  * A product header must be active in order to be mapped
  * A product header can be undisplayed but still be mapped
* Display Group
  * You lesson products can be in whatever Display Group works for your resort’s sales processes, but knowing where it can be found is important when it comes to [mapping the products](/flaik-knowledge-base/for-administrators/admin-settings-product-settings/pos-integration-product-mapping.md)
* Pricing
  * Products can only be sold (and therefore sync to flaik) if they are priced for that day.
  * Note: sales can only sync with a product date of July 1 - June 30 of the current season (Northern hemisphere) / Jan. 1 - Dec 31 (Southern hemisphere)
    * Products sold with a product date before July 1st (Northern hemisphere) / Jan. 1st (Southern hemisphere) can not sync into flaik.
* Rules
  * Customer Required - True
  * Maximum Quantity - True

### Mapping

Every lesson product sold in the POS that needs to appear in flaik must be mapped.

{% hint style="info" %}
Check out [POS Integration - Product mapping](/flaik-knowledge-base/for-administrators/admin-settings-product-settings/pos-integration-product-mapping.md) for more information
{% endhint %}

#### Additional Information

There are many other fields when creating or updating product headers in RTP. The fields above are what is relevant for products syncing to flaik, but to learn more about recommendations related to other product elements, check out [Product Headers - Optional Recommendations](/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/2.-optional-flaik-related-rtp-recommendations-and-best-practices/product-headers-optional-recommendations.md).


---

# 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://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/1.-essential-flaik-related-rtp-recommendations-and-best-practices/product-headers.md?ask=<question>&goal=<endgoal>
```

`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.