Settings, numbering, PDFs and vendor-portal options

Upload the purchase-order PDF logo

Store the logo used by purchase-order PDF output.

Audience: Purchasing staffPermission: purchase_settings: EditModule v1.7.9

Exact navigationAdmin Area → Purchase → Settings → Purchase Order Setting

Before you begin

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 this guide covers

Store the logo used by purchase-order PDF output. 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 → Purchase Order Setting.
Download or inspect the supported template/field requirements before preparing the file.
Choose the Import or Upload action and select the intended file only.
Run validation and correct rejected rows, file types or required values.
Complete the import/upload and review the created records, attachments and any error file.

Fields, choices and supported possibilities

ActionUpload the purchase-order PDF logo

Exact navigationAdmin Area → Purchase → Settings → Purchase Order Setting

Module version1.7.9

VerificationConfirm the saved record, status, output or setting in the same workspace and review any linked activity, file or notification.

Code-backed validations and workflow rules

Save through the module settings form and test with a controlled transaction.
Do not change unrelated purchase options during a scoped configuration update.

Expected result and verification

The supported upload the purchase-order pdf logo 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.