Buyers and approvers understand the next step.
A request above an agreed threshold needs a decision. Products, amount, company context and the reason for approval must remain connected.
Approver view
Transformer Station Pro
1 unit · Standard
- Request
- NL-2048
- Cost centre
- NL-1100
- Net order value
- €14,800.00
- Approval reason
- Amount above €500
Review the request
- Task
- Review requirement and rule
- Possible decision
- Approve or reject with a reason
Buyer and approver see the same requirement. The next step shows approval as an example decision.
View example decisionAgora connects the buyer’s request with the responsible person’s view. The Nordlicht example considers a €14,800 request against a €500 approval threshold. The public walkthrough explains the same request from both perspectives.
How it works.
Recognise the approval trigger
The purchasing rule explains why ordering cannot continue immediately. In this example, the order value exceeds the configured threshold.
Pass on the request
Items and amount stay attached to the request. The responsible role receives the request to decide.
Make the decision
The responsible person reviews the request and the intended approval or rejection workflow. A reason helps explain the decision.
Return to the buyer
Status and next step are considered again in the original ordering context. The decision does not confirm delivery.
The decision belongs to the original request.
An approval should not be an isolated status. The approver needs the related items and the buyer must be able to find the outcome. The approval sequence previously shown separately is therefore integrated directly into the Nordlicht example.
What we configure for your shop.
- Trigger
- Amount thresholds and other agreed rules determine when a decision is needed.
- Responsibility
- Who may approve or reject each request within the company context?
- Feedback
- Buyers should understand the status, any required correction and the next action.
- Additional approval steps
- Requested substitutes, escalations or multi-stage chains are defined as concrete project scope.
Frequently asked questions.
Can approval be needed when sufficient budget is available?
Yes. Budget and approval thresholds check different rules. A request may fit the financial framework and still require a decision.
Can I make a real decision here?
The public view presents a guided example workflow. A separate test session is offered only after its access and approval workflow has been fully checked.
Fits your workflow.
How should your shop use this feature?
We develop Agora and use it to build your individual B2B shop. Let us discuss the workflow, configuration and integrations you need.
Discuss your shop project