TL;DR
- What this guide covers: A complete walkthrough for configuring purchase order approval workflows in your B2B ecommerce platform, from prerequisite setup through multi-level approval chains and ERP sync.
- Who it’s for: eCommerce Managers and Ops Directors at B2B manufacturing and industrial distribution companies.
- Platform covered: Adobe Commerce (Magento), integrated with Epicor, NetSuite, or SAP Business One.
- What you’ll be able to do: Build a repeatable, step-by-step PO approval workflow that enforces spending thresholds, routes orders to the right approvers, and syncs approved purchase orders directly to your ERP.
- Proof it works: Duke Industrial Equipment automated their approval workflow and reduced order processing time from 48 hours to 4 hours while eliminating unauthorized purchases and improving margin control.
B2B orders stalling in email inboxes for two days while a regional manager hunts for the right approval threshold is a problem that costs real revenue. This guide gives you a clear, step-by-step process for building PO approval workflows in Adobe Commerce so every order routes to the correct approver, enforces your spending rules, and syncs back to your ERP without manual re-keying. If you’re an eCommerce Manager or Ops Director at a manufacturing or industrial distribution company running Adobe Commerce with Epicor, NetSuite, or SAP Business One, this is the playbook you need to set up purchase order approval processes that actually match how your buyers and internal teams operate.
Why eCommerce Manager / Ops Directors Get This Wrong
Most B2B companies start with manual PO approval processes because they seem simple enough: a buyer submits an order, someone reviews it in email, and the order gets entered into the ERP. The problem compounds quickly. Without structured approval rules, orders above spending limits slip through without proper sign-off. Buyers submit POs to the wrong approver because there’s no role-based routing. Finance discovers unauthorized purchases weeks later during reconciliation. The downstream cost is significant: one industrial distributor we spoke with estimated that 12% of their orders required manual correction because approval rules weren’t enforced at the point of purchase. That’s wasted labor, delayed shipments, and eroded customer trust.
Gartner research shows companies with well-structured digital commerce experiences see a 25% increase in customer satisfaction and a 20% boost in repeat purchases, and a broken approval process undermines both.
The root cause is usually a disconnect between how the business thinks approvals work and how the ecommerce platform is actually configured. ERP systems like Epicor or NetSuite have their own approval logic, but if that logic isn’t mirrored in Adobe Commerce, buyers experience a gap: they place an order online, it gets approved in the portal without proper checks, and the ERP rejects it hours later. This creates a loop of rework that frustrates buyers and burns internal resources. Duke Industrial Equipment faced exactly this problem. After fixing their approval workflow configuration, they reduced order processing from 48 hours to 4 hours, and unauthorized purchases were eliminated, improving margin control across their entire operation.
What You Need Before You Start
Before you configure anything in Adobe Commerce, confirm these prerequisites are in place. Missing even one can stall your implementation or create sync issues with your ERP.
- ERP approval logic documented: Pull your current approval rules from Epicor, NetSuite, or SAP Business One. You need the exact spending thresholds, approval hierarchies, and any exception rules (such as rush orders or contract-specific overrides) written down before you touch Adobe Commerce.
- Adobe Commerce B2B module enabled with admin access: The B2B module must be active, and you need admin-level configuration rights. Confirm that Company Accounts are enabled under Stores > Configuration > General > B2B Features.
- Company account hierarchy mapped: Document every buyer role, department, and reporting structure for each company account. Adobe Commerce uses this hierarchy to route approvals, so if your org chart is wrong in the platform, approvals will route to the wrong people.
- Stakeholder sign-off on approval rules: Get your eCommerce Manager, Ops Director, and Finance lead to agree on threshold amounts, the number of approval levels, and what happens when an approver is unavailable. Don’t configure first and negotiate later.
- ERP integration middleware confirmed: Your integration layer (whether it’s a connector like Celigo for NetSuite or a custom middleware for Epicor) must support two-way order status sync. Approved POs need to flow to the ERP, and rejection statuses need to flow back to the buyer’s portal.
- Email notification templates drafted: Prepare the content for approval request emails, approval confirmation emails, and rejection notifications. Adobe Commerce sends these automatically, but the default templates rarely match B2B expectations.
How to Set Up Purchase Order Approval Workflows in B2B Ecommerce: Step-by-Step
Step 1: Enable Purchase Orders for Company Accounts
In Adobe Commerce Admin, go to Stores > Configuration > General > B2B Features and set “Enable Purchase Orders” to Yes. This activates the PO functionality at the platform level, but it doesn’t turn it on for individual company accounts yet. You’ll do that per-account in the next step. Without this global toggle, buyers won’t see the option to submit POs during checkout, regardless of their account settings.
Step 2: Configure Company-Level PO Permissions
Navigate to Customers > Companies, select a company account, and enable Purchase Orders under the company’s configuration. This is where you define whether buyers within that account can use POs as a payment method. Each company account operates independently, so a manufacturer with 200 dealer accounts can enable PO workflows for high-volume dealers while keeping credit card checkout for smaller buyers. This flexibility matters for B2B approval workflow configuration because not every account needs the same process.
Step 3: Build Your Approval Rule Structure
This is the core of your PO approval workflow. In Adobe Commerce, approval rules are tied to company accounts and define the conditions that trigger an approval requirement. Go to the company’s admin panel and create rules based on order value thresholds. For example: orders under $5,000 get auto-approved, orders between $5,000 and $25,000 require a department manager’s sign-off, and orders above $25,000 require VP-level approval. These thresholds should mirror what’s already enforced in your ERP. If Epicor requires a two-level approval for orders above $10,000, your Adobe Commerce rules need to match exactly, or you’ll create conflicts during order sync.
Step 4: Assign Approvers by Role in the Company Hierarchy
Adobe Commerce uses the company hierarchy to determine who can approve what. Each user in a company account has a role: Buyer, Senior Buyer, Department Manager, Company Admin. Assign approval permissions to these roles so the platform knows where to route each PO. A common mistake is assigning approval rights too broadly. If every Senior Buyer can approve every PO, you lose the control that approval workflows are supposed to provide. Be specific: tie approvers to departments, regions, or spending categories. This is especially important for online PO approval processes at B2B manufacturers with multiple divisions placing orders through a single portal.
Step 5: Configure Multi-Level Approval Chains
For orders that require more than one sign-off, set up sequential approval chains. Adobe Commerce supports multi-level approvals where a PO moves from one approver to the next based on the rules you defined in Step 3. The order doesn’t proceed to fulfillment until every required approver has signed off. Watch out for bottlenecks here: if your VP of Procurement is the final approver on every order above $10,000, and they’re traveling for a week, your entire order pipeline stalls. Build in backup approvers or escalation rules. Some companies set a 24-hour auto-escalation so that if the primary approver doesn’t act, the PO routes to the next person in the hierarchy.
Step 6: Set Up Email Notifications and Status Visibility
Configure email notifications for every stage of the approval process: submission, pending review, approved, and rejected. Buyers need to know their PO status without calling your sales team. In Adobe Commerce, go to Stores > Configuration > Sales > Sales Emails and customize the PO-related templates. Make sure the notification includes the order total, the approver’s name, and a direct link to the approval queue. For ERP-connected setups, configure your middleware to push approval status updates back to the buyer portal so the status stays consistent between Adobe Commerce and NetSuite, Epicor, or SAP Business One.
Step 7: Test the Full Workflow with Real Scenarios
Before going live, run test orders through every approval path. Submit a PO under the auto-approval threshold and verify it flows to the ERP without manual intervention. Submit one that triggers a single-level approval and confirm the right person receives the notification. Submit a high-value order that requires multi-level approval and verify the chain executes in sequence. Test a rejection and confirm the buyer receives the rejection email with a reason. HumCommerce typically runs a parallel testing phase where real orders are processed through both the old manual workflow and the new automated one simultaneously, comparing results for two weeks before cutting over entirely.
3 Mistakes to Avoid
Mistake 1: Copying ERP Approval Rules Without Adapting Them
Your ERP approval logic was designed for internal purchase requisitions, not customer-facing ecommerce. Applying the same 5-level approval chain to an online buyer’s $8,000 order creates unnecessary friction and increases cart abandonment. Adapt your rules for the ecommerce context: fewer levels, faster turnaround, and auto-approval for routine reorders from trusted accounts.
Mistake 2: Ignoring Backup Approver Configuration
A single-point-of-failure approver is the fastest way to stall your order pipeline. If one person holds approval authority and they’re unavailable, every PO above the threshold sits in limbo. Always configure at least one backup approver per level, and set time-based escalation rules so orders don’t age in a queue.
Mistake 3: Not Syncing Approval Status Back to the ERP
Approving a PO in Adobe Commerce means nothing if the ERP doesn’t know about it. Without two-way sync, your warehouse team may process an order that was later rejected in the portal, or a buyer sees “approved” online while the ERP still shows “pending.” Ensure your integration middleware pushes approval and rejection statuses in near real-time to your ERP. Quote turnaround times have been reduced from 3-5 days to hours at companies that automated these approval and status sync processes end-to-end.
Real Example: Duke Industrial Equipment
Duke Industrial Equipment, a mid-market industrial distributor, was struggling with a manual PO approval process that relied on email chains and spreadsheet tracking. Buyers would submit orders through their Adobe Commerce portal, but approvals happened offline. Orders sat in limbo for an average of 48 hours, and unauthorized purchases regularly slipped through because there was no systematic enforcement of spending thresholds.
After getting this right:
- Approval workflow automation reduced order processing from 48 hours to 4 hours
- Unauthorized purchases eliminated, improving margin control
The specific changes were straightforward but required careful configuration.
Duke’s team built three-tier approval rules in Adobe Commerce tied to order value: auto-approve under $3,000, single approval for $3,000-$15,000, and dual approval above $15,000. Each tier mapped directly to the approval logic already in their ERP, so when a PO was approved in the portal, the integration middleware pushed the approved order to their ERP with the correct approval metadata attached.
Rejection reasons synced back to the buyer’s portal in real time, eliminating the back-and-forth emails that had previously consumed hours of their operations team’s week.
The result was a process in which the e-commerce platform and ERP behaved as a single system for approval purposes, rather than two disconnected tools.
Need Help Implementing This?
Setting up PO approval workflows is conceptually straightforward, but the configuration details matter enormously. Threshold logic, role hierarchies, multi-level chains, ERP sync, and email notifications all need to work together without gaps. For B2B manufacturing and industrial distribution companies running Adobe Commerce with Epicor, NetSuite, or SAP Business One, the integration layer is where most implementations hit friction: approval statuses that don’t sync, rules that conflict between systems, or buyer-facing workflows that don’t reflect the ERP’s source of truth.
HumCommerce specializes in exactly this type of implementation. We’ve configured PO approval workflows for manufacturers and distributors where the ecommerce platform behaves like an extension of the ERP, not a separate system. Our team has delivered 75% faster quote workflows for complex B2B manufacturers by connecting Epicor CPQ with Adobe Commerce, and the same integration discipline applies to approval chain configuration.
Talk to a HumCommerce consultant about your B2B ecommerce purchase order approval setup.
