Sales Order Renewals SuiteApp: Automated and Manual SO Renewal via Custom Transaction Form

The Sales Order Renewals SuiteApp introduces a mechanism to renew sales orders either on a batch schedule or manually. This is a SuiteApp-delivered feature — not a core platform change — so it must be installed from the SuiteApp Marketplace before any of the described records, fields, or buttons are available in your account.

What changed

After installation, the SuiteApp deploys a custom transaction form named Sales Order Renewals that can be applied to sales orders (or other transaction forms). The form exposes the following custom fields on the SO record:

• Renew SO Automatically — checkbox; enables scheduled automatic renewal.
• Renewal Price — sets the price on the renewed order.
• Uplift Percentage — percentage increase applied to the renewal price.
• Renewal Of — back-reference linking the renewal to its source SO.
• Renewed Order — forward-reference to the generated renewal SO.
• Renewal in Days Before Expiry — lead-time trigger for automatic renewal.

Renewal processing runs in two modes:

1. Batch / Scheduled — a scheduled script (deployed by the SuiteApp) processes eligible SOs automatically based on the Renewal in Days Before Expiry value and the Renew SO Automatically flag.
2. Manual — a Create Renewal button is added to the SO form for on-demand renewal.

Compatibility constraints

• Supports the Multiple Currencies feature and the Multi-Subsidiary Customer feature.
• Sales orders with Canceled status cannot be renewed.
• Sales orders tied to subscriptions are excluded from renewal.
• Mutually exclusive with the Contract Renewals SuiteApp. If Contract Renewals is installed, you must uninstall it before installing Sales Order Renewals, and vice versa. This is a hard constraint — both SuiteApps likely write to overlapping custom fields or script deployments on the SO record.

What to do

1. Check for conflicts — If you currently use the Contract Renewals SuiteApp, evaluate whether Sales Order Renewals is a suitable replacement before uninstalling. The two cannot coexist.
2. Install the SuiteApp — Deploy from the SuiteApp Marketplace. Post-install, verify that the custom form and fields appear on the Sales Order record.
3. Assign the custom form — Either set Sales Order Renewals as the preferred form on relevant SO transactions or merge its fields into your existing custom forms.
4. Review scripting impacts — If you have User Event, Client, or Workflow scripts on the Sales Order record, test them against the new fields and the SuiteApp's scheduled script to avoid execution-order conflicts or governance issues. The SuiteApp deploys its own scheduled script for batch renewal; check Customization > Scripting > Script Deployments post-install to see what was added.
5. Validate with multi-currency / multi-sub — If you use either feature, confirm that renewed SOs inherit the correct currency and subsidiary from the source order.
6. Test edge cases — Verify behavior for canceled SOs and subscription-linked SOs to confirm they are properly excluded.

Caveat

The source documentation does not specify the SuiteApp's Bundle ID, the internal IDs of the custom fields, or the script IDs of the deployed scheduled script. Before integrating with existing automations or SuiteScript customizations, inspect the bundle contents under Customization > SuiteBundler > Search & Install Bundles (installed tab) to identify exact script and field IDs. The release version for this SuiteApp is also not stated in the source — confirm the applicable NetSuite release in the SuiteApp's bundle documentation or release notes.