Skip to content

Uninstalling

GST Manager separates deactivation (a safe, reversible pause) from full data removal (a deliberate, irreversible cleanup). This page covers both, plus a lighter option if you only want to pause.

Deactivate (reversible)

To turn GST Manager off, go to Setup → Addon Modules, find GST Manager, and click Deactivate. WHMCS confirms with:

Deactivation message

"GST Manager Deactivated. Tables preserved."

Deactivation removes the generated files (the hook stub), so the module's client-area hooks stop firing — for example, the invoice bank-details block no longer appears for clients. Your database tables are preserved on purpose (configuration, report data and history), so deactivating and later reactivating is lossless: everything comes back exactly as you left it.

Remove all data (irreversible)

If you want GST Manager's data gone entirely, first deactivate it (above), then manually drop its database tables — every table with the mod_gst_* prefix.

This cannot be undone

Dropping the mod_gst_* tables permanently deletes all GST Manager configuration and stored report data. There is no recovery. Take a database backup first if there's any chance you'll want this data back.

Two things GST Manager set up live on the WHMCS side, not in the module's own tables, so they are not removed by deactivating or by dropping the mod_gst_* tables:

  • The seeded WHMCS tax rules — the IGST 18% and CGST 9% + SGST 9% rules created during setup remain in WHMCS's tax configuration.
  • The deployed theme templates — the GST invoice templates copied into your themes stay in place.

If you want these gone too, remove them yourself: delete the GST tax rules under WHMCS's tax settings, and restore or remove the invoice templates in your theme folders. (The Setup Wizard backed up any templates it replaced, so you can restore the originals.)

Temporarily disable instead

You don't need to fully remove GST Manager to pause it. Simply deactivate it under Setup → Addon Modules as above — the client-area hooks stop firing, but your tables are preserved, so reactivating whenever you're ready restores everything with nothing lost. Deactivation is the right choice during maintenance, or while you sort out an unrelated issue.

Documentation for the Relyweb app catalogue.