Versions Compared

Version Old Version 13 New Version Current
Changes made by

Michael Stivers

Michael Stivers

Saved on

Key

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

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

2024.7.0 Release

Starting from October 15, 2024, ShipHawk TMS customers will start receiving version 2024.7.0.

...

  • Fixed issue with link to print USMCA certificate. (Internal ID: 23519)

  • Generating PDF per package label now allowed for single package shipments. (with separate_pdf_package_labels setting). (Internal ID: 23483)

  • Resolved issue with TForce Freight LTL account access. (Internal ID: 23443)

  • Improved getting Final Mile (vs. LTL) accessorials. (Internal ID: 23430)

  • Use the warehouse from existing proposed shipment when updating the proposed shipment via API and the warehouse_code is not present in the request. (Internal ID: 23327)

  • Allow users to view and sort by bin number on the Select Items modal window. (Internal ID: 23142)

  • For workstations, Smart Packing suggestion pop-up displays when order is opened. (Internal ID: 23115)

  • Fixed issue with saving quote numbers. (Internal ID: 22994)

  • Add ability to ignore re-rate or apply Shipping Policies to set external carrier on ‘Save & Book’ when the configuration setting “Clear carrier selection when package information is changed manually” is selected. (Internal ID: 22767)

  • Added sending USMCA information to FedEx via ETD (and UPS paperless). (Internal ID: 20623)

  • Added support for ShipDate parameter with Amazon Merchant booking and rating requests when the new setting tmp_amz_merch_use_ship_date_for_rating_and_booking is enabled. (Internal ID: 23229)

  • Added controllable Purpose of Shipment and Parties to Transaction fields for ETD Commercial Invoices (Internal ID: 23271)

  • Added field <Accessibility>INACCESSIBLE</Accessibility> in the <DangerousGoodsDetail> for lithium batteries. (Internal ID: 23073)

  • Moved Tax ID to the Exporter field in FedEx ETD. (Internal ID: 22130)

  • ‘Shipped’ status now preserved when updating tracking information during NS ItemFulfillment update. (Internal ID: 23195)

2024.7.2 Release

Starting from November 7, 2024, ShipHawk TMS customers will start receiving version 2024.7.2, which includes the following:

  • Added 2025 holidays in order to calculate correct delivery estimates for next year. (Internal ID: 23640)

  • Fixed issue with markup display in user interface (Internal ID: 23602)

  • Fixed issue with UPS Signature accessorial not returning rate when shipping from Canada to US with UPS Standard (Internal ID: 23595)

  • Added ability to upload commercial invoices of ShipHawk to FedEx (Internal ID: 23559)

  • Fixed issue with kits not generating with kit component box data when Smart Packing is off (Internal ID: 23552)

  • Fixed issue with SPS Commerce UCC-128 pallet label failing to render custom reference fields (Internal ID: 23549)

  • Fixed issue with retrieving BOL for C.H. Robinson shipments (Internal ID: 23495)

  • Retain and display order level Destination Instruction field when order API request contains rate_id (Internal ID: 23463)

  • Fixed issue where Serbia could not be selected as a destination country when creating new shipment (Internal ID: 23452)

  • Resolved “unknown attribute ‘sh_dimensioner_images’ for Package” error message during attempts to ship or save a proposed shipment (Internal ID: 23372)

  • Fixed issue with incorrect pickup date sent to carrier in rating request (Internal ID: 23359)

  • Fixed rating multiple fulfillments when rule filters out all rates (Internal ID: 23324)

  • Fixed issue with default 4x6 packing slip not generating (Internal ID: 23260)

  • Removed Notify Prior Delivery accessorial from BOL for FedEx Freight Direct Shipments (Internal ID: 23154)

  • Resolved Invalid Packaging Type error when rating with AAA Cooper (Internal ID: 23096)

  • Fixed rate discrepancy issues caused by case sensitive zip-codes for Canadian addresses (Internal ID: 22857)

  • Use pro_number or shipment_id as BOL number if BOL is empty (Internal ID: 22822)

  • Added ability to print return labels for Loomis Express (Internal ID: 22808)

  • Update commercial invoice country declaration dynamically depending on origin country (Internal ID: 22775)

  • Fixed issue where customs data was cleared when proposed shipment was generated (Internal ID: 22687)

  • Instant SKU/UPC scan when the user inputs during Ready-To-Ship (RTS) mode (Internal ID: 22082)

  • Now, when account setting ‘Select items button mode’ is set to ‘in_all_pieces’, the carton/pallet template variable package.items_count splits the quantity between packages/boxes. (Internal ID: 21676)

  • Improved error message for missing customs data (Internal ID: 21604)

2024.7.3 Release

Starting from November 15, 2024, ShipHawk TMS customers will start receiving version 2024.7.3, which includes the following:

  • Added: print parties to transaction and purpose of shipment on commercial invoice (Internal ID: 23667)

  • Resolved error when installing NetSuite bundle (Internal ID: 23080)

  • Metropolitan Integration (Internal ID: 22993)

  • Added: use pallet pricing when rating with SEFL (Internal ID: 10003)

  • Added: make an override parameter optional or set to false in the SOAP requests. Do not send an override parameter for the Address entity upon Item Fulfillment (IF) create and update in NetSuite. Added new account setting tmp_ns_do_not_send_override_addr_on_if_create_or_update to control this process. If enabled, the parameter won't be sent; otherwise, the parameter will be sent with its value set to true. (Internal ID: 23570)

  • Fixed issue with uploading shipments via CSV (Internal ID: 23504)

  • Enhanced 'Create Table Rate’ rating action with shipping price set to 0 (zero) (Internal ID: 21958)

  • Do not display UPS Simple Rate boxes as proposed shipment materials when UPS Simple Rate service is not active (not enabled by shipping API credentials). (Internal ID: 23104)

  • Fixed issue with FedEx Ground populating on orders that should be FedEx Ground Home Delivery (Internal ID: 23622)

