Skip to main content

NetSuite Product Categories To iPaaS.com Mapping Documentation

How NetSuite product categories are captured into iPaaS.com, with parent-category resolution to preserve the hierarchy.

NetSuite Product Categories To iPaaS.com Mapping Documentation

Summary

A NetSuite product category can be captured into iPaaS.com as a product category. The integration records the category name and resolves its parent category to maintain the category hierarchy. Product categories are a reference record the item-capture collections depend on — an item's category assignments resolve against the categories created here.

ID Format

Manual Sync ID Format

Enter the category exactly as its value is named in your NetSuite category list: its category number and name joined by a hyphen, for example 3.1-Shirts. The number places the category in the hierarchy: 3 is a top-level category, 3.1 is a child of 3, and 3.1.2 is a child of 3.1.

External ID Format

iPaaS.com records the category's number (for example 3.1) as the external-ID link, so later transfers update the existing category rather than creating a duplicate, and so child categories can resolve their parent by its number (3 for 3.1).

Deleted Record Support

There is no Product Categories delete collection in this set — category removal is not propagated by this collection.

Mapping Collection Status

  • Status: Enabled (a single Add/Update collection).

  • Trigger Events: none. NetSuite sends no category events; categories are captured automatically when an item that carries them is captured, and on demand from Manual Sync.

Duplicate or Conflicting Mappings

None. A single Add/Update collection captures product categories.

Supported Child Collections

None. Hierarchy is represented by each category's ParentId resolving to another captured category.

System Caveats

iPaaS.com Caveats

  • Product Category data type. This collection populates the iPaaS.com Product Category entity.

  • Parent categories are created automatically (best-effort). If a category's parent is not yet in iPaaS.com, the integration attempts to create it automatically as a prerequisite. Because that parent creation is best-effort — a failure does not block the child category — capturing categories parent-first, or re-running, is the reliable way to guarantee nested categories resolve their parent link.

  • Prerequisite for item category capture. The item-capture collections (Product, Assembly, Non-Inventory, Service) assign categories via ConvertNetSuiteProductCategoriesToiPaaS, which matches against the categories created here. That item-side capture also requires the CATEGORY LIST ID setting in the integration's Subscription Settings in iPaaS.com: the script ID of the NetSuite custom list that holds your categories. See the item-capture docs for details.

  • Category values must carry a category number. Each value in the category list must be named with its category number and name, joined by a hyphen (for example 3-Apparel, 3.1-Shirts, 3.1.2-Polo Shirts). The number must contain only digits and dots. A value without the number and hyphen stops the capture of an item that carries it.

Setup Requirements

  • Sync categories first (parent-first). Establish the category hierarchy in iPaaS.com before relying on item category assignments.

  • Configure the CATEGORY LIST ID setting (in the integration's Subscription Settings in iPaaS.com) with the script ID of your NetSuite category list, and name each list value with its category number and name (for example 3.1-Shirts).

Authentication

The integration authenticates to NetSuite using the connection configured for the integration; the webhook scripts that emit NetSuite events are documented in NetSuite Connections and Settings.

Integration Flow

  1. A NetSuite product category is captured — automatically when an item that carries it is captured, or on demand (the category number and name, for example 3.1-Shirts).

  2. The integration creates or updates the iPaaS.com product category with its name and resolves its parent category (when the parent is already in iPaaS.com) to maintain the hierarchy.

Mappings

Add/Update NetSuite Product Categories TO iPaaS.com

iPaaS.com data type: Product Category

Captures a NetSuite product category into an iPaaS.com product category.

Mapping Type

Source Field (NetSuite)

Destination Field (iPaaS.com)

Description

Field

Name

Name

Required. The category name.

Dynamic Formula

return await GetSpaceportIdAsync(ParentId, "Product Category", ...)

ParentId

Optional. The iPaaS.com id of the parent category (for nested categories); resolves only when the parent has already been captured.

Error Handling

  • Parent category not linked: a category whose NetSuite parent is not yet in iPaaS.com is created without its parent link. Resolution: capture the parent category, then re-sync the child.

Testing & Validation

Test Scenarios

  1. Capture a top-level category. Manually sync a NetSuite category with no parent and confirm an iPaaS.com category with the name.

  2. Capture a nested category. After its parent exists in iPaaS.com, sync a child category and confirm its ParentId resolves to the parent.

  3. Item assignment. Confirm an item's category assignments match the captured categories (with the CATEGORY LIST ID setting configured).

Validation Checklist

  • The category hierarchy is captured parent-first.

  • The CATEGORY LIST ID setting holds your category list's script ID, and every list value is named with its category number and name.

Additional Notes

  • These categories are what the item-capture docs' Categories mapping resolves against; see the Product / Assembly / Non-Inventory / Service capture docs.

  • Known limitations are collected in NetSuite Known Limitations.

Related Documents

Related Mapping Documentation

Did this answer your question?