CSV Import Adds SaaS Metric Tracking Fields for Items

NetSuite 2026.1 expands the Items CSV Import to support three new fields tied to the SaaS Metric Reporting feature. If your account does not have that feature enabled, nothing changes for you.

What changed

Three new columns are now mappable when importing items via CSV:

• SaaS Metric Tracking — Boolean. When true, the two date fields below become available on the record.
• SaaS Metric Start Date — Required when tracking is enabled.
• SaaS Metric End Date — Optional.

The release notes do not publish the internal field IDs (e.g. custitem_* vs. native saasmetric*) or specify whether the start/end date fields are conditionally required at the validation layer or only in the UI. Verify the exact internal IDs in Customization > Lists, Records, & Fields > Record Browser or by inspecting an item record in your 2026.1 sandbox before building your CSV mapping.

Supported item types

• Non-inventory Item for Sale
• Non-inventory Item for Resale
• Service Item for Sale
• Service Item for Resale
• Inventory Item
• Lot Numbered Inventory Item
• Serialized Inventory Item
• Kit/Package Item
• Matrix Items

Notably absent from the published list: Assembly/BOM items, Download items, Gift Certificates, and Other Charge items. If you need SaaS metric data on those, the CSV import path is not (yet) an option — you'll need SuiteScript or the UI.

What to do

1. Confirm whether the SaaS Metric Reporting feature is enabled at Setup > Company > Enable Features. The new CSV columns will not appear otherwise.
2. In a 2026.1 sandbox, open the Record Browser (or an Item record source) to capture the exact internal field IDs for the three new fields. Document them for your import templates.
3. Update existing CSV import templates and saved import maps for the affected item types to include the new columns where applicable.
4. If you load items via SuiteScript (N/record) or REST (/services/rest/record/v1/inventoryItem, etc.) rather than CSV, check whether the same fields are exposed there — this release note only documents the CSV path. Test a record.load + getField against an item to confirm before assuming parity.
5. For required-field handling: ensure your ETL/source system populates SaaS Metric Start Date on every row where SaaS Metric Tracking is true, or the import will reject those rows.
6. If you maintain Matrix Items, decide whether the metric fields belong on the parent matrix item, the child SKUs, or both — the release note doesn't specify. Test both paths.

Caveats

The Oracle release note is light on technical detail: no field IDs, no governance impact, no mention of REST/SOAP parity, and no statement on whether existing saved import maps will auto-surface the new columns or need to be re-created. Treat the items above as the verified surface area and confirm everything else against a 2026.1 sandbox before promoting changes to production.