Grandfathered WordPress Plugin Pricing, Explained

Grandfathered WordPress plugin pricing preserves defined older commercial terms for eligible customers under stated conditions.

Verify the protected account, plan, amount, duration, and actions that preserve or end those terms.

What is grandfathered WordPress plugin pricing?

It lets an eligible existing customer continue some earlier pricing after current offers change.

The protection can cover one term while others change. Grandfathered never means universally unchanged.

Grandfathering needs five answers

1. Who qualifies?
2. Which product qualifies?
3. What term remains protected?
4. How long does protection continue?
5. Which events end or change it?

Without these answers, grandfathered is only a reassuring label.

Identify the protected customer

Eligibility can attach to an account, order, subscription, purchase date, or customer cohort.

Record the exact account and order. Do not assume every company account shares protection.

Identify the protected product

A vendor can grandfather one plugin, plan, add-on, bundle, or service. Related products may differ.

Match the order’s product identifier and plan name. Marketing names can change later.

Identify the protected amount

Protection can preserve a fixed renewal amount, a percentage discount, or another pricing basis.

Those mechanisms behave differently after list-price changes. Save the actual account-specific renewal amount.

Identify the protected billing period

Monthly, annual, and multi-year plans can have separate legacy treatment. Switching intervals may change eligibility.

Record charge frequency and coverage period. Do not annualise without preserving cash timing.

Identify the protected site allowance

An older price can apply only to its original site limit. Added capacity may use current pricing.

Verify staging, development, multisite, and reassignment treatment. Capacity rules can remain separate.

Identify the protected feature scope

Legacy pricing may preserve an old plan without adding every later premium feature.

Compare actual entitlements, not modern plan names alone. Renamed tiers can obscure differences.

Identify the protected support scope

Old pricing can retain standard support while new priority tiers cost more. Check requester and site eligibility.

Price protection does not create response guarantees. Support terms require separate evidence.

Identify the protected service quota

AI, storage, email, analytics, and templates can use separate limits or periods.

A grandfathered plugin price may not protect hosted consumption. Inspect each service line. There is a whole post on what happens when a WordPress plugin price increases.

Identify the duration

Protection can continue indefinitely, for a defined period, or while subscription conditions remain satisfied.

Do not translate unspecified duration into forever. Ask for the applicable condition.

Grandfathered pricing is not lifetime pricing

Grandfathering preserves earlier recurring terms. Lifetime pricing usually concerns a one-time payment or duration promise.

An annual subscription can be grandfathered for years while remaining annual.

Grandfathered pricing is not a universal price lock

Tax, currency, fees, add-ons, quantities, or services can still change. Define protected components.

Use invoice lines and account terms. A stable total can hide changing components too.

Grandfathering can be automatic

A platform can leave existing recurring totals unchanged when public product prices rise.

WooCommerce documents this default in one existing-subscriber price-update scenario. Vendor choices can override outcomes.

Grandfathering can be explicit

A vendor notice can promise legacy terms to a named cohort. Preserve the complete dated notice.

Confirm whether it modifies existing terms or merely describes current intent.

Grandfathering can be account-specific

Support can apply a discount or price directly to one subscription. Public pages may never show it.

Keep the ticket, account screen, and next invoice. Record any stated conditions.

Use an evidence hierarchy

1. Account-specific next renewal.
2. Named vendor notice.
3. Order and invoice history.
4. Applicable subscription terms.
5. Dated support clarification.
6. Public pricing and announcements.
7. Community reports.

Community experience can reveal questions. It cannot prove another account’s eligibility.

Save evidence before changing anything

• Account and order references.
• Original invoice.
• Current renewal amount.
• Plan and allowance.
• Grandfathering notice.
• Applicable terms.
• Support confirmation.
• Next charge date.

Protect account and payment data. Store evidence according to organisational retention rules.

Continuous renewal can be a condition

Legacy terms may require the subscription to remain active. Cancellation can end the protected relationship.

