Purchase orders overview
Audience: Inventory managers and center admins who procure products from external vendors or move stock between centers via internal orders.
On this page
- Before you begin
- Permissions reference
- PO types
- PO lifecycle
- Worked example β full and partial delivery
- Creating and raising a PO
- Recording deliveries
- Returns
- Editing, copying, and back-dating
- Auto-PO generation
- Tax invoices and barcode printing
- Related articles
A purchase order (PO) is the primary mechanism for procuring products from vendors in Zenoti. The purchase order tracks every step from order creation through delivery and final reconciliation, giving you a complete audit trail for each procurement transaction.
For day-to-day procedures, see Create and raise a purchase order and Manage Procurement. For configuration, see Set up purchase orders.
Before you begin
- Your center must have the Inventory module license active.
- You must have an associated vendor with products assigned to the center where you are creating the purchase order. See Associate vendors and products.
- To back-date a purchase order, the organization must allow PO back-dating and you must have the corresponding permission (see permissions reference below).
Permissions reference
All purchase-order permissions are actions on the Inventory row of the Inventory Manager section. To grant them, open Configuration > Security > Security roles, select the role, and use its PERMISSIONS tab.
| Capability | Action label (UI) | When required |
|---|---|---|
| Create a purchase order | Add | To draft a new PO |
| Modify an existing PO before it is raised | Edit | To change line items, quantities, or pricing |
| Raise a created PO to the vendor | RAISE_ORDER | To move the PO from Created to Raised |
| Modify a raised PO with restrictions | EditPOLimited | To correct details after the PO is sent to the vendor |
| Modify a raised PO without restrictions | EditPOLimitless | To modify quantities, pricing, or delivered values after raise |
| Back-date a purchase order | PO_BACK_DATE (rendered with its raw name) | To set a PO date earlier than today |
| Close a delivered PO | Reconcile | To mark a fully delivered PO as Reconciled |
The action labels above appear exactly as the role editor renders them on the PERMISSIONS tab (Inventory Manager section, Inventory row); some are shown with their raw names, such as RAISE_ORDER and PO_BACK_DATE.
PO types
Zenoti supports two types of purchase orders:
- External β An order placed with an external vendor to purchase products. This is the standard procurement workflow.
- Internal β An inter-center transfer represented as an internal order. Internal purchase orders are created automatically when you raise a transfer order; see Transfer orders overview for how transfers trigger internal POs.
PO lifecycle
Every external purchase order moves through a defined lifecycle:
| Status | Description |
|---|---|
| Created | The purchase order is drafted with vendor, center, line items, quantities, and pricing. It can still be edited freely at this stage. |
| Raised | The purchase order is finalized and sent to the vendor for fulfillment. In organizations that separate creation from approval, centers may create purchase orders while the corporate office raises them. |
| Updated | The order details have been modified after the initial recording β typically through a Modify Delivery action. |
| Partially delivered | Some but not all ordered products have been received. The status displayed in the order listing is synthesized from the delivery record β it does not correspond to a separately stored status value. Stock at the receiving center increases by the received quantity; the remaining quantity stays open against the order. |
| Delivered | Products are received from the vendor. Zenoti supports both full and partial deliveries. |
| Reconciled | The purchase order is closed for further modification. |
A PO moves from Delivered to Reconciled either manually, by choosing the option on the delivery screen that records the delivery and closes the order in one step, or automatically when all line items are fully received and the organization setting that auto-reconciles fully delivered POs is enabled.
For the per-status editable-field detail (which fields you can change while the PO is in each status), see Manage purchase orders β Editable fields by PO status. For the delete-eligibility rule, see Delete a purchase order.
Full and partial deliveries
- Full Delivery β All ordered products arrive in a single shipment. The purchase order moves to Delivered status.
- Partial Delivery β Only some products arrive. Recording the delivery moves the order on and it is shown as Partially delivered while the remaining quantity stays open against it. Each partial delivery creates a history record tracking received quantities per line item.
Worked example β full and partial delivery
A center raises a PO for 12 units of a shampoo product:
- Day 1 (Created): Inventory manager drafts the PO with 12 units. Status: Created.
- Day 2 (Raised): Manager raises the PO and emails it to the vendor. Status: Raised.
- Day 4 (Partial delivery): Vendor delivers 8 units. Manager records delivery of 8 units. The order now shows as Partially delivered with 4 units outstanding.
- Day 7 (Full delivery): Vendor delivers the remaining 4 units. Manager records the delivery and closes the order in one step. Status: Reconciled.
- Outcome: Store quantity for the shampoo product increases by 8 on Day 4 and by 4 on Day 7. The PO detail screen shows two delivery history rows and the perpetual weighted average cost (see Inventory costing and valuation) recalculates at each receipt.
Creating and raising a PO
- Create a purchase order by selecting a vendor and adding products with quantities and pricing.
- Use the recommended quantity feature to auto-calculate order quantities based on desired stock levels. The formula is Recommended Qty = Desired Level - (On-hand Qty + Undelivered Qty), where "Desired Level" is the informal label for the Reorder optimum level field. When the result is zero or negative, no quantity is suggested for that product.
- Raise the purchase order to change its status from Created to Raised. Optionally email the order to the vendor during the raise β see Email orders to vendors for template configuration.
- Bulk raise multiple purchase orders simultaneously across vendors. See Raise purchase orders in bulk.
Recording deliveries
- Record full or partial deliveries against a raised purchase order. Received PO quantities land in the Store location by default; to move stock to the retail Floor, run a stock adjustment after receipt (see Adjust stock and Store and floor inventory).
- Assign batch numbers and expiry dates to received products during delivery (for batch-tracked items β see Configure batch and expiry management).
- A goods received note (GRN) number is auto-generated for each delivery if the organization-level GRN auto-generation setting is enabled.
- Modify delivery details after initial recording if corrections are needed. Modifications are limited after the PO is Reconciled.
Returns
- Create a return purchase order linked to the original order to send products back to a vendor.
- Return purchase orders reduce the Store quantity when processed and maintain a link to the original order for audit purposes.
Editing, copying, and back-dating
- Limited edit β With the EditPOLimited action, users can modify basic purchase order details after the order is raised.
- Limitless edit β With the EditPOLimitless action, users can modify all purchase order details including delivered quantities.
- Copy PO β Duplicate an existing purchase order, optionally targeting a different vendor or center.
- Copy PO to Transfer Order β Convert a purchase order into a transfer order, setting the current center as either the transfer source or destination. This option requires the Enable product transfers between centers organization setting and is hidden for partially delivered orders.
- Delete PO β Remove a purchase order that has not yet been delivered.
- Back-date PO β With the PO_BACK_DATE action (rendered with its raw name), users can change the purchase order date retroactively for accounting purposes. Back-dated POs appear in the order history with their original creation date; the back-dated value is used for stock-value and aging reports.
Auto-PO generation
Zenoti can automatically generate purchase orders when product stock levels fall below configured alert thresholds. The system compares the current on-hand quantity against the Reorder minimum level for each product-center combination. When stock drops below the minimum, the auto-PO feature uses the Recommended Qty formula above and creates purchase orders for the appropriate vendors.
Auto-PO, auto-transfer, and manual PO can coexist in the same organization. Auto-PO triggers when stock falls below the minimum; auto-transfer triggers when a surplus center can cover a deficit center's shortfall; manual POs are always available to override either.
To learn how to set up automatic ordering, see Configure automatic orders and Alerts and notifications.
Tax invoices and barcode printing
- Generate a tax invoice for delivered purchase orders to document the procurement transaction.
- Print barcode labels for products received through a purchase order delivery. See Configure barcode printing.
Related articles
Required next steps
Optional configuration
Related concepts