1. Home
  2. ERP
  3. NetSuite
  4. Setup
  5. NetSuite Custom Fields

NetSuite Custom Fields

StarShip can import NetSuite custom fields that apply to Item Fulfillment, and can write selected custom body fields back after you ship.

Which custom fields appear in Field Mapping

Customize Interface for Item Fulfillment lists custom fields from the Item Fulfillment REST catalog:

  • Transaction Body Fields on Item Fulfillment (custbody_*)
  • Transaction Line Fields on Item Fulfillment (custcol_*)
  • PackShip related-record fields (custrecord_packship_*) when they are on the Item Fulfillment catalog

The default list does not include Customer fields (custentity_*), Item fields (custitem_*), or other Custom Record fields that are not on the Item Fulfillment record. Saved maps are kept when the catalog is refreshed.

Note

StarShip cannot read NetSuite Display Type (Hidden) or Inactive from REST Web Services. Some Hidden or Inactive Item Fulfillment body and line custom fields may still appear in Field Mapping. Do not map fields you do not use.

Import

  1. Make sure the custom field applies to Item Fulfillment and is visible to the StarShip M2M role in NetSuite.
  2. In StarShip, open Customize Interface for Item Fulfillment.
  3. Map the custom field to a StarShip shipment, line, package, or user-definable field. Names look like Custom: ACTUAL SHIPPING COST (custbody_shipengine_shipping_cost) or [Line Item] Custom: Package Length (custcol_alf_package_length).
  4. Click Save All Maps.

You can map a custom field across levels: a line custom field to a package or header destination, or a header custom field to a line or package destination. StarShip uses the first line value when a line field is mapped to a package. Same-level maps (header to header, line to line, package to package) still work.

If a mapped header custom field is not in the REST record, StarShip reads it with SuiteQL.

Write-back

Only maps on the Custom Write-Back Setup tab of the interface you used to ship are sent. Imported custom fields from another interface are not written back.

  1. In Customize Interface, open the Custom Write-Back Setup tab for Item Fulfillment.
  2. Map StarShip values to NetSuite custom body fields (custbody_*, custbody1, or doubled ids such as custbodycustbody_shipengine_shipmethod).
  3. Click Save All Maps.
  4. Ship/Process the shipment.

Example used for applied freight:

NetSuite Item Fulfillment field Value maps from
Custom: ACTUAL SHIPPING COST (custbody_shipengine_shipping_cost) [Shipment Charges Applied Total]

Custom Write-Back Setup: ACTUAL SHIPPING COST mapped from Shipment Charges Applied Total

After process, NetSuite shows the applied amount on the Shipping tab:

NetSuite Item Fulfillment Shipping tab: ACTUAL SHIPPING COST after write-back

Important

Line custom columns (custcol_*) and package custom fields can appear for import mapping. They are not written back. If a mapped custom field fails, status and tracking still write; StarShip reports the field that failed.