Transfer labelling and receiving improvements

Print transfer labels per package, and hold supplier returns until ready to send.

Jungle now supports printing per-package transfer labels as they are packed, which can be used to identify the transfer at the receiving location.

These labels are then used at the receiving location to quickly identify the contents of a transfer package, and easily start a receiving workflow.

Supplier return fulfilment hold

Supplier returns now support fulfilment holds, which allow you to hold a return to a supplier until you are ready to send it. This is useful when you are working through confirmation on a return with the Supplier, but want to allocate and assign the items in the Supplier Return.

  • Pack jobs are now correctly cancelled when their assigned inventory is reassigned to fulfill a POS sale.
  • Pack jobs that are no longer associated to a location do not show up in list of jobs for that location.
  • In certain cases, expected Inventory events on new Orders were not being created as expected, this is no longer the case.
  • Sometimes when adjusting inventory the adjusted in items would not assign as expected, this is no longer the case.
  • Searching for Notes on any given object now returns the expected results in a timely manner.
  • Order routing using split to closest location rules no longer forces proximity selection, and can use location preferences if defined.
  • Allocation and Transfer feeds no longer order the results, matching behaviour and speed of other feeds.
  • ReturnLineItem.product now correctly resolves the expected Product in the API.
  • Purchase order bulk creation now supports using location name, supplier name, and product sku instead of their respective Ids.
  • Product names can now be up to 255 characters long, up from 100.
  • Product skus can now be up to 255 characters long, up from 120. Note that it is still preferential to have small SKUs.
  • XID values can now be up to 255 characters long, up from 120.
  • Line items now support filtering over their source object, aka a specific Order, Purchase or Return.
  • Wave building now supports filtering ready allocation based on the sales channel.
  • PurchaseReturn now supports directly querying associated XIDs.
  • Pack jobs now resolve .actions that describe if it may be cancelled or not.
  • Searching orders at a specific location returns results 10 times faster.
  • Our API now supports zstd compression encoding, as an alternative to gzip. It can reduce the size of responses significantly, especially for larger datasets, such as Feeds.