Study guide

3.1 Features That Need NetSuite Support

Oracle NetSuite SuiteFoundation Specialist Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction and Exam Facts

1.1 Current Exam Facts 1.2 The 2025 Program Change and Keeping the Credential 1.3 The Five Weighted Domains and How to Study Them

2 Enable Features and Renaming Records

2.1 What Enable Features Controls 2.2 Renaming Records and Transactions

3 Support-Only Features and Classifications

3.1 Features That Need NetSuite Support 3.2 Classifications and Subsidiaries

4 SuiteBuilder and Platform Tools

4.1 Custom Forms, Fields, Records, and Subtabs 4.2 Bundles, SuiteApps, and SuiteFlow

5 Navigation, Performance, and Preferences

5.1 Roles, Centers, and Navigation Tools 5.2 Browser Experience and Performance 5.3 User Preferences That Change the Interface

6 Shortcuts, Activities, and the File Cabinet

6.1 Shortcuts Portlet versus the Shortcuts Menu 6.2 Activities, Email, and the File Cabinet

7 Sales Cycle, Quotas, and Forecasts

7.1 Setting Up Sales Force Automation 7.2 Leads, Prospects, and Customers 7.3 Quotas and Forecast Reporting

8 Cases and Marketing Campaigns

8.1 Case Management Setup and Use 8.2 Campaigns and SuitePromotions

9 Sales Orders, Fulfillment, and Payments

9.1 Sales Orders and General Ledger Impact 9.2 Fulfillment Controls 9.3 Customer Payment Methods

10 Returns, Credits, and Refunds

10.1 Return Authorization Forms and Ledger Impact 10.2 Return Controls and Refunds

11 Item Types and Inventory

11.1 Item Types and Best Uses 11.2 How Transactions Change Inventory Levels 11.3 Advanced Inventory Features

12 Pricing, Billable Costs, and Payables

12.1 Sales Pricing Options 12.2 Billable Time and Expenses 12.3 Purchase Approval Routing 12.4 Accounts Payable Steps and Ledger Impact

13 Finding Records and Saved Searches

13.1 Global Search, Lists, and Reports 13.2 Elements of a Saved Search

14 Portlets and Data Management Tools

14.1 Portlet Types 14.2 Inline Editing, Mass Update, CSV, and Duplicates

15 Support, Help Resources, and Releases

15.1 Working with NetSuite Support 15.2 Where to Look Up a Feature 15.3 Release Cycles and Release Preview

16 Custom Roles and Data Access

16.1 What a Custom Role Can See and Do 16.2 Building Roles Instead of Sharing Administrator

17 Authentication, Security Questions, and Settings

17.1 Passwords and Two-Factor Authentication 17.2 Security Questions 17.3 The Settings Portlet

18 Tracking Changes to Records

18.1 System Notes and Other Audit Tools 18.2 Ledger Impact and Field-Type Changes

3.1 Features That Need NetSuite Support

Key Takeaways Explain This Topic AI

Administrators turn features on at Setup > Company > Enable Features, but a checkbox is not automatically reversible after transactions or an inventory distribution exist.

After Multi-Location Inventory is enabled and items are distributed, Oracle NetSuite Help says you cannot turn the feature off without contacting Customer Support.

Enabling Multi-Location Inventory leaves existing unallocated quantities in a null location until an Inventory Distribution places them into one or more locations.

To disable Multi-Subsidiary Customer, reverse or delete transactions for customers and their secondary subsidiaries, then remove all secondary subsidiaries from the customer records.

Inactivating a customer, or leaving the primary subsidiary plus one secondary subsidiary, does not finish that cleanup.

Last updated: September 2026

The March 2024 SuiteFoundation study guide asks you to identify NetSuite features that require NetSuite Support intervention. The study method is narrower than a tour of every checkbox. Review the SuiteAnswers topics on enabling Multi-Location Inventory and the other Enable Features topics, and know that some features cannot be fully undone by an administrator after transactions exist. An administrator still does the turning-on. The page is Setup > Company > Enable Features. Several current Help topics reach that same page through Setup > Company > Setup Tasks > Enable Features. Checking a box makes a capability available. Clearing the box later depends on which feature you chose and on the transactions or quantities already saved.

