Mass Delete Records

A step-by-step wizard interface walks administrators through the entire deletion process from module selection to final confirmation. Each step presents clear options and requires deliberate action to proceed.

Why it matters: eliminates guesswork and reduces the risk of errors during high-stakes data operations — administrators always know exactly what will be deleted before confirming.

Delete records from Sales, Purchases, Inventory (Stock), Invoicing (Account), Manufacturing, and Projects — all from a single administrative interface without navigating into each module individually.

Why it matters: database cleanup after testing, migration, or demo cycles typically spans multiple modules — handling them all from one place turns a multi-hour task into a single workflow.

A dedicated option to clear complete datasets from selected modules in a single action rather than selecting specific record ranges or types.

Why it matters: when resetting an environment after a demo, clearing test data before go-live, or starting fresh after a failed migration, the All Data option eliminates the need to identify and select individual records manually.

Every deletion action triggers a confirmation dialog that explicitly states what will be removed and requires deliberate user approval before proceeding. No deletion executes without explicit confirmation.

Why it matters: bulk deletion is irreversible — confirmation prompts create a mandatory pause that prevents accidental data loss from mis-clicks or incorrect module selection.

Every deletion action is recorded in a detailed log that captures what records were removed, the exact timestamp of the operation, and which user performed it. The log persists as a permanent audit record.

Why it matters: administrative transparency and compliance requirements demand knowing who removed what data and when — this logging provides that accountability without any additional configuration.

The Mass Clean Data feature is accessible only through Settings with Developer Mode enabled, restricting bulk deletion capabilities to administrators who have elevated system access.

Why it matters: by gating access behind Developer Mode, the module ensures that standard users cannot accidentally discover or trigger bulk deletion workflows — only users with explicit administrative authority can access the tool.