Services · Streamline & Outsource

NetSuite custom tab and subtab configuration

Arrange each record so users can find what they need quickly. By grouping subtabs by task, naming them in your language and ordering them by use, your teams no longer have to search for everyday fields hidden several clicks away, whichever record they are working on.

Grouped by taskNamed in your language
The problem

Most subtabs were never planned, so fields end up in the wrong places

Fields were placed wherever NetSuite form customisation put them, with the credit detail on ‘Custom’, the operational flag under ‘System Information’ and the daily-use field sharing a tab with fields no longer in use. Reorganising subtabs is low-cost work with a large benefit. Fields are grouped by the task that uses them, tabs are named for the people who use them and everything is ordered by frequency, so users can find their way around the record easily.

What we run

How we configure each NetSuite custom tab and subtab

Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.

  • Field-location auditWe map where each field currently sits against who actually uses it, so the redesign starts from the real layout.
  • Grouping by taskEach NetSuite custom tab is organised as a task area, such as credit, logistics or compliance, so related fields sit together.
  • Names your teams recogniseTab titles use the words your teams use, so a vague label like ‘Custom Fields’ is replaced by a name that says what is inside.
  • Frequency orderingDaily-use tabs come first and archive tabs come last, so the tab order matches how the work is done.
  • Tabs scoped by roleTabs are shown only to the roles that use them, applying the same role scoping as the entry-form design at tab level.
  • Consistency across recordsThe same logic is applied across record types, so the customer and vendor records feel like one system.

Records cluttered with unused tabs?

We arrange tabs and subtabs so each role sees what matters. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.

The payoff

What handing it over buys you

Fields get found first time

Task-grouped tabs make it clear where each field lives, even for fields used only occasionally.

Training gets easier

Self-describing names make the record readable for a new starter.

Users no longer click past unused tabs

Frequency ordering puts the used tabs up front.

Records follow one layout

A consistent approach gives every record the same layout logic.

How handover works

From an unplanned layout to an organised record

  1. Audit field locations – each field’s location is mapped against who uses it, per record type.

  2. Design the tabs – task groups, names and ordering are designed together.

  3. Scope per role – tabs are surfaced only where they are used.

  4. Apply consistently – the same approach is rolled out across record types through the change process.

Good to know

What to know before you hand it over

  • !Moving fields does not change how anything works. NetSuite subtab configuration only affects layout – sourcing, scripts and permissions all carry on unchanged, so reorganising is very low-risk.
  • !Names come from your vocabulary, gathered rather than invented. The naming pass uses the words your teams already use, so the labels match the way your teams talk.
  • !New fields need a home from day one. Without an agreed standard, new fields drift back into the wrong places, so our field-creation standards give each new field a proper home from the start.
Straight answers

Custom Subtab Configuration FAQs

How many subtabs should a record have?
Few enough that users can scan them easily. Task grouping usually lands at a handful of working tabs plus an archive, and the audit’s usage data decides the exact number. As a guide, a customer record often works well with tabs for sales, credit and finance, logistics and an archive for historic fields – but the right grouping follows your tasks, not a fixed pattern.
Can subtabs differ by role?
Yes, through form-level scoping. Each role’s entry form carries its own tab set, so the credit tab appears on finance’s form and not on the warehouse’s. Permissions still control what people can see – scoping simply keeps each role’s record uncluttered.
Does this touch the field dictionary?
The two work as a pair. The dictionary records each field’s purpose, the subtab layout sets where it sits, and placement updates are written back to the register. That keeps the documentation and the screens telling the same story, so an administrator can always check where a field lives and why.

Last reviewed: 21 October 2026 · Written by the Suite Generation team

Ready to hand this one over?

Tell us what you need and the problems you’re seeing, and we’ll scope the work.

Scoping Call — Sitewide

We reply within 24 hours.

or email hello@suitegeneration.net

Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.

Independent – no licence resellingSenior-led – solution-architect levelTrusted to fix failed implementations
Talk to a solution architect