Pacejet
  • ERPs
  • NetSuite
  • Displaying Custom Product Data on Paperwork and Labels

Displaying Custom Product Data on Paperwork and Labels


Overview

You can configure Pacejet to transmit custom product data from NetSuite and display it on paperwork or label forms without professional services work, added implementation cost, or extra lead time. This process is fully self-service for NetSuite and Pacejet administrators.

This example shows how to send the product Vendor Name from the NetSuite item master into Pacejet and display it on a packing list in Pacejet Self-Service Shipping Paperwork.

Use this same workflow for other product-level fields. The main differences are the source field you choose in NetSuite, the field name sent in the API payload, and where you place the field on the Pacejet paperwork or label template.


Before you Begin

  • Confirm you have administrator access in both NetSuite and Pacejet.

  • Identify the item field you want to expose in paperwork or labels.

  • Know which Pacejet paperwork or label form you want to update.



Identify the Item Field in NetSuite

Start in the NetSuite item master and locate the field you want to display on the document. In this example, the item record includes the Vendor Name/Code value, which appears as Apple Ipad 6 for item IPA6.


Configure Item Fields to Import in Pacejet Settings

  1. In NetSuite, go to NetSuite > Pacejet > Settings > Pacejet Settings.

  2. Edit the settings:

    1. Open the Import Settings tab, and in the Item Fields to Import area select Select Item Fields.
      This is where you define which NetSuite item fields Pacejet should receive for product-level custom data.


Select the Field to Send to Pacejet

  1. In the Select Item Fields for Pacejet Integration dialog, search for the item field you want to send.

  2. For this example, select Vendor Name/Code.

  3. Save the change.
    Once saved, NetSuite will include this field in the product data it sends to Pacejet for applicable transactions.


Review the Transmitted Field in the Pacejet API log

  1. Transmit a sample order to Pacejet

  2. Open Tools > API > Log in Pacejet.

  3. Find the PUT /shipments request and review the CustomFields section.
    For this example, Pacejet receives the field as vendorname. The API log confirms both the field name and the value format that Pacejet is receiving from NetSuite.


Use the field name exactly as shown in the API log when creating the custom data configuration in Pacejet. In this example, that field name is vendorname.


Create the Custom Data Field in Pacejet

In Pacejet, go to Tools > Custom Data > Custom Data Configuration and create a new field.

  • Set Source to Product

  • Set Name to the field name from the API log: vendorname

  • Optionally enter an Alternate Name such as Vendor Name

  • Set Type to Text for this example

This step tells Pacejet how to store and expose the incoming custom product data for use in forms and templates.


Place the Field on the Paperwork Template

  1. Open Setup > Paperwork > Paperwork Editor in Pacejet and load the form you want to update, such as a custom packing list.

  2. In the editor, navigate to the location where the value should appear on the document.

  3. On the Configured tab, expand the Custom Data Product section and insert the vendorname field into the template.

In this example, the field is added to the product description area, so the packing list displays the product description followed by the vendor's name.


Preview the Result on the Final Document

Run another sample transaction into Pacejet after the custom data setup is in place. Then preview the same packing list template to confirm the field appears as expected.

In this example, the packing list now shows the vendor's name next to each product line, including Apple Ipad 6 for IPA6.


Summary

To display custom product data on Pacejet paperwork or labels, first enable the NetSuite item field for Pacejet import, then confirm the transmitted field name in the Pacejet API log, create the matching custom data definition in Pacejet, and finally place that field on the paperwork or label template.

Because this workflow is self-service, administrators can extend paperwork and label output as business needs change without waiting for a product update or engaging implementation resources.

Related Considerations

  • Use the same pattern for other product fields, shipment fields, or user fields when supported by the relevant import and configuration options.

  • If a value does not appear on the document, first verify the field name in the API log, then confirm the custom data configuration source and type, and finally confirm the template references the correct configured field.

  • For labels, the overall process is the same: transmit the data, define it in Custom Data Configuration, and place it on the label form in the appropriate editor.

Back to top