Variable Component Price

Overview

A Variable Component sets the shape of pricing (flat, tiered, …). A Variable Component Price sets the numbers at a particular scope. Scopes are layered: a Global default, optionally overridden at a Module or Bundle scope, optionally overridden again at a single Subscription scope. At billing time Revvly walks the scopes from most-specific to least-specific and picks the first matching currency. Each scope can be further qualified by region (a per-market price) and by billing term (per-period overrides). This is what lets you ship 'enterprise rates' at the bundle scope, or one-off deals at the subscription scope, without touching the published component. A more specific scope replaces the price it beats rather than merging into it, so every row must carry the monetary fields the component's model bills on — one rate per tier for a volume or graduated tiered component, one flat fee per step for a stairstep one, both halves of the committed and overage pair. A mis-shaped row is rejected when you save it, at every scope, because it could never produce a charge.

How it connects

This concept highlighted in context. Click a peer to navigate.

• Prices a specific Variable Component version
• Resolved at billing time by walking Subscription → Bundle → Module → Global
• Custom Pricing Agreements override even the subscription scope

Key fields

What you’ll see when creating or editing a Variable Component Price.

Example