> 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/inntopia-and-privates-configuration-guide.md).

# Inntopia & Privates - Configuration Guide

A guide for the additional steps required to sell private lessons in Inntopia as compared to selling directly in RTP or via Aspenware.

If a resort uses inventory pools on their private lessons and wishes to sell their privates online through Inntopia, there are unique requirements for how to handle product configuration in RTP. This is a guide for how to best handle configuration in RTP as well as mapping the private products in flaik.

### Part 1 - Configuration Basics

Regardless of whether a private is sold in RTP, Aspenware, and/or Inntopia, start the product configuration with these essential steps. 

* [Create the instructor activity ](https://knowledgebase.flaik.com/flaik-knowledge-base/it-and-admins/ski-school-pos-integrations/rtp/instructor-activities-and-flaik-shifts-and-tasks)
* [Create the inventory pool](https://knowledgebase.flaik.com/flaik-knowledge-base/rtp-or-one-kb/rtp-configuration-recommendations/inventory-pool-configuration)

### Part 2 - Creating a 'standard' private lesson product

eg – for sales directly in RTP create a traditional private product header.

* Create the component 
  * Profile Type: Private 
  * Inventory: attach correct inventory pool, click yes to Auto Assign 
  * Statistic: add, based on the resort’s practices (eg ‘Lesson Day’) 
  * Private Lesson tab: correct Instructor Activity/Instructor Availability Type/Lesson Discipline/Allow No Instructor Booking setting
* Create the product - attach the component from the step above

### Part 3 - Creating the Inntopia versions

Inntopia is unable to sell a product in which a component with a profile type of ‘Private’ that also has an inventory pool. 

* Inntopia can either sell a product that is a private lesson or that has an inventory pool, but not both. 
* The solution is to sell two products – one that handles the inventory portion and one that handles the private portion. 

### Part 4 - Inntopia

As mentioned above, Inntopia will need to sell two products to accommodate an inventoried private lessons. The 'inventory' product will be priced and sold in Inntopia and the 'private' product will be bundled so that it is sold automatically along with it.

### Part 5 - flaik mapping

Map just the 'private' product and not the 'inventory' product, otherwise two instructors will end up being assigned to tasks for the same private.

### Product Configuration Summary

<table><thead><tr><th width="176"></th><th width="145">Standard Private</th><th width="145">Inntopia - Inventory</th><th width="145">Inntopia - Private</th></tr></thead><tbody><tr><td><strong>Component</strong></td><td> </td><td> </td><td> </td></tr><tr><td>Profile Type</td><td>Private</td><td>General</td><td>Private</td></tr><tr><td>Deferral Pattern</td><td>Front load</td><td>Front load</td><td>Front load</td></tr><tr><td>Report Revenue</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Inventory Pool</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Auto Assign</td><td>Yes</td><td>Yes</td><td>n/a</td></tr><tr><td>Customer Property Set*</td><td>Yes, if Child Reg is required</td><td>Yes, if Child Reg is required</td><td>No</td></tr><tr><td>Tax</td><td>Yes if applicable</td><td>Yes if applicable</td><td>Yes if applicable</td></tr><tr><td>Statistic*</td><td>Yes if applicable</td><td>Yes if applicable</td><td>No</td></tr><tr><td>Instructor Activity</td><td>Yes</td><td>Yes</td><td>n/a</td></tr><tr><td>Instructor Availability Type</td><td>Yes</td><td>Yes</td><td>n/a</td></tr><tr><td>Lesson Discipline</td><td>Yes</td><td>Yes</td><td>n/a</td></tr><tr><td>Allow No Instructor Booking</td><td>Based on resort's requirements</td><td>Yes</td><td>n/a</td></tr><tr><td> </td><td> </td><td> </td><td> </td></tr><tr><td><strong>Product Header</strong></td><td> </td><td> </td><td> </td></tr><tr><td>Sale Locations - Include Inntopia</td><td>No</td><td>Yes</td><td>Yes</td></tr><tr><td>Sales Channels</td><td>Can exclude Inntopia</td><td>Include Inntopia</td><td>Include Inntopia</td></tr><tr><td>Priced</td><td>Yes</td><td>Yes</td><td>$0</td></tr><tr><td> </td><td> </td><td> </td><td> </td></tr><tr><td><strong>flaik</strong></td><td> </td><td> </td><td> </td></tr><tr><td>Mapped</td><td>Yes</td><td>No</td><td>Yes</td></tr></tbody></table>

### Returns & Cancellations

For any returns or cancellations it is advised to follow the Inntopia-related policies already in place at your resort, but it is important to make sure that both the Inventory and the Private products are both returned/cancelled and not just one of the two.


---

# 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/inntopia-and-privates-configuration-guide.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.