Vendors, contacts and administrators

Create a vendor category

Add a vendor category with name, code prefix and description.

Audience: Purchasing staffPermission: purchase_vendors capabilityModule v1.7.9

Exact navigationAdmin Area → Purchase → Settings → Vendor Category

Before you begin

Use an account with purchase_vendors 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

Add a vendor category with name, code prefix and description. 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 → Settings → Vendor Category.
Choose the New, Add, Create or Start action exposed on that screen.
Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
Save or submit the form once; correct any validation message rather than bypassing it.
Open the resulting record and verify its number, status, totals, files, activity and downstream links.

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.

Code-backed validations and workflow rules

Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.

Expected result and verification

The supported create a vendor category 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.