Purchase Orders

Section: Purchase Management
URL: /admin/purchase/purchase_order
Page title: (2) Comenzi achiziție

Overview

Purchase Orders (PO) are formal commitments to buy from a vendor at agreed terms — the basis for goods receipt and vendor invoice matching.

Business value

Formal commitments to buy — the legal and operational document that triggers vendor delivery, goods receipt, and invoice matching. The cornerstone of procure-to-pay control.

Who uses it: Procurement, buyers, finance, warehouse
Key benefit: Prevents maverick spend (off-PO purchases) and enables three-way invoice matching that catches errors and fraud.
Metrics it influences: % spend on PO, PO cycle time, three-way match rate

Typical use cases:

PO → Goods Receipt → Vendor Invoice three-way match
Approval routing for POs over a threshold
PO commitment reporting for cash-flow forecasting

At a glance

Accessing this module

From the admin sidebar, navigate to Purchase Orders, or open the URL directly:

/admin/purchase/purchase_order

List view

The list view shows existing purchase orders records. Use it to search, filter, sort, and bulk-act on items.

Common actions

View existing records — open Purchase Orders from the sidebar to see the list view.
Search and filter — use the search box and column filters to find records.
Create a new record — click the Add / New button (or follow the "Create" URL above) and fill in the required fields.
Edit a record — click a row to open the detail view, then use the edit action.
Delete a record — use the row's delete action; deletion may be soft or hard depending on the module.
Bulk operations — select multiple rows via the checkboxes and apply a bulk action from the toolbar (export, delete, status change, etc., where supported).

API

This module is available via the REST API.

Authentication. All API requests require the header authtoken: <token> (generate one at /admin/api/api_management). Base URL. https://your-domain.tld/api/

Key endpoints:

Method	Path	Purpose
`GET`	`{{base_url}}purchase/items?page=1&per_page=50`	List
`GET`	`{{base_url}}purchase/items/{{purchase_record_id}}`	Get one
`GET`	`{{base_url}}purchase/items/search/{{search_key}}`	Search
`POST`	`{{base_url}}purchase/items`	Create
`PUT`	`{{base_url}}purchase/items/{{purchase_record_id}}`	Update
`DELETE`	`{{base_url}}purchase/items/{{purchase_record_id}}`	Delete
`GET`	`{{base_url}}purchase/vendors?page=1&per_page=50`	List
`GET`	`{{base_url}}purchase/vendors/{{purchase_record_id}}`	Get one
`GET`	`{{base_url}}purchase/vendors/search/{{search_key}}`	Search
`POST`	`{{base_url}}purchase/vendors`	Create
`PUT`	`{{base_url}}purchase/vendors/{{purchase_record_id}}`	Update
`DELETE`	`{{base_url}}purchase/vendors/{{purchase_record_id}}`	Delete
`GET`	`{{base_url}}purchase/vendor_items?page=1&per_page=50`	List
`GET`	`{{base_url}}purchase/vendor_items/{{purchase_record_id}}`	Get one
`POST`	`{{base_url}}purchase/vendor_items`	Create
`PUT`	`{{base_url}}purchase/vendor_items/{{purchase_record_id}}`	Update
`DELETE`	`{{base_url}}purchase/vendor_items/{{purchase_record_id}}`	Delete
`GET`	`{{base_url}}purchase/purchase_request?page=1&per_page=50`	List
`GET`	`{{base_url}}purchase/purchase_request/{{purchase_record_id}}`	Get one
`POST`	`{{base_url}}purchase/purchase_request`	Create

See the full payload schemas, query parameters, and example responses in the API reference (Purchase).

Captured: 2026-05-10T09:51:26.776Z · Source: demo.crmconnect.io/admin/purchase/purchase_order