Vendor portal and authentication

Open an order return in the vendor portal

Review return lines, status and refund information.

Audience: Vendor contactsPermission: Authenticated active vendor contact and enabled portalModule v1.7.9
Exact navigationVendor Portal → Order Returns → open return
Before you begin
  • 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 this guide covers

Review return lines, status and refund information. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Vendor Portal → Order Returns → open return.
  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, 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.
Return sourceReturn type, related purchase order/invoice or other source, vendor and selected items.
Return detailQuantity, warehouse where available, reason, amount, status, attachments and refund records.

Code-backed validations and workflow rules

  • Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.
  • Order-return states exposed by the register include Draft, Processing, Confirm, Shipping, Finish, Failed, Cancelled and On hold.
  • Approval and refund actions are separately validated from basic record editing.

Expected result and verification

  • The supported open an order return in the vendor portal 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.