RTP Two-Way Integration: Configuration

Use the information in this topic to configure your new RTP® Two-Way Integration including setting up products, mapping RTP Customer Profiles, and configuring optional features such as Delivery Methods/Locations, Auto-Fulfill, Liability Waivers, and Net Rate Overrides.

The process for mapping RTP product properties to Inntopia product categories is:

  1. Partner sends their RTP Web Service URL and credentials to Inntopia.
  2. Inntopia completes the RTP XML/product configuration and establishes the connection to the integration.
  3. Inntopia staff completes the product mapping. The estimated time to complete product mapping varies based on the complexity of the project.

Inntopia products are mapped to RTP products according to the following rules:

Single component products with multiple locations are supported as separate Inntopia products.

An RTP Ski Lesson product with two locations (Location 1: Base Lodge, Location 2: Spruce Peak) requires two Inntopia products with the following descriptions:

  1. Ski Lesson (Base Lodge)
  2. Ski Lesson (Spruce Peak)

Multi-component RTP products are supported with the following restrictions:

    • The product contains only one item classified as one of the following:
      1. PrivateLessonProfile
      2. ActivityProfile
      3. RentalInventoryProfile
      4. Any product component profile that is associated with an inventory pool
    • Only one product can be used to create the mapping to the Inntopia product category. To see a sample of supported RTP Product Properties and their corresponding Inntopia Product Categories, click here.
  1. Lift Ticket and Rental
  2. Lift Ticket, Rental, and Lesson

Below is an example of RTP product properties and how they map to Inntopia product categories. Only one product profile can be used to create the mapping to the Inntopia product category. Product Mapping will vary based on each partner’s unique RTP configuration.

RTP Product Profile Inntopia Product Category
AccessProfile Lift Tickets & Ski/Snowboard School
GeneralProfile Lift Tickets & Ski/Snowboard School
MediaProfile Lift Tickets & Ski/Snowboard School
RentalInventoryProfile Ski/Snowboard Rental
PrivateLessonProfile Ski/Snowboard School
ActivityProfile Miscellaneous Activities

Note: The Ski/Snowboard School AccessProfile (for lessons) supports both inventory pools and voucher printing directly from RTP. Voucher printing also applies to rentals. If you offer Ski/Snowboard lessons using either the General or Media profiles, inventory pools and voucher printing will not be available.

The RTP/Inntopia integration auto-creates the integrated RTP products in Inntopia.

  • All product rates and availability are maintained in RTP.
  • The product default status (active or inactive) is applied by Inntopia.

Once the supplier account has been initialized by Inntopia and the products are mapped:

  1. In RTP, make each product available at the "Inntopia/Connect" sale location and ensure the correct sales channel is added. The products will appear in your Inntopia RMS account as active products the next time the cache is refreshed.

    2. The product cross-reference code is created with the numeric RTP code followed by a dash and numeric location code included in XML.

    Cross Reference Code Only

    Cross Reference Code with Location Code

  1. Open the Products page of your Inntopia RMS account and review the auto-created products.
    • Products auto-created in a new integration are active but won't be visible to customers until the integration is live.
    • Products auto-created for an existing integration are inactive must be activated manually in the Settings menu in your Inntopia RMS Products page.
  2. Perform additional product configuration as needed.

For a new integration, Inntopia recommends creating products with an Active status. For an existing integration, Inntopia recommends creating new products with an Inactive status so that the supplier can review the setup prior to exposing the items for sale.

The applied default status directly correlates to an integration setting configured at the Product Category level. Each integrated supplier can choose to automatically have products in a particular category created in an active or inactive state. For example, you can choose to have your lift ticket products be automatically created as active and simultaneously set your rental equipment products to be automatically created as inactive.

The default status settings are applied by an Inntopia software engineer.

To enhance system performance, Inntopia builds an integration cache during times of low-volume traffic by pulling all RTP rates and inventory that are valid starting on that day through six months into the future (or until such time as designated for your integration). Inntopia CRS and Inntopia eComm then reference these cached rates in searches for the next 24 hours (or until the next auto-refresh). Due to this caching feature, any new products or pricing modifications entered into RTP come through to Inntopia the next time the cache is refreshed. The frequency with which the cache is refreshed varies depending on your specific integration.

