Configure prices by audience, period and currency: Capability Test Specification
Coverage
The frontmatter lists a proof scenario or finding for every required rule and records each applicable category. Scenario coverage describes what to check; bindings identify the assertions that already exist, and execution results remain unverified. Precision limits, all amount endpoints, concurrent replacements and full cross-capability allocation scenarios require execution. Workflow edges not named by a scenario remain in this finding rather than gaining a binding from shared workflow membership.
Interactions With Related Capabilities
Price changes affect later component and revenue-allocation validation. A product holds migrated audience rows, components and fixed revenue shares. Resubmit after Commerce vocabulary activation; once the audience is admitted, lower the standard price and attempt component and setup allocations above that price. Audience admission gates the edit; subsequent component and setup saves use the new applicable price, without claiming automatic revalidation of existing shares.