> 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-components-optional-recommendations.md). # Product Components - Optional Recommendations When creating or updating components in RTP, there are many fields to update. The importance of any given field will depend on your resorts requirements and how the component and associated product(s) need to behave. The following section is for product component 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. * Product Group/Category * Influences your revenue reporting in RTP * Deferral Pattern * Influences your revenue reporting in RTP * Report Revenue * Generally, any priced component should have this checked. * Any component that has earned accounting of a revenue account should also likely have this checked. * Inventory Pool * Determines how much of a product can be sold, which should align with staffing levels. * Auto Assign - if an inventory pool is only available at one location you’ll likely want to select this option, as it speeds up the sales process. * Tax * Must be set as per government requirements. * Statistic * Configured as per resort requirements. * Private Lessons: * Discipline * May be required depending on lesson schedule sync settings at your resort. * Allow ‘No Instructor Bookings’ * Will be required for online sales * May or may not be required/desired for front-line sales depending on internal sales procedures. As software, flaik isn’t aware of any of the values you’ve used when configuring a lesson component. Saying that, if you’re unsure of how best to set these values we do have some recommendations. * Product Group, Product Category, Units, Deferral Pattern * These values combine to form the foundation of a resort’s revenue reporting. * These values are typically determined by a resort’s Finance/Accounting team. * Security Level * Always leave it set to 0 for a component. Nothing good will come from this being above a 0. * Active/Display * Unchecking either of these will make it difficult to search for older components and may impact your revenue reporting. --- # 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-components-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.