Wrike is not a dedicated procurement system, but your team can configure it for purchasing. Here are some approaches that work.
A full procurement workflow in Wrike
This first setup uses a purchase request form as the entry point. Every purchase starts with a form submission that captures all the data the procurement team needs.
Automations then move the request from the intake state to active and route it into the associated job.
All drawings, quotes, shipping information, and comments are added to the purchasing task as the order progresses. Project managers can see when procurement due dates are approaching. Receiving staff can see what should have arrived. Floor staff can see whether required parts have hit the build bays. Spare parts history is searchable.
The custom workflow covers the full range of procurement states such as approvals, supply problems, chasing confirmations, and partial deliveries.
The workflow structure that works for purchasing
An effective workflow structure for purchasing looks something like this: New Request, Approval Requested, Request Approved, PO Issued to Supplier, PO Acknowledged, Ordered, At Goods In, QC Passed, Partially Arrived, Fully Arrived, To Be Returned, and Cancelled.
Custom fields can be used heavily to categorise each purchase. An approval built into the workflow automatically sends approval requests to the procurement manager when a request reaches the Approval Requested status.
The practical starting point is to map your current procurement stages and build a custom workflow that mirrors them. Create a request form that captures what the procurement team needs at intake. Connect the two with an automation that creates a procurement task from the form submission and places it in the right project. Add custom fields for the information tracked at the order level: supplier, budget code, expected delivery, and PO number.