All modules
Modules 07 and 08

Procurement and Warehouse

Controlled buying and stock

Everything on the shelf, and everything on order

Move approved demand into purchasing, and record materials used and stock movements.

Purchase demand, approval thresholds, the order placed in your own ERP, delivery notes, partial receipt, quality rejection, and operating-source links stay controlled through the buying cycle. Reservations, issues, receipts, transfers, adjustments, minimum stock, costing, and work-order consumption run through controlled stock movements.

1 ledgerfor the stock and the accountability
A one-minute film of the Procurement and Warehouse module. The data shown is for demonstration.
The problem it addresses

Stock and accountability beside your ERP

Before a system, parts are issued on paper. After it, issue and consumption are recorded against the work order.

CAFMPRO does not replace your ERP. One ledger keeps the stock and the accountability: every movement, and who made it, valued, beside any ERP you use.

When stock runs low, it becomes a purchase request, approved before anything is ordered. It travels through your own ERP, whichever you use, and comes back to the operations team as material. Full integration is discussed in detail.

Who uses it

Each role on its own screen

Supervisor

Requests the material from the warehouse against the work order.

Store manager

Sees what is asked, and approves.

Storekeeper

Issues the material to the technician by name, starts the purchase request from the low-stock alert, and receives deliveries into a named store and slot.

Technician

Confirms what he actually used, so the store and the job agree.

Commercial manager

Reads what is asked and why, then approves. Nothing is ordered before that.

Your purchasing team

Places the order in your own ERP.

Operational story

How the module works in practice

01

Reserve and issue

Material leaves the store against a reservation tied to a work order: requested, approved, issued, received.

02

Request

When stock runs low, it becomes a purchase request, approved before anything is ordered.

03

Order

Your purchasing places the order in your own ERP, and the purchase order number comes back onto the record.

04

Receive

Material is received on a delivery note, into a named store and slot. Accept or reject lines and pass clean quantities to stock.

Operational value

What the module controls

Procurement turns operational demand into approved supply while ensuring that only accepted quantities proceed into stock and receiving evidence remains traceable. Warehouse protects stock value and technician accountability by reserving before consumption and preserving an immutable movement history for every quantity change.

01

Reserve before consume

Work-order demand is committed before issue, keeping available and reserved quantities commercially meaningful.

02

Movement history is immutable

Receipts, issues, transfers, and adjustments preserve source, user, quantity, time, and reason.

03

Costing stays controlled

FIFO and weighted-average methods support consistent stock valuation across accepted movements.

04

Approval follows value

The request routes through the correct authority based on configured thresholds and purchasing context.

05

Demand keeps its source

Maintenance, PPM, events, warehouse minimums, and direct requests can retain the reason the purchase was raised.

06

Receipt has a quality gate

Partial, accepted, rejected, and outstanding quantities remain explicit before stock is updated.

Expected operational benefit

What the operation gains

See a purchase request go out and come back as material

A scope workshop and live demonstration, in Arabic or English, on a sample of your own asset register.

The modules in scope are agreed in the Discover step.