NetSuite 2026.2: Sales, Pricing & Order Updates

This is the fifth installment of our NetSuite 2026.2 Release Notes Series, broken down by role so you only read what applies to your work.

For sales, pricing, and subscription teams, 2026.2 is about explaining and automating pricing — where a number came from, how it gets applied at scale, and what happens when the payment does not match the invoice.

A note on sourcing. This is based on Oracle's Release Preview release notes for 2026.2, which every page marks as subject to change. Details can shift before general availability, and we will update this post if Oracle revises them.

---

The CPQ AI Assistant

NetSuite CPQ Configurator 1.8.0 introduces a generative AI assistant that guides sales reps and buyers through complex product configurations using natural language.

When a user selects a configurable item on a transaction, a Configure with CPQ Assistant button appears in the bottom-right corner. It opens a guided chat that collects configuration details and offers real-time recommendations, clarifying options as it goes. The stated goal is letting people of any experience level finish a complex configuration — which, if your configurator has a hundred interdependent questions, is the difference between a rep quoting today and a rep escalating to product.

The part that decides whether it works: someone has to prepare it. Users with the Administrator or CPQ Product Builder role set up product, question, and answer records on the CPQ AI Assistant subtab on each related record. From there you review readiness, write and improve AI descriptions, check records meet quality standards, and control where and when end users see the assistant at all.

So this is not a switch. It is a content project on your configurator's metadata, and the quality of those descriptions is the quality of the guidance your reps get.

Availability caveat: limited to accounts in supported locations and users whose language preference is set to a supported language.

---

Migrating the CPQ Configurator bundle — read before you start

If you are moving from the NetSuite CPQ Configurator bundle to the corresponding SuiteApp, 2026.2 ships a migration bundle: NSCPQ Bundle Migration (version 1.0.0, ID 596110). It preserves configuration records and transaction field data created by the old bundle, cutting how much you have to export and import.

The sequence matters:

1. Update the NetSuite CPQ Configurator bundle to the latest version.
2. Install the migration bundle.
3. Export bundle data.

Without the migration bundle installed, the CPQ Configurator bundle cannot be uninstalled during migration at all.

And the warning worth putting in bold in your runbook: keep the migration bundle installed after migration if you want to continue editing existing configured items added to transactions by the old bundle. Uninstalling it permanently deletes configuration and transaction data from the CPQ Configurator bundle.

---

Pricing you can actually explain

Advanced Pricing Context on sales order lines. Sales order lines now show how NetSuite arrived at each item's final price, and whether base pricing, rule-based pricing, or customer-specific pricing applied. Click the tag icon on the item line to open the Pricing Details summary.

This is a small feature with disproportionate value. "Why is this customer seeing this price?" is a question that normally costs someone twenty minutes in the price rule configuration. Now it is on the line.

Item collections and customer groups in price rules. Price rules can use item collections and customer groups to apply pricing. When those are dynamic — driven by a saved search — NetSuite refreshes membership on a schedule, precomputing and storing a snapshot of which items or customers belong.

Price evaluation then reads the snapshot instead of re-running the saved search every time. That is a real performance change for anyone whose pricing rules currently depend on live saved-search evaluation, and it is the reason to revisit rules you simplified previously because they were too slow.

Pricing records in the CSV Import Assistant. Price rules and price rule entries could previously only be created one at a time — a genuine obstacle for migrations and high-volume pricing changes. Now you can import many in a single file: Setup > Import/Export > Import CSV Records, choose the Accounting import type, then Price Rule or Price Rule Entry. All standard and custom fields available in the UI, REST, or SuiteScript can be mapped, using your existing permissions.

Price Level view in Advanced Pricing. One place to see how each price level relates to items, customers, and pricing configuration — useful before you change pricing for a customer group and want to know what else you are about to touch.

Sales by Price Rule pivot table joins the Sales Pricing Overview Workbook, showing total invoiced value by active price rule over a date range. It answers which rules actually drive revenue, which tiers are trending, and which rules exist but never fire.

