Procurement

Procurement turns a need into a delivered item without losing the thread: a requisition, a request for quotation, a comparison of offers, a purchase order with approval, the delivery and, when necessary, the return. Every supplier sits in one register with a risk status built from the record.

Two people reviewing a tablet at a loading dock beside stacked crates and a truck
Module
  • Requisitions with approval paths
  • Supplier register with risk status
  • RFQs and side-by-side offer comparison
  • Purchase orders, inbound deliveries and returns

From need to delivery on one thread

A purchase usually starts in an email, continues in a spreadsheet of offers and ends in the ERP, with the reasoning for the choice lost along the way. In Hurukan a requisition becomes a request for quotation, the answers are collected against it, the comparison is kept, and the purchase order carries a link back to all of it. When somebody asks a year later why this supplier was chosen, the answer is in the record.

Suppliers you can judge

The supplier register is built from what actually happened. Late deliveries, rejected batches, expiring certificates and concerns noted by colleagues add up to a risk status that shows its evidence. An agent comparing offers takes that status into account, so the cheapest offer from a supplier with three open non-conformances is shown with those non-conformances next to its price.

Approval where money is committed

Requisitions and purchase orders are routed for approval by value, category and risk. Agents prepare and check — against the budget in Finance, against stock and reservations in Inventory and Logistics — but sending an order that commits the company’s money is always a person’s decision.

After the order

Inbound deliveries are checked against the purchase order on arrival. Differences become tasks with an owner, and returns to the supplier are recorded with their reason, so the supplier’s record reflects what happened and the inbound invoice can be matched against what was actually received.

What the module covers

01

Requisitions

Needs raised by people or proposed by agents from stock levels and plans, routed for approval by value and category.

02

Supplier register

Every supplier once, with contacts, documents, certificates and a risk status built from delivery performance, quality and expiring paperwork.

03

Requests for quotation

RFQs sent to selected suppliers from the record, with answers collected against the same request instead of in separate inboxes.

04

Offer comparison

Offers set side by side on price, lead time, terms and supplier risk, with an agent's summary of the differences and the sources it used.

05

Purchase orders with approval

Purchase orders prepared from the chosen offer and approved by a person according to value and risk before they are sent.

06

Deliveries and returns

Inbound deliveries checked against the order, and returns to suppliers recorded with the reason and the non-conformance behind them.

Questions

Can an agent place a purchase order?

An agent can prepare it from the chosen offer and check it against budget and stock. Sending a purchase order commits the company's money, so a person approves it.

How is supplier risk assessed?

From the record: late or incomplete deliveries, quality non-conformances, expiring certificates and documents, and concerns logged by people. The status shows the evidence behind it.

Is procurement connected to finance?

Yes. Approved purchase orders count as committed spend against the budget, and inbound invoices are matched to the order and the delivery before they are approved.

Build the company's operating system with us

Hurukan is pre-launch. If you run a company and want a sovereign, agentic system rather than another suite, we would like to hear what you need.