Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Vendor portal and authentication

View vendor portal purchase requests

Follow this guide to review shared/authorised purchase requests. 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: Vendor contactsPermission: Authenticated active vendor contact and enabled portalModule v1.7.9
Jump to steps
Where to goVendor Portal → Purchase Request
Before you start
  • Use an account with Authenticated active vendor contact and enabled portal 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

Review shared/authorised purchase requests. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Vendor Portal → Purchase Request.
  2. Select the relevant record, filter, report, model or configuration described below.
  3. Use the displayed action or read the current values without altering unrelated data.
  4. Compare the output with the code-backed rules and expected result in this guide.
  5. Record or correct any mismatch before relying on the output in production.

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.
Request headerRequest code/name, requester, type, department, project, related sales estimate/invoice, currency and rate.
Request linesItems, description, quantity, unit, tax, price, discount, subtotal and total.
SourcingSelected vendors, attachments, public share/request-for-quotation actions and approval status.

Rules the system enforces

  • Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.
  • Purchase-request status changes use the dedicated purchase_request status capability in addition to record access.
  • Department can be mandatory when pur_department_required_condition is enabled.

How to confirm it worked

  • The supported view vendor portal purchase requests 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.
Delete a quotation file in the vendor portalOpen a shared purchase request in the vendor portalOpen the vendor portalCreate a vendorCreate a purchase itemBrowse all Purchase Management guidesExpenses FinanceInvoices PaymentsContracts Documents