Skip to content

2 · Approval ​

Who acts: approvers in the buyer's company, and its owner for some cases. Starts with: a request or an RFQ award that one of the company's rules catches. Ends with: approved (the orders go out), sent back for changes, or rejected.

Homeowners never see this step. Companies decide their own rules, so a small team might approve nothing and a large one might approve everything over a threshold.

Typical rules ​

The company owner sets the rules. The usual ones are:

RuleWho must approve
Order above an amountAny approver whose personal limit covers it
Order above a higher amountTwo different approvers
Project would go over budgetThe owner
A correction brings in a substitute productAn approver

Each approver can have a personal limit. An approver with a USD 25,000 limit can approve orders up to that amount; above it, the approval waits for someone with a higher limit or the owner.

What the approver sees ​

The whole order before it is placed: the lines, the chosen suppliers, the total, the project and its budget, and the checks that triggered the rule. They then:

  • Approve. The purchase orders are created and sent to suppliers. When two approvers are needed, the first approval waits for the second.
  • Request changes. The request goes back to the buyer as a draft, with the approver's comment.
  • Reject. It goes back with a reason; nothing is ordered.

Nobody approves their own request.

How it ends ​

OutcomeWhat happens next
ApprovedPurchase orders go out: step 3
Changes requestedThe buyer edits and issues again
RejectedNothing is ordered; the reason is kept on the request

The same step applies to RFQ awards: when the buyer picks winning quotes worth more than a rule allows, the award waits here before its purchase orders are created.

A high-level guide: flows, states and rules. Screen-by-screen detail lives in the product.