2026.1 Inventory SuiteApps: SCM Mobile Config/Customization Overhaul and Quality Management Auto-Sampling

NetSuite 2026.1 ships two distinct sets of changes under Inventory Management SuiteApps: a substantial expansion of the SCM Mobile configuration/customization surface, and automation of sampling summary calculations in the Quality Management SuiteApp. Both are SuiteApp-level changes — there is no new SuiteScript module or REST endpoint mentioned in the source. Engineers maintaining custom mobile processes or QM inspection workflows will need to revisit existing configurations.

SCM Mobile — what changed

iOS browser support

Mobile apps (standard and custom processes) are now accessible from iOS devices via Safari or Chrome. Previously this was Android-only in practice. Verify your devices against the SuiteApp's Hardware and Software Requirements page before rolling out — the source does not enumerate minimum iOS or Safari versions.

Expression-driven configuration

Several Mobile Customization fields now accept expressions that evaluate to true/false against mobile state data:

• Mandatory Condition on page elements — when Is Mandatory is checked but the condition evaluates false, the field is treated as optional. A static true/false works too.
• Label field on pages and page elements — labels can now be dynamic, reading from mobile state via the documented Mobile State Data and Keys API.
• Visibility Condition for X Icon on popup windows — controls whether the close icon is rendered at all.

Popup close icon action hook

A new On Close Action for X Icon field lets you bind a mobile action to the popup X tap. Default behavior (close window, possibly cancelling the in-progress task) is unchanged when left blank, so this is opt-in and non-breaking.

Dynamic Action Button visibility via refreshElement()

Action Button elements in page footers and popups can now be re-evaluated at runtime. The pattern: customize the button with Visibility Condition, Label, and Disable Field Condition, then add a refreshElement() call as a parameter on another element's mobile action (for example, a dropdown selection). The button re-renders against current state when that action fires. This removes a long-standing limitation where button visibility was effectively static after page load.

Table improvements

• Default sorting — pick one column per table (or one per side for Transfer Tables) plus order/method. Settings persist across user sort changes until cache is cleared.
• Right-side custom columns on Transfer Tables — the new Column Location field lifts the previous left-side-only restriction.

Image capture compression options

The Image Compression field on the Capture Image icon now exposes two strategies:

• By File Size (<10 MB) — only compresses images larger than 10 MB, down to ≤10 MB.
• By Image Size (600 px in width) — only compresses images wider than 600 px, preserving aspect ratio.

Behavior change to watch: if the field is left blank, the app compresses all images to 600 px wide regardless of original size. If you previously relied on full-resolution captures and never set this field, your images may already be downscaled. Audit existing Capture Image configurations.

Print to File without PrintNode

If Mobile Printing is enabled but PrintNode integration is not, you can now add Print buttons to NetSuite UI pages that select Print to File as the printer. The output is saved to the File Cabinet for manual download. Useful for environments that can't or won't deploy PrintNode.

Quality Management — what changed

Auto-Calculate Sampling Summary Fields

A new QM Parameters record (Quality > Preferences > Parameters) exposes two checkboxes:

• Auto-Calculate Sampling Summary Fields — system evaluates manually entered or CSV-imported sample data and populates totals in the sampling summary.
• Disable Sampling Summary Fields — locks the summary fields in the QM tablet UI. Only valid when auto-calculate is also checked.

An Evaluate Sample Data button appears next to Record on the tablet inspection screen and forces a recalculation regardless of the auto-calc setting — useful for on-demand recompute or when auto-calc is off.

Defect Counting Method (Statistical Sampling)

The QM Statistical Sampling Template record (Quality > Setup > Statistical Sampling Template) gains a Defect Counting Method dropdown that only takes effect when auto-calculation is enabled:

• All Categories (default) — every defect in every sample is counted.
• By Defect Severity — only the most severe defect per sample is counted, based on the configured severity order (e.g., Critical > Major > Minor).

Worked example from Oracle: two samples where Sample 1 has Critical+Major+Minor and Sample 2 has Critical+Major. Under All Categories: Critical=2, Major=2, Minor=1. Under By Defect Severity: Critical=2, Major=0, Minor=0. If you switch existing templates to By Defect Severity, historical-style reports will diverge — validate downstream saved searches and dashboards before flipping the setting.

What to do

1. Audit Capture Image elements in all mobile configurations. Set Image Compression explicitly if you depend on a particular image size; the blank-default now downscales everything to 600 px wide.
2. Inventory custom mobile pages using static Is Mandatory, label, or button visibility logic that you previously implemented via workarounds (extra pages, conditional navigation). Refactor toward expressions, Mandatory Condition, dynamic Label expressions, and refreshElement() on Action Buttons to simplify flows.
3. Test SCM Mobile flows on iOS Safari and Chrome if you plan to support iOS devices. Confirm device hardware against the SuiteApp's requirements page (not enumerated in the release note).
4. Decide on QM auto-calculation per environment. Enable Auto-Calculate Sampling Summary Fields on QM Parameters, then decide whether to also lock the fields with Disable Sampling Summary Fields. Train inspectors on the new Evaluate Sample Data button.
5. Review Statistical Sampling Templates and consciously choose a Defect Counting Method. If switching to By Defect Severity, re-validate saved searches, KPIs, and any SuiteAnalytics workbooks that aggregate defect counts — the totals will change.
6. If you currently rely on PrintNode, no action needed. If not, evaluate whether Print to File + File Cabinet retrieval is acceptable for your label/document workflow.
7. Update internal mobile customization documentation. The new fields (Mandatory Condition, On Close Action for X Icon, Visibility Condition for X Icon, Column Location, Image Compression) should be reflected in your team's standards before customizers start using them ad hoc.

What the source does not say

The Oracle page is SuiteApp release notes, not SuiteScript documentation. It does not mention any new N/record, N/query, or REST endpoint surface for these features. The refreshElement() API is part of the SCM Mobile customization framework (not a generic SuiteScript module). If you need to drive these settings programmatically rather than through the Mobile Configuration/Customization UI, verify the underlying record types and field IDs in your sandbox — the release note does not publish them.