A build-to-order Magento 2 / Adobe Commerce extension that routes company-account orders through configurable multi-level approval rules before they are placed. Built, installed, and supported on your store by ECOSIRE. One-time license from $499.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.

A build-to-order Magento 2 / Adobe Commerce extension that routes company-account orders through configurable multi-level approval rules before they are placed. Built, installed, and supported on your store by ECOSIRE.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
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.
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
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.
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.
Runs a wholesale or distributor store and wants company buyers to self-serve while managers retain a controlled gate over what actually gets fulfilled.
Manages Company Accounts and wants approval rules layered onto existing buyer roles, credit limits, and shared catalogs without forking core.
Buy the license on ecosire.com and download the B2B Order Approval Workflow module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for B2B Order Approval Workflow, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Multi-level approval rules with spending-limit and credit triggers | ||||
| Works on Magento Open Source (no native B2B company accounts) | ||||
| Built, installed, and configured on your store for you | ||||
| Custom rules tailored to your exact procurement policy and hierarchy | ||||
| Instant self-service download and one-click install | ||||
| REST + GraphQL endpoints for headless / PWA storefronts | ||||
| Full source ownership under app/code | ||||
| Post-launch warranty and version-upgrade support from the builder |
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.
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.
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.
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.
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.
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.
A build-to-order Magento 2 / Adobe Commerce extension that routes company-account orders through configurable multi-level approval rules before they are placed. Built, installed, and supported on your store by ECOSIRE.