Create a purchase order from a purchase request
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Copy request header/lines and select the vendor.
Where to goAdmin Area → Purchase → Purchase Request → open request → Convert/Copy to Purchase Order
Before you start
- Use an account with purchase_orders capability and purchase-order status capability where applicable 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 helps you do
Copy request header/lines and select the vendor. 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 → Purchase → Purchase Request → open request → Convert/Copy to Purchase Order.
- Select the New, Add, Create or Start action exposed on that screen.
- Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
- Save or submit the form once; correct any validation message rather than bypassing it.
- Go to the resulting record and verify its number, status, totals, files, activity and downstream links.
Fields and options
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.
Order headerOrder name/number, vendor, linked request/quotation, department, project, type, buyer and optional linked clients/sales invoices.
Commercial dataCurrency/rate, items, tax, discount type/value, shipping fee, days owed and totals.
Delivery dataShipping address/country, Incoterm, vendor note, terms, delivery date/status, files and payments.
Rules and limits
- 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.
- Purchase-order status changes require the dedicated purchase_order status capability.
- Delivery states include Undelivered, Pending delivered, Partially delivered and Completely delivered.
- Project can be mandatory when pur_order_project_required_condition is enabled.
Check it worked
- The supported create a purchase order from a purchase request 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.
Related guides
Was this guide useful?Your response is stored only in this browser.