ShipHawk ERP Integration Guide

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

For receiving information from ShipHawk, the ERP must meet the following requirements:

1. ERP must receive ShipHawk shipment webhook and update accordingly

When a shipment has been booked in ShipHawk, the ERP must be able to receive a webhook request from ShipHawk with the shipment information, and must update the syncing entity (ERP) accordingly. 

  1. If enabled, the connector must also populate the correct tables for an EDI provider- such as SPS, TrueCommerce, etc 

  2. Serial/lot numbers must be synced and populated correctly. 

 Technical details

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

    • 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

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

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

2. LTL shipments updated PRO number received into ERP by ShipHawk webhook

For some LTL shipments, if the PRO number is updated by a carrier after the shipment has been booked, then it must be received into the ERP via ShipHawk’s tracking update webhook.

 Examples

  • No labels

Contact Technical Support
© ShipHawk 2023. All Rights Reserved.