Package Codes
Prerequisites for Package Codes
Package setup involves defining package elements, which are additional products or services included in the rate or sold in addition to the rate. You can link package elements to rate codes to create pre-defined package rates. Or, you can add package elements directly on blocks or reservations to create ad-hoc package entitlements for reservations.
Package elements have rules that define the calculation of their price as well as the frequency of their posting; the item price for the package item is auto-posted to guest ledger account during End Of Day, based on the frequency specified. When the Item Inventory function is active it is also possible to associate inventory items to a package item so that when selling the package rate or selling the package item separately via the reservation the associate inventory items are also applied to the reservation. This is useful for associating inventory items such as extra bed and cribs to reservations and at the same time posting a charge for their supply via the package element.
Optionally, with the Advanced Package function active, package elements can be configured with an allowance amount as well as item price. For package items with an allowance amount defined the actual sales charge is either posted manually in OPERA Cloud or posted by an integrated system such as a point of sale (POS) workstation or an in-room video when consumed. With package allowances, a credit is posted to package ledger either during check or during each night audit and the sales charges posted to the package ledger to offset the credit - as a result the charge for package element does not appear on the guest folio. For allowances based package items, OPERA Cloud deducts the item price from the rate code rate amount. When multiple allowance based items are linked to a rate code the nett accommodation revenue for the reservation is the rate amount - sum (item price) for all package items included in the rate.
Table 13-4 Example - Package Rate Breakdown
Honeymoon | Item Price | Allowance | Calculation Rule |
---|---|---|---|
Rate Amount |
$540 |
||
Dinner |
$45 |
$70 |
Per Adult |
Breakfast |
$20 |
$40 |
Per Adult |
Champagne |
$40 |
$60 |
Flat Amount |
Nett Accommodation |
$370 |
Based on 2 Adults |
Allowance based package items also support consumption in multiple revenue centers via the setup of alternate outlets - specifying the alternate sales transaction codes permitted for the package item.
For example, a breakfast package element could be consumed in the restaurant or as a room service breakfast.
-
Posted amount equal to or less than the allowance amount are posted to package ledger.
-
Posted amounts exceeding the allowance amount are posted to the guest ledger account as an overage.
-
Allowances not consumed or under consumed are posted to a "package profit" revenue transaction code to the package ledger, based on the item price.
-
Allowance amounts exceeding the item price are automatically adjusted by a posting to "package loss" revenue transaction code to the package ledger.
Examples of allowance based package elements would be dinner or breakfast, where the sales charges for each would be post via a POS solution when the guest consumes their dinner or breakfast.
If the guest does not consume their entitlement OPERA Cloud posts the revenue to 'package profit' to balance the package ledger.
The charge for the package rate is posted to Guest Ledger using a system (non-revenue) transaction code referred to as 'Package Wrapper' - this transaction code is defined by linking a transaction code About Transaction Codes to a transaction group of type Wrapper. For package rates both the accommodation transaction code and the package wrapper transaction code must be selected on the Financials panel of the rate code About Rate Codes.
Table 13-5 Example - Ledger Transactions
Honeymoon | Guest Ledger | Package Ledger | Allowance | Sales Revenue | Notes |
---|---|---|---|---|---|
Dinner Allowance |
-$90 |
$140 |
On Check-in |
||
Champagne Allowance |
-$40 |
$60 |
On check-in |
||
Dinner |
$140 |
$140 |
Posted from POS |
||
Dinner Loss |
-$50 |
-$50 |
End of Day |
||
Champagne |
$60 |
$60 |
Posted from POS |
||
Champagne - Loss |
-$20 |
-$20 |
End of Day |
||
Honeymoon Package |
$540 |
-$370 |
Package Wrapper |
||
Accommodation |
$370 |
$370 |
End of Day |
||
Breakfast Allowance |
-$40 |
$80 |
End of Day (Next Day =Y) |
||
Breakfast - Profit |
$40 |
$40 |
Breakfast not consumed On Check-out |
||
Totals |
$540 |
$0 |
$540 |
- Configuring Package Codes
- Configuring Package Code Definition
- Configuring Package Code Post Attributes
- Configuring Package Code Pricing Schedule
- Configuring Package Code Transaction Details
- Package Formula Functions
- Package Posting Rhythms
- About City Tax Package Function
Related Topics
Parent topic: Rate Management