Create upgrade paths between plans or products
Upgrades help existing buyers move from one plan, offer, or product to another. Use them when the buyer should not go through a normal first-purchase checkout.
What upgrades control
| Area | Purpose |
|---|---|
| Source plan or product | The buyer's current purchase or subscription context. |
| Destination plan or product | The offer the buyer should move into. |
| Upgrade price | The amount or rule used for the upgrade. |
| Upgrade link | The link shared with the buyer or support team. |
| Reporting | Helps separate upgrades from normal first purchases. |
When to use an upgrade
| Use upgrades when | Use normal checkout when |
|---|---|
| An existing buyer should move to a higher plan. | A new buyer is purchasing for the first time. |
| Support is helping a customer change plans. | The buyer has no existing purchase relationship. |
| The flow requires upgrade-specific price rules. | The same public offer applies to everyone. |
Create an upgrade path
- Confirm the product and destination plan are ready.
- Open the pricing or upgrades area.
- Choose the source plan or buyer context.
- Choose the destination plan, offer, or product.
- Set the upgrade price or discount rule.
- Save the upgrade.
- Generate or copy the upgrade link.
- Test the link with the expected buyer path.
- Confirm Sales and Subscriptions reflect the upgrade correctly.
Upgrade checks
- The destination plan has the right billing period.
- The upgrade price is clear to the buyer.
- Support knows when to share the upgrade link.
- Normal checkout links are not used for upgrade-specific flows.
- Existing subscriptions are reviewed before sharing the upgrade.
Best practices
- Name upgrade paths clearly so support can choose the right one.
- Keep upgrade links separate from campaign checkout links.
- Test upgrade behavior before using it in support conversations.
- Update support scripts when upgrade pricing changes.
FAQ
Can I use a normal checkout link for an upgrade?
Use an upgrade link when the buyer already has a purchase or subscription context. Normal checkout links can create reporting or subscription confusion when the intent is to upgrade.
Who should share upgrade links?
Usually support, sales, or account teams share upgrade links after confirming the buyer is eligible for that path.
What should I test before using an upgrade link?
Open the link, confirm the destination offer and price, complete the expected flow when possible, and verify Sales or Subscriptions show the result correctly.