Streamlining B2B Procurement: Purchase Orders and Requisition Lists in Adobe Commerce

Learn how to configure and optimize Adobe Commerce purchase order approval workflows and requisition lists to automate B2B procurement, reduce errors, and deliver the self-service buying experience your customers expect.

B2B buyers are done waiting on sales reps to place routine orders. Recent research from Gartner shows that 61 percent of B2B buyers now prefer a completely rep-free buying experience, and McKinsey reports that even orders exceeding half a million dollars are increasingly completed through self-service channels. The message is clear: if your B2B storefront cannot handle purchase orders, approval workflows, and repeat-ordering through requisition lists, you are losing deals to competitors who can.

Adobe Commerce includes native B2B procurement tools that most platforms require expensive third-party add-ons to replicate. Purchase order workflows with configurable approval rules, requisition lists for repeat ordering, and deep company hierarchy integration are all built into the platform. The challenge is not whether Adobe Commerce supports these workflows — it is whether your implementation uses them effectively.

This guide walks through the practical configuration of purchase orders and requisition lists in Adobe Commerce, the approval rule patterns that map to real organizational structures, and the integration points that connect procurement to your ERP.

Why Purchase Orders Matter in B2B Commerce

In B2C, a customer adds items to a cart and checks out with a credit card. In B2B, procurement is governed by budgets, approval chains, and compliance requirements. A warehouse manager in Tulsa cannot simply buy forty thousand dollars worth of industrial parts without someone in procurement reviewing and approving that order.

Purchase orders formalize this process. They create an auditable record of what was requested, who approved it, under what terms, and when the approval happened. Without digital purchase order support, B2B buyers resort to emailing PDFs, calling sales reps, or using offline procurement systems that never sync with your storefront — all of which introduce errors, delays, and friction that erode buyer loyalty.

Adobe Commerce’s purchase order module handles this natively. When enabled, every order placed by a company user is routed through a configurable approval workflow before it becomes a live order. This means your storefront becomes the system of record for procurement, not a workaround that procurement teams tolerate.

Configuring Purchase Order Approval Rules

Adobe Commerce lets company administrators define approval rules that enforce their internal procurement policies directly within the storefront. These rules determine which orders require approval, who can approve them, and under what conditions.

Approval Rule Components

Each approval rule in Adobe Commerce consists of three elements:

Conditions define when the rule triggers. The most common condition is order total — for example, any purchase order exceeding five thousand dollars requires manager approval. You can also set conditions based on the number of line items or shipping cost thresholds.

Approvers define who can approve orders that match the conditions. Adobe Commerce supports role-based approvers (anyone with the “Approver” role in the company hierarchy) and specific user approvers (a named individual). You can require approval from a single approver or configure multi-level approval chains where the order escalates through multiple levels of the company hierarchy.

Rule priority determines which rule applies when multiple rules match the same order. Higher-priority rules take precedence, which lets you build layered approval logic — a general rule for routine orders and stricter rules for high-value purchases.

Real-World Approval Patterns

The most effective approval configurations we implement at Creatuity map directly to how companies actually operate:

Threshold-based approval is the most common pattern. Orders under a set amount proceed automatically. Orders above that threshold require one level of approval. Orders above a higher threshold require two levels. This mirrors how most manufacturing and distribution companies structure their procurement authority.

Department-scoped approval uses Adobe Commerce’s company hierarchy to route approvals to the appropriate division. A facilities team purchase routes to the facilities manager, while a production line order routes to the operations lead. This prevents bottlenecks where a single approver must review every order across the organization.

Budget-period controls combine approval rules with company credit limits to enforce quarterly or monthly procurement budgets. When a team approaches their budget ceiling, approval requirements tighten automatically, giving finance visibility without blocking day-to-day operations.

Requisition Lists: The Engine Behind Repeat B2B Ordering

While purchase orders govern how orders get approved, requisition lists govern how orders get built. In B2B commerce, buyers do not browse your catalog the way a consumer shops on a retail site. They know exactly what they need, they order the same products regularly, and they need to build orders fast.

Adobe Commerce requisition lists allow company users to save curated product collections that they can reorder with minimal effort. Unlike wishlists, requisition lists are purpose-built for B2B workflows. They support multiple lists per user, bulk add-to-cart functionality, and integration with the company account structure.

Setting Up Requisition Lists Effectively

Enable requisition lists in the Adobe Commerce admin under Stores > Configuration > Customers > Requisition Lists. The key configuration decisions are:

Maximum number of lists controls how many requisition lists each user can maintain. For distributors with buyers who manage multiple job sites or projects, setting this to ten or more prevents users from hitting artificial limits. For simpler organizations, five lists may suffice.

List sharing within the company hierarchy allows a procurement manager to build a requisition list that their entire team can use. This is particularly valuable for standardized orders — safety equipment kits, monthly office supplies, or maintenance parts packages — where one person curates the list and multiple buyers place orders from it.

