Department Purchasing
Use Sublogin when several departments buy through one Magento customer account but need separate people, addresses or controls.
Example structure
Northstar Industrial Supplies GmbH
└── Operations
├── Procurement
└── Warehouse
The base package creates the individual buyer accounts. The Role add-on creates the groups shown above and gives each job a reusable permission set.
A practical setup
| Buyer | Base controls | Optional add-ons |
|---|---|---|
| Procurement buyer | Selected office and warehouse addresses, own-order view | Buyer role, monthly budget |
| Warehouse buyer | Warehouse delivery address, restricted shipping methods | Restricted product catalog |
| Operations approver | Company-order visibility | Approver role and parent group |
These are examples, not records or roles installed by the package.
Build it in a safe order
- Create the main customer and verified company addresses.
- Create one buyer per real person, not one shared login per department.
- Test base checkout and order ownership.
- Add Role and create the smallest set of reusable roles.
- Add groups only when the hierarchy is needed for administration or approval.
- Add Budget, Custom Catalog or Order Approval one at a time.
- Repeat checkout as every buyer type.
Avoid hidden conflicts
A product may be allowed by the role but removed by Custom Catalog. A payment method may be allowed for the sublogin but hidden by Budget enforcement. An order may pass Budget but still cross the buyer's approval threshold.
When a journey fails, inspect the controls in that order rather than granting broad permissions.
Related: Roles, Permissions and Groups, Budget Management, and Order Approval.