How ShipHawk Works with EDI Providers

This article explains how ShipHawk works with EDI providers to update pertinent item fulfillment data used by EDI providers. Included are detailed instructions on how to configure shipment field mappings that are used by common EDI providers. 

How ShipHawk Works with EDI

ShipHawk does not directly integrate with electronic data interchange (EDI) providers. However, users are able to make shipments in ShipHawk using the most common data fields required by an EDI provider, which are the following:

• ShipHawk Shipping Method

• Shipment ID

• Carrier Service

• Carrier Name

• Shipping Cost (at time of label generation aka billed or accrued shipping cost)

• SSCC Code

• Carton SSCC

• Pallet SSCC

• Package ID

• Shipper Email

• Tracking Number / PRO #

• ShipHawk Reference Field(s)

ShipHawk customers are able to retrieve the above fields via an API call (GET) or a webhook, which can then be sent to the EDI provider.

ShipHawk and NetSuite

Although ShipHawk does not directly integrate with an EDI provider, customers who have integrated their EDI providers with their NetSuite accounts can facilitate the transfer of data between the EDI provider and ShipHawk. NetSuite serves as the conduit for data between the two services. ShipHawk writes shipment data to NetSuite item fulfillment records, which are then synchronized to your organization’s EDI provider. 

As mentioned above, ShipHawk writes package details, shipment ID, cost, weight, and tracking numbers and a mix of NetSuite standard fields and ShipHawk custom fields to the item fulfillment record. For our customers that use common EDI providers, such as SPS Commerce or TrueCommerce, ShipHawk can also be configured to write certain information to integrated fields on the item fulfillment record.

When ShipHawk fulfills an order that originates from NetSuite, we update or create the Item Fulfillment record in a SHIPPED status and the above data can transfer over as well. From there, the EDI provider can use that information to create an ASN (Advance Ship Notice) to fulfill the vendor’s requirement.

Some common EDI providers you may hear about are: SPS Commerce, TrueCommerce, B2B Gateway, Mulesoft, and Dell Boomi. While ShipHawk does not directly integrate with any of these providers, our customers and their EDI Provider may access all shipment data required in NetSuite or via API to meet their needs.

Out of Scope

ShipHawk only writes data to NetSuite with our SuiteApp. If an EDI provider has an integrated tab installed on the item fulfillment record, ShipHawk can write to those fields in NetSuite. ShipHawk does not write directly to an EDI provider’s software. If EDI providers need to access this data a different way, they can use ShipHawk’s public APIs and/or webhooks to access this information (see https://docs.shiphawk.com ) to GET on the ShipmentID or subscribe a callback URL for the shipment.create_from_order webhook event.

Configure Shipment Field Mappings to Write Shipment Data to an EDI Provider’s Custom Fields in NetSuite

1. Log into your ShipHawk account.

2. Click on the Settings icon > Integrations. The Integrations screen is displayed.
   
   

   Open

   

3. Click on the NetSuite tile. You will be redirected to the Manage Your Accounts screen for NetSuite.
   
   

   Open

   

4. Select the NetSuite Shipment Field Mappings tab. The NetSuite Shipment Field Mappings screen appears.
   
   

5. Choose which fields you want to pass to NetSuite. Your EDI provider’s fields will show up under the NetSuite Field column if they are available to be written to.
   
   

   
   When properly configured, data required to generate an ASN, like PackageID , SSCC code, and cost can be written directly into the EDI providers field in NetSuite. This allows ShipHawk customers to automate the data retrieval process from ShipHawk to the EDI provider through NetSuite.