This chapter stays with the two examples NetSuite's own materials use. The March 2024 study notes name Multi-Location Inventory as the inventory example, and the October 2024 sample test uses Multi-Subsidiary Customer as the customer example. Oracle NetSuite Help does not hand you a longer catalog of features that Customer Support must enable, so this chapter does not invent one. Where Help is silent, do not add a Support requirement. Help does require Customer Support for one specific action below, and it does not require Customer Support to enable or disable Multi-Subsidiary Customer. NetSuite's materials still use both features as the published examples: one shows a Support call after inventory has been distributed, and the other shows a feature an administrator cannot fully undo until the related transactions and subsidiary assignments are cleaned up.

Multi-Location Inventory and the quantities you already own

Multi-Location Inventory associates each inventory item and each inventory transaction with a location. You can track purchasing cost, sales income, on-hand quantity, and value for an item in each location, and you can transfer inventory between locations. Reports can filter inventory status, revenue, valuation, activity, and fulfillment by location, depending on the other features in the account. That reporting power is the reason companies turn the feature on. It is also the reason they need a plan before they do it.

Help tells administrators to understand the feature before they enable it. The Locations overview says to read the Multi-Location Inventory topic and decide whether it fits the company. The practical reason is the stock you already have. Enabling the feature does not leave those quantities in a company-wide bucket you can label during a later weekend. After the feature is on, unallocated inventory items are treated as sitting in a null location. Help says to distribute any unallocated inventory before you enter those items on inventory transactions. Until that happens, the quantity is not ready for ordinary inventory activity.

That placement is an Inventory Distribution . The transaction allocates inventory from its original, unassigned state to one or more locations and updates item details and quantities for the locations you choose. A simple distribution sends stock to a single location. A manual distribution lets you enter the quantity for each location. Help recommends doing the work during non-peak hours, distributing all unassigned inventory at one time, and avoiding changes to transactions dated before the distribution. If you change those earlier transactions and then return to distribution, the undistributed quantity can look wrong or negative. The documented correction for that error is an inventory adjustment at Transactions > Inventory > Adjust Inventory. Inventory is distributed only when the stock level is zero or greater. None of those details is optional color. They show why an administrator who checks the box without a location plan immediately owns a data-cleanup project.

An administrator enables the feature. Nobody files a Support case just to check it. Help's inventory-setup table for inventory with Multi-Location Inventory lists the prerequisites by subtab: Locations on the Company subtab; Sales Order, Advanced Shipping, and Advanced Receiving on the Transactions subtab; and Inventory plus Multi-Location Inventory on the Items & Inventory subtab. The Items & Inventory feature list states the same dependency in shorter form. You also need Locations, Inventory, Advanced Shipping, and Advanced Receiving. Enabling Multi-Location Inventory creates system-generated Transfer Orders and Inventory In Transit accounts. Locations themselves are a separate checkbox. Go to Setup > Company > Enable Features, open the Company subtab, check Locations, and save. A location record means an office or a warehouse. Help says not to use a location record for a bin, shelf, or dock inside a warehouse, because that choice causes problems with fulfillments, LIFO and FIFO costing, and reporting. Bins belong to the bin features.

The point where Customer Support enters

Help draws the Support line at disable time, not at enable time. After you enable Multi-Location Inventory and distribute items, you cannot turn the feature off without contacting NetSuite Customer Support . The same warning appears on the inventory setup comparison and on the Items & Inventory subtab. Help does not say Customer Support must check the box. OneWorld adds a planning consequence rather than a different enable path. Help says the Multi-Location Inventory feature is required for NetSuite OneWorld accounts that use the Inventory feature. That is a requirement to track item quantities by location. It does not make a warehouse into the legal entity, and it does not mean the Locations checkbox and the Multi-Location Inventory checkbox are the same switch. The next section separates those ideas.

For this objective, remember the sequence. An administrator turns the feature on. Existing unallocated quantities must be placed into locations before they are used on inventory transactions. After that distribution, Customer Support is who Help tells you to contact if the feature needs to be turned off. An administrator who treats the original checkbox as a switch that can be cleared on Friday afternoon is describing a different product than the one Help documents.