B2B portal development for order approvals covers user roles, spending limits and the rules by which a purchase request becomes an order for a supplier. An employee prepares the purchase, an authorised person checks the amount and terms, and transmission follows the required approvals. Before development, agree what happens when a request changes, an approver is absent or transmission to the supplier fails.
This workflow makes sense when a company has several buyers, branches with different budgets or purchases that need a separate decision. If one person handles purchasing independently, extra approval levels may simply delay the work. The rules should reflect the company's actual responsibilities.

When is an approved request sent to the supplier?
In this workflow, only the final approved version of a request is sent to the supplier. The portal should show the buyer's internal decision, transmission and confirmed receipt separately. Receipt by the system does not mean the supplier has accepted the commercial terms or confirmed fulfilment.
The "Send for approval" button starts an internal process. If the warehouse receives a picking instruction at that point, it may prepare goods the manager is still considering. When connecting business software, agree which event allows order processing to begin.
Scroll the table sideways to see all columns.
| Status | Meaning | Who acts |
|---|---|---|
| Draft | The buyer is still editing the items. | The buyer. |
| Awaiting approval | The request needs a decision from an authorised person. | The assigned approver. |
| Returned for changes | A change is required, with a reason provided. | The buyer. |
| Approved, awaiting transmission | Approval is recorded; transmission has not started. | The system or person responsible for transmission. |
| Sent, awaiting receipt acknowledgement | The request has been sent; supplier receipt is not yet confirmed. | The system or person checking receipt. |
| Received by the supplier | The supplier has the final version for processing. | The supplier, under the agreed sales terms. |
Rejection closes the current attempt while retaining the decision. Returning a request for changes lets the buyer continue the same request. The status and notification should make that distinction clear.
Who can prepare, change and approve a request?
Permitted actions are defined by user, partner company and branch. The buyer selects products and an authorised cost centre, while the approver sees the information needed for a decision. Specify whether the approver may edit items or only return the request to its author.
The person who creates employee accounts does not necessarily have authority to approve purchases. If an administrator holds both responsibilities, that should be an explicit agreement. When a manager changes the content, the buyer should be able to see the change.
OWASP's access control guidance recommends minimum necessary permissions and permission checks on every request. In a portal, hiding a button is insufficient: the server must check who is trying to approve which order.
How should an approval limit be defined?
A limit needs an amount, a calculation basis and the period or purchase it applies to. It may cover one order, a project or total monthly purchasing. Specify whether tax and delivery are included and how cancellation affects the remaining budget.
Check several requests awaiting decisions at the same time. Two orders may each fall below a limit while exceeding the available budget together. For aggregate control, define when a request uses part of the budget and when it releases it. Partial approval also needs a rule: which items proceed and what happens to the rest.
Where terms differ by branch, approval should use the appropriate price list. We explain this in our guide to customer-specific prices and product ranges.
What if the amount changes after approval?
A change affecting the approved amount or purchasing responsibility should trigger the agreed review. The portal keeps the previous version and shows what changed, so the approver knows which purchase their decision covers.
In a fictional example, a branch requests consumables worth RSD 48,000. The manager's limit is RSD 50,000. Both amounts use the same agreed calculation basis. After approval, the buyer adds items and the total rises to RSD 56,000.
The proposed workflow returns the new version to someone with sufficient approval authority. Only the final approved version is sent to the supplier. Consider changes to the delivery address or cost centre too: the amount may remain unchanged while responsibility shifts. A minor internal note may be changed without renewed approval if the company accepts that rule.
Does approval reserve the price and stock?
Reservation depends on the agreement with the supplier and what its system supports. Establish whether a pending request holds the price and stock, how long the hold lasts and what happens when it expires. If there is no reservation, the buyer should know that availability and price will be checked again.
Agree what happens if an item is no longer available or its price increases. Changes outside the approved terms return for review under the buyer's rules. Approval should not automatically transfer to a replacement product simply because it costs the same.
Who approves purchases when the manager is away?
An assigned substitute approves within a defined period and scope. They should use their own account, so the decision remains attributable. A reminder can flag a delay; elapsed time alone does not grant approval unless that rule has been explicitly agreed.
For urgent purchases, define a visible exception process with a reason and a responsible person. If an exception is approved by phone, decide who records it and what evidence is required. This does not permanently extend the buyer's permissions for later requests.
What should be checked before business buyers start using the portal?
Walk through the complete process with a buyer, an approver and the person processing purchases at the supplier. Record the expected outcome for each scenario and check records on both sides. The following are proposed tests for the agreed scope:
- A user without permission for the relevant company or branch cannot view or approve the request.
- A person without sufficient approval authority cannot confirm the purchase.
- Changes to the amount, address or cost centre trigger the agreed review.
- A double click or repeated transmission attempt does not create two orders.
- A connection failure leaves a visible status and a receipt-checking procedure before transmission is retried.
- The supplier receives the final version, while the buyer can see its status and decision history.
While some buyers still send the same requests by email, the team needs one processing record. Our guide to introducing a B2B portal alongside email orders covers that transition and checking for duplicates.
What should you prepare for an estimate?
Prepare one routine request, one that exceeds a limit and a list of the people involved. Add the branches, reservation rules and the name of the software receiving orders. Examples can exclude real customer data.
When discussing B2B portal development, explain who makes the decision and which changes require another approval. This lets us work through the steps from purchase preparation to confirmed supplier receipt and distinguish the first release from later additions. Send the workflow for a project estimate.
