B2B Company Accounts & Sub-Users

Key Features

Storefront company registration that provisions a company entity, an admin sub-user and a default permission tree on customer_register_success

Unlimited sub-accounts under one company with invite-by-email and per-user activation/deactivation

Role and permission model (buyer, approver, viewer, custom) gating cart, checkout, quote and requisition actions via ACL-style resources

Company credit / payment on account: a custom Magento\Payment\Model\MethodInterface method with credit limit, running balance ledger and exposure check at sales_order_place_before

Sales representative assignment — link an admin user to each company, shown as a ui_component column in the Sales > Orders grid via a back-office plugin

Requisition lists for saving, sharing and one-click re-ordering of frequent baskets per sub-user or company-wide

Service contracts (PHP interfaces under Api/) for every company, sub-user, role and credit operation — no direct model coupling

GraphQL mutations and queries plus REST endpoints (webapi.xml) for Hyvä, PWA Studio and headless storefronts

Admin grids and forms for companies, users, roles and credit, secured by Magento_Backend ACL with granular resource entries in acl.xml

Declarative db_schema.xml tables (no core schema edits) with data/schema patches for safe install and upgrade

Configurable cron job emitting company credit statements and low-balance / over-limit notifications

Event observers and plugins/interceptors only — zero core-file overrides, upgrade-safe across your Magento minor versions

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

B2B Company Accounts & Sub-Users brings native-feeling B2B account structures to Magento Open Source — the company hierarchy, sub-user roles, and payment-on-account that Adobe Commerce B2B ships as a paid edition feature, rebuilt as a clean, owned module on your install.

This is built to order by ECOSIRE, not an instant Marketplace download. We develop it as a versioned module under app/code/Ecosire/CompanyAccounts, wire it into your store through di.xml, plugins/interceptors, and observers on events like customer_register_success and sales_order_place_after, then install, configure and support it on your environment.

What it does. A buyer registers a company from the storefront; ECOSIRE provisions a company entity, an admin sub-user, and an ACL-style permission tree. The company admin invites sub-users and assigns roles (buyer, approver, viewer) that gate cart, checkout, quote and requisition actions. Company credit / payment on account adds a custom payment method (Magento\Payment\Model\MethodInterface) with a credit limit, balance ledger and exposure checks at sales_order_place_before. Each company can carry an assigned sales representative (admin user) surfaced in the order grid via a ui_component column and a back-office plugin. Requisition lists let teams save and re-order frequent baskets.

Everything is exposed over service contracts with matching GraphQL mutations/queries and REST endpoints, so your Hyvä/PWA/headless front end and any ERP integration consume it cleanly. Admin screens respect ACL (Magento_Backend::admin) and ship with a setup cron for credit-statement digests.

We honor Magento engineering standards — no core hacks, no sql.raw()-style queries, declarative schema in db_schema.xml, and full upgrade compatibility across your Magento minor versions. You own the source. Honest lead time and post-launch support are included.

What you get

Versioned Magento 2 module (Ecosire_CompanyAccounts) delivered under app/code with full source you own

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

di.xml, db_schema.xml, acl.xml, webapi.xml, GraphQL schema and crontab.xml wired to your store

Storefront company-registration, sub-user management and requisition-list UI matched to your theme (Luma or Hyvä)

Admin company/user/role/credit management screens with ACL roles configured

Composer-installable package plus a README covering setup, upgrade and configuration

Smoke-test pass on your environment (registration → sub-user → role gate → credit order → requisition reorder) and a short handover walkthrough

Post-launch support window and compatibility maintenance for your Magento minor-version upgrades

Who this is for

Wholesale distributor selling to trade accounts

Sells to dozens of business buyers whose purchasing teams need separate logins, spend approval and net-terms billing. Uses company credit and sub-user roles to let each customer's staff order without sharing one password.

Manufacturer with named account managers

Assigns a sales representative to every corporate buyer and wants that rep visible on the order grid and reachable from the account. Uses sales rep assignment plus requisition lists for repeat BOM-style orders.

B2B operations / ecommerce manager avoiding Adobe Commerce B2B licensing

Runs Magento Open Source and needs company-account hierarchy and payment-on-account without upgrading to the paid Adobe Commerce edition. Wants an owned, upgrade-safe module rather than a recurring license.

How B2B Company Accounts & Sub-Users Compares

Criterion	ECOSIRE	Custom Build	Competitor
Runs on Magento Open Source without the paid Adobe Commerce B2B license	Included	Included	Partial support
Company hierarchy with sub-users, roles and permissions	Included	Partial support	Included
Company credit / payment on account with credit limit and ledger	Included	Partial support	Partial support
Sales representative assignment surfaced in the admin order grid	Included	Partial support	Partial support
GraphQL + REST service contracts for headless / PWA / ERP	Included	Partial support	Partial support
Upgrade-safe: plugins/observers/declarative schema, no core hacks	Included	Not included	Partial support
Source code owned by you, no recurring license fee	Included	Included	Not included
Installed, configured and supported on your environment by the vendor	Included	Partial support	Not included

Frequently Asked Questions about B2B Company Accounts & Sub-Users

How long does delivery take, and is this an instant Marketplace download?

It is not an instant download. ECOSIRE builds, installs and configures this module on your own Magento install. Typical lead time is about 2-4 weeks depending on whether you run Luma or Hyvä, the depth of your credit/approval rules, and any ERP integration. We confirm a firm timeline after a short scoping call and deliver to your staging environment first.

What do I get for ongoing support and updates after launch?

A post-launch support window is included to fix any defects and answer configuration questions. Because the module uses plugins, observers and declarative schema with no core overrides, it stays upgrade-safe across your Magento minor versions; we provide compatibility maintenance for those upgrades and can extend support under a maintenance agreement. You own the source, so you are never locked in.

Does this work on Magento Open Source, or do I need Adobe Commerce B2B?

It works on Magento Open Source. The whole point is to deliver company accounts, sub-user roles and payment-on-account — features Adobe Commerce ships in its paid B2B edition — as an owned module on Open Source. It also installs cleanly on Adobe Commerce if you prefer, coexisting with or replacing the native B2B feature set per your needs.

How is company credit / payment on account implemented technically?

We add a custom payment method implementing Magento\Payment\Model\MethodInterface, backed by a credit-limit and balance-ledger table in db_schema.xml. An observer on sales_order_place_before checks available exposure before allowing an on-account order, and a cron job emits statements and over-limit alerts. All access runs through service contracts with parameterized queries — no raw SQL, no core hacks.

Can our headless / PWA / Hyvä storefront and our ERP use these features?

Yes. Every company, sub-user, role and credit operation is exposed through PHP service-contract interfaces with matching GraphQL mutations/queries and REST endpoints declared in webapi.xml. Your Hyvä, PWA Studio or custom front end consumes the same API as the Luma storefront, and your ERP can read or write company and credit data over REST for sync.