B2B Order Approval Workflow

Key Features

Multi-level approval rules with conditions on cart subtotal, grand total, requester role, and company hierarchy, evaluated via a dedicated rule engine bound through di.xml

Spending-limit and credit-based triggers that hold orders exceeding a buyer's or company's configured threshold or available credit

Approver email notifications plus an admin grid and optional storefront company dashboard showing every pending request

Bulk approve / reject with mandatory or optional comments, written to the order's comment history and audit trail

Custom order statuses (e.g. Pending Approval, Approved, Rejected) mapped to Magento sales order state so held orders stay out of fulfilment

Plugin/interceptor on OrderManagementInterface and an observer on sales_order_place_before so the gate engages without core rewrites

REST and GraphQL endpoints over Magento service contracts for headless / PWA Studio storefronts to submit and act on approvals

Granular admin ACL resources controlling who can configure rules, view the queue, and approve or reject

Configurable cron job for approval reminders and automatic escalation of stale requests to the next approver level

Adobe Commerce B2B Company Accounts integration where available; company and approver structures provisioned for Magento Open Source

Full email template set integrated with Magento's transactional email system and store-view localisation

Complete source delivered under app/code, installed on your environment and covered by a post-launch warranty

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

The B2B Order Approval Workflow is a custom Magento 2 module that inserts an approval gate between checkout and order placement for your company-account buyers. When a purchase exceeds a configured spending limit, credit threshold, or matches a defined rule condition, the order is held in a pending-approval state and routed to the right approver instead of going straight to processing.

This is not an instant Adobe Commerce Marketplace download. ECOSIRE designs, codes, and installs the module directly on your Magento Open Source or Adobe Commerce install, then supports it. We build it as a proper module under app/code/Ecosire/OrderApproval with a clean di.xml, a plugin/interceptor on the order placement service contract (OrderManagementInterface), and an observer on sales_order_place_before so approval logic engages without rewriting core.

Rules are evaluated against cart totals, requester role, and company hierarchy. Pending orders use custom order statuses mapped to Magento's state machine, so they stay out of fulfilment until released. Approvers receive email notifications and work from an admin grid (and optional storefront company dashboard) where they bulk approve or reject with comments. A configurable cron job sends reminders and can auto-escalate stale requests.

Everything is exposed through Magento service contracts with REST and GraphQL endpoints for headless or PWA storefronts, guarded by granular admin ACL resources. On Adobe Commerce we integrate with native B2B Company Accounts and shared catalogs where present; on Magento Open Source we provide the company/approver structures the workflow needs. You get the full source, deployed and warranty-backed.

What you get

A production-ready Magento 2 module (Ecosire_OrderApproval) under app/code, written to Magento coding standards and PSR-12

Installation and deployment on your Magento Open Source or Adobe Commerce environment (staging first, then production)

di.xml, plugins, observers, ACL, cron, email templates, and REST/GraphQL endpoints configured for your store

Admin configuration of approval rules, spending limits, statuses, and approver assignments to match your procurement policy

Full source code with technical README and inline documentation, owned by you

Post-launch warranty period plus optional ongoing support and Magento version-upgrade compatibility

Who this is for

B2B Procurement Manager

Needs every order above a threshold reviewed before it is placed, with a clear queue, comments, and an audit trail to enforce company spending policy.

Magento Store Owner / Operations Lead

Runs a wholesale or distributor store and wants company buyers to self-serve while managers retain a controlled gate over what actually gets fulfilled.

Adobe Commerce B2B Administrator

Manages Company Accounts and wants approval rules layered onto existing buyer roles, credit limits, and shared catalogs without forking core.

How B2B Order Approval Workflow Compares

Criterion	ECOSIRE	Custom Build	Competitor
Multi-level approval rules with spending-limit and credit triggers	Included	Partial support	Included
Works on Magento Open Source (no native B2B company accounts)	Included	Partial support	Partial support
Built, installed, and configured on your store for you	Included	Partial support	Not included
Custom rules tailored to your exact procurement policy and hierarchy	Included	Included	Not included
Instant self-service download and one-click install	Not included	Not included	Included
REST + GraphQL endpoints for headless / PWA storefronts	Included	Partial support	Partial support
Full source ownership under app/code	Included	Included	Partial support
Post-launch warranty and version-upgrade support from the builder	Included	Partial support	Partial support

Frequently Asked Questions about B2B Order Approval Workflow

How long does delivery take, since this is built to order?

Typical build, configuration, and installation runs about 2 to 4 weeks depending on your rule complexity, whether you are on Magento Open Source or Adobe Commerce, and any custom company-hierarchy or credit logic. After our scoping call we confirm a firm timeline and milestones. We deploy to a staging environment first for your sign-off, then schedule the production install. This is custom work performed on your store, not an instant Marketplace download.

What ongoing support and updates are included?

Every build includes a post-launch warranty covering defects in the delivered functionality. Beyond that we offer optional ongoing support and maintenance, including compatibility fixes for future Magento and Adobe Commerce patch and minor version upgrades. Because you receive the full source under app/code, your own developers can also maintain or extend it. Support terms are agreed up front so you know exactly what is covered.

Does this work on both Magento Open Source and Adobe Commerce?

Yes. On Adobe Commerce we integrate with the native B2B Company Accounts, buyer roles, and credit limits where they exist, so approval rules layer onto your existing structures. On Magento Open Source, which has no built-in company accounts, we provision the company and approver structures the workflow needs. We confirm your edition and version during scoping and tailor the build accordingly.

Will it modify or break Magento core, and is it upgrade-safe?

No core files are overwritten. The module lives under app/code/Ecosire/OrderApproval and hooks in through supported extension points: a plugin/interceptor on the order placement service contract, an observer on sales_order_place_before, di.xml preferences, custom statuses, ACL, and cron. This keeps the work upgrade-safe and compatible with Magento's standard deployment and dependency-injection compilation.

Can the approval workflow be used with a headless or PWA storefront?

Yes. All approval actions are exposed over Magento service contracts with both REST and GraphQL endpoints, so a PWA Studio or other headless frontend can submit orders for approval and let approvers act on the queue. Access is protected by Magento's standard authentication and the module's admin ACL resources.

How are approval rules and spending limits configured?

Rules are managed in the Magento admin under a dedicated, ACL-protected configuration area. You define conditions on cart subtotal, grand total, requester role, and company hierarchy, set spending or credit thresholds, and map the resulting custom order statuses. We configure your initial policy during the build and hand over documentation so your team can adjust rules later.