Overview
The Pacejet Shipping for NetSuite 26.1.5 release focuses on configuration resilience and processing reliability for the NetSuite bundle. Custom field configurations are now preserved when import settings are edited, and administrators can manually enter NetSuite field IDs that are not listed in the field chooser. This release also improves the reliability of scheduled shipment processing, resolves Item Fulfillment update failures, and adds automatic handling of shipments when an Item Fulfillment is deleted in NetSuite. In addition, this release includes verified support for Built for NetSuite (BFN) 2026.2 and the new NetSuite Next versions.
Item Fulfillments Deleted In NetSuite, Removed in Pacejet
🟨 New Feature: When an Item Fulfillment is deleted in NetSuite, the related Pacejet shipment can now be handled automatically based on a new integration setting with three options: Warn, Stop, or Void. Warn alerts the user if the shipment has already shipped but allows deletion to proceed; Stop blocks deletion of a shipped record and directs the user to void it in Pacejet first; Void automatically deletes the related shipment (shipped or unshipped), voiding the label if needed. This eliminates the duplicate, orphaned shipments that previously remained in Pacejet after a fulfillment was deleted.
Built for NetSuite 2026.2 and NetSuite Next
🟪 Enhancement: This release includes verified support for Built for NetSuite (BFN) 2026.2 and the new NetSuite Next versions.
Custom Fields Configuration
🟪 Enhancement: Editing the Custom Fields import settings no longer removes fields that the field chooser cannot display. Previously, saving import settings could silently delete configured fields (such as custbody_erg_entityid or kitmemberof) that were not visible in the chooser, changing shipment processing behavior. Configured fields are now preserved unless an administrator explicitly removes them.
🟪 Enhancement: Administrators can now manually enter valid NetSuite field IDs that are not available through the field chooser. This lets customers configure custom body, line, and system fields immediately, without waiting for a field chooser update or risking loss of existing mappings.
Bug Fixes
🟩 Resolved Issue: Improved the reliability of scheduled shipment processing. An unexpected error on a single record could previously stop the remaining scheduled queue from running. Scheduled processing now continues past an individual record error. For best throughput during peak periods, we recommend configuring at least five SuiteCloud processors.
🟩 Resolved Issue: Resolved Item Fulfillment update failures that occurred when the shipping cost value exceeded NetSuite's 20-character limit. The bundle now validates the value stored in User Field 13 before updating the NetSuite Shipping Cost field, and defaults to a valid value when the stored value is missing or non-numeric. User Field 13 remains reserved for standard Pacejet bundle use.
🟩 Resolved Issue: Resolved intermittent Item Fulfillment update failures that occurred when other scripts or workflows changed the record at the same time Pacejet was assigning the shipment URL during import. The bundle now retries the update several times before reporting an error.