Elastic Path Account Management Overview Guide

Account Management Workflow

Account Management Workflow

This section explains Account Management service workflow in association with Elastic Path Commerce.

The merchandisers use Elastic Path Commerce Manager to configure store catalogs, pricing, and other store configurations. The seller administrators use the Account Management service to create and manage corporate accounts for buyer organizations and the divisions of these stores.. The following diagram provides the workflow for the buyer and seller within Account Management service:
Figure 1. Elastic Path Account Management Workflow

Seller Admin Workflow

The seller administrators adds organization and the divisions as in the following workflow:
  1. The seller administrators logs in to the Account Management user interface with the credentials.
  2. The seller admin is redirected to the Keycloak identity provider for authentication.
  3. Browser is redirected back to the Account Management user interface with authentication code if authentication is successful. An error code or message is returned if authentication fails.
  4. The Account Management user interface calls the Account Management APIs to create the organization or divisions or to add associates as required.
  5. The Account Management API queries database to get the details of the existing organizations or to add the new organization configuration.
  6. The Account Management service uses the division-based or organization-based pricing to map an associate shopping for a division to a specific customer that belongs to a customer segment to provide exclusive commerce experience for the division. For more informations, see the Elastic Path Account Management Configuration Guide.

Buyer's Shopping Worflow

Only an associate can shop on behalf of a division in B2B commerce. The following workflow provides list of activities in an associate shopping workflow:

  1. An associate logs in to the seller organization’s commerce site or storefront.
  2. The associate is redirected to the Keycloak identity provider for authentication.
  3. The associate enters user credentials in to the identity provider.
  4. Browser is redirected back to the storefront with authentication code if authentication is successful. An error code or message is returned if authentication fails.
  5. Storefront sends the authentication code to the Account Management API.
  6. The Account Management API verifies the associate's identity with the identity provider using the authentication code.
  7. The Account Management API returns an access token to the storefront to access the storefront commerce shopping API.
  8. The storefront uses the The Account Management API's access token to query and select a division to shop.
  9. The Account Management user interface returns an access token to the storefront for the selected role that the associate selects.
  10. The storefront uses the shopping API access token to complete the shopping.