Open Buy Requests
Follow this guide to review purchase-interest 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.
Where to goAdmin Area → Requests & Applications → Buy Requests
Before you start
- Use an account with real_buy_request: View or View Own 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 purchase-interest requests. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Requests & Applications → Buy Requests.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields and options to review
Exact actionOpen Buy Requests
Exact navigationAdmin Area → Requests & Applications → Buy Requests
Module version1.0.0
Access rulereal_buy_request: View or View Own
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Request recordCode, client, property/item, request type, currency, property price, term and inspection choice.
Notes and billingClient note, admin note and billing/shipping data where the form exposes them.
ConversionCheck status and linked customer/property before converting to a contract or invoice.
Rules the system enforces
- The table is loaded through property_request_table.
- Buy and rent requests use separate real_buy_request and real_rent_request capability groups.
- Status changes and conversion actions validate the current request and linked record IDs.
How to confirm it worked
- The supported open buy 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.