How QCDR Preserves Paid Configuration Across Downgrades and Renewals

A QCDR entitlement downgrade is designed to remove access to paid behavior, not erase the administrator's saved configuration. Higher-tier Rule and Token settings remain stored so they can resume when a qualifying entitlement returns.

Saved Configuration Is Not Deleted on a Tier Drop

QCDR calculates the tier required by each Rule and Token from the features it actually uses. When Effective tier drops below that requirement, the item can appear locked in the Administrator while its saved row and higher-tier options remain stored.

This applies to paid targeting/options and higher-tier Token types. QCDR contains explicit preservation paths so editing unrelated allowed fields does not silently wipe an already-saved paid dependency merely because the current tier is lower.

Locked Configuration Does Not Execute

Preservation is not the same as continued paid execution. The runtime engine independently checks the current Effective tier. A Rule whose required tier is no longer allowed is skipped as plan-locked. A paid Token that is unavailable is not replaced with an empty value; QCDR preserves the author's original Token placeholder or the Rule's original matched text where the Token cannot resolve safely.

PHP Tokens receive an additional server-side Max check and do not execute after a downgrade below Max.

Renewal Can Restore the Existing Configuration

When Authorized Domain entitlement again resolves to the required tier, the stored configuration does not need to be rebuilt. After entitlement is refreshed and task integrity is healthy, previously plan-locked features can become available again using their preserved settings.

Always review the Rules/Tokens involved before enabling broad live processing after a long lapse, because the site's frontend markup or business requirement may have changed while the configuration was locked.

A Task-Health Fallback Behaves Like a Temporary Tier Loss

If Entitlement Revalidation is structurally unhealthy, QCDR forces Effective Basic even if a paid Base tier was previously known. Paid configuration remains stored, but paid execution stays locked until task integrity and entitlement are restored.

What a Downgrade Does Not Do

A normal entitlement change does not delete Rules, Tokens, their processing order, runtime settings, preview history, or Discovery data. It changes what the current entitlement is permitted to configure or execute.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.