Items, units, groups and vendor items

Bulk-delete vendor-item mappings

Select mappings and use the mass-delete action.

Audience: Purchasing staffPermission: purchase_items or purchase_vendor_items capabilityModule v1.7.9

Exact navigationAdmin Area → Purchase → Vendor Items → Bulk Actions

Before you begin

Use an account with purchase_items or purchase_vendor_items capability and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Select mappings and use the mass-delete action. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Admin Area → Purchase → Vendor Items → Bulk Actions.
Select the exact record or option described in this guide.
Complete the displayed fields or action using the rules below.
Save or submit once and resolve any validation response.
Verify the resulting record, status, file, notification or integration effect.

Fields, choices and supported possibilities

Vendor identityCompany/name, code, tax/VAT, phone, website, category/group, address and status as exposed by the vendor form.

Contacts and accessVendor contacts, vendor administrators, portal status, language and welcome/notification settings where applicable.

Item masterCommodity/item code, description, group/subgroup, unit, purchase price, tax and purchase eligibility.

Vendor-item mappingVendor, group and selected item list, shared visibility and vendor-specific values where exposed.

Files/importAttachments, spreadsheet import rows, validation errors and generated barcode/code.

Code-backed validations and workflow rules

Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.
Item and vendor-item operations use separate capability groups.
Spreadsheet imports can create an error file for rejected rows; review it before retrying.

Expected result and verification

The supported bulk-delete vendor-item mappings flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.