The UX Problem in NetSuite
NetSuite ships with forms that show every possible field for every possible use case. A sales order form might have 80+ fields visible, most of which are irrelevant to the person entering the order. Tabs are cluttered. Required fields are not clearly distinguished from optional ones. The result is a system that feels overwhelming, leads to data entry errors, and drives users to build workarounds in spreadsheets.
Good NetSuite UX is not about making it look pretty. It is about removing friction from the tasks people do 50 times a day.
Clean Forms: The Foundation
Role-specific forms
Create separate transaction forms for each role. A warehouse worker entering a fulfillment does not need to see revenue recognition fields. An AP clerk entering a vendor bill does not need to see project tracking fields. Each role gets a form that shows only what they need.
Logical field ordering
Fields should follow the order in which users think about the transaction. For a sales order: customer first, then items, then shipping, then payment terms. Not the default NetSuite layout which scatters related fields across multiple tabs.
Hide what is not needed
If a field is only relevant 5% of the time, hide it by default and show it conditionally. Use field display logic (client scripts or form configuration) to show fields only when they are relevant to the current transaction.
Inline help text
Every custom field should have help text that explains what it is for and how to fill it in. This eliminates the need for separate training documents and reduces errors from guessing.
Workflows and Scripts: When to Add Steps
The instinct is to add validation scripts and workflow steps to prevent every possible error. This backfires. Every popup, every required field, every blocking validation adds friction. The rule should be:
Add a blocking validation only if the error is unrecoverable (wrong subsidiary, wrong period, duplicate record)
Use warnings (non-blocking) for issues that are recoverable (missing optional field, unusual amount)
Never use a popup to communicate information that could be shown inline on the form
If a workflow requires more than 3 approval steps, question whether the process itself needs simplification
Popups: The Most Abused Feature
Alert popups in NetSuite are overused. Users develop "popup blindness" and click through them without reading. If you have more than 2-3 popups in a typical transaction flow, your users are ignoring them. Replace popups with:
Inline field validation messages (red text below the field)
Banner messages at the top of the form for important notices
Conditional field highlighting (change background color of fields that need attention)
Confirmation dialogs only for destructive or irreversible actions
Dashboards That Drive Action
A good dashboard is not a wall of numbers. It is a decision-making tool. Each portlet should answer a specific question and drive a specific action:
"What needs my attention today?" (items pending approval, overdue tasks, open issues)
"How are we tracking?" (KPIs with trend indicators, not just current values)
"What is at risk?" (aging items, stalled deals, exceptions)
Build role-specific dashboards. The CFO dashboard is different from the AP Manager dashboard. Each person should see their world, not the entire company's data.
Measuring UX Improvement
You can measure whether your UX changes are working:
Time to complete common transactions (before vs. after)
Error rate on key transaction types
Support ticket volume related to "how do I" questions
User satisfaction surveys (quarterly, 3 questions max)
How We Approach UX Improvement
UX work requires collaboration with the people who use the system daily. We sit with your team, observe their workflows, and identify where the system creates friction. The fixes are informed by real usage patterns, not assumptions about what "should" be easier.
Our full-stack expertise means we understand the downstream impact of every UX change. Removing a field from a form might break a workflow. Adding a confirmation popup might conflict with an existing script. We test holistically before deploying.
Through StrongSupport, UX improvements are ongoing. As your team grows, as processes change, as new modules are activated, the interface evolves with them. Your support team is always accessible to make adjustments, answer questions, and implement refinements.
NetSuite UX is not a one-time project. It is an ongoing process of observing how people use the system, identifying friction points, and making targeted improvements. Start with the forms your team uses most frequently and work outward from there.
Or email us directly at hello@sixstrong.io
