Versions Compared

Old Version 6

changes.mady.by.user jonathan.day

Saved on

compared with

New Version 7

changes.mady.by.user Michael Stivers

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

For sending information to ShipHawk, the following requirements must be met:

Table of Contents

1. Shipments must be synced to ShipHawk

When a shipment is ready to be packed and/or shipped in ShipHawk, the shipment must be synced over to ShipHawk. Only the object related to the actual shipment needs to be synced. 

  1. For example, in NetSuite there are Sales Order objects, and each Sales Order may have multiple Item Fulfillment records which represent the pick task and shipment. 

  2. This sync must take into account the mappings that have been configured by the administrator. 

Expand
titleTechnical details

Order sync uses the order sync endpoint. The following fields are required:

  • The order_number of the object being shipped.

  • Origin address block, with the warehouse code field populated.

    • The warehouse code is an ID that is set in ShipHawk to differentiate warehouses. The order creation request should include a warehouse ID that corresponds to a warehouse inputted in ShipHawk:

  • The destination address block

  • The items being shipped, in the order_line_items block:

    • Required:

      • sku

      • name

      • description

      • qty

      • item weight

      • ShipHawk specific Smartpacking information:

        • item_type (parcel, handling_unit, unpacked)

        • type_of_item (loose, box, pallet)

        • do_not_pack_with_other_items (boolean)

        • do_not_palletize (boolean)

        • do_not_pack_before_palletize (boolean)

    • If available:

  • order status

  • order level reference_numbers, as mapped by the administrator

  • billing_details, if mapped by the administrator

    • Note: If the bill_to field is not populated by the mapping, then the field should default to ‘sender’

  • requested_rate_id, for cases where the user rates the shipment. See #2 below.

2. Users must rate order in the ERP with ShipHawk

Prior to fulfillment, users must be able to rate the order in the ERP with ShipHawk by clicking a button. Upon clicking this button, the connector must send a rating request to shiphawk, receive rates from ShipHawk, and display them in a dropdown menu. If a rate is selected, it is to be applied to the ‘ship method’ field. 

  1. In our other integrations, this rating exists at the Sales Order level, and not at the shipment level object. 

  2. Not all customers will use this, but it is important for some B2B use cases. 

3. Serial/lot numbers must be synced with ShipHawk

The serial/lot numbers available for packing/ shipping must be synced with ShipHawk so that they can be verified in ShipHawk. 

  1. The user must be able to scan a serial/lot number into ShipHawk.

  2. ShipHawk must have a list of serial/lot numbers in stock for that SKU, and be able to verify the serial number scanned. 

  3. After a shipment is booked, the serial/lot numbers must be recorded in the ERP using webhooks.