2026.1 Item Record Management: Advanced Pricing, Standard Cost Transfers, and Breaking Subrecord Script ID Changes

The 2026.1 Item Record Management section bundles four changes. One of them — the item subrecord script ID rename — is a breaking change for any integration or saved query that touches item subrecords. Read that section first if you maintain SuiteQL, REST, or ODBC code.

Item Subrecord Script ID Changes (Breaking)

Selected item subrecord script IDs are being shortened to fit a 40-character identifier limit. Oracle's stated reason is alignment with protocol constraints for cross-interface compatibility. After your account is upgraded to 2026.1, any query referencing the old IDs may fail or silently return no results until updated.

Affected channels:

• SuiteQL queries (REST /query/v1/suiteql and the SuiteQL workbook)
• REST web services integrations under /services/rest/record/v1/... that traverse item subrecords
• SuiteAnalytics Connect queries against the NetSuite2.com ODBC/JDBC data source

The release note does not enumerate the affected subrecord IDs in-page. Oracle points to SuiteAnswers ID 1025032 ("Item Subrecord Script ID Changes for SuiteQL and SuiteAnalytics Connect") for the full old-to-new mapping. You will need that document to do the migration — the release note alone is not actionable.

What to do

1. Pull the old-to-new mapping from SuiteAnswers ID 1025032 before your account is promoted to 2026.1.
2. Grep your SuiteScript, RESTlets, integration middleware, and saved SuiteQL workbooks for any of the old subrecord IDs. Pay special attention to FROM, JOIN, and column references in SuiteQL.
3. Audit external BI tools (Tableau, Power BI, custom ODBC clients) hitting NetSuite2.com for hard-coded subrecord identifiers.
4. Test in a Release Preview / sandbox account on 2026.1 — note that silent "no results" failures are possible, so validate row counts, not just exceptions.
5. Update the IDs in place. There is no compatibility shim mentioned in the release note.

Use Item Cost as Transfer Cost — Now Supports Standard Cost Items

The Use Item Cost as Transfer Cost preference can now be applied to transfer orders and intercompany transfer orders containing items that use the Standard costing method. Previously this preference did not cover standard cost items. With it enabled, NetSuite uses the item's standard cost at the source location as the transfer cost, and posts cost differences to Purchase Price Variance (PPV).

The release note does not specify which field on the transfer order body or which preference page exposes this setting for standard cost items, nor does it confirm how this surfaces in the SuiteScript record model. Verify in a sandbox whether existing scripts that set transfer-cost-related fields on transferorder records via N/record need any change, and whether new GL impact lines appear that custom GL plug-ins should account for.

What to do

• Confirm with Accounting whether enabling this preference is desired — it changes PPV posting behavior for standard cost transfers.
• Re-run any custom GL impact / variance reports against a sandbox transfer order with standard cost items after enabling the preference.
• Review SuiteScripts that compute or override transfer cost on transferorder records; the new automation may conflict with manual cost overrides.

Advanced Pricing: Price Rules

A new Price Rules feature is gated behind the Advanced Pricing feature flag (Setup > Company > Enable Features > Transactions > Sales > Advanced Pricing). Rules live at Lists > Accounting > Price Rules and let you auto-apply a price level to a sales transaction based on:

• Customer or customer group (static or dynamic)
• Item
• Start / end date range

Rules apply automatically to sales orders, cash sales, estimates, invoices, credit memos, and return authorizations. The lookup precedence per the release note is: matching price rule → price defined directly on the customer record → item base price.

Compatibility caveat (important). Oracle explicitly states the following areas are not compatible with Advanced Pricing and should not be used while the feature is enabled:

• Price Lists
• Customer Center and SuiteCommerce pricing
• The Pricing search type in saved searches

If you run SuiteCommerce or expose pricing via Customer Center, do not enable Advanced Pricing in production yet. The release note does not name the new record type's script ID or any new SuiteScript / REST endpoints for managing price rules — verify the record ID (likely something like pricerule) in a sandbox before scripting against it.

Advanced Pricing: Cost-Plus Pricing

The price level record gains a Pricing Method selector with two options:

• Markup/Discount — existing behavior, unchanged.
• Cost+ — new. Pick a cost basis and a markup/discount percentage.

Cost basis options:

• Average Cost — uses the existing averagecost field on the inventory item.
• Cost for Pricing — a new item record field for a manually maintained cost, intended for items without standard costing or with volatile costs.

The item record's old Discount % column on the price level sublist has been renamed to Pricing Method. This is a UI rename but it likely corresponds to a sublist field change on the item record. Any SuiteScript using record.getSublistValue against the price level sublist on items, or any CSV import mapping that targets the old discount column, should be reviewed.

What to do

1. If you have SuiteScripts or CSV imports that read/write the price level sublist on item records, inspect them for references to the old Discount % column and verify the new field ID in a sandbox.
2. If using Cost+ with the new Cost for Pricing field, identify the new item field's script ID via the Records Browser or field-level help and update item maintenance scripts and integrations accordingly.
3. Do not enable Advanced Pricing in any account that depends on SuiteCommerce, Customer Center pricing, Price Lists, or the Pricing saved-search type.

Summary of Engineering Impact

• Breaking: Item subrecord script ID renames affecting SuiteQL, REST, and SuiteAnalytics Connect. Mapping is in SuiteAnswers 1025032.
• Behavioral: Standard cost items now respect Use Item Cost as Transfer Cost, changing PPV postings on transfer orders.
• New feature, gated: Advanced Pricing (Price Rules + Cost+) — incompatible with SuiteCommerce, Customer Center, Price Lists, and Pricing saved searches.
• Schema: New Cost for Pricing field on item; price level sublist column renamed from Discount % to Pricing Method.