> 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/2.-optional-flaik-related-rtp-recommendations-and-best-practices/product-headers-optional-recommendations.md). # Product Headers - Optional Recommendations When creating or updating products in RTP, there are many fields to update. The importance of any given field will depend on your resorts requirements and how the product needs to behave. The following section is for product configuration that aren't relevant in flaik but will have an impact on selling, staffing, or reporting on lesson products. Therefore we recommend that care and attention are used when deciding on how to configure these fields. Elements of a product header configuration that *aren’t* synced to flaik but will have an impact on your resort selling, staffing, or reporting on lesson products: * Display * Determines whether staff can see the product or not to sell it * Security Level * Determines whether staff can see the product or not to sell it * Display Category * Does not impact any sales or revenue reporting * Is strictly utilized for organizing your resort’s products in such a manner as to be as intuitive and logical as possible for frontline sales staff. * Price Type * Can be either ‘Season’ or ‘Date’, but for 99% of products ‘Season’ is the best practice in RTP. * Price Date Type * Can be either, but Product Date is the best practice in RTP 99% of the time * LOB/Sales Report Group/Sales Report Category * As determined by a resorts Finance/Accounting team * Sale Locations * Determines where a product can be sold. * Components * Attach the relevant components as needed * If your resort uses a waiver on lesson products, as a best practice we recommend adding a waiver specific component instead of the waiver details to regular components * Sales Channels * Determines which customer types can purchase a product as well as the price they’ll pay * Accounting * As determined by a resorts Finance/Accounting team * Pricing * Discounts * Prompts * Rules * Inventory Pool Required * This rule isn’t required from a flaik perspective but is essential to a resort’s operations for controlling sales. * Customer Minimum/Maximum Age/Calculate Customer Age by Product Date * Beneficial if limiting sales of the product to just certain ages (eg kids lessons) --- # 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/2.-optional-flaik-related-rtp-recommendations-and-best-practices/product-headers-optional-recommendations.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.