Skip to main content

Informational Post – License Downgrade Process and Unexpected Deactivation

I am sharing my experience in a clear, chronological manner to help identify potential issues in the downgrade process and prevent similar situations for other users.

  1. Initial Purchase
    I purchased the 50-site Lifetime license based on the product roadmap and initial expectations.
  2. Issues Encountered
    Over time, the platform did not reach the level of stability required for production use. This led to:
  • project delays
  • postponed implementation decisions
  • financial impact due to reliance on expected improvements
  1. Downgrade Request
    I opened a support ticket (#1614) requesting a downgrade from the 50-site LTD license to the 5-site LTD license, aiming to reduce exposure while continuing limited usage.
  2. Official Confirmation
    Support confirmed that:
  • the downgrade to the 5-site LTD license was completed
  • all remaining split payments were canceled

At this stage, the request appeared fully resolved.

  1. Current Critical Issue
    Following this confirmation, my license is now completely inactive.
    I no longer have access even to the 5-site LTD license, which is currently impacting active projects.
  2. Key Concern
    There is a clear inconsistency between:
  • the confirmed downgrade
    and
  • the actual license status (inactive)
  1. Extended Use Case – Multi-Level Client Scenario
    A critical concern arises in a real-world usage scenario:

If I build a website for a client and include FluentCart, and that client further uses the system to generate or manage licenses for their own customers, what happens if a downgrade or similar issue occurs at my level?

Specifically:

  • If my main license becomes inactive, does it automatically impact all downstream client installations?
  • Will my client’s customers also lose access or functionality as a result?
  • Is there any isolation between license layers (developer β†’ client β†’ end user), or is everything dependent on the root license?
  • In such a case, what is the recovery procedure to restore all affected environments quickly?
  • Are there safeguards to prevent a cascading failure across multiple client sites?

This scenario introduces significant risk in agency or SaaS-like implementations, where one license issue could propagate across multiple businesses.

  1. Purpose of This Post
    This is not intended as criticism, but as a request for clarity and process validation.
    The goal is to ensure that other users do not encounter similar disruptions.

I will provide updates once the issue is resolved.

Helmar Rudolph

Shahjahan JewelΒ or anyone else responsible for licensing issues?