The bundle parent is treated like any other order line as far as pricing is concerned. The line total is computed like any other order. The order total includes the bundle parent as well as any components. A bundle can have a unit price, charges, and taxes like any other line.
There is an attribute at the order line level which can suppress the price of a line to be excluded from the order total or the overall amount a customer has to pay. If you want to have a price for a line but do not want to include it in the order total, set the attribute for the component. For bundles, if price of a component is included in the package itself but you want to store the price of an individual line in case of cancellation or a return, you may set the attribute on the line. In order to reflect the special price of a bundle, you may choose to set attributes for the components so that the price of the component is not reflected in the total price of the order.
Using the following table as an example, the pricing for the bedroom package bundle and its components could be:
|Bedroom package||Line total amount||Price for information only|
|Bedroom Package (Bundle)||$500|
|Bed Set Package (Bundle)||$300||Y|
Under normal circumstances, the order total would be the sum of all lines, which in this case is $1100. Instead, if the order should be priced differently based on the bundle parent, and you do not want the component level price to be included in the invoice, you can set an attribute at the component level during order creation. For more information about these attributes, see the IBM Sterling Order Management: Javadoc.