In B2B, a single person rarely places the order; an entire team does: for complex procurement, a buying group typically includes 6 to 10 decision makers (Gartner). At the same time, around 80% of all B2B sales interactions are expected to run through digital channels by 2025 because buyers want control and speed (Gartner). Together these create a clear requirement for every professional B2B online store: orders must be placed digitally but released under control. That is exactly what approval workflows with budgets, role hierarchies, and multi-step authorization deliver. This guide shows how B2B order approval works technically and organizationally, why it prevents uncontrolled spending (maverick spend), and how we implement such workflows in Shopware and custom store solutions.
Why B2B Order Approval Decides Budget Discipline
The economic lever behind approval workflows is spend control. Through what is known as maverick spending, that is, procurement outside approved contracts and channels, companies lose up to 10 to 20% of their negotiated savings (Ivalua). In extreme cases, a large share of all invoices stems from such uncontrolled orders. Mapping approval processes digitally in the store closes exactly this gap at the source: before an order leaves the building, the system checks budget, role, and contract reference.
This need for control meets a growing self-service share. 78% of business buyers say their company is more careful with spending today than before (Gartner), and a rising share runs six-figure orders through self-service (McKinsey). Without digital approval, a conflict of goals would arise: either fast but uncontrolled orders, or controlled but slow processes. Approval workflows resolve this conflict by combining speed and control.
By contrast, the status quo of many organizations is inefficient: how long a purchase takes depends heavily on the processes. Top-performing organizations place an order in a median of around eight hours, while other organizations need a median of around eleven hours to get from the requirement to the placed order (APQC). Manual approvals by email or phone cost time and create no traceability. A workflow integrated into the B2B store makes every decision documented, rule-based, and auditable.
Up to 20% of savings lost to maverick spend (Ivalua), around eight hours per order at top performers versus around eleven hours at other organizations (APQC), and 78% of buyers with higher spending discipline (Gartner): digital order approval addresses all three at once by moving control directly into the ordering process.
Mapping Roles and Hierarchies Cleanly
The foundation of every approval workflow is the customer's organizational structure in the store. A single customer account is not enough in B2B, because behind it stands an entire company with departments, locations, and different authorizations. Since a buying group typically includes 6 to 10 decision makers (Gartner), the store must be able to manage several users per company account with clearly defined roles.
Administrator
Manages the company account, creates users, defines budgets and approval rules. The admin is usually based in purchasing or finance.
Approver
Approves or rejects orders that exceed a threshold. Several approvers form a chain for higher amounts.
Buyer
Builds carts and places orders. Within their budget without approval, above it automatically routed for authorization.
Location / department
Roles can be staggered per branch or cost center so that each unit gets its own budgets and approvers.
Observer
Controlling or accounting receive read access to order and approval history without placing orders themselves.
Deputy
If an approver is absent, a defined deputy steps in so the process does not stall and orders are not left waiting.
These roles are organized in a hierarchy: a buyer reports to a department lead, who in turn may report to management. The workflow follows this structure automatically and routes an order to the relevant level. It is important to derive the roles from the customer's real organizational structure, not from technical assumptions. Well-designed role modeling is closely related to the B2B self-service portal, in which customers manage their own users and permissions.
Defining Budgets and Thresholds
The core of order approval is budgets and thresholds. A threshold defines the order value above which approval becomes necessary: orders below the limit pass through without delay, while those above it automatically enter the approval process. This keeps day-to-day business fast while large expenditures are controlled. This is exactly where the prevention of maverick spend, which costs up to 20% of savings (Ivalua), comes in.
Budgets go one step further: they define a spending limit per user, department, or period. A buyer with a monthly budget of, say, 20,000 euros sees their remaining allowance in the store and can order freely only within this limit. If an order exceeds the budget, approval applies again. This combination of budget and threshold reflects the typical approval logic in B2B.
| Control mechanism | Function | Typical use |
|---|---|---|
| Threshold | Approval above a defined order value | Standard for all orders over X euros |
| User budget | Limit per buyer and period | Operational buyers with a fixed allowance |
| Department budget | Limit per cost center | Branches, project teams |
| Product rule | Approval for specific ranges | Capital goods, regulated items |
| Multi-step chain | Several approvers in sequence | High amounts, multiple levels of responsibility |
Thresholds set too low create unnecessary approvals and frustration, while thresholds set too high let control run empty. A multi-level staggering has proven effective, for example approval above 1,000 euros by the department lead and above 10,000 euros additionally by management. Customer-specific assortments can be combined with product rules so that capital goods, for instance, always require approval regardless of the amount.
Multi-Step Authorization as a Workflow
For high amounts, a single approval is rarely enough. Multi-step authorization routes an order through a chain of approvers who must agree in sequence or in parallel. This reflects the reality in which B2B buying groups include 6 to 10 decision makers (Gartner) and decisions are spread across IT, finance, purchasing, and management. The workflow ensures that every responsible level documents its approval.
- Place the order - the buyer fills the cart and submits the order, just like a normal checkout.
- Rule check - the system automatically checks budget, threshold, and product rules and decides whether approval is needed.
- First approval stage - if the order is above the limit, it goes to the first responsible approver, such as the department lead.
- Further stages - for very high amounts, additional approvers follow according to the hierarchy until the final stage agrees.
- Notification - all parties are automatically informed about status, queries, or rejections.
- Release and handover - after full agreement, the order is released and handed over to ERP, inventory management, and shipping.
Transparency in the process is decisive. Every party can see the status of their orders at any time, and approvers receive a clear list of open items with all relevant information. If an approver rejects, the buyer receives a reason and can adjust the order. This traceability is also why digital approvals are superior to manual email loops: they leave a complete audit trail.
Technical Implementation in Shopware and Custom Stores
Technically, order approval can be implemented in several ways. In Shopware, the B2B functionality maps company accounts, roles, and approvals; for individual requirements we develop the logic as a tailored extension. In both cases, the core consists of a state machine that moves an order through the states open, in approval, released, and rejected, evaluating the stored rules at each transition.
<?php
// Simplified approval logic at checkout
public function evaluateOrder(Order $order, BuyerContext $ctx): ApprovalDecision
{
$total = $order->getGrossTotal();
$budget = $ctx->getRemainingBudget();
// Budget or threshold exceeded?
if ($total > $budget || $total > $ctx->getThreshold()) {
$chain = $this->buildApproverChain($ctx, $total);
return ApprovalDecision::requiresApproval($chain);
}
// Product rule: certain ranges always require approval
if ($this->hasRestrictedItems($order, $ctx)) {
return ApprovalDecision::requiresApproval(
$this->buildApproverChain($ctx, $total)
);
}
return ApprovalDecision::autoRelease();
}The approval engine is triggered via events: as soon as an order changes status, the system fires an event that sends notifications and triggers follow-up actions. We described this event-driven architecture in detail in the webhook and event-driven integration; it ensures that approvals, ERP handover, and email dispatch run decoupled and reliably. For latency-critical checks, such as budget queries directly at checkout, rules can also be evaluated close to the user via serverless edge functions.
Order approval reaches its full value only in combination with downstream systems. After approval, the order is handed over to ERP systems such as SAP Business One or the JTL inventory management. Budgets and cost centers can be synchronized with the ERP so that the released allowance always stays current.
Connecting to the Buyers' Procurement Systems
For large customers, approval does not end in the store but often begins in the buyer's own procurement system. This is where procurement integration comes in: the buyer selects products in the supplier store, the filled cart returns to their procurement system, and there the order runs through the internal approval process before it comes back as a binding order. This bridge is built by PunchOut catalogs via OCI and cXML.
Both worlds complement each other: some customers use the approval integrated into the store, others bring their own approval process from their procurement system. A well-designed B2B store supports both models. Since around 80% of B2B sales interactions are expected to run through digital channels by 2025 (Gartner) and PunchOut is the decisive signal of transaction readiness for large buying organizations, this flexibility is not a nice-to-have but a prerequisite for selling to large business customers.
Those who master both paths can offer their customers seamless order approval, whether it takes place internally in the store or externally in the procurement system. Complemented by fast reorders via the quick order for regular customers, this creates an ordering process that serves speed and control at the same time.
Economic Value and Measurable Effects
The value of digital order approval is measurable. Organizations with comprehensive procurement automation achieve 25 to 30% lower process costs and 50 to 80% shorter cycle times (Spendflo). Benchmarks show how wide the gap is: top-performing organizations place an order in a median of around eight hours, while other organizations need a median of around eleven hours (APQC). At the same time, a manually processed item costs significantly more than an automated one.
On top of this comes the effect on contract compliance. According to the Hackett Group, top organizations manage 97.3% of their direct spend, while other companies have only around 70% under control (Hackett Group). This spend-under-management ratio is directly linked to better terms, because more volume runs through negotiated contracts. Approval integrated into the store is one of the most effective levers for raising this ratio.
Around eight hours per order at top performers instead of around eleven hours at other organizations (APQC), 25 to 30% lower process costs (Spendflo), and up to 97.3% managed spend among top performers (Hackett Group): digital order approval combines the speed of digital B2B sales, where around 80% of interactions are expected to run through digital channels by 2025 (Gartner) with the control purchasing needs.
For suppliers, this is a sales argument: a store with clean order approval lowers the entry barrier for large buying organizations that are not even allowed to order digitally without approval processes. As an agency with a B2B focus from Lower Saxony, Germany, we design and develop these workflows individually, from role modeling through budgets and thresholds to multi-step authorization and the connection to ERP and procurement systems. This turns the B2B store into a reliable ordering channel that serves both speed and spend control.
This article is based on data from: Gartner (number of decision makers per buying group, self-service share of B2B transactions, buyer spending discipline, rep-free buying preference), Ivalua (maverick spending and lost savings), APQC (order cycle time of top-performing and weaker organizations), McKinsey (six-figure self-service orders), Spendflo (process costs and cycle times of procurement automation), and the Hackett Group (spend-under-management ratio of top organizations). The figures cited may vary depending on industry, company size, and implementation.
Approval Workflows as a Foundation for B2B Growth
B2B order approval is far more than a technical formality. It connects the expectation of fast self-service with the need for controlled spending and thus makes the online store usable for professional buying organizations in the first place. Those who cleanly map roles, budgets, thresholds, and multi-step authorization win customers who could not order digitally without these processes, while increasing contract compliance within their own assortment.
The path there leads through a precise analysis of the customer's organizational structure, a realistic staggering of thresholds, and an architecture that cleanly decouples approvals, ERP handover, and procurement connection. This is exactly where we support you with our B2B e-commerce expertise: from concept through development to integration into your existing system landscape.
Frequently Asked Questions about B2B Order Approval
B2B order approval is a digital approval workflow in the online store that can check whether an order may be released. Based on budgets, thresholds, and roles, the system decides whether an order is placed directly or must first pass through one or more approvers. This helps reduce uncontrolled spending, which according to Ivalua can cost up to 20% of savings.
That depends on the size of the organization and the amounts involved. Since B2B buying groups typically include 6 to 10 decision makers (Gartner), two to three stages often make sense, such as department lead and management. As a rule of thumb: as few stages as possible, as many as necessary, so the process stays controlled but not sluggish.
In Shopware, company accounts with several users, roles, and budgets can be mapped so that orders above a threshold are automatically routed for approval. For individual requirements we develop the logic as a tailored extension. In both cases, a state machine maps the workflow from open through in approval to released.
Budgets define a spending limit per user, department, or period, while thresholds define the order value above which approval becomes necessary. If an order exceeds the budget or threshold, the approval process applies. This combination ensures that routine orders pass through quickly and only larger expenditures are controlled.
Yes. Via PunchOut catalogs using OCI or cXML, the cart can be transferred from the supplier store into the buyer's procurement system, where the internal approval process applies. A well-designed B2B store supports both the approval integrated into the store and the connection to external procurement systems.
Procurement automation typically lowers process costs by 25 to 30% and shortens cycle times by 50 to 80% (Spendflo); in benchmarks, top-performing organizations place an order in a median of around eight hours, while other organizations need a median of around eleven hours (APQC). Contract compliance also rises, which can lead to better terms because more volume runs through negotiated contracts.