> 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/in-touch-integration/programs-selling-and-configuration.md). # Programs - Selling & Configuration In order to have your multi-week programs work to the their best in flaik, it's important to follow these steps in your POS for setting up and selling these products. ### Sales Process #### Overview * Best Practice: the product date in your POS should be set to match the first program date. * Minimum Requirement: in order for a lesson product to sync from your POS to flaik, the product date must fall between the Season Start Date and Season End Date fields as set in flaik. * To confirm the season dates used in flaik, go to Settings > General Settings > Season Dates. * For more information, visit [season dates configuration](https://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/season-switchover-blue-banner/set-up-your-new-season#usable-date-ranges). * Whichever date is used, the participants will appear in flaik in Scheduling on that date (if the date is in the season date range from above). Examples: * A program starting Jan. 8th is sold for Jan. 1st, all the program participants will appear in Scheduling on Jan. 1st plus all dates added to the flaik task. This will result in a large quantity of participants appearing on a non-lesson day, something to strive to avoid have happen. * A program starting Jan. 8th is sold for April of the previous season. As this is outside the season dates set in flaik, these lesson participants won’t sync into flaik. * As a result, it is best to sell the product in the POS for the program start date. ### Product Configuration * The most important factor in determining how many products for programs will be required is the number of tasks that will be needed in flaik and mapping the POS products to the flaik tasks. * Create a unique product for each unique set of start dates. * eg if you have a 6 week program starting in January and another starting in late February, they each need to be separate product headers for mapping purposes. ### Ability Levels Resorts often want to use a different ability level scale for programs, but it's important to remember that the levels need to be able to map to your existing ability level scale in order for Class Management, Report Cards, and other functionality to work. ### Additional Information Check out [the main Knowledge Base article on multi-week programs](/flaik-knowledge-base/for-administrators/multi-week-programs.md) to see more details on what configuration is required in flaik. --- # 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/in-touch-integration/programs-selling-and-configuration.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.