Next-generation platform

Launching Sterling Store Engagement from another application

You might want to embed certain capabilities of Sterling Store Engagement within other web applications. In such cases, you can launch a specific wizard of Sterling Store Engagement from another application.


  • In case of SSO, if you are not authenticated the login screen displays. Post authentication you are taken to the requested URL. If you are already authenticated, you are directly taken to the requested URL.
  • In case of non-SSO, you are already authenticated and there is a valid active Sterling Order Management System session.


  1. Identify the URL for a particular business flow by launching the application in any environment and navigate to the flow.
  2. Copy the URL from the address bar in the browser.

    Any URL used in Sterling Store Engagement can have static and dynamic content.

    For example, http://<localhost>:<port number>/isf/store-frontend/shell/shipment/summary/SO20200818CSHPKey. In this URL, isf/store-frontend/shell/shipment/summary/ is the static content. The SO20200818CSHPKey is the shipment key and dynamic content. The shipment key is different for each shipment.

    For more information about routing definition, see the ShipmentListSummaryRoutingModule routing module that is present in <store_temp>/packages/features/shipment-list-summary/src/app/features/shipment-list-summary/shipment-list-summary-routing.module.ts

    To understand the dynamic content of a URL, see the angular route definition of a particular feature.

const routes: Routes = [
                                        path: 'summary/:shipmentKey',
                                        component: ShipmentSummaryPageComponent,

From the route definition, you can view the dynamic content that maps to the shipment key.

When an external application launches the Shipment summary screen for a particular shipment, the URL will be http://<localhost>:<port number>/isf/store-frontend/shell/shipment/summary/<ShipmentKey>