In our latest release, we're pleased to release an improvement to our Shopify webhook, a new carrier for eHub, and fixes and improvements related to serial numbers.
There was an issue with KOD components that require serial numbers. When an order containing a KOD with components that require serial numbers was unfulfilled, the component serial numbers were not being unassigned. This prevented the serial number from being used for future order fulfillment. Now, when an order is unfulfilled, the serial numbers are removed from the order and are able to be used for fulfillment in the future.
There is a new Item Serial Scheme Configuration "Allow Unique Serial Returns". Item Serial Schemes that require unique serial numbers prevent users from entering a serial number that already exists in the Item Serial table even if the Item associated with the Serial Number was no longer in Inventory.
When "Allow Unique Serial returns" is set to "True", users are now able to enter a serial number that already exists in the Item Serial table that is no longer in Inventory and has an Order number attached to it. When the User enters the Serial Number, the existing record in the Item Serial table is updated. The record will now show "In Inventory" as "True" and the Order filed will now be null.
The overall idea of this feature is to allow Items that require unique serial numbers to be re-received into Inventory without having to delete the Serial Number record in the table.
This also prevents Serial Numbers from being deleted that are associated with an Order. Item Serial Numbers can only be deleted if there is no Order associated with the Item Serial record.
In summary, the main points of this story are as follows: