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

Version 1 Current »

May 28 - June 4, 2024

Starting from May 28, 2024, customers will start receiving version 2024.4.0.
Please see your release communication email from ShipHawk for more information.

This document provides an overview of the new features in the 2024.4.0 release.

Two-Factor Authentication (2FA)

Two-factor authentication (2FA) adds further security when you sign in to ShipHawk TMS and reduces the chance of unauthorized access to your ShipHawk account. With 2FA, you must use two ways to identify yourself for extra security. The first way is when you sign in by entering your password; the second way is when you enter a verification code sent to a separate device, typically your mobile phone. Once the system administrator has enabled two-factor authentication (2FA), users will have additional sign in steps when accessing ShipHawk, and will need to provide a verification code every time they sign in:

As a new user accessing a system using 2FA, or as a current user accessing the system right after 2FA has been enabled, you will need to get an authenticator app downloaded and installed on your mobile device or computer.  ShipHawk tested this feature with popular authenticator apps that are available from Google Play or Apple’s App Store that can easily be installed on a mobile device including:

  • Google Authenticator (recommended)

  • Salesforce Authenticator

  • Microsoft Authenticator

  • 2FAS Authenticator

See Using Two-Factor Authentication (2FA) in ShipHawk TMS for more information.

As a system administrator, you can enable and manage 2FA for your system, and reset 2FA for your users as needed. When 2FA is initially enabled, your users must install an authenticator app on a mobile device and then enter the ShipHawk-generated code or QR barcode into that app.  This will only display the first time you login to ShipHawk or if your admin resets your user account. Once configured, your users will be asked to enter your password and 2FA code from the Authenticator app every time you log in to ShipHawk. System administrators can refer to Managing Two-Factor Authentication (2FA) in ShipHawk TMS for more information.

Print All Carton Labels During Box Packing Workflow

On the box packing workflow, you can now print all carton labels before clicking the Finish button. This can improve efficiency and accuracy because you can use the box packing screen to check which carton labels should go on which boxes after the carton labels have been printed.

Show Unpacked Items During Pallet Packing Workflow

You can now pack items on pallets without first having to pack those items into boxes. In some cases, you might want to simply put items on pallets without needing to pack them into boxes first. In this way, the workflow can support simpler use cases that do not require carton labels.

Separate Rate Timeouts for each ERP or E-Commerce Connector

You can now have separate rate timeouts for each rate request source, such as Shopify, NetSuite, or Magento. Some platforms, such as Shopify, have inflexible rate timeouts, while others are more flexible. By setting separate rate timeouts, you can rate more effectively from multiple sources, assuring better performance across multiple platforms. Contact your ShipHawk account manager to adjust rate timeouts.

New Parcel Carrier Integrations

LaserShip is now a supported carrier integration. In general, ShipHawk has expanded the carrier connections it can support and simplified carrier management. Many carriers not currently supported can be quickly added based on customer request. Please ask for more information from your ShipHawk account manager.

Expanded Accessorial Support

Expanded accessorial support includes the following:

  • HAZMAT for FedEx Freight

  • Notify Prior Delivery for FedEx Freight

  • Limited Qty Dangerous Goods for FedEx Freight

  • Appointment Delivery for XPO

Apply Billing Rules on Save after Carrier Change

You can now have the Shipping Policies related to billing and 3rd-party carrier accounts automatically apply when you manually change the carrier and save the changes. Existing Shipping Policies allowed the user to configure rules to automatically set preferred 3rd party carrier account details but these rules were only applied on order import.  If the Shipping Clerk manually selected a different carrier, they had to manually update the new billing details.  With this update, ShipHawk will re-evaluate the Shipping Policies related to Billing Details and 3rd Party Account details when the changes are saved in the Order Details page.  This eliminates the need for Shipping Clerks to know billing details and reduces the potential for mistakes when manually entering billing details.

Rules Criteria for Package Dimensions

New criteria options for individual package sizes:

  • Package Height

  • Package Length

  • Package Width

  • Package Volume

  • Package Girth (that is, 2 x Height  plus  2 x Width)

Note that the package dimension criteria are only available after the packing and rating steps are complete given that the package dimensions are determined during packing. Rule Actions that are applied pre-rating are not compatible with these criteria.  Please contact ShipHawk with any questions. 

Support for Multiple Brokers

You can now pre-load multiple brokers and select brokers using a Shipping Policy, which improves automation, reducing manual tasks.

Additional Improvements

Further additional improvements in the release include:

  • Drop down auto-complete for Category and Subcategory values in UI fields.

  • On the Compare Carrier Rates screen, you can now sort rates when comparing Parcel vs. LTL.

  • Option to map markup rate value to 4x8 Doc Tab

  • Pass warehouse at item level with Packed Order API

  • No labels