Today we released some changes to the way that item group configurations / case configurations work on inbound and outbound shipments. These updates were to prepare for future updates to our inventory management system as well as resolve some long-standing bugs when managing cases across inbound and outbound shipments.
There are no major changes to that way that you configure cases on the shipment, but we have changed the architecture to remove the link between cases created on inbound and outbound shipments. This link provided some limited benefits in that it tracked physical movements of boxes from receiving to outbound shipments, but that utility was far outweighed by the complications that it added to our stock management, location management, and simple processes like updating quantities of items.
Minor Changes
While there are no major changes, here is a list of all the minor changes you may notice:
- We have improved the speed of updating items in shipments
- Instead of automatically using case configurations if they have been configured on a shipment when arranging transport to Amazon, we copy those configurations to the box contents screen. This allows you to make edits if needed and immediately print the box labels before submitting the shipment.
- The move groups between locations feature has been removed as it is no longer relevant
- The image popup to view a larger version of an image has been made larger
- The button to remove a case configuration has been moved into a large button rather than the X on the dimensions badge
- The button to add a case configuration has been moved into a new Actions dropdown beside the item
- The button to remove an item has also been moved into the Actions dropdown
- You can now add multiple case configurations to the same item
- You can now delete an unsellable item directly from the shipment page
- Case configurations now appear on pick lists
Bug Fixes
- When using cases, you will no longer get an error when updating an inbound shipment about a particular case being linked to an outbound shipment and therefore no longer updatable.
- When editing locations, some locations could get “stuck”, so that they could no longer be removed from a particular item. This has been fixed.
- The view location page is now loading items properly to display the contents of the location.
- Orders are now searching by item identifiers
API Changes - Breaking Updates
While the front-end changes are minimal, the API changes are significant.
- Items for shipments are now updated individually, rather than using a bulk update for all items
- Updating an item with a zero quantity no longer removes the item from the shipment
- You can longer pass items along with the create shipments requests, items must be added in a separate call
- The quantityToSend parameters have all be renamed to quantity
- Some of the endpoints have been moved to a different location
- Moves no longer have a movable id and type, instead they simply have an item_id
The API documentation has been updated, so please review any endpoints that you are using related to inbound/outbound shipments.