2026.1 Order Management: FedEx REST API, New CSV Import Records, SuiteBilling C+O, and Sales Order Renewals

Order Management in 2026.1 is mostly plumbing work: the FedEx integration is being forced onto FedEx's new REST Ship API, three more transaction record types become CSV-importable, SuiteBilling gets a real shared-commitment model, and a new first-party Sales Order Renewals SuiteApp lands (which is mutually exclusive with Contract Renewals). None of the SuiteBilling/SaaS metrics items mention specific SuiteScript modules or REST endpoints in the source — treat the script-level surface as unchanged unless you verify otherwise in the Records Browser.

FedEx Integration: REST API Cutover

This is the item with the highest operational risk. FedEx is retiring its legacy Web Services Ship API, and NetSuite's bundled integration is being moved to the REST replacement. Three concrete impacts:

• MFA re-registration is mandatory. Every existing FedEx account configured under Setup > Accounting > Shipping > Add FedEx Account must be re-registered through the new Authorize your FedEx Account section. Until that PIN flow (SMS, phone, email, invoice details, or FedEx support) completes, label generation can fail silently from the user's perspective.
• New Hazmat fields on two records. Item Fulfillment gains Regulation and Option Type on the Hazmat tab. The Item record gains Technical Name on the Hazmat/Dangerous Goods tab. If you have SuiteScript, workflows, CSV imports, or SuiteTalk integrations that build item fulfillments for hazmat shipments, these fields are now part of the data FedEx expects — missing values may cause label/document generation to fail at fulfillment time.
• New ZPLII tire label formats. Two new entries appear in FedEx Label Types on the FedEx Registration page: ZPLII (4 x 8-1/2) and ZPLII (4 x 10-1/2). When either is selected, the Doctab Location control is locked to the FedEx default (sidewall bar code below main label).

What to do (FedEx)

1. Inventory every active FedEx account in every subsidiary and schedule MFA re-registration before users notice failed labels. Coordinate with whoever owns the FedEx account credentials — the PIN goes to them, not necessarily to the NetSuite admin.
2. Audit any custom code or SuiteFlow that creates/updates Item Fulfillments for hazmat items. Add the new regulation, optiontype (Item Fulfillment) and technicalname (Item) fields to your field maps. Verify the internal IDs in the Records Browser before hardcoding — they aren't published in the release note.
3. Check any saved searches, SuiteAnalytics workbooks, or CSV import templates referencing the Hazmat tab — new columns mean stale templates are likely incomplete rather than broken.
4. Confirm your thermal printer profiles before enabling the new ZPLII tire formats; the locked Doctab Location is by design and not a misconfiguration.

CSV Import Assistant: Three New Transaction Types

Cash Refund, Customer Deposit, and Customer Refund are now first-class import targets under Setup > Import/Export > Import CSV Records, Transactions import type. Per Oracle, the Cash Refund import surface covers "all standard and custom fields available in the UI, REST, or SuiteScript" — i.e., parity with the scriptable record. The release note does not promise the same for Customer Deposit/Customer Refund; verify field coverage in the Import Assistant before retiring any SuiteScript-based bulk loaders.

What to do (CSV)

1. If you have RESTlets or scheduled scripts whose only job is bulk-creating these three record types, evaluate whether CSV Import + the existing Import CSV File permission is now sufficient. Fewer governance units, fewer scripts to maintain.
2. Re-test data migration runbooks — historical "this record type isn't supported by CSV" workarounds can now be removed.
3. Permissions are inherited from the importing user; no new permission was introduced for these record types beyond the existing Import CSV File.

SuiteBilling: Commit Plus Overage and Cross-Subscription Drawdown

Two related changes to consumption billing:

• Commit Plus Overage (C+O). A single C+O line can now share its commitment pool across multiple usage services, with overage priced per usage line rather than per C+O. Practical implication: the per-usage overage price plan and frequency fields are ignored when usage is booked against a specific service — overage pricing comes from each service's own price plan. Breakage and overage revenue still post to the C+O line, so revenue recognition mappings shouldn't need rework, but reporting that joins overage revenue back to a single service line will behave differently.
• Prepay drawdown across subscriptions. A prepay service on subscription A can be burned down by usage on subscription B, scoped by the customer / currency / subsidiary tuple. If you have integrations that reconcile prepaid balances per-subscription, that assumption is now wrong.

SaaS Metrics: Customer-Level Recurring Revenue + Acquisition Date

Recurring revenue impacts (new, upsell, downsell, churn) are now tracked at the customer grain rather than the contract grain, and a new acquisition month field is added to revenue records to support cohort analysis. The Customer record's Financial subtab gains an Acquisition Date field; if left blank it defaults to the date of the customer's first transaction or the earliest imported analytical impact.

The release note does not name the exact internal IDs of the new revenue-record field or the customer field. Before writing SuiteScript or SuiteAnalytics workbooks against them, confirm the IDs in the Records Browser for 2026.1.

What to do (SaaS metrics)

1. If you have ETL pipelines pushing NetSuite data into a warehouse for MRR/ARR reporting, plan to add the new acquisition-month column on revenue records and the customer-grain attribution.
2. For customers migrated from another billing system, decide a policy for back-filling Acquisition Date rather than letting it default to whatever the earliest transaction happens to be — the default can produce misleading cohorts.

Sales Order Renewals SuiteApp 26.1.1

New first-party SuiteApp from the SuiteApp Marketplace. It adds a custom form with a Renew SO Automatically checkbox (for batch-scheduled renewal) and a Create Renewal button (for on-demand renewal), plus fields for renewal price, uplift percentage, and dates.

Hard constraints from Oracle:

• Requires the Sales Orders and Advanced Billing features, plus Client SuiteScript and Server SuiteScript.
• Mutually exclusive with the Contract Renewals SuiteApp — you must uninstall one to use the other. This is the single most important deployment decision here; do not install in a sandbox attached to a production account that uses Contract Renewals without a migration plan.
• Will not renew sales orders in Canceled status, nor sales orders associated with a subscription.
• Compatible with Multiple Currencies and Multi-Subsidiary Customer.

Items Mentioned but Not Detailed in the Source

The release-notes page also lists NetSuite Ship Central enhancements, Electronic Invoicing enhancements, NetSuite Pay enhancements, additional Subscription Metrics enhancements, and Brazil/Chile localization changes, but provides no body copy for them on this page. Pull the dedicated topic pages before relying on any of these in design work.