SuiteCommerce Extensibility API

Note:

This information refers to the SuiteCommerce and the Aconcagua release of SuiteCommerce Advanced and later.

SuiteCommerce includes a conceptual layer on top of existing SuiteCommerce architecture. This layer lets extension developers customize a Commerce web store and SuiteCommerce InStore (SCIS) with extensions, so that they don't have to change or customize the underlying application code.

Layers of the SuiteCommerce architecture with the Application layer on the bottom, the Extensibility API layer in the middle, and the Developer Code layer on the top.

Developers build extensions in their local environment with the extension developer tools. This environment/workspace is represented by the Developer Code Layer in the image above. Each extension can include JavaScript, SuiteScript, or configuration files to do its job. In this code, developers include API calls to components in the Extensibility API. This is represented by the Extensibility API Layer.

The API accesses frontend and backend modules, such as routers, models, and views, in the Application Layer. This way, extensions are separated programmatically from the main application and interact only with the API, not with the application. This makes customization easier and seamless for extension developers and ensures that future updates to the application do not compromise customizations.

See the following topics for more information about the Extensibility API:

See the Overview topic of Extensibility API reference for information about each component and its methods and properties.

Related Topics

General Notices