Settings, numbering, PDFs and vendor-portal options

Configure order-return numbering

Set the return-order prefix and next return number.

Audience: Purchasing staffPermission: purchase_settings: EditModule v1.7.9

Exact navigationAdmin Area → Purchase → Settings → Order Return

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

Set the return-order prefix and next return number. 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 → Order Return.
Open the exact setting, option or record named in this guide.
Enter or select the required value; leave unrelated options unchanged.
Save the form and wait for the success response.
Reload the page or open a controlled record to confirm the stored value is being used.

Fields, choices and supported possibilities

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

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