Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Settings, numbering, PDFs and vendor-portal options

Require item selection by vendor

Enable item_by_vendor so order/request item choices are filtered through vendor mappings. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Purchasing staffPermission: purchase_settings: EditModule v1.7.9
Jump to steps
Where to goAdmin Area → Purchase → Settings → Purchase Options
Before you start
  • Use an account with purchase_settings: Edit 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 you’ll accomplish

Enable item_by_vendor so order/request item choices are filtered through vendor mappings. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin Area → Purchase → Settings → Purchase Options.
  2. Select the exact record or option described in this guide.
  3. Complete the displayed fields or action using the rules below.
  4. Save or submit once and resolve any validation response.
  5. Check the resulting record, status, file, notification or integration effect.

Fields and options to review

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.

Rules the system enforces

  • Save through the module settings form and test with a controlled transaction.
  • Do not change unrelated purchase options during a scoped configuration update.
  • 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.

How to confirm it worked

  • The supported require item selection by vendor 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.
Allow direct purchase orders without a request or quotationShow only the purchase-order prefix and numberConfigure purchase-order numberingPurchase Management module overviewUnderstand Purchase Management capability groupsBrowse all Purchase Management guidesExpenses FinanceInvoices PaymentsContracts Documents