Procurement Work
Procurement work is the full path from planned demand to delivery. In Grinea, that path is split across records so each team works in the part they own.
The main distinction is whether the request comes from a project BOM or from an indirect CAPEX/OPEX need. Both paths eventually use Purchase Requisition, Request for Quotation, and Orders.
Project Purchases
Project purchases begin with Project Profiles and Bill of Materials.
Project Profiles supply the context that later records rely on: project locations, assigned team members, and budget ownership. Bill of Materials turns the project need into planned material and service lines.
The BOM must be active before procurement work can be generated from it. Once it is active, the buyer can create a project Purchase Requisition from eligible BOM line items.
The PR is the first place where planned demand becomes a request to buy. The buyer confirms the selected lines, delivery schedule, and documents before sending it through approval.
After approval, the PR lines move into RFQ staging. Staging exists because one PR does not always equal one RFQ. A buyer may split approved lines by supplier market, category, delivery timing, or sourcing strategy.
Non-Project Purchases
Non-project purchases start directly in Purchase Requisition.
Use this path for CAPEX or OPEX spend that does not belong to a project BOM. The PR holds the business context that a project would normally provide: org unit, cost centre, warehouse, transaction details, line items, delivery locations, and receiving contacts.
CAPEX and OPEX matter because they route to different approval chains. CAPEX has Investment Controller and CEO review before Purchasing Director assignment. OPEX moves through a shorter chain before buyer acceptance.
Once the buyer accepts the assigned work, the rest of the sourcing path looks familiar: approved PR lines move to RFQ staging, suppliers respond, supplier selection is approved, and an order is created.
Status Gates
Statuses are not cosmetic. They decide which actions the app exposes.
A draft BOM cannot create procurement work. A PR that is not approved cannot be staged for RFQ. A draft RFQ has not notified suppliers. A closed PO blocks later receive and reject actions.
When an action is missing, first read the record status and current owner. Most missing buttons are caused by a record not being ready, the user not owning the next action, or required data still being incomplete.