Custom Extensions for SuiteCommerce Advanced Functionality

Starting with SuiteCommerce Advanced (SCA) customization, it's important to note that for optimal results, especially for implementations after the Kilimanjaro release, using themes and extensions is recommended over direct source code modifications. This practice ensures better maintainability and aligns with the modern extensibility strategies provided by NetSuite.

Why Customize SuiteCommerce Advanced?

Customizing SCA allows businesses to tailor their eCommerce sites according to specific needs. Developers can create unique functionalities that enhance the user experience and streamline processes.

Customization Best Practices

When customizing SuiteCommerce Advanced:

• Avoid Direct Edits: Direct modifications to SCA source code are discouraged. Instead, use developer tools to extend or override existing functionalities.
• Leverage TypeScript: As of SCA 2019.2, the source code has migrated from JavaScript to TypeScript, providing better type-checking and development efficiency. Typescript files end with the .ts extension, while earlier versions use .js.

Key Examples of Customizations

1. Create a Custom Module: Introduce new functionality by organizing modules in the appropriate directory structure.
2. Modify JSON Configuration Files: Tailor configuration settings to suit specific business needs.
3. Extend Frontend Configuration Files: Enhance user interface components effectively.
4. Override Template Files: Implement custom designs without compromising the underlying system.
5. Add Custom Web Fonts: Personalize the aesthetic appeal of the site.
6. Display Device-Specific Content: Utilize the responsive capabilities of SCA to provide different visuals for various devices.

Code Structure Examples

• For SCA 2019.2 and later, source files are stored under:
  • Advanced
  • Backend
  • Commons
  • Custom modules should reside in a newly created directory at the same level.
• For SCA 2019.1 and earlier, all custom modules need to be within the Modules directory under a newly created extensions subdirectory.

Getting Started with Custom Modules

To begin creating a custom module, ensure you set up the module directory in the appropriate format: module_name@x.y.z, where module_name indicates the custom feature you are developing.

Conclusion

By adhering to these guidelines, developers can ensure their SCA customizations are aligned with best practices, utilizing the most recent advancements in the SCA environment for improved performance and functionality.

Key Takeaways

• Use themes and extensions for SCA customizations where possible.
• Prefer TypeScript over JavaScript for new developments.
• Organize custom modules properly within the directory structure.
• Follow best practice guidelines to avoid maintenance issues.

Source: This article is based on Oracle's official NetSuite documentation.