Renewals and amendments

Renewals

When a contract approaches the end of its term, Pinion’s RenewalService creates a renewal opportunity from the contracted subscriptions. Every carried-forward line is re-priced on the renewal effective date — the customer’s active contracted price and discount schedule are applied (falling back to the subscription’s verbatim price only when neither matches), not the snapshot from the original deal. Re-pricing is always on; there is no org-wide opt-out.

Amendments

When a customer modifies an active contract (adds licenses, removes seats, swaps tiers), Pinion’s AmendmentService creates an amendment opportunity from the contract’s subscriptions. Carried-forward lines are re-priced against the customer’s active contracted price and discount schedule as of the amendment’s effective date (falling back to the subscription’s verbatim price only when neither matches). Re-pricing is always on; there is no org-wide opt-out.

A mid-term price change is prorated for the remaining contract term from the effective date, using the product’s Proration Type — the same granularity floor the segment-quantity path uses, so quoting and amendments prorate consistently.

Multi-instance bundles across the lifecycle

Bundles configured as multiple instances (the same bundle fanned into per-site / per-region copies, each with its own price, quantity, and dates) carry forward through both renewals and amendments — each instance renews / amends independently, keeping its own InstanceName__c, price, and child quantities. Multi-instance authoring is a Plus-tier feature; see the dedicated Multi-Instance Bundles guide.

Precedence

Re-pricing precedence (most → least specific): active contracted price → discount schedule → subscription verbatim price. Custom logic (Apex extensions, flows) does not run inside the renewal or amendment kernel.