Fixed Price Components (FPC)

A Fixed Price Component is an option type that behaves like a Component for quantity (parent qty × option qty) but with a special price rule: the option’s stored unit price is rawSalesPrice / effectiveOptionQty, where effectiveOptionQty = parent.Quantity × option.Quantity. Here rawSalesPrice is the FPC’s own configured price on the option metadata, not the parent’s stored UnitPrice.

The “Fixed” in the name means fixed total. The FPC contributes a flat rawSalesPrice to the bundle no matter how many of the parent bundle the rep buys.

Worked example

A Starter Bundle has an FPC child “Implementation Service” with rawSalesPrice = $5,000 and option.Quantity = 1. The rep configures parent.Quantity = 3 of the bundle.

  • effectiveOptionQty = 3 × 1 = 3 → child Quantity = 3
  • UnitPrice = $5,000 / 3 ≈ $1,666.67
  • TotalPrice = Quantity × UnitPrice = 3 × $1,666.67 = $5,000 ✓ flat

Changing parent quantity from 1 to 100 still leaves the FPC’s TotalPrice at $5,000.

Why FPC exists

Some bundles include a child that should be priced as a one-time flat fee regardless of how many of the parent the rep configures — think “implementation package,” “onboarding fee,” or “setup charge.” You don’t want the fee to scale (that’s a Component); you want a single fixed dollar contribution to the bundle.

When to use

  • Implementation / onboarding fees included with a subscription.
  • One-time setup or installation charges bundled with a product.
  • Any line that should contribute a flat dollar amount per bundle configuration, not per parent unit.