ShipHawk 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 13 Next »

This document describes the ShipHawk 2024.6.x releases, starting with the major release (2024.6.0) and then subsequent minor releases.

2024.6.0 Release

Starting from September 3, 2024, ShipHawk TMS customers will start receiving version 2024.6.0.

ShipHawk WMS customers can now contact their account manager to get new WMS features.

Please see your release communication email from ShipHawk, which includes the 2024.6.0 Release Notes.

ShipHawk WMS New Features

This section provides an overview of the new features in the ShipHawk WMS. ShipHawk is continuously enhancing the WMS. Please contact your ShipHawk account manager to let us know about your latest requirements and learn about the latest features.

If you would like to have these new features in your implementation of ShipHawk WMS, please contact your ShipHawk account manager.

Ship at Pick

With this feature, pickers can pick directly into a shipping container, bypassing the packing step and reducing overall fulfillment time.

Acumatica WMS Items Sync

This feature enables WMS users to automatically sync item-level information from Acumatica to ShipHawk. In this way, users can make pick, pack, and ship decisions without having to access Acumatica, providing faster performance and the ability to use item attributes for warehouse operation rules.

ShipHawk TMS New Features

This section provides an overview of the new features and fixes in the ShipHawk TMS 2024.6.0 release. 

Write Back Parent Kit SKUs to SPS Commerce

ShipHawk now provides the ability to write back parent kit SKUs to SPS Commerce, as contrasted with writing back only kit components. This approach provides better support for EDI use cases.

Integration Infrastructure Updates

Integration infrastructure changes include the following:

  • Fixed Issue: previously, Amazon Merchant rates were not returning when another carrier tariff is selected

  • Upgrade NetSuite gem and Savon gem

  • Fixed Issue: previously, country of origin was  transmitted incorrectly from NetSuite to ShipHawk

  • In BigCommerce, now creating a line level warehouse code assignment for products

  • Now including line level source_system_id in shipment GET response

  • Added field SourceDate mapping to NetSuite-ShipHawk bundle

Ward Carrier Now Supported

ShipHawk now includes support for Ward Trucking.

Partners - WARD Trucking

Carrier Infrastructure Updates

Carriers infrastructure changes include the following:

  • Updated directed Roadrunner integration

  • Support for the USPS merge of “Parcel Select Lightweight” into “Parcel Select”

  • Added support for HAZMAT LTL for TForce Freight

  • Send NMFC and declared value information to FedEx

Set Handling Unit Weight at Handling Unit Level

ShipHawk users can now set Handling Unit (HU) weight at the HU level. In this way, users can tell ShipHawk the weight of the entire pallet instead of the commodity / material weight.

When using this feature, the Order Details display includes a Total Weight field for a handling unit (pallet). The value of this field must be entered manually. Important: the value of this field is the only weight put on the BOL in the carrier information section. The individual commodity weight fields, which show the weight of the items in the commodity, are not included on the BOL or sent to the carrier. The only place the individual commodity weight fields are used is in determining the weight of each piece (box) on the pallet for carton label / SPS Commerce / EDI purposes.

Contact your ShipHawk account manager if you would like to find out more about this feature, which must be enabled for your account (‘Set total weight at handling unit level’).

Integration of SPS Commerce for Pre-built Carton Labels

You can now use SPS Commerce to get carton labels from the SPS Commerce library.

With this feature, ShipHawk sends information to SPS Commerce, who would then be respond with the carton label. The advantage of this is that SPS Commerce has already built these label templates according to what the vendor needs (for example, Target, Walmart, and so on) so it will be easy to add vendors this way.

When enabled, from Settings > Pallet/Carton Labels > Add New Carton Label, you can specify whether to generate a label by default or using SPS Commerce:

For more information, see How do I use carton labels from SPS Commerce? .

Contact your ShipHawk account manager if you would like to use this feature.

Platform Infrastructure Updates

Platform infrastructure changes include the following:

  • Allow pallet packing workstation to use presets to set FC/NMFC

  • Improvements for Active Admin / Tariffs edit page

  • Added USPS EasyPost carrier

  • Allow for leading zeros for SSCC GS1 company prefix 

  • Incorrect total items value are sent in customs data to ePost Global

2024.6.1 Release

Starting from September 13, 2024, ShipHawk TMS customers will start receiving version 2024.6.1, which includes the following:

  • Update Item Names on Master Pick Ticket (Internal ID: 22751)

  • Packed Orders API: Add async Shipment creation (Internal ID: 22888)

  • UPS REST: Ground Freight Pricing blocking all other UPS rates (Internal ID: 22805)

2024.6.2 Release

Starting from September 18, 2024, ShipHawk TMS customers will start receiving version 2024.6.2, which includes the following:

  • Veyer integration improvements (Internal IDs: 23013, 22848, 22845)

  • Added Carrier Rating zone in Shipments Reports for UPS and OnTrac (Internal ID: 22437)

  • API ability to receive package labels separately for every  package (Internal ID: 20674)

  • No labels