Verify before disabling renewal. A later repurchase may use current pricing.

A failed payment can threaten continuity

Retry, grace, suspension, cancellation, and reactivation states vary. Price treatment can change after a lapse.

Maintain approved payment ownership. Resolve failures through documented vendor controls.

Cancellation can end legacy terms

Some systems preserve terms during pending cancellation. Others require a new current-price purchase later.

WooCommerce documents resubscribe cases preserving old terms. That behaviour does not govern every vendor.

An upgrade can end or reshape protection

Moving to a higher tier can replace the old subscription with current commercial terms.

Ask whether the existing amount, discount, period, and entire plan change.

A downgrade can also change protection

Lower tiers may use current pricing and different features. Returning upward may not restore legacy terms.

Request a complete before-and-after quote. Include future renewal, not only immediate credit.

Changing billing frequency can matter

Monthly and annual versions can be separate products or terms. Conversion can trigger current pricing.

Compare payment timing and protection. Do not assume equivalent annual totals. The mechanics are in how payment timing changes WordPress plugin costs.

Adding sites can matter

Extra capacity can require a modern plan. Some vendors may price only the increment differently.

Verify whether old sites remain protected. Use credible concurrent site demand.

Removing sites can matter

Deactivating a site usually changes utilisation, not necessarily subscription terms. Vendor rules vary.

Do not reduce the purchased tier unintentionally. Distinguish site assignment from plan change.

Changing account ownership can matter

Transfers, mergers, and client handoffs can affect commercial eligibility. Software installation can remain unchanged.

Verify transfer terms before initiating. The recipient may need a current-price entitlement.

Changing payment method should be verified

A routine card update should not automatically imply a plan change. Still confirm the next amount afterward.

Use official account controls. Avoid cancelling and repurchasing merely to replace payment details.

Changing billing information can differ

Updating an address or tax identifier can change invoice totals without changing base price.

Separate tax effects from lost grandfathering. Consult finance staff where appropriate.

Refunds can end the protected order

A refund normally reverses the eligible purchase and entitlement. Later buying can use current terms.

Do not request a refund while expecting old-price access to continue.

Vendor acquisition can create uncertainty

A new owner can migrate accounts, plans, billing, or product names. Preserve the original order.

Review transition notices and acceptance steps. Do not assume either automatic loss or perfect preservation.

Plan renaming does not answer entitlement

An old plan can map to a renamed tier while keeping different scope. Compare actual fields.

Ask about price, features, sites, services, support, and future change rights separately.

Product retirement can end practical value

A protected price has little value when the product or required service disappears.

Monitor maintenance, compatibility, security, and migration notices. Grandfathering is commercial, not operational continuity.

Calculate the legacy-price saving

Subtract protected comparable cost from current comparable cost. Use matching scope and payment periods.

Project only across a credible continued-use horizon. Do not assume indefinite renewals.

Do not mistake saving for value

A discount on an unnecessary plan creates no useful outcome. Review actual need and utilisation.

Compare the protected plan against the cheapest suitable route, not only current list price.

Account for switching cost

Leaving old pricing can require product migration, content conversion, retraining, and parallel licences.

Those costs can justify preservation. They can also reveal unhealthy lock-in.

Account for opportunity cost

Staying on an old plan can block better workflows or consolidation. Cheap continuity can delay improvement.

Compare required outcomes, not emotional attachment to a rare deal.

Use a preservation decision matrix

• Current capability fit.
• Actual site utilisation.
• Legacy-price saving.
• Upgrade requirement.
• Continuity evidence.
• Support and update value.
• Switching cost.
• Client ownership needs.

Document why keeping, changing, or leaving serves the organisation. Price protection is one input.

Ask precise preservation questions

• Which account qualifies?
• Which order and plan qualify?
• What exact amount is protected?
• Does the discount or amount remain fixed?
• Which changes preserve it?
• Which changes end it?
• What happens after failed payment?
• Can ownership transfer?
• How long does protection last?

