This guide explains how to delete projects safely and confidently in Productized Services for WooCommerce.

It covers:

• where deletion actions are available
• what data is removed
• permission and safety controls
• single deletion vs bulk deletion
• expected notices and redirects
• practical operational best practices for teams

Why Project Deletion Matters #

Project deletion is a high-impact cleanup feature designed for invalid, duplicate, or accidental records.

Used correctly, it helps you:

• maintain accurate project reporting
• reduce clutter in project queues
• remove test/sandbox artifacts from production operations
• keep task and communication lists focused on active work

Because project deletion cascades across associated records, it should be used intentionally and with a quick pre-delete review.

What Gets Deleted #

When a project is deleted, Productized Services removes the project and related records tied to that project ID.

The deletion flow removes associated data such as:

• project record
• project tasks
• project message history/conversations
• onboarding form submissions
• project assignee/collaborator association data
• message read-tracking records

The admin UI also warns that this action is permanent.

Where You Can Delete a Project #

There are three practical deletion entry points in admin workflows:

1. Details tab card + confirmation modal (single project)
2. Row action “Delete” on the Projects list page (single project)
3. Bulk action “Delete” on the Projects list page (multiple projects)

Method 1: Delete from the Project Details Tab (Recommended for Review-First Deletion) #

Use this path when you want to validate project context before deleting.

Navigation #

1. Go to /wp-admin/admin.php?page=psfw-projects.
2. Open the target project (Project ID link / Manage action).
3. Switch to the Details tab.
4. Find the Delete Project card.

What the Delete Card and Modal Provide #

The Details-tab delete UI is designed to reduce mistakes:

• prominent warning styling
• explicit “cannot be undone” language
• Delete button opens a confirmation modal
• modal lists the key associated data that will also be removed
• final action requires Confirm deletion

Step-by-Step #

1. Open the project in manage view.
2. Go to Details.
3. Click Delete in the Delete Project card.
4. Read the confirmation modal.
5. Click Confirm deletion.

Expected Result #

On success:

• project and associated data are deleted
• project caches are invalidated
• you are redirected to the projects page
• success notice appears like:
  • Project #123 and all associated data deleted successfully.

Method 2: Delete from Projects List Row Action (Fast Single-Project Cleanup) #

Use this when you already know the exact project to remove and do not need to open full details.

Navigation #

1. Open /wp-admin/admin.php?page=psfw-projects.
2. Find the target row.
3. Click Delete in row actions.
4. Confirm browser prompt.

Expected Result #

On success:

• selected project is deleted with associated data
• you return to projects list context
• success notice indicates deleted project count or project ID context

Method 3: Bulk Delete from Projects List (Batch Cleanup) #

Use this for larger cleanup operations (for example, test projects or invalid batch imports).

Step-by-Step #

1. Open /wp-admin/admin.php?page=psfw-projects.
2. Select multiple projects using checkboxes.
3. Choose Delete from bulk actions.
4. Apply the bulk action.

Expected Result #

After execution:

• each selected project is processed for deletion
• associated records are removed per project
• global/list caches are refreshed
• success notice appears with count, for example:
  • 3 projects deleted successfully.

Context Preservation After Bulk Delete #

The list flow attempts to preserve current list context where applicable, including:

• view=mine
• status filter

This is useful when performing repeated cleanup inside one filtered queue.

Permissions and Access Rules #

Project deletion is protected by capability and access checks.

Single Project Deletion #

A user must have:

• permission to delete projects
• access to the target project

If checks fail, deletion is blocked.

Bulk Deletion #

A user must have:

• admin access for this area
• permission to delete projects

Additionally, in restricted visibility modes, project IDs are filtered to only deletable/accessible entries.

Built-In Safety Controls #

Productized Services applies multiple safeguards in deletion flows:

• nonce verification for form/link integrity
• capability checks before destructive actions
• project-access checks for single-item deletion
• explicit confirmation step (modal or browser confirmation)
• visible admin success notices after completion

Operational benefit:

• lower risk of accidental or unauthorized destructive operations

Single vs Bulk: Which Should You Use? #

Choose single deletion (Details tab) when:

• you need to review project data first
• deletion decision is sensitive
• you want strongest visual confirmation workflow

Choose single deletion (row action) when:

• cleanup is straightforward
• you’re deleting one obvious invalid record quickly

Choose bulk deletion when:

• removing many known-invalid projects
• cleaning up a filtered queue (status/mine views)

Recommended Team Workflow (Deletion SOP) #

Use this lightweight SOP to keep deletions safe and consistent.

1. Confirm the project is truly invalid/duplicate/test.
2. Check whether status update/closure is better than deletion.
3. Verify you are in the correct list filter/view.
4. Delete through the appropriate method.
5. Confirm admin notice message.
6. Recheck list filters before the next deletion pass.

What to Use Instead of Deletion (When History Should Be Preserved) #

Deletion is not always the best lifecycle action.

Use project updates instead when you need historical context:

• update project status
• adjust assignee/collaborators
• maintain project timeline for operational auditing

Good rule:

• delete invalid records
• preserve legitimate delivery records

Common Mistakes and Better Practice #

Mistake: Deleting Active Projects to “Clean” the List #

Better practice:

• use status transitions for completed/paused items and keep historical records.

Mistake: Bulk Delete Without Verifying Filters #

Better practice:

• confirm current view and status filter before applying bulk delete.

Mistake: Confusing Redirect with Failure #

Better practice:

• rely on success notices after redirect to confirm deletion outcome.

Mistake: Deleting Before Team Confirmation #

Better practice:

• for shared accounts/teams, confirm project ownership and impact before deletion.

Troubleshooting #

I Don’t See Delete Actions #

Likely causes:

• current role lacks delete-project capability
• you do not have access to that project

Clicking Delete Does Not Complete #

Check:

• you completed the final confirmation step
• nonce/session state is still valid (reload and retry)

Bulk Delete Removed Fewer Projects Than Selected #

Possible cause:

• access filtering excludes projects outside your allowed scope

I Was Redirected Back to Projects Page #

This is expected for successful delete flows.

Validation Checklist After Deleting #

Use this quick checklist after every deletion event:

• success notice displayed
• deleted project no longer appears in intended list/filter
• related team members informed when needed
• no additional unintended projects affected

Quick Reference #

Single Project (Details Tab) #

• location: project manage view → Details tab → Delete Project card
• confirmation: modal + Confirm deletion
• notice: project-specific success message

Single Project (List Row) #

• location: projects list row actions
• confirmation: browser confirm prompt
• notice: success feedback on return

Bulk Projects #

• location: projects list checkboxes + bulk action
• confirmation: bulk action submission with security checks
• notice: deleted count message

Summary #

Project deletion in Productized Services is a controlled, security-checked cleanup workflow that removes the project and associated records.

For best outcomes:

• use deletion for invalid/test/duplicate records
• use status and assignment updates for legitimate delivery history
• apply a short pre-delete and post-delete checklist for team-safe operations