Implementing Value adds in your interface

This topic provides two approaches to integrating the Value adds functionality into your interface:

To learn more about implementing the Value adds functionality, see Managing value adds.

Advantages between the two approaches

The following table compares the advantages between the two approaches:

Benefits	Using value adds directly	Using the value adds bundle	Notes
Effort needed to implement the UI recommendation	Easy	Moderately easy	When using bundles you must create additional UI elements to collect and group value-added services as a bundle.
Add multiple value adds to a bundle	Yes	Yes	The API supports adding multiple value adds to a bundle when creating/updating a roomrate.
Support creating multiple value adds bundles	No	Yes	The API does not support this functionality out of the box. You must implement a logic where you store the bundle name and the associated value-added services selected by the partner.
Attach a value adds bundle across multiple roomrates	No	Yes	The API does not support this functionality out of the box. You must implement a logic where you can retrieve the value-added services based on a bundle name and update all relevant room rates with the same set of value-added services.

This section lists the steps to implement value adds directly in the user interface.

Implementing value adds directly.

This section lists the steps to implement value adds using bundles in the user interface.

Implementing value adds with value adds bundles.