SuiteCommerce InStore Integration for Point-of-Sale Management

SuiteCommerce InStore (SCIS) is a web-based point-of-sale application designed specifically for the U.S. market, providing a touch-based user interface optimized for tablet use. This integration empowers merchants to manage commerce transactions both online and in-store efficiently. With SCIS, transactions are categorized into distinct records based on their origin; for instance, web orders create a Sales Order record, while in-store purchases can generate either a Cash Sale or an Invoice record.

Key Features of SCIS

When connecting your commerce website with SCIS, customers benefit from a unified transaction overview, enabling them to:

• Access a comprehensive list of all purchases on the Purchase History page, with the ability to filter between in-store and online purchases. The Origin column clarifies the source of each transaction.
• Print a detailed PDF receipt for any transaction directly from the Purchase Details page.
• Check if a purchase correlates with a sales quote for continuity in order tracking.

Implementation Considerations

To successfully implement SuiteCommerce InStore integration, ensure that your system meets the necessary prerequisites:

1. Installation: Make sure the latest SuiteCommerce InStore and SuiteCommerce or SuiteCommerce Advanced bundles are installed in your account.
2. Configuration: You need to configure NetSuite for SCIS Integration. Depending on which version of SuiteCommerce Advanced you are utilizing, follow the corresponding steps for site configuration.

Configuration Steps for SCIS Integration

1. Navigate to Commerce > Websites > Configuration in your NetSuite dashboard.
2. Select the appropriate domain you wish to configure.
3. Locate the My Account tab and then the SCIS Integration subtab within the SuiteCommerce Configuration record.
4. Modify the feature properties as required and save the Configuration record.

Additional Setup for Specific Versions

For users operating under SCAs like Denali and Mont Blanc, customization procedures involve:

1. Creating a custom module that specifies the backend Configuration object.
2. Setting the isSCISIntegrationEnabled property in the module to true before saving and deploying the changes.
3. Avoid modifying the original Configuration.js file directly; refer to the SCIS Integration Subtab for best practices in custom JavaScript development.

Who This Affects

The implementation of SCIS primarily impacts:

• Administrators: Responsible for the overall system setup and configuration.
• Developers: Tasked with creating custom integration solutions or enhancements.
• Retail employees: Utilizing SCIS for everyday transactions and customer service.

Key Takeaways

• SuiteCommerce InStore allows efficient in-store and online purchase management through a tablet-friendly interface.
• Clear differentiation of transactions by origin is provided, enhancing customer experience.
• Proper configuration of SCIS ensures seamless integration with existing order management systems.
• Developers must understand customization best practices to leverage SCIS effectively.

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