Make NetSuite navigation work the way your team works
The NetSuite Create New menu gives users a fast way to start transactions, records, and other common activities. However, the default menu does not always reflect how a finance, sales, operations, or purchasing team actually works. When users repeatedly search for the same transaction types or scroll past options they never use, a small navigation problem becomes a daily productivity drain.
We recommend customizing the menu around each role's real responsibilities. A finance user should reach journal entries, vendor bills, and customer payments quickly. A sales user needs a different set of actions, such as opportunities, sales orders, and customer records. Warehouse and purchasing users need another arrangement entirely.
This guide explains how to customize the NetSuite Create New menu, how to decide which links belong there, and how to keep the experience consistent without creating unnecessary complexity.
Why customize the NetSuite Create New menu?
NetSuite is designed to support many business processes in one environment. That flexibility is valuable, but it also means the standard navigation experience may expose more options than an individual user needs.
A personalized Create New menu improves the user experience in several ways.
It reduces repeated navigation. Users reach frequently used records without opening multiple menus or relying on global search.
It supports role-based work. The most useful actions differ between an accounts payable specialist, a sales representative, an inventory manager, and an executive.
It improves adoption. A workspace that reflects familiar processes feels easier to use, especially for occasional NetSuite users. Role-based dashboards, shortcuts, quick searches, and configurable layouts are among the reasons NetSuite is generally adaptable when it is configured around user responsibilities. Our NetSuite FAQs and user experience guidance provides additional context on configuring NetSuite for different users.
It lowers training overhead. A focused menu gives users fewer choices to interpret. Training becomes more practical because instructions point to a short, relevant set of actions instead of a broad system menu.
It reduces navigation errors. Users are less likely to select a similar but incorrect transaction when the menu emphasizes the records they actually create.
Customization is not about adding every possible shortcut. It is about making the right actions obvious.
Understand what the Create New menu controls
Before changing the menu, separate three different areas of NetSuite navigation:
The Create New menu, which provides quick access to record and transaction creation.
The navigation tabs and menus, which provide broader access to records, reports, lists, and setup areas.
Dashboard shortcuts, which place selected links directly on the user's home page.
These tools overlap, but they serve different purposes. The Create New menu should contain actions users initiate frequently. A dashboard shortcut is more suitable for a report, saved search, or record list that users review repeatedly. A navigation tab is better for broader exploration.
For example, "Create Vendor Bill" belongs in a Create New menu for an accounts payable role. "Open the Vendor Bills Due report" is generally better as a dashboard shortcut or report link. Confusing those purposes produces clutter rather than efficiency.
The available options also depend on the user's role, permissions, enabled features, and account configuration. A user should not see or receive a shortcut to a transaction they are not authorized to create. Menu design must follow permissions, not bypass them.
How to customize the NetSuite Create New menu
NetSuite account configurations and interface versions differ, so labels and placement may vary slightly. The overall process remains consistent: open the menu, enter its customization mode, select the relevant actions, arrange them logically, and test the result as the intended role.
1. Review the current menu from the target role
Sign in with the role you want to improve and open Create New. Review the menu as the user experiences it today.
Do not begin by asking which links look useful in theory. Start with actual work patterns. Review recent transactions, common requests to the finance or systems team, and the actions users perform several times each week.
Pay attention to:
Actions users access repeatedly.
Transactions users struggle to locate.
Options that are irrelevant to the role.
Similar labels that could cause confusion.
Actions that require a different approval or permission path.
Items that belong in a dashboard shortcut instead.
If several people use the same role, gather feedback from more than one person. One user's preferred shortcut is not necessarily the right standard for the whole group.
2. Open the menu customization controls
Open the Create New menu and look for the available Customize, Edit, or configuration control within the menu interface. In some accounts, the option appears at the bottom of the menu or through a settings icon. In other environments, customization is controlled through role, center, or administrator settings.
If the direct personalization option is not available, check the user's permissions and role configuration before assuming the feature is unavailable. Some customization is user-specific, while other changes require an administrator or a role administrator.
This distinction matters. A personal menu change improves one user's experience. A role-based change affects everyone assigned to that role. Decide which outcome you need before saving changes.
3. Add only the actions that support the role
Select the record types and transactions the user creates regularly. Keep the list focused. A menu that contains every available transaction recreates the original navigation problem.
A useful rule is to prioritize actions that meet at least one of these conditions:
The user creates the record frequently.
The action is time-sensitive.
The action is difficult to locate in the standard navigation.
The action is central to the user's daily process.
A shortcut removes several repeated clicks.
Do not add an item simply because it exists. If a user opens a report, searches a list, or reviews a dashboard more often than they create a record, use another navigation method.
4. Arrange items in a logical order
Order matters because users scan menus quickly. Place the highest-frequency actions first, then group related tasks in a sequence that reflects the business process.
For instance, a purchasing role might move from purchase requisition to purchase order, then item receipt and vendor bill. A sales role might use customer, opportunity, estimate, and sales order. An accounting role may work with journal entry, vendor bill, customer payment, and bank-related transactions.
Use familiar business language when the available labels permit it. Avoid creating an order based solely on alphabetical sorting if the process itself follows a different sequence.
If NetSuite allows an item to be removed or hidden from the customized menu, remove low-value options rather than leaving them in place "just in case." Users still have other methods to access authorized records when an occasional need arises.
5. Save and test the result
Save the customization, close the menu, and reopen it. Confirm that the ordering and selected actions appear as expected.
Then test the menu using the actual role and permissions. Do not rely on an administrator's view if the change is intended for another role. Verify that:
Each link opens the intended record or transaction.
The user has the necessary permissions.
The selected form is correct.
Required fields and defaults behave as expected.
The menu remains usable at the screen size your team relies on.
The changes apply to the intended user or role scope.
A menu change is complete only when it works in the real workflow, not when the configuration screen shows a saved status.
Choose the right menu for each NetSuite role
A single standard menu rarely serves every user equally well. NetSuite's role structure gives organizations a better option: align navigation with responsibilities.
| Role type | Useful Create New actions | Items better placed elsewhere |
|---|---|---|
| Accounts payable | Vendor bill, vendor credit, purchase order, bill payment | Aging reports, payment history, saved searches |
| Accounts receivable | Customer invoice, customer payment, credit memo, customer deposit | Receivables dashboards and collection reports |
| Sales | Customer, lead, opportunity, estimate, sales order | Pipeline reports and activity searches |
| Purchasing | Purchase requisition, purchase order, vendor, item receipt | Vendor analysis and spend reports |
| Inventory and operations | Item receipt, inventory adjustment, transfer order, work order | Stock dashboards and demand reports |
| Finance leadership | Journal entry, budget, forecast-related records, approval actions | Financial statements, KPIs, and trend analysis |
| System administrators | Custom record, workflow-related records, employee, role, setup actions | User-facing operational transactions |
This table is a starting point, not a fixed template. The right menu depends on transaction volume, approval responsibilities, and how your organization divides work.
A role that approves transactions does not necessarily need the same Create New menu as the person who enters them. In fact, separating entry and approval workflows often makes the interface clearer and supports stronger control.
Personal customization versus role customization
NetSuite navigation improvements usually fall into two categories.
Personal customization is appropriate when an individual user has a specialized workflow. A senior accountant, project manager, or administrator may need a small set of shortcuts that would not benefit everyone else assigned to the same role.
Role customization is appropriate when a group shares the same responsibilities. It creates a consistent starting point and reduces the need for each user to configure the system independently.
The decision should be based on the reason for the change. If the problem is that one person needs a specialized action, use personal preferences where available. If the problem affects a department, standardize the role instead.
Document the difference. Without documentation, a support request such as "the Create New menu is missing an option" becomes difficult to troubleshoot. Record whether the menu is controlled by the user, the role, or a broader center configuration.
This is also where governance matters. NetSuite administration involves user management, workflow improvements, dashboards, saved searches, system monitoring, and ongoing optimization. Our NetSuite managed services guidance illustrates the same principle in another area of the platform: small configuration decisions reduce clicks and create more consistent work.
What belongs in a shortcut instead?
Not every frequently used item belongs in Create New. Use the type of activity to determine the best location.
A creation activity belongs in the Create New menu. Examples include creating an invoice, customer, purchase order, or journal entry.
A review activity belongs in a dashboard portlet, saved search, report shortcut, or analytics workspace. Examples include checking unpaid invoices, reviewing open sales orders, or monitoring inventory exceptions.
A navigation activity belongs in a tab, center category, or list view. Examples include reviewing all vendors, browsing items, or exploring customer records.
A decision activity may belong in a dashboard or approval queue. Examples include reviewing pending approvals, comparing forecast values, or checking operational exceptions.
This distinction keeps the Create New menu concise. It also makes each NetSuite interface element more useful because it matches the user's intent.
If your team relies heavily on saved searches, consider pairing menu customization with search optimization. NetSuite provides tools that help users work more independently, including saved searches, SuiteAnalytics Workbooks, datasets, and configurable dashboards. We discuss broader reporting and user enablement considerations in our guide to moving from Microsoft Dynamics GP to Oracle NetSuite.
Common mistakes to avoid
Adding too many options
The most common mistake is treating customization as an opportunity to display everything. A long list increases scanning time and weakens the value of prioritization. Start with the actions users perform most frequently, then add items only when a clear need emerges.
Designing for the administrator instead of the user
Administrators understand the system structure, but operational users think in terms of tasks. "Create a transaction" is not a business task. "Record a supplier invoice" or "enter a customer payment" is much closer to how the user works.
Interview users briefly and observe their current process before changing the menu. Their language and sequence should guide the design.
Ignoring permissions
A shortcut does not grant access. If a user lacks the required permission, the link may fail, expose an unexpected error, or direct the user into an incomplete process. Check role permissions and transaction access before publishing a standard configuration.
Changing the menu without testing forms
Two users may create the same transaction type but require different forms, subsidiaries, locations, or classifications. Confirm that the shortcut opens the correct form and that defaults do not create downstream data quality problems.
Removing occasional but critical actions
A focused menu should not make urgent tasks inaccessible. Before removing an item, confirm that users know where to find it when needed. The goal is to reduce clutter, not to hide important capabilities.
Failing to review after system changes
New features, role changes, custom forms, and workflow updates can make an existing menu less effective. Review the menu after major NetSuite changes and during regular user access reviews.
A practical review process for ongoing improvement
Menu customization should be treated as a small part of continuous NetSuite optimization, not a one-time cosmetic adjustment.
Start with usage feedback. Ask users which actions they search for, which links they never use, and which tasks require the most navigation. Compare that feedback with role permissions and transaction volumes.
Next, review the menu for duplication. If the same action appears in several locations, decide which location should be the primary route. A shortcut is useful when it is predictable.
Then, verify the sequence. Business processes change. A role that once began with purchase orders may now begin with requisitions or vendor approvals. The menu should reflect the current process rather than the original implementation design.
Finally, communicate the change. Tell users what was updated and why. A short message prevents confusion and reinforces the intended workflow. When a menu is redesigned without explanation, users may assume an item disappeared because of a permission problem.
When direct customization is not enough
The Create New menu improves access to existing actions, but it does not solve every navigation or process issue. If users still struggle after the menu is simplified, the underlying problem may involve:
Unclear role permissions.
Inconsistent transaction forms.
Poorly designed approval workflows.
Missing dashboard shortcuts.
Duplicate or outdated saved searches.
Inadequate training.
Custom records that are difficult to locate.
Processes that should be automated rather than navigated manually.
At that point, review the complete user journey. A shortcut can reduce the number of clicks, but it cannot repair an unclear approval policy or a poorly structured record design.
NetSuite customization should support business processes, not compensate for processes that need redesign. Where appropriate, workflow automation, SuiteScript, custom forms, custom records, and integrations provide a stronger long-term solution. Our NetSuite 2026.2 overview also highlights how newer, more natural interactions are intended to reduce dependence on memorizing exact menu paths and terminology.
