Closed ihoment-dengjianhong closed 1 month ago
大哥解决了吗?
+1, seeing the same issue. This combined with there not being any endpoint to see which boxes go with which shipment will make it difficult to assign labels.
大哥解决了吗?
This issue has not been resolved
You can overlay it with data that you want to see yourself. Amazon doesn't care... As a matter of fact - we just build the whole label ourself...
You can overlay it with data that you want to see yourself. Amazon doesn't care... As a matter of fact - we just build the whole label ourself...
How to overlay it with data? I have set POST_FBA_INBOUND_CARTON_CONTENTS
but not working,still Mixed SKUS
.
Hi, Did you have support case opened for this issue ? If yes can you please provide the case numbers ?
Hi, Did you have support case opened for this issue ? If yes can you please provide the case numbers ?
caseID:15210053801
Response from the Selling Partner API Developer Support team.
Our internal team confirmed that At this time, API doesn't have case pack function, meaning that all labels will read as mixed SKU. However, we have taken this feedback and when a seller inputs a single-SKU box, we are taking action to retrieve a box label that does have the SKU content on it.
You can overlay it with data that you want to see yourself. Amazon doesn't care... As a matter of fact - we just build the whole label ourself...
Sorry, I know this isn't the best place to ask about this but I can't find solid info online and having no other way to contact you.... Any requirements on rolling your own labels? We've wanted to do it but didn't think it was allowed. Is it as simple as "Make sure the labels have the two amz barcodes and you can do whatever else you want" or do we have to stick pretty close to their formatting?
We keep it fairly close to what they have. We overlay it with extra data that we need (including WH destination code). We've been doing it for years... As far as I understand - they don't really care as long as you have a QR code with the content info. As a matter of fact we were not able to find a way to connect "package id" to a particular label... We cant even get labels at this moment (LTL non sponsored) as its troughing errors with no explanations for when we try to choose a transportation method... There is a note that Sponsored LTL is not available through this API yet, but seems its not working for any LTL. So we end up sending package info - getting through to the shipments and then guessing what shipment is particular box belongs to... And printing box label based on that... Kind of crazy if you ask me...
Hi Team, We understand the pain points here. As of now even though you have single SKU but multiple boxes the label shows up as MIXED. FBA Inbound team will be launching a new API shortly that maps BoxId to ShipmentID. We will provide more details as we launch on the specifications.
An entire new API? Will it also be rate limited to 1 call a second with a burst of 1? Adding minutes to a workflow now that shipment splits are generating 20 shipments per plan?
Surely it makes more sense to put it in the current API, where we upload box contents...... 🥲
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.
This issue has not been resolved
Hi Team, We understand the pain points here. As of now even though you have single SKU but multiple boxes the label shows up as MIXED. FBA Inbound team will be launching a new API shortly that maps BoxId to ShipmentID. We will provide more details as we launch on the specifications.
@puppsupr Hi,puppsupr.New Fulfillment Inbound API v2024-03-20 has been officially released. We have re-obtained the label and it still shows MIXED. I want to know what we should do next and when the new API will be updated.If you have any news please let me know, thank you very much.
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.
closed for inactivity
Closed as not planned? That's wrong, right?
I'm submitting a...
I don't know if there is any problem with my operation. I followed the fulfillment-inbound-api-v2024-03-20-use-case-guide and no errors were prompted for any operation. However, the box mark results are different from what I expected. Please help to confirm whether there is a problem with the new creation process.
When I created the inbound plan, I only selected one SKU and did not select other SKUs to be issued together. Why does mixed installation occur?
1.setPackingInformation https://sellingpartnerapi-na.amazon.com/inbound/fba/2024-03-20/inboundPlans/{{inboundPlanId}}/packingInformation
{ "packageGroupings": [ { "packingGroupId": "pgdxxxx", "boxes": [ { "weight": { "unit": "LB", "value": 30.8203 }, "dimensions": { "unitOfMeasurement": "IN", "length": 16.93, "width": 16.93, "height": 12.01 }, "quantity": 25, "templateName": "inbound-test-06-box", "contents": [ { "msku": "skuxxx", "quantityInBox": 12, "prepOwner": "SELLER", "labelOwner": "SELLER" } ], "contentInformationSource": "BOX_CONTENT_PROVIDED" } ] } ] }
2.listInboundPlanBoxes https://sellingpartnerapi-na.amazon.com/inbound/fba/2024-03-20/inboundPlans/{{inboundPlanId}}/boxes
{ "boxes": [ { "quantity": 1, "templateName": "P1 - B13", "packageId": "pkxxxx", "weight": { "unit": "LB", "value": 30.8203 }, "items": [ { "labelOwner": "SELLER", "msku": "skuxxxx", "quantity": 12, "fnsku": "xxxxxx", "asin": "xxxxxxx", "prepInstructions": [ { "prepType": "ITEM_LABELING", "prepOwner": "SELLER" }, { "prepType": "ITEM_NO_PREP", "prepOwner": "SELLER" } ] } ], "dimensions": { "unitOfMeasurement": "IN", "length": 16.93, "width": 16.93, "height": 12.01 } } ..... ], "pagination": {} }
3.getLabels https://sellingpartnerapi-na.amazon.com/fba/inbound/v0/shipments/shipmentId/labels?PageType=PackageLabel_Letter_6&LabelType=SELLER_LABEL&PageSize=5
expected outcome![image](https://github.com/amzn/selling-partner-api-docs/assets/71131842/84b71d63-930f-4db4-809e-b6052d8dbbe9)
SP-API Name and Version or Report/Feed Type
Expected Behavior
Current Behavior
Context/Screenshots
Your Environment