Receiving Information from ShipHawk TMS Requirements

When a shipment is booked, the Shipment Create From Order Event occurs.

The following information MUST be updated in the shipment object:

• The carrier and service used for the shipment, including the carrier SCAC code

• The date the shipment was booked

• The cost of the shipment

• The tracking number of the shipment

• The packaging information. For each packaging container (box or pallet) shipped, the following are required if present:

  • The dimensions of the container being shipped

  • The weight of the container

  • The contents of the container, is represented by the package_items object.

    • Each package_item is linked to one of the order line items

  • The SSCC code for the container (if applicable)

    • If the container is a pallet, we must properly consume both the pallet AND carton level SSCC codes. In the ShipHawk- Netsuite connector, there is a custom table created by ShipHawk TMS to write back this information. In Acumatica, the default packages tab is used. In order to send this information to an EDI provider, this information is typically mapped from this table to the table used by the EDI provider. In some cases, additional mappings are not needed.

    • This is what ShipHawk's table looks like in Netsuite:

      Open

      

       

  • The individual tracking number for the container (if applicable)

• If the shipment is LTL, also include the BOL number