Payments | How to manage item prices in POS Dining?

In the POS dining service you can manage the prices for dining items as item price or bundle price. This is part of the configuration for the POS Dining service. Your Cubigo SPOC will help you.

Each dining item has it's specific (unit) price. Bundle prices are applicable for a combination of dining items, e.g. a 3 course dinner for residents at a fixed bundle price.

We configure for you the bundle price per role per timeslot. Eg a specific price for residents for dinner, or a specific guest price for lunch. A bundle price includes by default all ordered dining items and drinks. There is no automatic control mechanism on the number of items in the order (eg max 1 main course etc).

Next to the active bundle prices, we configure prices on item level. Team members can manually mark items as billable, on top of the bundle price. Item prices are the same for all users/roles. Item prices are the same for take out and eating in restaurant.

An example: a glass of wine can be included in the bundle price for dinner. An additional glass of wine is priced as item price.

For 'take out'or 'in suite' dining:

• the bundle price for the user applies
• if a delivery price is configured for the community, then this price is charged on top of the bundle price when delivery is selected. Eg a resident orders lunch for room delivery:
  price is $0 (bundle price) + $5 delivery cost.
• if there is a charge for the dining order, either on bundle price or delivery, the order is automatically marked as billable and 1 or multiple billing lines are exported to the dining domain, at the moment the dining request status is set to closed.
• we can configure a separate billable reason and charge code for the bundle price and the delivery cost (give information to Cubigo SPOC)
• the billable lines will contain the resident code, the property code, transaction type ‘charge’, transaction date, billable amount and charge code. The transaction date is the date on which the meal was delivered.

For 'restaurant' eat in dining:

• the bundle price for the user applies
• items can be marked as billable during the order flow, the price of these items is counted on top of the active bundle price
• For restaurant orders, we can configure specific billable reasons and charge codes (separate from the take out orders).
• The default billable reason will be used for all items that are marked as billable. The reason can be changed in the table history details if necessary. A separate billable reason can be configured for bundle prices (charge code per bundle price per role).
• If there is a charge for the dining order, either on bundle price or additional item price, the order is automatically marked as billable and 1 or multiple billing lines are exported to the dining domain, at the moment the table status is set to closed.

The billable lines will contain the resident code, the property code, transaction type ‘charge’, transaction date, billable amount and charge code. The transaction date is the date on which the table was closed.