NetSuiteFree referencePDF, Excel, Word exportNetSuiteDiscrete Manufacturing

NetSuite Manufacturing and Item Record Types Reference

Manufacturing in NetSuite is spread across item records, engineering records and transactions. This reference lists the record ids you need when scripting, calling REST or writing documentation, grouped so that you can see how an assembly, its BOM and its routing relate.

Download:

Record id	Record	Group	What it is used for
inventoryitem	Inventory Item	Item	Purchased stock item tracked in quantity and value
assemblyitem	Assembly/Bill of Materials Item	Item	Built item with a bill of materials
lotnumberedinventoryitem	Lot Numbered Inventory Item	Item	Stock item tracked by lot number
lotnumberedassemblyitem	Lot Numbered Assembly Item	Item	Built item tracked by lot number
serializedinventoryitem	Serialized Inventory Item	Item	Stock item tracked by serial number
serializedassemblyitem	Serialized Assembly Item	Item	Built item tracked by serial number
kititem	Kit/Package Item	Item	Group of items sold together, not built
noninventoryitem	Non-Inventory Item	Item	Item not tracked in inventory quantity
serviceitem	Service Item	Item	Labor or service line
otherchargeitem	Other Charge Item	Item	Freight, fees and similar charges
discountitem	Discount Item	Item	Discount applied on a transaction
descriptionitem	Description Item	Item	Text only line on a transaction
bom	Bill of Materials	Engineering	Container for the component list of an assembly
bomrevision	BOM Revision	Engineering	Dated version of a BOM with effective dates
manufacturingrouting	Manufacturing Routing	Engineering	Sequence of operations for an assembly
manufacturingcosttemplate	Manufacturing Cost Template	Engineering	Labor and machine cost rates used for routing costing
manufacturingoperationtask	Manufacturing Operation Task	Shop floor	Operation line generated from a routing on a work order
workorder	Work Order	Transaction	Request to build a quantity of an assembly
workorderissue	Work Order Issue	Transaction	Issues components to a work order
workordercompletion	Work Order Completion	Transaction	Records completed quantity and operation progress
workorderclose	Work Order Close	Transaction	Closes a work order and releases open commitments
assemblybuild	Assembly Build	Transaction	Consumes components and produces the assembly item
assemblyunbuild	Assembly Unbuild	Transaction	Reverses a build back into components
inventoryadjustment	Inventory Adjustment	Transaction	Changes quantity or value outside a normal receipt
inventorytransfer	Inventory Transfer	Transaction	Moves stock between locations
location	Location	Setup	Warehouse, plant or other stock location

Record ids are the script ids used by record.load, REST record URLs and N/record. The matching record.Type enum in SuiteScript uses the same name in upper case with underscores. Availability depends on enabled features such as Work Orders, Assemblies and Advanced BOM.

Mapping NetSuite manufacturing data?

Request a short review of your item, BOM and routing structure before you integrate.

Optional. The tool and every export work without this. No spam.

How to use the table

Search by name or purpose and copy the record id. Use it as the type in record.load, as the path segment in a REST request, or as the record type in a CSV import mapping discussion. The Group column separates item records from engineering data, shop floor tasks and transactions, which makes it easier to scope an integration.

How the records connect

An assembly item points to a BOM, and the BOM has one or more revisions with effective dates. A routing is linked to the assembly and the BOM revision, and a manufacturing cost template supplies labor and machine rates. When a work order is created, the system copies the revision components and generates operation tasks from the routing. Transactions then record issue, completion and close.

Item defines the thing being built
BOM and revision define what goes in
Routing defines how and in what order
Work order carries the plan, builds and completions carry the result

Feature dependencies

Several records appear only when features are enabled. Work orders and assembly builds need the Assemblies and Work Orders features, routings and operation tasks need the manufacturing routing and work center setup, and lot or serial variants require the matching inventory tracking features. If a record id returns not found, check the feature before debugging the script.

Common mistakes

Developers often load an assembly with the inventoryitem type, which fails because the record type is specific. Another mistake is treating a kit item as a built item. A kit is not built and has no work order, while an assembly is built and costed from components.

Frequently Asked Questions

What is the difference between an assembly item and a kit item?

An assembly item is manufactured through a work order or build and has its own inventory and cost. A kit item is a sales grouping of other items that is not built. Choose assembly when you need production and costing, and kit when you only bundle for sale.

Why does record.load fail for my assembly?

The record type must match the item subtype. A lot numbered assembly uses lotnumberedassemblyitem and a plain assembly uses assemblyitem. Loading with the wrong id returns an error even though the internal id is valid.

Do I need BOM revisions?

BOM revisions are how NetSuite tracks effective dated changes to components. If your engineering changes are frequent or you need history for audits, use revisions. Very simple products can run with a single revision.

Is this the full NetSuite record list?

No. It focuses on manufacturing and item records. Use the Records Catalog inside NetSuite for the full set, including fields and sublists for each record in your account.

If you are mapping NetSuite manufacturing data into a planning tool or an AI assistant, we can help you validate the record relationships against your own account.

Talk to an Expert Explore More Free Tools

Related Tools

NetSuite

More NetSuite tools

See all

Back to All Tools