B2B Ecommerce Account Management: Organizations, Users, Roles and Permissions

B2B account management models customers as organizations, not individuals. A company has commercial terms (payment terms, credit limit, tax status), one or more locations with ship-to and bill-to addresses, and users with roles such as administrator, buyer, approver and viewer. Permissions control ordering, spending, approvals, invoice access and user management, often per location. Let customer administrators manage their own users, sync terms from the ERP, enforce rules at checkout and keep an audit trail of every change.

This article covers the account data model and permissions. The buyer-facing portal is covered in B2B customer portal, catalogs in customer-specific catalogs, approvals in approval workflows and the overall build in B2B ecommerce development.

Many B2B customers buy for several sites: branches, stores, job sites or departments. Model each as a location with its own addresses and, where needed, its own catalog, payment terms and approvers. Assign users to one or more locations, and let them switch location context when ordering so prices, catalog and shipping are correct.

Visibility should follow responsibility. Buyers see their own orders; location managers see their location; administrators and finance see the company. Invoices, statements, credit notes and payment status should come from the ERP or finance system so they match accounts receivable. See B2B ERP integration.

B2B addresses are often controlled: customers may not be allowed to ship to new addresses without approval, for tax, credit or fraud reasons. Support approved address lists per location, a request process for new addresses, and clear display of bill-to versus ship-to.

Attach payment terms (such as net 30), allowed payment methods and credit limits to the company or location, synchronized from the ERP. At checkout, show available credit, enforce limits (block, warn or route for approval) and record purchase order numbers.

Approvals depend on the account model: who approves for which location, above what amount and for which categories. Store approval rules with the company or location and let administrators adjust them. See approval workflows.

Apply least privilege by default, require stronger authentication for administrators and payment actions, and record an audit trail of user, role, permission, address and payment changes and approvals. Large customers may require SSO with their identity provider and periodic access reviews. See ecommerce security.

Many commerce platforms include B2B account features (companies, locations, roles, catalogs and payment terms), with availability depending on platform and plan. Shopify, for example, provides company profiles and locations in its B2B features. Check whether the platform's model fits your customers' structures before customizing.

An illustrative scenario, not a client case: a building supplies distributor gives each trade customer one shared login, so it cannot tell which employee placed an order and customers cannot control spending. The team introduces companies, locations and individual users with buyer, approver and administrator roles, lets customer administrators invite colleagues, and syncs payment terms and credit limits from the ERP. Support requests to add or remove users drop because customers manage them directly.

B2B accounts work when the model matches real organizations: companies, locations, users and roles, with configurable permissions, synced terms, controlled addresses and audit. Related: customer-specific catalogs and approval workflows.