Uninstall the Delivery Note module and understand data loss
This guide explains the destructive uninstall flow before removing the module. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Modules → Delivery Note → Uninstall/Delete
What you’ll accomplish
Understand the destructive uninstall flow before removing the module. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Export or retain required PDFs and evidence under the organisation’s retention policy.
- Verify that no active recipient links or signing workflows remain.
- Use the supported module uninstall action only after approval.
- Check both module tables and all module options are removed.
- Verify the module directory cleanup outcome.
Fields and options to review
- Drops prefixed delivery_notes table
- Drops prefixed delivery_note_events table
- Deletes all Delivery Note options
- Recursively empties the module directory
Rules the system enforces
- Uninstall is destructive and is not the same as deactivation.
- Delivery notes, signatures, hashes, secure links and audit events are lost when tables are dropped.
- The supplied uninstall code does not create a backup or archive.
- Core invoices remain, but their delivery-note evidence is removed.
How to confirm it worked
- The module and its owned data are removed only after an authorised retention decision.
Safety checks and troubleshooting
- Use deactivation instead when records must be preserved.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.