Uninstall the Delivery Note module and understand data loss
Understand the destructive uninstall flow before removing the module.
Exact navigationAdmin Area → Setup → Modules → Delivery Note → Uninstall/Delete
What this guide covers
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.
Exact step-by-step process
- Export or retain required PDFs and evidence under the organisation’s retention policy.
- Confirm that no active recipient links or signing workflows remain.
- Use the supported module uninstall action only after approval.
- Verify both module tables and all module options are removed.
- Confirm the module directory cleanup outcome.
Fields, choices and supported possibilities
- Drops prefixed delivery_notes table
- Drops prefixed delivery_note_events table
- Deletes all Delivery Note options
- Recursively empties the module directory
Code-backed validations and workflow rules
- 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.
Expected result and verification
- The module and its owned data are removed only after an authorised retention decision.
Checks, security 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.