# NetSuite Custom Record Design Spec Template

> Source: https://netray.co/tools/netsuite-custom-record-design-spec-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A design spec for a new NetSuite custom record type: purpose, fields, relationships, access and reporting, ready to approve before anyone builds it.

## Category

netsuite

## Erp

NetSuite

## Audience

- NetSuite administrator
- NetSuite consultant
- Business analyst

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Project or change name

**Key:** project

**Type:** text

**Default:** Tooling Calibration Tracker

#### Custom record name

**Key:** record_name

**Type:** text

**Default:** Tooling Calibration

#### Record script ID

**Key:** record_id

**Type:** text

**Default:** customrecord_tool_calibration

#### Author

**Key:** author

**Type:** text

**Default:** Maria Chen

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Business purpose

**Key:** purpose

**Type:** textarea

**Default:** Track calibration due dates and results for gauges and fixtures used on the shop floor so quality can show evidence at audit.

#### Fields

**Key:** fields_list

**Type:** textarea

**Default:** Name (free-form text, required)
Gauge item (list/record: Item)
Last calibration date (date)
Next due date (date)
Result (list: Pass, Fail, Adjusted)
Certificate (document)

#### Relationships to other records

**Key:** relationships

**Type:** textarea

**Default:** Parent: Item record for the gauge. Optional link to Location for where the gauge is stored.

#### Who can view and edit

**Key:** roles

**Type:** textarea

**Default:** Quality Manager: Full. Production Supervisor: View. All other roles: None.

#### Reporting needs

**Key:** reporting

**Type:** textarea

**Default:** Saved search of gauges due in the next 30 days, emailed weekly to the quality manager.

#### Integration or automation

**Key:** integration

**Type:** textarea

**Default:** None in phase 1. Phase 2 may add a scheduled script to email overdue gauges.

**Blocks:**

#### Custom Record Design Specification

**Body:** Project: {{project}}
Record: {{record_name}}
Script ID: {{record_id}}
Author: {{author}}
Date: {{date}}

#### Business purpose

**Body:** {{purpose}}

#### Fields

**Body:** {{fields_list}}

#### Relationships

**Body:** {{relationships}}

#### Access and permissions

**Body:** {{roles}}

#### Reporting

**Body:** {{reporting}}

#### Integration and automation

**Body:** {{integration}}

#### Build and test plan

**Table:**

**Columns:**

- Task
- Owner
- Sandbox date
- Production date

**Rows:**

**0:** Create record type and fields

**0:** Set permissions on roles

**0:** Build saved searches

**0:** User acceptance test

**0:** Deploy to production

#### Approvals

**Signatures:**

- Business owner
- NetSuite administrator
- Developer

**Notes:** A starting point for your own change process. Custom record script IDs must start with customrecord and cannot be changed easily after records exist, so agree the naming before building.

## Content

**Intro:** Custom records are the quickest way to track things NetSuite does not model out of the box, and the quickest way to create clutter. A one-page spec before you build forces the right questions.

**Sections:**

#### How to use the spec

**Body:** State the business purpose in one or two sentences, list each field with its type, and name the records it connects to. Then decide who can view and edit it and how it will be reported on. Share the exported document with the business owner before anyone opens the Customization menu. Approving a spec takes minutes and saves a rebuild later.

**Bullets:**

- Write the purpose before listing fields
- Give each field a type: text, list, date, check box, currency and so on
- Name the parent record, if any
- Decide reporting needs up front

#### Design choices that matter

**Body:** Choose between a custom record and a custom field on an existing record first. If the data belongs to one transaction or item, a field is usually enough. A custom record suits many-to-one data such as inspection results, calibration events or approvals. Use custom lists or records for fields with repeating values, and decide early whether child records should be a subtab on the parent. Keep script IDs consistent, because they appear in saved searches and scripts.

#### Permissions and data volume

**Body:** Access to custom records is granted per role at levels from None to Full, so list them in the spec rather than discovering the gap in testing. Think about volume too. A record created for every work order operation behaves differently in searches than one created per supplier. Note the expected rows per year so developers can plan for indexing and search filters.

#### Common mistakes

**Body:** Teams duplicate existing fields, forget to restrict access, or build a custom record for something the standard Item, Location or Subsidiary records already cover. Another trap is skipping the sandbox. Even a simple record should be built, tested and moved by a SuiteCloud project or customization deployment so you can repeat it.

**Cta:** If you plan customizations alongside AI over your NetSuite data, Netray can review the spec and how it would surface in an ERP assistant.

**Faq:**

#### When is a custom field better than a custom record?

**Answer:** When the data describes one existing record and has one value per record, a field is simpler. Use a custom record for repeating or independent data, such as multiple calibration events per gauge.

#### Can the script ID be changed later?

**Answer:** Script IDs are set when the record type is created and are hard to change once data and scripts reference them. Agree a prefix convention before building and keep it consistent across customizations.

#### Do I need a sandbox for a small record?

**Answer:** It is strongly recommended. Building in a sandbox lets you test roles, searches and any scripts, then deploy the same definition to production instead of recreating it by hand.

#### Should the spec list saved searches?

**Answer:** Yes. Listing the searches and who receives them shows how the data will actually be used and often reveals missing fields before they are built.

## Search terms

netsuite custom record design template, netsuite custom record spec, netsuite customization requirements template, netsuite functional specification template, netsuite custom record fields list, netsuite customization design document, netsuite custom record permissions, netsuite technical design document

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json