2024.7.4 Release

Starting from December 11, 2024, ShipHawk TMS customers will start receiving version 2024.7.4, which includes the following:

  • Fixed issue where order could not be booked when the same lot number was in multiple packages (Internal ID: 24059)

  • Fixed issue with loading and displaying tracking number on Shipment Details page (Internal ID: 23719)

  • Fixed issue with incorrect LPN numbers assigned to carton labels (Internal ID: 23089)

  • Fixed issue with LTL workstations packed order shipped with no SKUs (Internal ID: 23864)

  • Allow disable tracking URLs with sequential integers (Internal ID: 23170)

  • Added ability to display KIT item (parent SKU) only on the carton/pallet labels (Internal ID: 20983)

2024.7.5 Release

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

  • Integrated REST API for Echo 3PL for rating only (Internal ID: 23341)

2024.7.6 Release

Starting from January 9, 2025, ShipHawk TMS customers will start receiving version 2024.7.6, which includes the following:

  • Migration of products and variants to GraphQL API (Internal ID: 24238)

2024.7.7 Release

Starting from January 16, 2025, ShipHawk TMS customers will start receiving version 2024.7.7, which includes the following:

  • Improved two-factor authentication (2FA) so admins can specify whether all users must use 2FA or whether individual users can enable it. Additionally, allow individual users to change their passwords from the user profile page. Show which users have enabled 2FA. (Internal ID: 24420).

  • Improved IP whitelist management, and require admin users to use 2FA. (Internal ID: 24421).

  • Improved session management, user 2FA verification, and 2FA management. To generate API Keys, you must log in to ShipHawk TMS using 2FA. (Internal ID: 24491).

  • Added email confirmation for 2FA enablement for admin users. (Internal ID: 24470)

  • Enhanced logging and notifications about security-related changes. (Internal ID: 24441).

See the following for 2FA and IP whitelist management:

Two-Factor Authentication (2FA)

Two-Factor Authentication (2FA) adds an extra layer of security for your account.

With 2FA, you must have an authentication app on a mobile device or PC. Authenticator apps are available from Google, Microsoft, Salesforce, and more. Once configured, you will be prompted for a code each time you login to ShipHawk.

For your security, two factor authentication is now required for admin users.

Additionally, to generate API Keys from the ShipHawk TMS user interface, you must now first log in to the user interface using 2FA.

Configuring Your 2FA as a User

As a user, you can enable 2FA for your account. On the right side of the menu bar, choose User Profile:

...

Next, on the user profile settings page, under Multi Factor Authentication, select Enable two factor authentication:

...

Once selected, you will be prompted to set up 2FA upon your next login.

For more information on setting up 2FA as a user, see Using Two-Factor Authentication (2FA) in ShipHawk TMS .

Configuring Your System’s 2FA as an Admin User

As an admin, to configure 2FA for your system, choose ⚙️ > Settings > System Access / 2FA.

...

To require 2FA for all users of your system, under Multi Factor Authentication, select Enable two factor authentication for all users.

Now, users will be prompted to set up 2FA the next time they login. Setting up 2FA is simple but requires users to have an authentication app on a mobile device or PC. Authenticator apps are available from Google, Microsoft, Salesforce, and more. Once configured, users will be prompted for a code each time they login to ShipHawk.

Admins can reset 2FA for any user from the Settings > Users page.
(If all admins lose 2FA access, contact ShipHawk Support for assistance.)

Configuring Your System’s IP Address Whitelisting

ShipHawk highly recommends that you use IP whitelisting for your security and for your customers’ security.

Admins can restrict access to the ShipHawk TMS user interface based on pre-configured Internet Protocol (IP) address ranges for groups of users.

Setting IP limits, also known as IP whitelisting, allows admins to restrict access to ShipHawk to PCs or devices with specific IP addresses (or a range of IP addresses).

Multiple IP ranges can be configured for merchants with multiple warehouses, and different restrictions can be applied based on different User Roles in ShipHawk.

Important: ShipHawk strongly recommends using whitelisted IP addresses for regular users. Doing so can significantly reduce the risk of unauthorized access and potential security breaches. If your ISP does not provide static IPs, we recommend exploring affordable solutions like VPNs with static IPs or working with your network provider to obtain a reserved range.

Note: IP whitelisting restrictions do not apply to admin users, who must always use 2FA. This gives admin users more flexibility about how they can access ShipHawk, but to assure additional security, they must use 2FA. Further, 2FA is required for users who want to generate an API key.

As an admin, to configure IP whitelisting for your system, choose ⚙️ > Settings > System Access / 2FA.

Under IP Address Restrictions, click +ADD IP ADDRESS to specify an allowed IP address. You can specify IP address whitelists. This will restrict ShipHawk TMS access to just the particular IP addresses that your PCs / devices are using.

If you wish, you can specify that regular users who have 2FA enabled are not restricted by IP address whitelisting. To skip IP whitelisting for those users who have enabled 2FA, select Skip IP whitelist for users with enabled 2FA.