For situations in which you cannot wait for the next scheduled cache refresh, such as a last-minute, same-day promotion, you can submit a request through your SAM to have Inntopia perform a manual cache refresh. If, after the manual refresh is completed, no new information is received from RTP, check the RTP DAL Cache setting in the web.config file. If the new Inntopia request for data is made within the duration dictated by this setting, the response will be sent from RTP cache and no changes will appear.

For example: If the RTP DAL Cache setting is 12 hours AND you were to pull data at 1 p.m. AND the pull-data request had been called less than 12 hours before that time, the pull-data request would go to the cache, rather than the RTP proc to get new data.

To prevent the pull-data request from going to the cache instead of initiating a new cache build in RTP, you can adjust the RTP DAL Cache setting in RTP.

Note: Any search for products beyond the six-month window of the cache, system performance will be slower as the search will be in RTP “real-time”.

  • All Inntopia supplier accounts integrated with RTP automatically have a Remote System Cache report available within the reporting areas of Inntopia CRS and Inntopia RMS. You can use this report to reference the product information contained within the cache.
  • The Rsys Cache Report, available within Inntopia CRS Reports & AR/AP under the Administrative heading, contains the cache for all RTP-integrated suppliers. This report can be large and load rather slowly.

Specific customer requirements can be mapped to downstream to the RTP Customer IP associated with an order. The customer requirements populate various fields in the Rental, Child Registration, and Skier/Snowboarder profiles found in the RTP Customer Manager. Partners can choose the profiles they want to implement based on their own unique configuration with RTP.

Note: When using customer requirements to transmit order data to RTP, the products must be itemized individually in the itinerary.

For Equipment Rentals, you may want to require First Name, Last Name, and Date of Birth (DOB). In this instance, the following information would then be sent to RTP for each customer with a line-item-level product:

  • DOB, as entered by the guest or agent on the customer requirements screen
  • Address profile of the order customer
  • Customer’s First and Last name (as entered by the guest or agent on the customer requirements screen)
  • Primary phone profile of the order customer (auto-sent by Inntopia)
  • Shoe size
  • Skier or snowboarder ability level

The instructions below are intended for implementing a new customer requirement configuration. The instructions for updating an existing configuration may differ slightly.

  1. To inquire about mapping specific customer requirements for your integration, contact your Inntopia Strategic Account Manager (SAM).
  2. Your Inntopia SAM reviews customer requirements and the Customer Profile Mapping spreadsheet with you to determine the need for new customer requirements and/or values to be added to the Inntopia System.
  3. Based on the customer requirements needed for your integration, your Inntopia SAM prepares and sends you a customized Profile Mapping spreadsheet.

    4. Note: Customer Name and Date of Birth (DOB) are standard Inntopia customer requirements and must be configured for each product sold as part of the integration. These two customer requirements are not included in the Profile Mapping spreadsheet. Configure Customer Requirements.

    Inntopia Customer Requirement RTP Code ID RTP Mapped Field
    Height 362 Rental Profile
    Weight 354 Rental Profile
    Ability 385 Rental Profile
    Goofy 351 Rental Profile
    Shoe Size 6 Rental Profile
    Alpine Ability 360 Skier Profile
    Snowboard Ability 361 Skier Profile
    Primary Emergency Contact 344 Child Registration Profile
    On-Site Emergency Phone Number 343 Child Registration Profile
    Alternate Emergency Contact 349 Child Registration Profile
    Alternate On-Site Emergency Phone Number 350 Child Registration Profile
    Alternate Emergency Contact 2 488 Child Registration Profile
    Alternate On-Site Emergency Phone Number 2 489 Child Registration Profile
    Medication 345 Child Registration Profile
    Food Allergy 348 Child Registration Profile
    Drug Allergy 347 Child Registration Profile
    Special Condition 346 Child Registration Profile

    Note: Adding new customer requirements to the Inntopia System can take up to four weeks or longer depending on the number of customer requirements and the complexity of their associated values.

  4. Complete your customized Profile Mapping spreadsheet by typing Yes or No in the Partner column corresponding to each profile that will be sent to RTP for the corresponding product.
    • Yes – the profile will be sent to RTP.
    • No – the profile will not be sent to RTP.

      • Note: The Profile Mapping spreadsheet cannot contain hidden columns as it causes issues with the import.

  5. Provide the following information to Inntopia:
    1. Completed customized Profile Mapping spreadsheet
    2. Inntopia RTP Supplier Name and ID
    3. Preferred environment to which this spreadsheet should be applied: Stage/Test or Production
  6. The Inntopia Engineering team completes necessary configuration in the preferred environment based on information provided in your Profile Maping spreadsheet. When the profile mapping is complete, a subset of your specific customer requirements appears within each RTP supplier in Inntopia.
  7. If necessary, your Inntopia SAM reviews how to add the Customer Requirements to the appropriate products in Inntopia RMS with you.

    8. Note: Customer Requirements cannot automatically be applied to products. You must apply them manually to ensure accuracy.

  8. Add the customer requirements to the products in your Inntopia RMS account.
  9. With your SAM, review your configured customer requirements for accuracy.
  10. Test the customer requirements configuration to ensure that:
    1. RTP orders are down-streaming correctly, and
    2. Customer requirement data is appearing in the correct fields in RTP.
  11. Once testing is complete, you can begin collecting the customer requirement information in both Inntopia CRS and Inntopia eComm for down-streaming to RTP.

    12. Note: If the preferred environment of the initial Customer Requirement configuration was STAGE, your Profile Mapping spreadsheet must be also applied to the PRODUCTION environment after testing is complete. If there are changes to your mapping spreadsheet as a result of testing, submit these to your Inntopia SAM.

