Standard and Custom Records in SuiteCommerce InStore

Understand how standard and custom records work in SuiteCommerce InStore to manage sales, customers, and transactions efficiently.

·2 min read·1 views·View Oracle Docs

SuiteCommerce InStore (SCIS) is a web-based point-of-sale application that leverages NetSuite's data structures to manage sales and transactions, making it essential for efficient retail operations. SCIS utilizes both standard NetSuite records and custom records to facilitate a smooth transactional experience.

What Are Standard and Custom Records?

SCIS stores data using both standard records—such as items, customers, and employees—and custom records that are part of the SCIS SuiteApp. When installing SCIS, additional SCIS custom fields are incorporated into the standard NetSuite records to enhance data handling. This integration is crucial for efficiently managing employee access and customer transactions.

Importance of Employee Records

When creating employee records in SCIS, it’s vital to assign appropriate roles that align with their responsibilities. For instance, employees tasked with processing returns need more than just basic transaction permissions. Proper configuration of employee roles ensures smooth operation and compliance with your organization’s policies.

Configuration of Custom Fields

Many of the custom fields and records introduced by the SCIS SuiteApp allow for optional configuration. Administrators can evaluate the necessity of these fields based on business needs. To view the complete list of custom fields related to SCIS, refer to the section concerning SCIS Custom Fields, Lists, Records, and Searches.

Managing Sales and Transactions

Once a transaction is processed through SCIS, administrators can access and alter it within NetSuite. This capability allows for comprehensive oversight of sales activities, giving sales associates the tools they need to manage customer profiles, check transaction histories, and handle returns or exchanges effectively.

Key Considerations

  • Ensure the correct location and subsidiary records are set up for employee access.
  • Understand the SCIS user roles necessary for transaction processing.
  • Explore configuration options available for SCIS custom records and fields.

Note: Configuration options for the SCIS SuiteApp can differ based on your organization’s setup. Always review your custom fields for potential impacts on transactions and employee records.

Related Topics

  • SuiteCommerce InStore Installation
  • SCIS Configuration
  • Configuring Records for SCIS
  • Customizing the Configuration File
  • SCIS Roles and Permissions
  • SCIS Cash and Transactions
  • SCIS Custom Fields, Lists, Records, and Searches

Understanding the interplay between standard and custom records in SuiteCommerce InStore enhances your organization’s capability to deliver exceptional customer service and efficiently manage retail operations.

Frequently Asked Questions (4)

Do I need to configure custom fields when using SCIS?
Many custom fields introduced by the SCIS SuiteApp are configurable. Administrators should decide on their necessity based on business needs by reviewing the SCIS Custom Fields section.
What roles should employee records have in SCIS to handle returns?
Employees tasked with processing returns need more than basic transaction permissions. Proper configuration of employee roles aligned with their responsibilities is crucial for operations.
How do standard and custom records interact in SuiteCommerce InStore?
SCIS uses standard records like items and customers, alongside custom records from the SCIS SuiteApp. This integration enhances data handling, particularly for employee and transaction management.
Are there specific considerations for setting up location and subsidiary records in SCIS?
Yes, it's important to ensure that the correct location and subsidiary records are set up for employee access, as these are key for transaction processing and managing sales activities.
Source: Standard Records and Custom Records Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Commerce

View all Commerce articles →