---

Automated payment adjustments

Previously, when a payment did not exactly match the invoice — a bank fee, a convenience fee, a small underpayment — someone entered the adjusting entry by hand.

The Payment Adjustments feature automates those postings. You can adjust the payment amount directly from the customer payment or customer deposit transaction. For any team processing volume where a two-dollar variance is not worth a manual journal but also cannot be ignored, this is the release's quiet time-saver.

---

Externally rated usage billing for SuiteBilling

For usage subscription line service types, there is a new Use Usage Amount Only option. With it, usage records can carry charge amounts calculated externally — by a third-party mediation or rating platform — instead of NetSuite computing the usage charge itself.

You bring in final usage quantities and billable amounts for downstream billing, balance consumption, and contract-driven invoicing. It works with standard usage billing, Commit Plus Overage, and Prepaid subscription models.

Importantly, those usage-driven amounts also flow into Advanced Revenue Management, so invoicing, revenue allocation, and revenue recognition stay aligned rather than diverging the moment rating happens outside NetSuite. If you have been reconciling an external rating engine against NetSuite by hand, this is the feature to evaluate first.

---

Subscription Metrics: broader coverage

Three additions, all requiring SaaS Metric Reporting enabled and configured:

• Memorized transactions can now be source transactions. Caveat worth knowing: historical changes made to memorized transaction templates before the feature starts processing them are not tracked. Tracking begins from that point forward, so your history will have a start line.
• Sales order renewals created through the Sales Order Renewal SuiteApp can be source transactions, which requires that SuiteApp installed.
• Prepay subscription lines now create analytical impact records, giving a more accurate recurring revenue picture for upfront and prepaid billing models.

Together these widen what counts toward recurring revenue metrics beyond straight subscription records — which matters if a meaningful share of your commitments live as renewals or prepayments.

---

Smaller changes

• Payment Token Type field. A customer-extensible classification for both general tokens and payment card tokens, so you can distinguish Google Pay from Apple Pay from anything else. Useful the first time someone asks for a breakdown of payment methods by wallet.
• Attachments from CPQ configurations to transactions. In CPQ Configurator 2.0.1, an Attach to transaction checkbox on the attachment question record pushes files submitted during configuration onto the transaction, under Communication > Files. Each file attaches once, and deleting an attachment while editing the configuration removes it from the transaction too.
• QTable popup list filtering by row, without scripts. On the answer record's Popup Tables and Lists subtab, add a filter to Product Table Filter and append the _@ suffix to the popup list's answer code. A condition like {ACCESSORIES/QUANTITY_@} == 3 evaluates per row, with the suffix replaced by the row number at processing time.
• Order fulfillment from sales order lists — start fulfillment straight from a filtered or saved sales order list instead of opening each order.
• Electronic Invoicing SuiteApp 10.4.0 adds Location, Class, and Department on inbound e-document conversion, improved vendor credit conversion using the purchase order number from the inbound XML, and a PEPPOL-based transaction response template with extension plug-ins for customizing generated XML.

---

What we would test first

1. Dynamic item collections in price rules, to confirm the snapshot behaviour gives you the performance headroom to build the rules you actually want.
2. The CPQ migration path, if you are still on the bundle — specifically the "keep the migration bundle installed" requirement, because the failure mode is permanent data loss.
3. Externally rated usage flowing through to ARM, if you rate outside NetSuite.

Your account's upgrade date is in the New Release portlet on your dashboard. The rest of the series — finance, developers, system administrators, and operations — is indexed on our complete NetSuite 2026.2 breakdown, which also lists every change by feature area. For the wider 2026 cycle, see the NetSuite 2026 release notes hub.

Frequently asked questions

What clients ask before signing

What is the NetSuite CPQ AI Assistant?expand_more

How do dynamic item collections work in NetSuite price rules?expand_more

What is externally rated usage billing in SuiteBilling?expand_more

What should I know before migrating the NetSuite CPQ Configurator bundle?expand_more