Let’s talk about how we can build your commerce project — tailored to your business, powered by Rigby
In most B2B organizations, the person placing an order is not the person authorized to approve it.
- A junior buyer assembles the cart.
- A department manager reviews the total.
- A finance controller checks it against the quarterly budget.
- For orders above a certain threshold, a VP signs off.
This structure is the default purchasing process for companies of any meaningful size and involves multiple stakeholders.
Yet most B2B eCommerce platforms treat approval workflows as secondary functionality: a feature added late, restricted to premium tiers, or delegated to third-party apps.
The result is that one of the most fundamental B2B requirements is consistently underserved, forcing buying teams back into email threads, Slack messages, and spreadsheets to manage approvals outside the system.
Compare what platforms support complex B2B workflows before committing to an architecture that forces approval flow into external tools, manual processes, or custom-built extensions.
In this chapter, you will discover:
- What functional B2B approval workflow process requires?
- How do leading platforms (Shopify, Magento, OroCommerce & BigCommerce) support multi-level routing and role-based permissions?
- Where platforms' limitations force custom development or third-party dependencies to provide an effective approval workflow?
Key insights
- In most B2B organizations, the person placing an order is not the person authorized to approve it, yet most eCommerce platforms treat approval workflows as a premium add-on, not a core capability.
- Shopify Plus supports only two B2B user roles and has no native user-to-user order approval. Multi-step approval chains require custom development or third-party apps.
- Adobe Commerce has the most developed native approval workflow among the four platforms, but it's exclusive to the paid Commerce edition, starting at $22,000/year, and the configurable conditions are limited.
- BigCommerce B2B Edition provides three predefined buyer roles with basic approval functionality. Independent reviews consistently describe the approval gates as limited, lacking granular controls for complex routing scenarios.
- OroCommerce delivers the deepest approval workflow capabilities – configurable chains, granular role-based permissions, dynamic routing – but implementation requires Symfony expertise and timelines measured in months.
- When platforms can't support approval workflows natively, the workarounds create audit gaps, compliance risk, and order abandonment that directly affect revenue.
What is a B2B approval workflow, and why does it matter?
A B2B approval workflow is a structured process that routes an order through one or more designated approvers before it is confirmed and sent to fulfillment.
In B2B eCommerce, most organizations of meaningful size operate with internal purchasing controls: spending limits per buyer, budget allocations per department, and authorization rules that determine who can commit the company to a purchase.
An eCommerce platform that can't model these controls forces buyers to either bypass their own procurement policies – creating compliance risk – or manage approvals manually outside the platform – adding friction that slows ordering and reduces digital channel adoption.
When the digital channel is harder to use than calling a sales rep, buyers use the phone. It's a platform capability problem.
The business case for automated approval workflows is direct. Faster approvals mean faster order confirmation, shorter cash conversion cycles, and fewer orders abandoned mid-process because an approver didn't see a pending approval request in time.
For teams managing multiple departments and multiple approvers simultaneously, approval workflow software that handles routing automatically removes a significant source of unnecessary delays and manual processes.
As B2B buying becomes more digital – 73% of B2B buyers now willing to place orders over $50,000 through self-service channels – the inability to model internal approval processes within the eCommerce platform becomes a direct barrier to digital channel adoption across multiple stakeholders.
Why approval workflows matter for buyers and sellers
The impact of inadequate approval workflows hits both sides of the transaction.
For the buyer's organization
The absence of proper approval controls forces buyers into one of two positions: bypassing internal procurement policies, which creates compliance risk and audit exposure, or managing those policies manually outside the eCommerce platform, which adds friction and slows down every order.
Neither outcome encourages adoption of the digital channel. When buyers find that managing approvals through the platform is more complicated than their existing manual process, they stop using the platform for anything beyond the simplest transactions.
For the seller
Approval bottlenecks delay orders. Manual workarounds create the risk of order abandonment.
If a buyer's organization cannot manage its own purchasing controls within your platform, it will gravitate toward competitors whose systems accommodate its procurement process.
The selling organization's ability to retain and grow B2B accounts depends, in part, on whether the platform can model the buyer's internal workflow.
Every delayed order, abandoned cart mid-approval, and account that returns to phone ordering because the digital channel doesn't support their review process represents a direct revenue impact.
5 types of approval workflows in B2B eCommerce
Not all approval workflows work the same way. The right workflow type depends on your buyers' organizational structure, order volume, and compliance requirements.
1. Sequential approval workflow
Orders move through a fixed chain of approvers in a defined order. The first approver must act before the request reaches the second, and so on until final sign-off is granted.
This is the most common approval process in organizations with clear hierarchies – department manager, then finance controller, then procurement director.
Sequential workflows give organizations strict control over the entire process, but they slow down when any single approver in the chain is unavailable.
2. Parallel approval workflow
The approval request is sent to multiple approvers simultaneously. The order proceeds once all required approvals are obtained, or once a defined minimum number of approvers have signed off.
Parallel workflows reduce the overall time to final approval in organizations where multiple departments need to review an order independently. They work well for high-value orders where compliance requires sign-off from multiple stakeholders at the same time.
3. Conditional approval workflow
Approval routing changes dynamically based on order characteristics: order value, product category, cost center, buyer role, or department. An order under a set threshold proceeds automatically. An order above it triggers a specific approval chain.
Conditional workflows are the most flexible and the most demanding to configure. They mirror how B2B purchasing actually works across multiple departments with different spending limits and approval criteria. They're also the workflow type that most platforms struggle to support natively without custom development.
4. Automatic approval workflow
Orders that meet predefined criteria – buyer role, order value below a threshold, pre-approved supplier – are confirmed automatically without requiring manual approval.
Automatic approval removes unnecessary delays for routine, low-risk transactions. A senior buyer reordering standard consumables under their spending limit shouldn't need to wait for a manager to approve a $200 order. Automating low-risk approvals frees your team members to focus on reviewing orders that require judgment.
5. Exception-based approval workflow
All orders proceed automatically unless a specific condition triggers a review, like an unusual product combination, an order from a new supplier, a quantity that exceeds typical patterns, or a total that approaches a budget limit.
Exception-based workflows reduce approval overhead across high-volume B2B operations while maintaining controls where they matter. They require a well-defined set of exception rules and proactive alerting when an order is flagged for review.
5 key components of an effective B2B approval workflow
Before evaluating what platforms deliver, it's worth defining what a functional approval workflow needs to support in a B2B eCommerce context.
1. Multi-level routing with configurable approval rules
The approval path should change depending on the order.
- An order under $5,000 might need one approver.
- An order between $5,000 and $25,000 routes to a regional manager.
- Anything above $25,000 requires the procurement director.
Some organizations add approval criteria based on product category, cost center, department, or the specific buyer's spending limit.
A functional approval workflow engine evaluates these rules dynamically and routes each order to the correct approver or sequence of approvers without requiring manual intervention at each step.
Custom approval flows that reflect actual purchasing hierarchies are what separate a platform built for B2B from one that was retrofitted.
2. Role-based permissions with meaningful granularity
Not all users in a buying organization have the same authority.
- Buyers need permission to build carts and submit approval requests.
- Approvers need visibility into pending orders and the ability to give final approval, reject, or return for revision.
- Account administrators need to define rules and manage team members.
- Finance teams need read access to order history without purchasing authority.
Two or three static roles cannot model this reality, and platforms that offer only basic role structures force organizations to simplify their procurement processes to fit the platform, rather than the other way around.
The right approval workflow software provides customizable workflows with role definitions that mirror the actual account context of each buying organization.
3. Delegation and escalation handling
Approvers go on vacation, change roles, or don't respond in a timely manner.
A functional approval workflow process needs delegation – allowing an approver to temporarily assign their authority to someone else – and escalation – automatically routing an approval request to the next level if no action is taken within a configured timeframe.
Without these capabilities, a single unavailable approver can block an entire purchasing queue. An unnecessary delay that erodes buyer confidence in the platform and pushes orders back to manual processes.
4. Automated notifications across multiple channels
Every participant needs to know when action is required.
Buyers need confirmation that their order is pending approval. Approvers need approval notifications – by email, within the portal, or both – that an approval request is waiting for final sign-off.
Automated notifications reduce approval cycle time and reduce the number of orders that stall because a team member wasn't aware that an action was required. They also eliminate the back-and-forth communication that makes manual data entry and approval processes so time-consuming across multiple departments.
5. Audit trail and compliance logging
Every approval decision needs to be logged: who gave final approval or rejected the order, when, and with what comments. For organizations with strict compliance requirements – regulated industries, public procurement, enterprise purchasing policies – this audit trail is non-negotiable.
An approval workflow without complete logging creates risk management gaps that can surface during audits, compliance reviews, or disputes over whether an order was properly authorized.
How leading B2B eCommerce platforms support approval workflows?
The gap between what functional approval workflows require and what top B2B eCommerce platforms offer is where most purchasing friction originates.
The table below shows how each platform handles approval workflow support at a glance.
Shopify Plus
Shopify Plus provides company profiles with contacts and locations, but supports only two user roles for B2B. There is no native user-to-user order approval, which means the platform cannot route an order from a buyer to a manager for final sign-off within the storefront.
The available workaround is the draft order flow: B2B checkouts can be automatically converted into draft orders that a sales rep reviews and confirms on the admin side. This gives the seller control over orders but does not give the buyer's organization the ability to manage its own internal approval process or account context.
Multi-step approvals, spending limits per user, budget controls, and buyer-side approval chains all require custom development or third-party apps. Multiple analyses confirm that approval chains, quoting systems, and budget controls are not natively supported on Shopify Plus.
For teams that need custom approval flows on Shopify Plus, the most common approach combines Shopify Flow with external notifications across Slack or email. The approval logic ends up distributed across multiple systems – making it difficult to maintain, audit, or adapt as business rules change.
Adobe Commerce
Adobe Commerce's B2B functionality ships as a separate extension – the B2B module – that adds company accounts, shared catalogs, negotiable quotes, requisition lists, and purchase order workflows on top of the core platform.
Company administrators can define approval rules on the storefront, and the system routes purchase orders to the appropriate approvers based on company hierarchy and role. This is a meaningful capability, but it comes with significant caveats.
This module, including purchase orders and approval rules, is exclusive to the paid Commerce edition, starting at $22,000/year. It is not available in Magento Open Source.
The approval criteria support a limited set of conditions (order total, shipping cost, and SKU count) but don't natively support more complex routing based on product category, cost center, or department-level budgets.
Extending the approval flow logic requires custom development on an already complex platform.
The purchase order flow also interacts differently with online versus offline payment methods, adding another layer of implementation complexity that teams regularly underestimate during project scoping.
BigCommerce
BigCommerce B2B Edition provides three predefined buyer roles – Junior Buyer, Senior Buyer, and Admin – with the ability to create custom roles.
- Junior Buyers can submit shopping lists for approval.
- Senior Buyers can approve submissions and place orders.
- Admins manage the account.
This covers basic approval scenarios, but the approval workflow process remains relatively simple. Independent reviews consistently describe the approval gates as limited, lacking granular controls over authorizations and custom approval flows.
For organizations that need multi-level approvals with dynamic routing based on order characteristics – product category, cost center, buyer-specific spending limits – BigCommerce requires partner-built enhancements or custom workflows built on top of the B2B Edition.
That adds cost and a third-party dependency that introduces ongoing maintenance risk.
OroCommerce
OroCommerce, built specifically for B2B from the ground up, offers the deepest approval workflow capabilities of the four platforms.
It supports configurable approval chains, granular role-based permissions, and seamless integration with broader business processes through its built-in workflow engine.
For organizations with complex purchasing hierarchies – multiple departments, regional managers, finance controllers, and executive sign-off thresholds – OroCommerce delivers the flexibility that the other platforms in this comparison lack.
Custom workflows can be configured to reflect specific approval criteria, account context, and escalation rules without requiring hardcoded logic.
The trade-off is implementation complexity. Configuring these custom approval flows requires significant development effort and Symfony expertise.
Implementation timelines are measured in months, and the specialized developer pool for OroCommerce is smaller than for Shopify or Adobe Commerce, which affects both build cost and ongoing maintenance.
The hidden cost of approval workflow workarounds
When approval workflows are not natively supported, teams build workarounds. Those workarounds carry costs that go well beyond the obvious – in operational efficiency, compliance risk, and lost revenue.
Moving approvals outside the platform
The simplest workaround is to take approval requests out of the eCommerce platform entirely. A buyer places the order, emails the purchase details to their manager, the manager replies with confirmation, and the buyer proceeds.
This works at a small scale, but there is no audit trail, no enforcement of spending limits per buyer, and no way to verify that the approval was actually obtained before the order shipped.
There is also no scalability: what works with five buyers across two departments breaks down with fifty.
As order volume grows, the manual approval process becomes a bottleneck that directly delays fulfillment and increases the operational cost of processing each transaction.
Multi-system approval workflow automation
More sophisticated workarounds combine platform automation tools with external business systems. On Shopify Plus, some teams use Shopify Flow to tag orders for review and route automated notifications through Slack or email across multiple channels.
This creates a semi-automated approval flow, but the logic is distributed across systems, making it difficult to maintain, audit, or adapt as approval rules change.
When your approval workflow spans three systems and requires a developer to modify, it's not a structured process but a liability.
Third-party approval workflow software
Apps attempt to fill the gap left by platform limitations, but they introduce their own set of problems with integration capabilities and ongoing maintenance. Each app adds a dependency on a vendor whose pricing, feature roadmap, and continued existence are outside your control.
The right approval workflow software needs to integrate cleanly with B2B-specific features like company accounts, customer-specific pricing, and account context. When the platform updates its API or data model, the app may break – leaving the entire approval process non-functional until the vendor releases a fix.
The most expensive approval workflow failure is the one that happens silently – orders processing without required final approval because an app broke during a platform update, and no one noticed until a compliance review flagged it.
Choosing the right approval workflow for your B2B operations
The right choice depends on the complexity of your buyers' purchasing hierarchies and the volume of orders that flow through approval processes.
For simpler B2B operations – one or two approval levels, low order volume, limited role differentiation – the draft order workaround on Shopify Plus or the basic role structure on BigCommerce B2B Edition may be sufficient. The operational overhead is manageable, and the platform's other capabilities may justify the limitation.
For mid-market and enterprise B2B operations with multiple approval levels, department-level budget controls, delegation requirements, and compliance obligations, the gap between platform capability and business requirements is harder to close with workarounds.
If your buyers' procurement teams operate with more than two approval levels, spending limits per buyer, or department-specific routing rules, evaluate platform approval capabilities against those specific requirements.
The questions to ask before committing to a platform:
- Can the platform route orders to different approvers based on order value, product category, and cost center simultaneously?
- Can approvers delegate authority temporarily without admin intervention?
- Does the platform escalate automatically when an approver doesn't respond within a defined window?
- Is every approval decision logged with a timestamp, approver identity, and comments?
- Can approval rules be modified by company administrators without developer involvement?
If the answer to any of these is "requires custom development" or "needs a third-party app," factor the ongoing cost and dependency risk of that workaround into your platform evaluation.
Don't forget about licensing, implementation, and ERP integration costs covered in Chapter 3: Total cost of top B2B eCommerce platforms.
How to design an effective approval workflow step-by-step
Designing an approval process workflow that works in production requires more than configuring the platform. It requires mapping your buyers' real purchasing behavior first, then building the workflow to match it.
The most common reason approval workflows fail after implementation is that they were designed around platform capabilities rather than organizational reality. Your buyers' approval process existed before your eCommerce platform. The workflow needs to reflect it.
Step 1: map your buyers' actual purchasing hierarchy
Before touching any configuration, document how approvals actually happen in each of your major accounts.
- Who submits orders?
- Who approves them?
- What thresholds trigger different approval paths?
- Which departments have separate budgets and separate approvers?
Don't rely on org charts – talk to the procurement teams directly. The formal hierarchy and the real approval process are often different, and building a workflow against the wrong one creates friction from day one.
Step 2: define approval criteria for each workflow path
Once you understand the purchasing hierarchy, define the conditions that determine which approval path each order takes. Common criteria include: order value thresholds, product categories, cost center allocations, buyer role, and specific supplier or SKU combinations.
Document these as explicit rules before configuring anything. If you can't write the approval logic in plain language, you can't configure it correctly in the platform, and you won't be able to audit it when something goes wrong.
Step 3: configure role-based permissions to match actual authority levels
Map each role in the buying organization to a permission set in the platform.
- Buyers get cart-building and order submission rights.
- Approvers get visibility into pending approval requests and the ability to approve, reject, or return for revision.
- Admins get rule configuration and user management access.
Resist the temptation to simplify roles to fit what the platform offers natively. If your buyers operate with four distinct authority levels and the platform supports two, that gap needs to be addressed, either through custom development or by re-evaluating the platform.
Step 4: set up delegation and escalation rules
Define what happens when an approver is unavailable.
- Who covers during absence?
- After how many hours does the approval request escalate to the next level?
- Who receives the escalation?
These rules prevent a single unavailable team member from blocking an entire purchasing queue. They also need to be tested under realistic conditions.
Step 5: configure automated notifications and reminders
Set up automated notifications for every stage of the approval process:
- submission confirmation for buyers,
- approval request notification for approvers,
- automated reminders at defined intervals,
- and final approval or rejection confirmation for buyers.
Test that notifications fire correctly across all channels – email, portal, and any integrated business systems. A workflow that moves orders correctly but fails to notify approvers in a timely manner will stall just as badly as one with broken routing.
Step 6: build the audit trail before go-live
Confirm that every approval decision – approval, rejection, return for revision, escalation, delegation – is logged with timestamp, approver identity, and comments before the workflow goes live in production.
Don't treat audit logging as a post-launch task. If the first compliance review happens before logging is configured, you have no record of how orders were handled during that period.
Step 7: test under realistic B2B load
Run end-to-end tests with real order scenarios: a junior buyer submitting an order above their spending limit, an approver delegating during absence, an order escalating after no response, and an order that triggers multiple simultaneous approval paths.
Test with the actual users who will operate the workflow. Approval workflows that make sense in a configuration panel often break in ways that only surface when a real buyer tries to submit a real order under time pressure.
What are the benefits of a well-designed B2B approval workflow?
A well-designed approval workflow changes how buyers interact with your digital channel and how quickly orders move through your operation.
Faster order confirmation and shorter fulfillment cycles
When approval routing is automated, and approvers receive immediate notifications, the time between order submission and final approval drops significantly. Orders that previously waited days for manual email confirmation move through in hours.
Faster approvals mean faster fulfillment confirmation, which directly affects your buyers' procurement planning and their willingness to use the digital channel for time-sensitive purchases.
Reduced compliance risk across multiple departments
Automated approval workflows enforce spending limits and authorization rules consistently, across every order, without relying on individual team members to remember to check. Every approval decision is logged, timestamped, and attributable.
For organizations in regulated industries, this removes the manual compliance overhead of reconstructing approval chains after the fact. For all B2B organizations, it removes the risk of orders shipping without proper authorization.
Higher adoption of the digital channel
Buyers use channels that fit their process. When the eCommerce platform handles approval routing, notifications, and audit logging natively, the digital channel becomes easier to use than email-based manual approval.
Higher adoption means more orders flowing through the digital channel, which reduces cost to serve, improvesorder accuracy, and gives your team better visibility into purchasing patterns across accounts.
Better visibility into purchasing behavior across accounts
When all approval requests, decisions, and order history flow through a single system, your team gains visibility into purchasing patterns that manual processes make invisible.
- Which accounts are placing orders above their usual thresholds?
- Which buyers are consistently hitting spending limits?
- Which approval paths are creating the most delays?
This data supports better account management decisions and surfaces expansion opportunities that a fragmented approval process would miss.
How to solve common approval workflow issues?
Even well-designed approval workflows encounter operational problems. The most common issues have consistent causes and consistent solutions.
Approvals are stalling because approvers aren't notified
The cause is almost always a notification configuration failure: automated reminders aren't set up, or they're going to the wrong channel.
The fix is straightforward – configure automated reminders at defined intervals and test them with real users before go-live.
If the platform doesn't support automated reminders natively, treat that as a platform limitation, not a configuration problem to solve with workarounds.
Buyers submitting orders that bypass approval rules
This typically happens when approval criteria aren't comprehensive enough – a buyer finds a combination of order characteristics that doesn't trigger any defined rule and proceeds without approval.
Audit your approval criteria against real order patterns regularly, not just at implementation. Every gap in your approval criteria is a compliance gap that will eventually be exploited.
Approval chains blocked by a single unavailable approver
The cause is a missing delegation and escalation configuration.
The fix is defining explicit delegation rules and escalation timeframes for every approval level, and testing them before go-live.
If your platform doesn't support native escalation, document how your team handles unavailable approvers manually, and factor that operational overhead into your platform evaluation.
Audit trail gaps during platform updates
When a platform update changes how approval data is stored or surfaced, historical records can become inaccessible or incomplete.
Maintain external backups of approval logs at regular intervals, and verify audit trail continuity after every platform update.
A gap in your approval audit trail is a compliance failure regardless of its cause.
Workflow logic breaking after a platform update
Third-party approval apps and custom workflow extensions break when the platform updates its API or data model.
The fix is maintaining version-controlled documentation of all workflow logic and testing end-to-end approval scenarios after every platform update, before re-opening the system to buyers.
If your approval workflow requires a developer to fix after every platform update, that maintenance cost should be part of your platform TCO calculation.
Summary: How do approval flow gaps quietly reduce your B2B digital channel adoption?
Approval workflow gaps are one of the most consistent reasons B2B buyers reduce their use of a digital channel over time.
The initial adoption looks positive. Then procurement teams encounter their first multi-level approval scenario, find that the platform can't support it, and revert to email and phone, carrying other routine orders with them.
If your buyers' teams are managing approvals outside your platform, that's a signal worth taking seriously. It means the digital channel is adding process overhead rather than removing it, which is the opposite of what B2B self-service commerce is supposed to deliver.
The longer this continues, the harder it becomes to rebuild confidence in the platform as a primary ordering channel. Fixing approval workflow capability at the platform level is significantly cheaper than recovering accounts that have already reverted to manual ordering.
If approval workflow limitations are affecting buyer adoption or creating compliance gaps in your current setup, let's talk.
The next chapters of this guide break down how each of these platforms handles the specific B2B requirements and where the architectural gaps create the hidden costs.
- B2B features locked behind enterprise tiers.
- SaaS constraints that block deep customization.
- Performance degradation under extensions.
- API fragmentation that weakens integrations.
- ERP sync failures that create operational chaos.
- Pricing and payment terms that are not truly native.
→ Continue to the full The State of B2B eCommerce Platforms 2026 comparison guide.
→ To discuss your B2B architecture and TCO with our team, book a consultation.
FAQ on B2B approval workflow process in eCommerce
What is a B2B approval workflow in eCommerce?
A B2B approval workflow is a structured process that routes an order through one or more designated approvers before it is confirmed.
In practice, this means a buyer submits a cart for review, the system routes the request to the appropriate approver based on configurable rules – order value, product category, buyer role – and the order proceeds to fulfillment only after the required approvals are obtained.
Without this process, organizations either bypass procurement controls or manage approvals manually outside the platform, both of which introduce compliance risk and operational overhead.
What platforms support complex B2B workflows?
OroCommerce offers the most complete native approval workflow functionality of the four platforms in this guide – configurable multi-level chains, granular role-based permissions, delegation, escalation, and integration with broader business process workflows. The trade-off is implementation complexity and a narrower developer talent pool.
Adobe Commerce is the closest alternative with native purchase order approval rules, but the conditions are limited, and the capability is restricted to the paid Commerce edition.
Why are approval workflows important in B2B eCommerce?
Approval workflows are the mechanism through which B2B organizations enforce purchasing controls, compliance requirements, and budget accountability within their digital buying process.
Without a structured approval process, two things happen. Buyers either bypass internal procurement policies to complete orders faster – creating compliance risk and audit exposure – or they manage approvals manually outside the platform through email and messaging tools – adding friction that slows ordering and pushes volume back to manual channels.
The business consequence of inadequate approval workflows shows up in three places: delayed orders, reduced digital channel adoption, and compliance gaps that surface during audits.
For sellers, every approval bottleneck is a delayed order and a risk of abandonment. For buyers, every manual workaround is a reason to question whether the platform is actually easier than picking up the phone.
A well-designed automated approval workflow removes friction from both sides of the transaction and gives finance and procurement teams the visibility they need without adding operational overhead.
What are the differences between workflows and the approval process?
A workflow is a broader concept: it's the sequence of steps, rules, and automations that govern how a business process moves from initiation to completion. An approval process is a specific type of workflow – one focused on obtaining authorization from designated team members before an action proceeds.
In B2B eCommerce, you'll encounter both. An order workflow covers the entire journey from cart submission to fulfillment: approval routing, payment processing, inventory allocation, ERP sync, and shipping confirmation. An approval process is the specific stage within that workflow where the order is reviewed and authorized by one or more approvers before it moves forward.
