Before Sending Proposals connected to OPERA Cloud: Configuration Tips

While some of these settings are recommendations rather than strict requirements, following them will generally provide a smoother experience for your team.

We recommend creating dedicated price codes for your Catering Packages rather than overriding prices manually.

This makes it easier to maintain consistent pricing in OPERA Cloud and ensures that package prices are transferred correctly. It also reduces the need for manual price adjustments when creating proposals.

We recommend setting Default Function Spaces for your Catering Packages where appropriate.

This can save time when creating proposals in Proposales because the relevant function space can be populated automatically.

For example:

We recommend setting a Default Setup Style for your Function Spaces in OPERA Cloud.

This can save time when creating proposals in Proposales because the Default Setup Style is automatically selected when the function space is added to a proposal.

Of course, you will be able to do changes if you need another Setup Style than the default one.

All components of your Catering Packages should have the correct Revenue Type Mapping and corresponding Transaction Codes configured in OPERA Cloud.

This is important for ensuring that financial information and tax calculations are transferred correctly to Proposales.

If one of the components in a Catering Package is incorrectly configured, the VAT calculation displayed in Proposales may be incorrect.

We recommend creating Composed Menus at a practical level of granularity, for example at the “2-course dinner menu” level, rather than creating a separate Composed Menu for every possible variation.

For example:

2-course dinner menu
Starter + main course
​

This provides a good balance between flexibility and a manageable setup, making it easier for your team to build proposals without creating unnecessary complexity in OPERA Cloud.

Keep in mind that Composed Menu and Item names are displayed in Proposales as they are configured in OPERA Cloud. We therefore recommend using clear, client-friendly names.

For accommodation, we recommend attaching relevant rate packages or package groups to the Rate Code in OPERA Cloud. This allows package components to be automatically associated with the rate when it is used in a block, rather than having to add them manually each time.

This is particularly useful for recurring accommodation components such as:

For example, a Rate Code can have a breakfast package attached to it, so that the breakfast component is automatically included whenever that rate is selected. Package attributes can also determine whether a component is included in the rate or added as a separate line.

Using packages at the Rate Code level helps keep your OPERA Cloud setup consistent and reduces manual work when creating proposals in Proposales.

For accommodation, we recommend configuring a Room Pool if you want to offer Run of House accommodation.

A Room Pool allows you to simplify the room options presented to clients by offering a single room category or a limited number of categories, such as:

Instead of exposing multiple individual room types, the Room Pool provides a cleaner and more client-friendly overview while still allowing you to manage the underlying room inventory in OPERA Cloud.
​

If you want to send proposals in multiple languages, translations should be configured directly in your OPERA setup.

This applies to:

The required translations need to exist in the configuration for each language in which you want to create and send proposals.

For example, if your sales team sends proposals in both English and German, translations should be configured for both languages.

Because many pieces of information are transferred directly from OPERA Cloud to Proposales, it is important to treat your OPERA configuration as the foundation for your client-facing content.

This applies particularly to:

Before going live, review the names and descriptions from a client-facing perspective and adjust if necessary.