Resorts often sell activity products that can be picked up by guests or delivered to a specific location. The Inntopia/RTP integration allows resorts to define a list of delivery methods as well as delivery locations for each activity product configured within the integration. A delivery location is typically a specific hotel or lodge while a delivery method refers to type of delivery, such as hotel front desk or ticket window.

  • To ensure correct setup and down-streaming, the RTP Delivery Method and the RTP Delivery Location ID must be properly mapped to your RTP Delivery Method and RTP Delivery Location Name and must properly coincide with the Inntopia Customer Requirement.
  • Inntopia can set up customer requirements within Inntopia to give guests the ability to specify the delivery method and/or location for products such as lift tickets, lessons, rentals, etc. These customer requirements are then captured during the Inntopia checkout process and sent to RTP with the order (or itinerary) for guest fulfillment.
  • Delivery methods and delivery locations can only be set up at the itinerary level.
  • You can choose to set up delivery locations without delivery methods. You can specify delivery locations be applied at the product level or at the itinerary level.

Note: Only one delivery method/location can be chosen per itinerary.

You can give your guest the option of picking up their ski pass at the ticket window or their hotel front desk.

If a guest buying a season pass prefers to pick up their pass at their hotel rather than the resort ticket window, during checkout, they can select a Delivery Method of Deliver to Lodge and then select their hotel as the Delivery Location.

The setup procedure for implementing delivery methods and/or locations is initiated by the partner. Subsequent steps are a combined effort between Inntopia staff and the partner.

For information on fees associated with setting up delivery methods and/or locations, contact Inntopia Partner Services.

  1. Partner submits an INNTERACT request with the following information:
    • Sales ID
    • Specify delivery locations and/or delivery methods
    • Expected go-live date (expect 20 days from the time request is entered)
    • Contact info
  2. Inntopia staff contacts Partner to discuss generating a spreadsheet from RTP that includes the applicable columns and correct mapping information.

    The RTP Delivery Method Name (if applicable) and the RTP Delivery Location Name columns are used by Inntopia to create the list of customer requirements within Inntopia from which the online user will choose.

  3. Partner delivers the spreadsheet to Inntopia.
  4. Inntopia staff reviews the spreadsheet and creates a task for the Inntopia Engineering team to complete the setup.
  5. In the Inntopia Stage environment, Inntopia staff verifies setup and ensures customer requirements and default location work as expected.
  6. In the Inntopia Stage environment, Inntopia staff works with Partner to ensure delivery locations are down-streaming to RTP as expected.
  7. Partner specifies a go-live date.
Notes:
  • The list of delivery methods and/or delivery locations submitted to Inntopia must be a final list. Updates to the list incur an additional fee.
  • Each product included in the spreadsheet must have a default delivery location defined (RTPDeliveryLocationCode).
  • Only one delivery location is allowed per product.

