What We Can Sell

• Product Headers with components that are General or Private Lesson Profile Types.

• Any of the four pricing types are supported.

• Tax Calculation Methods supported are

  • Flat Tax on Net Amount

  • Percent Tax on Net Amount

  • Inclusive Tax

• We assume all components on a product header have the same taxes (like Aspenware and Inntopia).

• Pricing is synced from RTP nightly. When transactions are processed, if pricing in RTP does not match the price that flaik sends over, the price is split proportionally among the product components. If RTP has the product header priced at $0 but flaik does not, the price is split equally among the product components.

• The endpoint to post a transaction does not on its own post to RTP’s instructor schedule tables. A separate schedule sync is run after each transaction post. Without this schedule sync, the transaction is viewable in Transaction Viewers but cannot be returned or refunded in RTP.

• flaik Bookings will respect any Prompts you have set up on your product headers and will include those in the transaction, however the prompt data will be blank.

• flaik Bookings will respect the Maximum Quantity rule on Product Headers.

• Inventory Pools are supported, however multiple locations on those Inventory Pools are not supported. If an Inventory Pool has multiple locations set for the product date, we use the first one returned by the RTP database. The first one returned by the database is as follows (in proc_publicGetInventoryPoolLocation):

  • If the Inventory Pool Location Code matches the current Sale or Audit Location Code, that is returned first.

  • Otherwise, it is determined by the Display Order of the Inventory Pool Location, as defined in Administration/Location.

• Statistics are supported, including multiple statistics on a single component.

• Customer Property Sets are supported, however:

  • We are not updating Skier Profile, Rental Profile, or Child Reg/Emergency Contact Profile.

  • The values recorded in the Transaction tables for the Customer Property Set will be blank.

• Technically, Authorizations are supported.

  • We do not have any code that checks the customer’s Authorization status, and thus the sale is not prevented if the customer is missing an Authorization.

  • However, downstream processes like Aspenware Arrival, or No-Waiver Hotlisting will still correctly assess if the customer has the required Authorization for this transaction.

• The flaik Bookings ID will be posted into TransactionLineExternalOrder with a format of x-y-[ flaikbookingsid], where x is the Business Group Code, and y is the Business Unit Code (so, 1-1-[flaikbookingsid] or similar).