Subaccounts

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 complete the license update here. If you have an active support package, you receive updates automatically via Composer. If your support package has expired, you can renew your license here or in your account.

You can reach us anytime via Email.