Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BoxInput model is missing Template Name field (or other correlation identifier) #4331

Open
memotronics opened this issue Nov 15, 2024 · 0 comments

Comments

@memotronics
Copy link

There is currently no way to correlate a box created with setPackingInformation (BoxInput) to a Box object returned by ListShipmentBoxes. This, in turn, makes it hard/impossible to create a link between a printed label and the physical box that this label needs to go on.

Example:

  • Shipment is Small Parcel, it has 4 boxes with mixed SKUs.
  • The SKU mix in each box is different, but all 4 boxes have different content.
  • The boxes all have the same weight and size, but during packaging, the boxes get marked "A", "B", "C" and "D".
  • The box info (content/weights/dims) is entered into our system, along with "A", "B", "C" or "D" to identify to our system what items are in which box
  • Weights/Dims and Box Content uploaded via setPackingInformation. NO PLACE TO SEND UP the box-label (A/B/C/D)
  • Placement & Transport generated and confirmed
  • Call ListShipmentBoxes to get Box/Package IDs
  • Call GetLabels with Box/Package IDs

We now have 4 labels but no way of identifying which label (= which PackageID or BoxID) goes to which box ("A", "B", "C" or "D") because SetPackingInformation (more precisely: BoxInput) has no field for such an identifier.

In my view, BoxInput needs a field called "TemplateName", and the value of TemplateName that is passed-in during SetPackingInformation should be the value that appears in the already-existing TemplateName field of the Box objects returned by ListShipmentBoxes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant