SuiteCommerce Advanced Application Modules Overview
SuiteCommerce Advanced comprises three core applications: Checkout, My Account, and Shopping, each with distinct modules and starter files.
Starting with SuiteCommerce Advanced (SCA), the framework is designed to support multiple applications, namely Checkout, My Account, and Shopping. Each of these applications is equipped with its own distinct modules that play a critical role in defining dependencies and the overall layout of the application.
What Are the Core Applications?
The three core applications of SCA are:
-
My Account:
- Directory: MyAccountApplication
- Entry Point:
SC.MyAccount.Starter.ts
-
Checkout:
- Directory: CheckoutApplication
- Entry Point:
SC.Checkout.Starter.ts
-
Shopping:
- Directory: Shopping Application
- Entry Point:
SC.Shopping.Starter.ts
These applications not only provide essential functionalities but also structure the way users interact with the core features of SCA.
Understanding the Starter Files
Each application module contains a starter file that defines the starting node or entry point for the application. Depending on the version:
- Recent versions utilize TypeScript files (
.ts) - Earlier versions contained JavaScript files (
.js)
The starter files delineate all dependencies crucial for each application. Modules that are not referenced in these starter files will not be included in the application build.
Note: When developing a new module, it is imperative to include it in the starter file of each respective application relying on that module. This ensures that all necessary components are recognized during application execution.
The Hierarchical Structure
SCA modules are organized in a hierarchical manner, where:
- Top-Level Modules: Act as broader feature collections (such as Shopping, Checkout, My Account).
- Lower-Level Modules: Serve individual functionalities within these applications. This structured approach facilitates ease of development and maintenance.
Understanding this hierarchy is key for developers aiming to customize or extend any part of SCA.
For more insights on creating modules, please refer to the related topics.
Related Topics:
Who This Affects
This information is particularly relevant for:
- Developers: Engaged in customizing and extending SuiteCommerce Advanced applications.
- Administrators: Managing application functionalities and user experience.
Key Takeaways
- SuiteCommerce Advanced encompasses three primary applications: Checkout, My Account, and Shopping.
- Each application has specific modules with starter files that dictate dependencies.
- Creating new modules requires updates to respective starter files to ensure proper functionality.
Source: This article is based on Oracle's official NetSuite documentation.
Frequently Asked Questions (4)
How should I include a new module in a SuiteCommerce Advanced application?
Are the starter files for SuiteCommerce Advanced applications always in TypeScript?
What role do top-level modules play in SuiteCommerce Advanced?
Do undeclared modules in starter files get included in SuiteCommerce Advanced application builds?
Was this article helpful?
More in Commerce
- Available Items Only Feature in NetSuite 2026.1
Available items only filtering boosts sales efficiency in NetSuite 2026.1 with Intelligent Item Recommendations.
- Commerce Extensions in NetSuite 2026.1
Commerce Extensions in NetSuite 2026.1 enhance performance and user experience in eCommerce.
- Convert Multiple Transaction Line Items into Configured Items in
Enhance transaction processing in NetSuite by converting multiple line items into configured items with improved session handling.
- New SuiteCommerce Features in NetSuite 2026.1
New SuiteCommerce features in NetSuite 2026.1 enhance user experience and improve eCommerce efficiency.
