What the organization unites

AI Commerce organization groups customer accounts from the same company under a common organization ID. Each connected customer also has an Organization role. The Organizations view in the control panel shows the organization name, business ID, and the customer accounts connected to it.

The organization's administrator can view orders from customers in the same organization in the online store and manage members of the organization. Other roles limit ordering and transactions according to the role. However, an organization is not created simply because customers have the same Business ID: each customer account must be linked to the organization separately.

Check the organization register

AI Commerce 's organization register is opened from the Customers > Organizations view. The list shows existing organizations and their customer numbers. Open the organization to check the name, Business ID, and Organization's customers list.

You cannot create an organization in the control panel. The name and business ID of an existing organization can be edited, and field changes are saved automatically.

Edit organization name and business ID

AI Commerce organization information is edited by opening the organization from the list. The name is required. The business ID is optional, but two organizations cannot have the same business ID. Exit the edited field and wait for the automatic save to complete.

An organization can only be deleted when there are no more customer accounts associated with it. Move or disconnect all customers first. Deleting is a permanent action that cannot be undone.

Link an existing customer account to an organization

An existing AI Commerce customer account is linked to the organization from the Customers view:

1. Find the customer and open their details.
2. Open the client's Settings .
3. Select the correct organization in the Organization field.
4. Select Organization Role .
5. Wait for the field-specific recording to complete.

Return to the Organizations view and make sure that the customer appears in the Organization Customers list for the correct organization. The connection is also done in maintenance if the customer account has already existed in the online store before the organization was created.

Choose an organizational role based on your purpose

Choose AI Commerce organizational role based on your intended use: the e-commerce roles are Administrator, Subscriber, Viewer, and Requester. Their technical role IDs are 1–4. Verify the role ID before making a large-scale change.

• The administrator manages the organization's members and sees the orders of all customers in the organization.
• The subscriber can place orders on behalf of the organization.
• The viewer cannot take the order to the checkout.
• The requester uses a workflow based on the order request, depending on how the transaction is executed.

Every organization using self-service must have at least one Administrator. Test roles with separate test accounts before deploying; don't infer permissions based on username alone.

Manage members in the online store

Manage AI Commerce organization members in the online store by opening the Organization page of your account as an Administrator. The page displays the organization members and the Add New function. For a new member, enter the email address, name, and organizational role.

The system creates a customer account under the organization and sends the user a password change link. The user can then set a password and log in to the online store. The administrator can edit the allowed fields for organization members; The viewer is not allowed to make the same changes to member management.

In addition to the role, the organizational member's information may include blocked payment and delivery methods and payment reference enforcement. The visibility and exact use of these fields depend on the implementation of the online store, so please verify them for each store before giving customer instructions.

Check subscription rights and subscription history

Check AI Commerce organization's order rights and order history, as the role affects both checkout access and history restrictions. The viewer is blocked from checkout. The administrator's order history includes orders from their own account as well as orders from customers connected to the same organization; other roles only see orders from their own customer account.

Test at least one Admin, Subscriber, and Viewer account. Make sure Viewer cannot subscribe, Subscriber can subscribe, and Admin can see the organization's order history without logging into other members' accounts. Also, check for any cart or order request migration separately, as this may be a store-specific workflow.

Treat ERP connection as a separate integration

Treat AI Commerce 's ERP connection as a separate integration, as organizations do not solely determine the customer or price allocation in the ERP system. If organization-specific prices or entitlements are imported from the ERP, the integration must explicitly allocate the data to AI Commerce organization and its customer accounts.

The same Business ID does not replace an organizational union. Document the organizational identifier, customer account assignment, and pricing rule used in the integration and test them with one organization before widespread deployment.

Deploy your organization in a controlled manner

Deploy your AI Commerce organization in a controlled manner: first review the existing organization details, connect customer accounts, select roles, and finally test the e-commerce permissions. Creating a new organization is missing from the Control Panel, so the organization must be established through an approved maintenance process before starting the other steps.

First, name the Administrator, connect other customer accounts, test the roles, and only then check organization-specific prices, payment and delivery method restrictions, order history, and possible ERP connection.