All orders created in RTP must be fulfilled, or have the transaction completed, before a guest can use purchased products. If you would like your products to be automatically fulfilled for use upon completing purchase, you can submit a request to Inntopia to activate AutoFulfill for your account. For example, you can use AutoFulfill to allow guests direct-to-lift access after purchasing passes online thus eliminating the need to stop at a ticket window.

  1. The "Online Auto-Fulfill Line Item" setting on the RTP product header must be set to True for any products using auto-fulfill.
  2. Contact Inntopia Partner Services or enter an INNTERACT request containing the following information:
    • Clearly stated request to enable auto-fulfill
    • Supplier ID
    • RSys ID
  3. Once auto-fulfill is enabled on the provided supplier account, open the Cross References page in your Inntopia RMS account and set up auto-fulfill for specific products.

If Inntopia collects a liability waiver for an RTP-integrated product, Inntopia can send an authorization to your RTP Point-of-Sale (POS) system to release the product media to the customer. Inntopia maps the Authorization Type code by supplier to a release within Inntopia and passes the AuthorizationTypeCode to RTP via the integration. When the value is sent to RTP, the RTP system flags the release as accepted/approved.

If a guest purchases an additional pass for any activity, the Inntopia system detects if a valid liability waiver has already been accepted for that guest and is on file (within the Inntopia system only). If a valid release is detected, it is not presented to the guest again. If an expired release is detected, the release is once again presented to the guest in the checkout path and must be completed before any pass products are presented.

If a customer has purchased a Bike Lesson and Equipment Rental and has signed an online liability release, Inntopia will automatically send the authorization to the RTP POS system. When the customer arrives to pick up their lesson pass and bike rental, the cashier/agent can see the authorization to release both to the customer and quickly get them on the bike trail.

Allow 10 – 20 business days for Inntopia to complete liability waiver setup requests.

For information on fees associated with setting up liability releases , contact Inntopia Partner Services.

The following instructions are for setting up a standard Inntopia liability waiver for RTP-integrated products sold only through online sales channels:

  1. Submit the following information to Inntopia Partner Services: 
    • Supplier ID and Inntopia Product ID – Supplier ID and all associated product IDs for which you would like the liability waiver to appear. You can list one or many product IDs for a single waiver.
    • Waiver Language – Specify English or French. For information on how to include liability waivers in both English and French, contact Inntopia Partner Services.
    • RTP Authorization Type Code – # # # # #
    • RTP Authorization Code Description – Example: Summer Bike Lesson and Rental Waiver 2020
    • Waiver Name – Name of the waiver. Example: Summer Bike Lesson and Rental Waiver 2021.
    • Waiver Agreement Box Text (optional) – If you want the agreement box to say something other than the default I AGREE, submit the alternate text to Inntopia.
    • Waiver Authorization Age – Minimum age required to sign a liability waiver. Default is 18.
    • Waiver Expiration – Number of days until the waiver will expire. Default is 365 days. After the expiration has been met, the customer will be required to fill out a new liability waiver to purchase the same product again.
    • Waiver Text – Properly formatted HTML tags including inline styles and ‘embed’ tags for videos. The waiver can contain one or many sections; however, because each section must be accepted by the user, Inntopia recommends keeping as few separate waiver sections as possible to simplify the acceptance process.
    • Product Description – Enter a description for the product such as Downhill Package Half-Day.
  2. To ensure that the liability waiver will appear during the purchase process, check that each product using the waiver has the Customer Name and Date of Birth customer requirements added.
  3. Once the waiver has been set up by Inntopia, test for the following:
    1. Ensure the waiver looks as expected on-line, and
    2. Ensure the flag indicating a waiver has been signed is appearing as expected in RTP.
Notes:
  • When using the standard setup approach, you cannot assign a single liability release to two different suppliers; you must enter separate set-up requests for each release.
  • You can sell products that require a liability release in Inntopia CRS by setting up a special product bundle. This bundled setup approach bypasses the need for two separate liability release configurations. For more information, click here.

Inntopia has an integration with 1RISK|Risk Management Software for managing liability waivers through 1RISK. 1RISK supports managing RTP products requiring waivers; however, that relationship is separate from the Inntopia-RTP and Inntopia-1RISK integrations.

To learn more about the integration between 1RISK and RTP, contact 1RISK|Risk Management Software.

For orders integrated into RTP, the RTP OrderId can be used as the barcode in existing barcode and voucher functionality. For information on using and setting up barcode functionality, click here.

 

For Integration Highlights, Requirements, or Implementation Timeline information, click here.

For Order Processing and/or Order Modifications information, click here.

For Troubleshooting help, click here.