Product data freshness is a configuration detail that matters for ERP-integrated stores. When a buyer opens a requisition list, Adobe Commerce checks current pricing and availability. If your ERP integration feeds real-time inventory and pricing, requisition lists always reflect accurate data. If your integration runs on a batch schedule, buyers may see stale information — a friction point worth addressing early.

Requisition Lists and the New Adobe Commerce Storefront

Adobe recently released new B2B drop-in components for the Adobe Commerce Storefront, including a dedicated Requisition List component. This component enables cart-to-requisition-list synchronization, where products moved between the cart and requisition lists trigger automatic refreshes. For businesses building on the new storefront architecture, these components provide a faster, more responsive procurement experience without custom frontend development.

Connecting Purchase Orders to Your ERP

Purchase orders in Adobe Commerce become significantly more powerful when they sync with your ERP system. The goal is a closed-loop workflow: a buyer creates a purchase order in Adobe Commerce, it routes through approval, and once approved, the order data flows into your ERP as a sales order with matching terms, line items, and buyer information.

Integration Patterns That Work

Real-time webhook-based sync pushes approved purchase orders to your ERP immediately upon approval. This is the gold standard for organizations where fulfillment speed matters — distributors promising same-day shipping, for example. Adobe Commerce’s event-driven architecture supports this through the purchase order status change events that can trigger downstream integrations.

Batch sync on schedule collects approved purchase orders and pushes them to the ERP at defined intervals. This works for businesses where fulfillment operates on a daily cycle. It is simpler to implement and easier to monitor, but introduces a delay between approval and ERP visibility.

Middleware orchestration using an iPaaS layer (MuleSoft, Celigo, or similar) handles data transformation, error handling, and retry logic between Adobe Commerce and your ERP. For complex environments where purchase order data needs to be enriched, validated, or routed to multiple systems, this pattern provides the resilience that point-to-point integrations lack.

At Creatuity, we see the middleware pattern deliver the best results for manufacturers and distributors running Epicor, NetSuite, or SAP alongside Adobe Commerce. The upfront investment in integration architecture pays for itself in reduced manual data entry and fewer order errors.

When to Use Purchase Orders vs. Negotiable Quotes

Adobe Commerce supports both purchase orders and negotiable quotes, and understanding when to use each prevents workflow confusion.

Purchase orders work best for orders with known, catalog-based pricing. The buyer knows what they want, the price is established (whether through shared catalogs or customer-group pricing), and the only governance needed is internal approval. This covers the majority of repeat B2B orders.

Negotiable quotes work best when pricing is not fixed — large-volume orders that warrant a discount, custom product configurations, or new buyer relationships where terms are still being established. Quotes involve back-and-forth negotiation between the buyer and seller before an order is placed.

Many Adobe Commerce B2B implementations enable both features simultaneously. A buyer placing their standard monthly restock uses purchase orders. The same buyer negotiating a bulk deal for a new project uses the quoting workflow. Adobe Commerce keeps both workflows within the same storefront experience, which means buyers do not need to switch systems depending on the order type.

Common Implementation Mistakes

After implementing B2B procurement workflows for dozens of Adobe Commerce clients, we have identified the patterns that cause the most friction:

Over-engineering approval chains is the most frequent mistake. Companies try to replicate their entire organizational chart in approval rules, creating five-level approval chains that delay routine orders. Start with the simplest approval structure that enforces your actual procurement policy and add complexity only when business requirements demand it.

Ignoring mobile procurement is increasingly costly. Field teams, warehouse managers, and job-site supervisors place orders from phones and tablets. If your B2B self-service portal does not render requisition lists and purchase order approvals cleanly on mobile devices, you are forcing buyers back to phone calls and emails.

Skipping the pilot phase with a subset of company accounts leads to surprises at scale. Launch purchase order workflows with your most engaged buyer accounts first, gather feedback on approval timing and requisition list usability, and refine before rolling out to your full customer base.

Getting Started

If your Adobe Commerce instance has B2B features enabled but purchase orders and requisition lists are underutilized, the fastest path to value is:

1. Audit your current buyer workflows. Identify which accounts are placing orders through offline channels that could be handled through purchase orders.
2. Map approval authority. Document who approves what, at what thresholds, in your top ten accounts. These become your initial approval rules.
3. Build starter requisition lists. Work with your sales team to identify the twenty most reordered product combinations and create template requisition lists for key accounts.
4. Enable and test. Turn on purchase orders and requisition lists in a staging environment, validate with a pilot account, and measure the impact on order processing time.

The companies that get the most from Adobe Commerce B2B are the ones that treat procurement automation as a competitive advantage, not an IT checkbox. When your buyers can build orders from requisition lists, route them through sensible approval chains, and have those orders land in your ERP without manual intervention, you have built a storefront that earns loyalty.

Creatuity specializes in Adobe Commerce B2B implementations for manufacturers and distributors. If your procurement workflows need modernization, reach out to discuss your specific requirements.

Frequently Asked Questions