Magento 2 subaccounts extension for company users, employee logins, address control, order visibility, payment and shipping rules, with optional roles, budgets, approvals, catalogs, APIs, and Hyvä support.
SoftwareSilo Sublogin adds managed subaccounts to an existing Magento 2 customer account. A company no longer needs to share one password among several employees. Each buyer receives an individual login, while orders and account ownership remain connected to the main customer.
Built around the Magento customer you already use: The extension does not force every business customer into a separate company entity. A merchant enables subaccounts for the relevant customer, and that customer or an administrator can create and manage the permitted users. This makes it practical for Magento Open Source stores as well as Adobe Commerce projects with a customer-based account model.
Individual access with central oversight: Each subaccount has its own email, password, name, status, store and website context. New users can require email confirmation, be activated or deactivated, receive a password reset, and have an optional expiry date. The main account can be copied on selected messages and, if enabled, switch into a subaccount without asking for its password.
Know who placed an order: Quotes and orders keep the originating subaccount ID. The store can let a subaccount see only its own orders or make the wider customer history available. Order emails can go to the subaccount, the main customer, selected optional recipients, or the store owner according to configuration.
Three address models: Subaccounts can use the main customer's shared addresses, maintain individual address books, or work with a restricted set of approved addresses. The store can control whether new addresses may be created at checkout, whether customer defaults are applied, and whether the main account can use addresses created by its subaccounts.
Checkout rules without a role add-on: The base module can filter payment and shipping methods per subaccount. It can also bind users to the customer's default billing address. These controls are useful when a branch may use only an approved carrier, delivery address, or payment method.
Shared or separate shopping context: Decide whether carts and wishlists are shared with the main account or kept by the individual subaccount. A purchasing team can collaborate around one cart, while another merchant can keep each employee's work separate.
Self-service and admin management: Authorized main-account users manage subaccounts from My Account. Store administrators have a central grid and customer-level management. Frontend mass actions can activate, deactivate, or delete selected users according to configuration.
Reports are part of the core: The base extension includes subaccount order and product reports with CSV export. This gives the main account a practical view of who ordered which products without requiring the separate Import/Export add-on.
Roles and organization groups are optional: The Sublogin Role add-on adds reusable roles, a company-specific group hierarchy, and detailed permissions for catalog access, prices, cart, checkout, orders, invoices, subaccount management, and add-on functions. Permissions can distinguish all groups, the same level, and lower levels.
Budgets are optional: The Sublogin Budget add-on supports per-order limits and daily, monthly, and yearly budget periods for customers and subaccounts. The merchant chooses which order statuses consume budget and whether subtotal or grand total is used. A separate One-Time Budget add-on provides a single-use order allowance.
Order approval is optional: The Order Approval add-on routes selected subaccount orders through approval states. Approvers can approve, decline, or edit orders according to their permissions. Configurable notices, comments, statuses, and email recipients make the handoff visible to buyers and managers.
Catalog access is optional: The Sublogin Custom Catalog add-on assigns product sets to individual subaccounts and can combine them with the catalog rules of the main customer. This is useful when teams or branches may order only an approved assortment.
Integration and storefront add-ons: CSV Import/Export handles larger user sets. The SOAP/REST API add-on exposes subaccount search, create, update, and delete operations through Magento web APIs. Separate commercial options cover GraphQL and Hyvä, with Hyvä compatibility packages for Roles, Budgets, Order Approval, and Custom Catalog.
A modular alternative to a full B2B company suite: SoftwareSilo Sublogin fits merchants who want to start with individual users under a customer account and add governance only where it is needed. The base module can remain straightforward, while larger customers receive roles, groups, budgets, approvals, restricted catalogs, or integration tools through clearly separated add-ons.
Plan the account model before rollout: Decide who owns the account, who may create users, whether orders and carts are shared, which addresses are allowed, and which add-ons apply. A short pilot with one real customer organization usually exposes these choices more reliably than a generic feature checklist.
Create and manage subaccounts under one main account for teams, departments, or locations. The maximum number is configurable per customer account.
Define core access behavior and order visibility in the base module. Advanced role-based permissions are available via Sublogin Role (Add-On).
Use shared, individual, or restricted address usage depending on your process requirements.
Define whether subaccounts see only their own orders or shared history, while preserving clear order attribution.
Enable shipping and payment filters to control checkout behavior for each subaccount.
Enable a shared cart and shared wishlist across main account and subaccounts when your buying process requires it.
Allow main accounts to switch directly into subaccounts to handle setup, support, and process checks faster.
Use core reports for order and product analysis, including CSV export in the base module.
Extend subaccounts with default roles, group assignment, and inheritable rights for clearly structured team hierarchies.
Control budget logic, Pay on Budget rules, and checkout limits per subaccount through the add-on.
Define approval states, checkout notices, and handling rules for orders that require supervisor approval.
If your environment differs from the listed requirements, we can check compatibility in advance. Please contact us via our contact form.
It gives several people individual logins under one main Magento customer account. Each order remains linked to the customer and records which subaccount placed it, so a company can stop sharing one password among employees.
The base includes user creation and management, individual credentials, activation and confirmation, order attribution and visibility, three address models, payment and shipping filters, shared or separate carts and wishlists, email routing, login as subaccount, and order and product reports.
No. Roles and groups, budgets, order approval, custom catalogs, import/export, APIs, and Hyvä support are separate add-ons. This lets merchants buy only the governance features their customers require.
It solves the multi-user part of a company account by extending an existing Magento customer. It does not create the same standalone company entity used by Adobe Commerce B2B or some competitor suites. The customer remains the parent account.
Yes. Sublogin is designed to add company users to Magento Open Source and can also be used in Adobe Commerce projects. Check the current compatibility table on the product page against your Magento and PHP versions.
The permitted number is controlled at the customer level. A merchant can set the maximum appropriate for each main account instead of applying one universal number to every customer.
Yes. Each subaccount has its own email and password within its Magento website context. An email address cannot simultaneously belong to a normal customer and a subaccount on the same website.
Yes, when impersonation is enabled and the current account has permission. This helps the main customer review setup or assist an employee without asking for the employee's password.
Yes. The store can require a confirmation link before a new subaccount becomes usable. Password reset and reactivation emails have separate configurable templates.
Yes. Subaccounts have an active status and can have an expiry date. Authorized users can activate or deactivate accounts, and the store can configure reactivation behavior.
Yes. The store can restrict each subaccount to orders it placed. If a shared view is preferred, the wider customer order history can remain available.
Yes. The originating subaccount ID is stored on quotes and orders. Reports and order context can show which employee or branch created the purchase.
Yes. Email routing can copy the main customer, optional customer or subaccount addresses, BCC recipients, and the store owner for selected templates.
Shared mode uses the main customer's addresses. Individual mode gives each subaccount its own address book. Restricted mode limits the user to assigned, approved addresses.
The merchant decides. New addresses can be allowed or disabled at checkout, and the configuration also controls default addresses and visibility of customer addresses.
Yes. The base module can filter available payment methods for each subaccount when the payment filter is enabled.
Yes. The base module stores allowed full Magento shipping method codes per subaccount and filters checkout options accordingly.
Yes. Cart sharing with the main account is optional. If it is disabled, each subaccount keeps its own cart context.
Yes. Wishlist sharing is configured separately from cart sharing, so the merchant can choose either behavior independently.
It adds reusable roles, customer-specific groups and group hierarchies, plus detailed permissions for product lists, prices, carts, checkout, orders, invoices, user management, and supported add-ons.
Yes, with the Roles add-on. Context-aware permissions can apply to all groups, the current level, or lower levels in the customer's group structure.
It supports per-order caps and daily, monthly, and yearly budget periods for customers and subaccounts. Budget consumption can use selected order statuses and either subtotal or grand total.
Yes, through the separate One-Time Budget add-on. It provides a single order allowance and deactivates after the first applicable order.
Orders that require approval enter configured states. Authorized approvers can approve, decline, or edit them according to permissions, with configurable notices, comments, statuses, and emails.
Yes, with the Custom Catalog add-on. It assigns product sets to subaccounts and can combine those sets with the catalog rules of the main customer.
Yes, with the Import/Export add-on. It plugs into Magento data transfer for bulk user maintenance. The CSV reports included in the base module are reporting exports, not account import files.
Yes, through the SOAP/REST API add-on. It exposes Magento web API operations to search, read, create, update, and delete subaccounts subject to API authorization.
GraphQL is listed as a separate commercial add-on for headless storefront projects. Confirm the current schema and required package for the exact frontend before purchase.
Hyvä support is sold separately. The ecosystem also contains dedicated Hyvä compatibility packages for Roles, Budgets, Order Approval, and Custom Catalog, so the selected add-on combination should be reviewed.
Test user creation, confirmation, password reset, order visibility, attribution, all address models used, payment and shipping restrictions, cart and wishlist behavior, email recipients, refunds, and every purchased add-on with a real company structure.
The license is valid for one Magento installation, including multi-website operation. In addition, the module may be installed on any number of development or staging servers. You can find further details in our license terms.
Installation and configuration are not included in the price. On request, we can support you with a smooth integration into your system.
Composer is PHP's package manager, and Magento 2 uses it to install modules and their dependencies. After purchase, the commands for your module are available under Licenses in your customer account. First add the private SoftwareSilo repository and your license token. Then install the listed package with composer require and run php bin/magento setup:upgrade and php bin/magento cache:clean.
You can pay by credit card (Stripe) or bank transfer (prepayment). For credit card payments, the order is processed immediately and the access credentials are provided directly in a separate follow-up email.
After credit card payment, you immediately receive access credentials to obtain the module via Composer. For bank transfer, access is granted once the invoice is paid.
Custom requests are no problem. We tailor our Magento 2 modules to your project and maintain a dedicated internal version so we always know exactly what runs on your system for support.
On each module detail page, you can request your own demo instance and test the module intensively for 7 days. However, we do not provide a local demo version.
No, the source code of our modules is not encrypted. If you need a customization, feel free to send us a request. We will get back to you promptly with a non-binding quote.
You can add a support package to your order. It includes assistance as well as updates and upgrades related to the module. No continuous subscription is required.
You can reach us anytime via eMail.
Map purchasing, sales, or service units as dedicated subaccounts and control access by team.
Manage branch locations as subaccounts with clear separation of addresses and order context.
Run multiple locations under one main account and define which processes stay central or local.
Provide employees with dedicated accounts and limit visibility plus checkout options based on internal rules.
Organize sales structures with subaccounts and keep orders clearly attributed to the acting account.
Manage faculties or institutes as subaccounts and control access on one shared account level.
Request a personal demo and test the module with realistic sample data in Magento Admin and the storefront. Take your time to see whether it fits your requirements and workflows.
Practical Magento 2 guides, developer documentation, and API references for installation, configuration, and troubleshooting.
Go to Knowledge BaseDo your requirements go beyond the capabilities of our Magento 2 modules? We develop suitable Magento 2 modules and integrations for your business processes.
Request now