Procurement

Procurement in GreenVee has two distinct records: a Procurement Request (the internal demand) and a Purchase (the formal order placed with a supplier). They work in sequence — a need is identified, then actioned.

Procurement Request

A Procurement Request is an internal record that says: “we need this material for this task.” It does not automatically place an order — it signals demand that the procurement team then acts on.

Every Procurement Request is one of two types:

Type	What it means
STOCK	The material already exists in the warehouse — pull it from stock
PURCHASE	The material needs to be bought externally — create a Purchase

Key fields

Field	What it means
Variant	Which specific product is needed (the SKU-level item)
Project	Which project this demand belongs to
Type	STOCK or PURCHASE — how this demand should be sourced
Quantity	How many units are needed
Currency	Currency used for this request’s pricing context
Address	Delivery address for this request
Due Date	When the material is needed on site
Earliest Date	The earliest date the material can be delivered or picked up
Technical Structure Good	Optional link to the Required Good entry on a Technical Structure node, tying the demand to a physical installation point

For Engineers

When you define a Required Good on a Technical Structure node, that captures the design-level demand for a specific Variant. Procurement Requests are then raised via the procurement form to fulfil that demand — either from stock or by placing a Purchase. The Technical Structure Good can be referenced on the Procurement Request to keep the link between design and sourcing visible.

For Finance

Procurement Requests with type PURCHASE are the upstream signal for budget forecasting — they tell you what is going to need a Purchase before one is actually raised.

Purchase

A Purchase is a formal purchase order for a physical product on a project. It is created when a Procurement Request of type PURCHASE is actioned, or directly by the procurement team.

State machine

A Purchase moves through a much richer set of states than a simple approval flow. The main path runs from drafting through ordering, delivery, inspection, and payment, with several states covering exceptions:

State	Meaning
Draft	Being prepared, not yet sent to a supplier
Requested	Submitted for internal approval
Approved	Approved internally, ready to be placed with a supplier
Rejected	Turned down during internal approval
Ordered	Sent to the supplier, awaiting confirmation
Order Confirmed	Supplier has confirmed the order
Partially Delivered	Some, but not all, of the ordered quantity has arrived
Delivered	The full ordered quantity has arrived
Under Inspection	Delivered goods are being checked before acceptance
Accepted	Inspection passed — goods are accepted into the project
Rejected at Inspection	Inspection failed — goods did not meet requirements
Invoiced	The supplier’s invoice has been received
Paid	The invoice has been paid
Cancelled	The purchase was called off before completion
Returned	Accepted goods were later sent back (wrong item, damaged, etc.)
Disputed	A problem exists that is being resolved before the order can close
Expired	The purchase was not actioned in time and lapsed

Note

Rejected, Rejected at Inspection, Cancelled, Returned, Disputed, and Expired are exception states — a Purchase can land in any of them depending on what goes wrong and when.

Key fields

Field	What it means
Title	A descriptive name for the purchase order
Purchase Number	A user-facing reference number for the order
State	Current status (see table above)
Project	Which project this purchase is for
Variant	The specific product being purchased
Quantity	Number of units ordered
Delivered Quantity	Number of units actually delivered so far
Returned Quantity	Number of units sent back
Unit Price	Net price per unit from the supplier
Currency	Currency the prices are quoted in
Tax Rate	Applicable tax percentage
Discount	Discount percentage applied to the order
Additional Charges	Extra charge percentage applied on top (e.g. shipping)
Key Dates	Requested, ordered, delivered, invoiced, paid, and cancelled dates

For Finance

Unit Price × Quantity gives the line total before tax, discount, and additional charges. These figures feed directly into project cost tracking.

Caution

A Purchase in Disputed state is still open and unresolved. Make sure disputed purchases are reviewed promptly — they affect both your budget and your delivery schedule.

How they connect

Engineer defines Required Good on Technical Structure node (Variant + quantity)
  → Procurement team raises Procurement Request (type: PURCHASE)
    → Procurement team creates Purchase and sends to supplier
      → Supplier delivers goods → Purchase moves to Delivered
        → Purchase moves through Inspection to Accepted
          → an inbound Stock Movement updates warehouse inventory

The Procurement Request stays on record throughout, linking the original demand from the project plan all the way to the goods in the warehouse. See Warehouses & Stock for how Stock Movements update on-hand quantity.