Keep dated answers with the entitlement record. Avoid relying on chat summaries without order context.

Create preservation controls

• Organisation-owned account.
• Current recovery methods.
• Approved payment owner.
• Renewal reminders.
• Change approval gate.
• Saved terms and notices.
• Account-specific renewal checks.
• Client handoff rules.

Controls should prevent accidental loss. They should not prevent justified plan changes.

Review before every material change

Check grandfathering before upgrade, downgrade, cancellation, transfer, interval change, or account migration.

Capture a before state, expected after state, approval, and completion evidence.

Review after every material change

Confirm plan, amount, next charge, allowance, and services. Correct unexpected changes quickly.

Update budgets and renewal records. Preserve the old evidence for audit.

Distinguish fixed amount from fixed discount

A fixed renewal amount stays numerically stable. A fixed discount can rise with list price.

Record the mechanism, not only today’s total. Model its behaviour after another change.

Distinguish grandfathering from a coupon

A coupon can expire after defined payments or require eligibility. It may not be legacy protection.

Inspect invoice lines and coupon terms. Avoid treating every discount as permanent.

Distinguish base price from final charge

The protected base can remain stable while tax, quantity, currency, or fees change.

Reconcile each line before reporting lost protection. Update financial assumptions separately.

Do not assume every new feature is included

Vendors can place later features in new tiers or add-ons. Old-price customers may retain old scope.

Compare required outcomes before upgrading. The new feature may not justify losing legacy terms.

Do not assume old scope is frozen

A maintained plan can gain, lose, or change features under applicable terms. Review release and account notices.

Grandfathered price does not independently promise a permanent product specification.

Check bundled-product treatment

A legacy bundle can protect one combined charge. Splitting products may require current individual prices.

Conversely, moving separate plans into a bundle can replace their legacy relationships.

Check account consolidation

Merging vendor accounts can simplify ownership while changing subscriptions or billing. Obtain confirmation first.

Preserve source accounts until migrated entitlements, sites, and renewal totals pass verification.

Check early-renewal effects

Early renewal can extend a period or create another schedule under vendor-specific rules.

Ask whether it preserves price and changes the next date. Do not prepay from fear.

Check suspension or pause effects

Some subscription systems support paused or suspended states. Commercial treatment can differ from cancellation.

Verify whether billing, access, and legacy terms continue. Record the expected restart state.

Check vendor migration offers

A vendor can offer migration from an old plan to a modern equivalent. Compare the complete exchange.

Record price, scope, duration, services, and surrender conditions before accepting.

Check client billing consequences

An agency can hold protected portfolio pricing while client contracts use another cost method.

Follow the agreed commercial model. Do not describe internal allocation as vendor price.

Audit grandfathered accounts periodically

Confirm payment methods, owners, plans, amounts, sites, and next dates. Investigate unexplained differences.

Audit before organisational or vendor migrations. Repair weak evidence while channels remain available.

Know the honest weak case

Legacy protection can lose value when the plan no longer fits required sites or workflows.

A current plan can cost more while reducing operational friction. Compare complete outcomes.

Use the grandfathered-pricing checklist

1. Identify the eligible account and order.
2. Identify the protected product and plan.
3. Record the protected pricing mechanism.
4. Record billing period and currency.
5. Record site and feature scope.
6. Separate support and service treatment.
7. Find the stated duration.
8. Save account, notice, and invoice evidence.
9. Verify continuous-renewal conditions.
10. Check failed-payment and cancellation effects.
11. Check upgrade and downgrade effects.
12. Check interval and capacity changes.
13. Check transfer and account-change effects.
14. Calculate saving against a suitable alternative.
15. Review actual plan utilisation.
16. Estimate switching and opportunity costs.
17. Create change approval gates.
18. Confirm terms after each change.
19. Update budget and renewal records.

Frequently asked questions

The verdict

An old price is useful evidence, not a strategy. Understand its conditions before preserving or changing it. Review WP Block Suite’s $299 lifetime licence.